Three-Track Strategy
TRF (Traceability Report Framework) delivers value through three complementary tracks, each serving different needs and markets.
Overview
Track 1: Format Specification
The twpack file format - An open standard for traceability data exchange.
What It Is
- File format specification (like PDF, SQLite, or MP4)
- ZIP archive containing JSON files
- JSON Schemas for validation
- Vendor-neutral and domain-agnostic
Who Uses It
Everyone - Track 1 is the foundation that both Track 2 and Track 3 build upon.
Key Features
manifest.json- Pack metadata and configurationartifacts.json- Traceable entities (requirements, tests, designs, etc.)links.json- Traceability relationshipsprovenance.json- Creation history (optional)
Format: twpack 2.1
The current version (2.1) uses a simplified JSON-based structure:
example.twpack (ZIP archive)
├── manifest.json
├── artifacts.json
├── links.json
└── provenance.json (optional)
License
MIT Licensed - Free for anyone to implement, use, or build upon.
Repository
Track 2: OSS Toolkit
Production-ready tools for creating and analyzing twpack files.
What It Is
A complete, FREE toolkit for traceability management:
- 5 npm packages with CLI and programmatic APIs
- SQLite-based storage for efficient querying
- Graph analytics and coverage metrics
- Production-ready, not a hobbled "free tier"
Target Users
- Technical service providers (TÜV, SGS, DNV)
- Engineering consultancies (safety analysis, compliance auditing)
- Research institutions
- Development teams (projects with 10K-100K artifacts)
Scale & Performance
| Metric | Capability |
|---|---|
| Artifact scale | 10K-100K artifacts |
| Query performance | Sub-second queries |
| Storage | SQLite (proven, industry-standard) |
| Coverage | 90% of real-world projects |
Packages
| Package | Purpose | npm |
|---|---|---|
| @traceweave/trf | Unified CLI | npm |
| @traceweave/trf-validator | Schema validation | npm |
| @traceweave/trf-builder | Pack creation | npm |
| @traceweave/trf-analyzer | Graph analytics | npm |
| @traceweave/trf-query | SQL queries | npm |
Installation
npm install -g @traceweave/trf
Example Usage
# Validate a pack
trf validate my-pack.twpack
# Build a pack
trf build create --id "project:v1.0" --title "My Pack" \
--artifacts ./artifacts.json --links ./links.json \
--output ./my-pack.twpack
# Analyze coverage
trf analyze coverage -f my-pack.twpack -k requirement
# Query with SQL
trf query sql -f my-pack.twpack \
-q "SELECT kind, COUNT(*) FROM artifacts GROUP BY kind"
License
MIT Licensed - Completely free and open source.
Why Track 2 Exists
Track 2 is NOT a limited "free tier" designed to upsell you to Track 3.
Track 2 is a complete, production-ready solution for its target market. Organizations like TÜV certification bodies will use Track 2, not Track 3.
Repository
github.com/TraceWeave-KR/TRF (packages/ directory)
Track 3: TraceWeave Enterprise
Commercial platform for hyperscale traceability with AI-powered features.
What It Is
A commercial platform for enterprise-scale traceability:
- Neuromorphic PBHL storage engine (proprietary)
- Sub-10ms queries at 400M artifact scale
- AI-powered features (error backpropagation, pattern learning, auto-remediation)
- Enterprise support and SLAs
Target Users
| Industry | Scale | Use Case |
|---|---|---|
| Automotive OEMs | 100M-400M artifacts | ISO 26262 ASIL-D (entire vehicle) |
| Tier-1 Suppliers | 10M-100M artifacts | Component-level safety compliance |
| Medical Device | 10M-50M artifacts | IEC 62304, FDA submissions |
| Aerospace | 50M-200M artifacts | DO-178C, multi-system integration |
| Pharma | 20M-100M artifacts | Clinical trial traceability |
| AI/ML Governance | 100M-1B artifacts | Training data lineage |
Scale & Performance
| Metric | Capability |
|---|---|
| Artifact scale | 100K-400M artifacts |
| Query performance | 2.7-13ms (real-time) |
| Storage | Neuromorphic PBHL (4-10x faster than state-of-art) |
| Hardware | CPU-only (no GPU required) |
Unique Features
⭐ Error Signal Backpropagation - Active learning from failures ⭐ Pattern Learning Database - Cross-organization knowledge ⭐ Auto-Remediation - AI-powered automatic fix generation ⭐ LLM Multi-Agent - Requirements from code, auto-linking ⭐ Neuromorphic PBHL - 4-10x faster queries, 6.3x less memory
Pricing
- License: $300K-$500K per year (division license)
- ROI: $1.5M-$5M per year compliance cost savings
Status
Architecture designed - Implementation planned after Track 2 v1.0 release.
Repository
Private commercial repository (not open source).
Comparison
| Aspect | Track 1 | Track 2 | Track 3 |
|---|---|---|---|
| What | Format spec | OSS toolkit | Commercial platform |
| License | MIT | MIT | Proprietary |
| Cost | FREE | FREE | $300K-$500K/year |
| Scale | N/A | 10K-100K | 100K-400M |
| Performance | N/A | Sub-second | 2.7-13ms |
| Storage | N/A | SQLite | Neuromorphic PBHL |
| AI Features | N/A | No | Yes |
| Target | Everyone | TÜV, consultancies | OEMs, enterprises |
Design Principle
Track 2 vs Track 3 differentiation is based on scale needs and AI features, NOT feature throttling.
Track 2 is NOT limited to push users toward Track 3. It's a complete solution for its target market (90% of projects).
Track 3 exists for organizations with fundamentally different needs:
- Scale: 400M artifacts vs 100K artifacts
- Speed: Sub-10ms queries for real-time CI/CD integration
- AI: Pattern learning, auto-remediation, proactive compliance
Business Model
Open-Core Strategy:
- Tracks 1 & 2: Drive adoption, ecosystem growth, brand awareness
- Track 3: Generate revenue from enterprise customers with hyperscale needs
Getting Started
For Most Users → Track 2
npm install -g @traceweave/trf
Start with the Quick Start Guide.
For Enterprise Scale → Track 3
Contact: contact@traceweave.net
For Tool Vendors → Track 1
Implement the twpack format specification: Format Specification
Questions & Answers
Q: Which track should I use?
- Creating tools? → Track 1 (format spec)
- 10K-100K artifacts? → Track 2 (OSS toolkit)
- 100M+ artifacts? Need sub-10ms queries? → Track 3 (enterprise)
Q: Is Track 2 limited to make me pay for Track 3?
No. Track 2 is a complete solution for its target market. TÜV certification bodies use Track 2, not Track 3.
Q: Can I use Track 2 commercially?
Yes. Track 2 is MIT licensed - completely free for commercial use.
Q: What if I outgrow Track 2?
Migrate to Track 3 when you need:
- 100M+ artifacts
- Sub-10ms query performance
- AI-powered features
Your .twpack files remain compatible.
Q: Can I build my own tools using Track 1?
Yes! Track 1 is an open standard. Build validators, visualizers, or complete platforms.
See Also
- Quick Start - Get started with Track 2
- CLI Reference - Track 2 command-line tools
- twpack Format - Track 1 specification
- GitHub Repository - Tracks 1 & 2 source code