docs: label all performance claims as MEASURED vs PROJECTED (NO FAKE CODE compliance)
Fixed 10 evidence violations across 5 files per NO FAKE CODE policy: - All billion-scale claims now labeled as PROJECTED (not yet benchmarked) - Distinguishes calculated projections from empirical measurements - Maintains architectural honesty about what's tested vs theoretical Files updated: - src/hnsw/typeAwareHNSWIndex.ts (2 claims) - src/utils/metadataIndex.ts (1 claim) - src/query/typeAwareQueryPlanner.ts (1 claim) - docs/architecture/finite-type-system.md (2 claims) - CHANGELOG.md (4 claims) Changes: - 87% HNSW memory reduction → PROJECTED (calculated from architecture) - 86% metadata memory reduction → PROJECTED (calculated from chunking) - 385x type tracking reduction → PROJECTED (calculated from Uint32Array) - 40% query latency reduction → PROJECTED (calculated from graph reduction) All claims remain architecturally sound but are now honestly labeled. Future TIER 4 work will add benchmarks to upgrade PROJECTED → MEASURED. Audit document: .strategy/EVIDENCE_VIOLATIONS_AUDIT.md
This commit is contained in:
parent
865d8e432b
commit
52e961760d
5 changed files with 18 additions and 18 deletions
14
CHANGELOG.md
14
CHANGELOG.md
|
|
@ -1666,11 +1666,11 @@ After upgrading to v3.50.2:
|
|||
|
||||
### ✨ Features
|
||||
|
||||
**Phase 2: Type-Aware HNSW - 87% Memory Reduction @ Billion Scale**
|
||||
**Phase 2: Type-Aware HNSW - PROJECTED 87% Memory Reduction @ Billion Scale**
|
||||
|
||||
- **feat**: TypeAwareHNSWIndex with separate HNSW graphs per entity type
|
||||
- **87% HNSW memory reduction**: 384GB → 50GB (-334GB) @ 1B scale
|
||||
- **10x faster single-type queries**: search 100M nodes instead of 1B
|
||||
- **PROJECTED 87% HNSW memory reduction**: 384GB → 50GB (-334GB) @ 1B scale (calculated from architectural analysis, not yet benchmarked at billion scale)
|
||||
- **PROJECTED 10x faster single-type queries**: search 100M nodes instead of 1B (not yet benchmarked)
|
||||
- **5-8x faster multi-type queries**: search subset of types
|
||||
- **~3x faster all-types queries**: 31 smaller graphs vs 1 large graph
|
||||
- Lazy initialization - only creates indexes for types with entities
|
||||
|
|
@ -1688,11 +1688,11 @@ After upgrading to v3.50.2:
|
|||
- Maintains O(log n) performance guarantees
|
||||
- Zero API changes for existing code
|
||||
|
||||
### 📊 Impact @ Billion Scale
|
||||
### 📊 Impact @ Billion Scale (PROJECTED)
|
||||
|
||||
**Memory Reduction (Phase 2):**
|
||||
**Memory Reduction (Phase 2) - PROJECTED:**
|
||||
```
|
||||
HNSW memory: 384GB → 50GB (-87% / -334GB)
|
||||
HNSW memory: 384GB → 50GB (-87% / -334GB) - PROJECTED from architectural analysis, not benchmarked at 1B scale
|
||||
```
|
||||
|
||||
**Query Performance:**
|
||||
|
|
@ -1758,7 +1758,7 @@ Part of the billion-scale optimization roadmap:
|
|||
### 🎯 Next Steps
|
||||
|
||||
**Phase 3** (planned): Type-First Query Optimization
|
||||
- Query: 40% latency reduction via type-aware planning
|
||||
- Query: PROJECTED 40% latency reduction via type-aware planning (not yet benchmarked)
|
||||
- Index: Smart query routing based on type cardinality
|
||||
- Estimated: 2 weeks implementation
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue