2025-08-26 12:32:21 -07:00
/ * *
* Metadata Index System
* Maintains inverted indexes for fast metadata filtering
* Automatically updates indexes when data changes
* /
2026-06-11 14:51:00 -07:00
import { StorageAdapter , resolveEntityField , NounMetadata , VerbMetadata } from '../coreTypes.js'
2026-08-04 16:40:48 -07:00
import { SYSTEM_ENTITY_SCALARS , parseFieldAddress , UnresolvableFieldError , type FieldAddress } from '../db/fieldAddressing.js'
import { splitNounMetadataRecord } from '../types/reservedFields.js'
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
import { ColumnStore } from '../indexes/columnStore/ColumnStore.js'
feat: export provider contracts for the plugin surface brainy consumes
Native accelerators (cortex) register providers for metadataIndex, graphIndex,
hnsw, entityIdMapper, cache, columnStore, and aggregation. Until now the exact
method/property surface brainy calls on each was implicit — a provider could
drop a member brainy depends on and only fail at runtime when that path ran.
This defines and exports the provider contracts from the stable
@soulcraft/brainy/plugin entrypoint:
- MetadataIndexProvider, GraphIndexProvider, HnswProvider,
EntityIdMapperProvider, CacheProvider — each typed as exactly the surface
brainy calls (optional/feature-detected members like HNSW setPersistMode and
enableCOW are intentionally excluded).
- Re-exports ColumnStoreProvider and AggregationProvider (and the aggregate
types) from the same entrypoint so a plugin author can import the whole
provider surface from one place.
Brainy's own baseline classes now `implements` these contracts
(MetadataIndexManager, GraphAdjacencyIndex, HNSWIndex, EntityIdMapper,
UnifiedCache), so the interfaces can never silently diverge from what brainy
ships — and any provider that declares `implements` gets a compile error the
moment brainy starts requiring a new member.
The embeddings/embedBatch providers stay typed by the existing EmbeddingFunction
(no duplicate interface added). Type-only changes; no runtime behavior change.
2026-05-27 14:45:40 -07:00
import type { MetadataIndexProvider } from '../plugin.js'
2025-08-26 12:32:21 -07:00
import { MetadataIndexCache , MetadataIndexCacheConfig } from './metadataIndexCache.js'
2026-05-27 11:53:26 -07:00
import { compareCodePoints } from './collation.js'
2025-08-26 12:32:21 -07:00
import { prodLog } from './logger.js'
import { getGlobalCache , UnifiedCache } from './unifiedCache.js'
2025-10-15 13:52:21 -07:00
import {
NounType ,
VerbType ,
TypeUtils ,
NOUN_TYPE_COUNT ,
VERB_TYPE_COUNT
} from '../types/graphTypes.js'
2025-10-13 15:31:03 -07:00
import {
SparseIndex ,
ChunkManager ,
AdaptiveChunkingStrategy ,
ChunkData ,
ChunkDescriptor ,
feat: enforce data/metadata separation, numeric range queries, improved docs
- Store data opaquely in add() and update() instead of spreading object
properties into top-level metadata. data is for semantic search (HNSW),
metadata is for structured where-filter queries (MetadataIndex).
- Fix numeric range queries in MetadataIndex — use numeric-aware comparison
instead of lexicographic string comparison for normalized values.
- Add data field to RelateParams and Relation types for relationship content.
- Add where.type → where.noun alias in metadata-only find() path.
- Rewrite README: focused ~350 lines from 791, quick start first, feature
showcase with mini-snippets, organized doc links, no version callouts.
- Add DATA_MODEL.md and QUERY_OPERATORS.md reference docs.
- Remove 10 outdated/redundant doc files consolidated into API reference.
- Improve JSDoc on Entity, Relation, AddParams, FindParams, and core methods.
- Fix tests asserting data properties appear in metadata (data model violation).
- Deprecate verb.source/target in favor of from/to (public) and sourceId/targetId (storage).
2026-02-09 12:06:59 -08:00
ZoneMap ,
compareNormalizedValues
2025-10-13 15:31:03 -07:00
} from './metadataIndexChunking.js'
2025-10-13 16:39:06 -07:00
import { EntityIdMapper } from './entityIdMapper.js'
2026-01-06 14:09:02 -08:00
import { RoaringBitmap32 , roaringLibraryInitialize } from './roaring/index.js'
feat: production-ready value-based temporal field detection
Replaces unreliable field name pattern matching with DuckDB-inspired value analysis.
### Critical Bug Fix
- Fixes 618k file explosion from false positive temporal field detection
- Field name patterns like `.endsWith('at')` incorrectly flagged non-temporal fields
- Example: "cat", "bat", "hat" were treated as timestamps, creating millions of files
### New System: FieldTypeInference
- Analyzes actual data VALUES, not field names
- Unix timestamp detection: checks if numbers fall in 2000-2100 range
- ISO 8601 datetime detection: pattern matching for date strings
- 11 field types: TIMESTAMP_MS, TIMESTAMP_S, DATE_ISO8601, DATETIME_ISO8601, BOOLEAN, INTEGER, FLOAT, UUID, ARRAY, OBJECT, STRING
- Persistent caching for O(1) lookups at billion scale
- 95%+ accuracy vs 70% with pattern matching
### Architecture
- Zero configuration required
- No fallbacks - pure value-based detection only
- Progressive refinement as more data arrives
- Production patterns from DuckDB, Apache Arrow, Parquet
### Tests
- 39 comprehensive unit tests (all passing)
- Real-world scenarios including exact bug reproduction
- Full coverage: all types, cache, edge cases
### Performance
- Cache hit: 0.1-0.5ms (O(1))
- Cache miss: 5-10ms (analyze 100 samples)
- Memory: ~500 bytes per field
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 13:58:57 -07:00
import { FieldTypeInference , FieldType } from './fieldTypeInference.js'
2026-05-15 12:31:28 -07:00
import { BrainyError } from '../errors/brainyError.js'
2025-08-26 12:32:21 -07:00
2026-04-09 16:26:38 -07:00
/ * *
* Fields whose values are stored in the sparse index as BUCKETED values
* ( rounded to a coarser granularity to keep the index compact ) . Sorting
* and any precision - sensitive comparison on these fields must bypass the
* index and read the actual value directly from entity storage .
*
* Currently only timestamps are bucketed — they round to 1 - minute windows
* via ` Math.floor(ts / 60000) * 60000 ` in the chunking layer . If any new
* bucketed field is added ( e . g . a compressed float ) , add it here too .
* /
const BUCKETED_INDEX_FIELDS : ReadonlySet < string > = new Set ( [
2026-08-03 15:28:24 -07:00
'system.createdAt' ,
'system.updatedAt'
2026-04-09 16:26:38 -07:00
] )
2025-08-26 12:32:21 -07:00
export interface MetadataIndexEntry {
field : string
value : string | number | boolean
ids : Set < string >
lastUpdated : number
}
export interface FieldIndexData {
// Maps value -> count for quick filter discovery
values : Record < string , number >
lastUpdated : number
}
export interface MetadataIndexStats {
totalEntries : number
totalIds : number
fieldsIndexed : string [ ]
lastRebuild : number
indexSize : number // in bytes
}
export interface MetadataIndexConfig {
maxIndexSize? : number // Max number of entries per field value (default: 10000)
rebuildThreshold? : number // Rebuild if index is this % stale (default: 0.1)
autoOptimize? : boolean // Auto-cleanup unused entries (default: true)
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
// NOTE: the name-based indexedFields/excludeFields knobs died with the
// field-addressing law ("no special names"): EVERY user field indexes,
// whatever its name. Bulk-payload protection is value-SHAPE based and
// uniform across all names (large arrays never become posting scalars;
// long values index hashed) — shape is not a name carve-out.
2025-08-26 12:32:21 -07:00
}
2026-02-01 16:23:49 -08:00
export interface MetadataIndexOptions {
2026-07-02 15:11:41 -07:00
entityIdMapper? : EntityIdMapper // Optional pre-configured EntityIdMapper (e.g., native from cor)
2026-02-01 16:23:49 -08:00
}
2025-08-26 12:32:21 -07:00
/ * *
* Manages metadata indexes for fast filtering
* Maintains inverted indexes : field + value - > list of IDs
* /
2025-09-12 12:45:32 -07:00
// Cardinality tracking for optimization decisions
interface CardinalityInfo {
uniqueValues : number
totalValues : number
distribution : 'uniform' | 'skewed' | 'sparse'
updateFrequency : number
lastAnalyzed : number
}
// Field statistics for smart optimization
interface FieldStats {
cardinality : CardinalityInfo
queryCount : number
rangeQueryCount : number
exactQueryCount : number
avgQueryTime : number
2026-01-27 15:38:21 -08:00
indexType : 'hash' // Only 'hash' since all fields use chunked sparse indices with zone maps
2025-09-12 12:45:32 -07:00
normalizationStrategy ? : 'none' | 'precision' | 'bucket'
}
feat: export provider contracts for the plugin surface brainy consumes
Native accelerators (cortex) register providers for metadataIndex, graphIndex,
hnsw, entityIdMapper, cache, columnStore, and aggregation. Until now the exact
method/property surface brainy calls on each was implicit — a provider could
drop a member brainy depends on and only fail at runtime when that path ran.
This defines and exports the provider contracts from the stable
@soulcraft/brainy/plugin entrypoint:
- MetadataIndexProvider, GraphIndexProvider, HnswProvider,
EntityIdMapperProvider, CacheProvider — each typed as exactly the surface
brainy calls (optional/feature-detected members like HNSW setPersistMode and
enableCOW are intentionally excluded).
- Re-exports ColumnStoreProvider and AggregationProvider (and the aggregate
types) from the same entrypoint so a plugin author can import the whole
provider surface from one place.
Brainy's own baseline classes now `implements` these contracts
(MetadataIndexManager, GraphAdjacencyIndex, HNSWIndex, EntityIdMapper,
UnifiedCache), so the interfaces can never silently diverge from what brainy
ships — and any provider that declares `implements` gets a compile error the
moment brainy starts requiring a new member.
The embeddings/embedBatch providers stay typed by the existing EmbeddingFunction
(no duplicate interface added). Type-only changes; no runtime behavior change.
2026-05-27 14:45:40 -07:00
/ * *
* Implements { @link MetadataIndexProvider } : the metadata - index surface Brainy
* calls on whatever the ` 'metadataIndex' ` provider resolves to ( its own
2026-07-02 15:11:41 -07:00
* manager , or Cor ' s native Rust engine ) .
feat: export provider contracts for the plugin surface brainy consumes
Native accelerators (cortex) register providers for metadataIndex, graphIndex,
hnsw, entityIdMapper, cache, columnStore, and aggregation. Until now the exact
method/property surface brainy calls on each was implicit — a provider could
drop a member brainy depends on and only fail at runtime when that path ran.
This defines and exports the provider contracts from the stable
@soulcraft/brainy/plugin entrypoint:
- MetadataIndexProvider, GraphIndexProvider, HnswProvider,
EntityIdMapperProvider, CacheProvider — each typed as exactly the surface
brainy calls (optional/feature-detected members like HNSW setPersistMode and
enableCOW are intentionally excluded).
- Re-exports ColumnStoreProvider and AggregationProvider (and the aggregate
types) from the same entrypoint so a plugin author can import the whole
provider surface from one place.
Brainy's own baseline classes now `implements` these contracts
(MetadataIndexManager, GraphAdjacencyIndex, HNSWIndex, EntityIdMapper,
UnifiedCache), so the interfaces can never silently diverge from what brainy
ships — and any provider that declares `implements` gets a compile error the
moment brainy starts requiring a new member.
The embeddings/embedBatch providers stay typed by the existing EmbeddingFunction
(no duplicate interface added). Type-only changes; no runtime behavior change.
2026-05-27 14:45:40 -07:00
* /
export class MetadataIndexManager implements MetadataIndexProvider {
2025-08-26 12:32:21 -07:00
private storage : StorageAdapter
private config : Required < MetadataIndexConfig >
private isRebuilding = false
private metadataCache : MetadataIndexCache
private fieldIndexes = new Map < string , FieldIndexData > ( )
private dirtyFields = new Set < string > ( )
private lastFlushTime = Date . now ( )
private autoFlushThreshold = 10 // Start with 10 for more frequent non-blocking flushes
2025-10-13 15:31:03 -07:00
2025-09-12 12:45:32 -07:00
// Cardinality and field statistics tracking
private fieldStats = new Map < string , FieldStats > ( )
private cardinalityUpdateInterval = 100 // Update cardinality every N operations
private operationCount = 0
// Smart normalization thresholds
private readonly HIGH_CARDINALITY_THRESHOLD = 1000
private readonly TIMESTAMP_PRECISION_MS = 60000 // 1 minute buckets
private readonly FLOAT_PRECISION = 2 // decimal places
2025-09-12 13:24:47 -07:00
// Type-Field Affinity Tracking for intelligent NLP
private typeFieldAffinity = new Map < string , Map < string , number > > ( ) // nounType -> field -> count
private totalEntitiesByType = new Map < string , number > ( ) // nounType -> total count
2025-10-15 13:52:21 -07:00
2025-11-25 12:37:21 -08:00
feat: Stage 3 CANONICAL taxonomy with 169 types (v5.5.0)
Expand type system from 71 to 169 types achieving 96-97% coverage of all human knowledge.
NEW FEATURES:
- 42 noun types (was 31): Added organism, substance + 11 others
- 127 verb types (was 40): Added affects, learns, destroys + 84 others
- Stage 3 CANONICAL taxonomy covering all major knowledge domains
NEW TYPES:
Nouns: organism (biological entities), substance (physical matter)
Verbs: destroys (lifecycle), affects (patient role), learns (cognition)
Plus 95 additional types across 24 semantic categories
REMOVED TYPES (migration recommended):
- user → person, topic → concept, content → informationContent
- createdBy, belongsTo, supervises, succeeds → use inverse relationships
PERFORMANCE:
- Memory: 676 bytes for 169 types (99.2% reduction vs Maps)
- Type embeddings: 338KB embedded, zero runtime computation
- Coverage: Natural Sciences (96%), Formal Sciences (98%), Social Sciences (97%), Humanities (96%)
DOCUMENTATION:
- Added docs/STAGE3-CANONICAL-TAXONOMY.md
- Updated README.md with new type counts
- Complete CHANGELOG entry for v5.5.0
BREAKING CHANGES (minor impact):
Removed 6 types (user, topic, content, createdBy, belongsTo, supervises, succeeds).
Migration path provided via type mapping.
Timeless design: Stable for 20+ years without changes.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-06 09:02:23 -08:00
// Phase 1b: Fixed-size type tracking (Stage 3 CANONICAL: 99.2% memory reduction vs Maps)
2025-10-15 13:52:21 -07:00
// Uint32Array provides O(1) access via type enum index
feat: Stage 3 CANONICAL taxonomy with 169 types (v5.5.0)
Expand type system from 71 to 169 types achieving 96-97% coverage of all human knowledge.
NEW FEATURES:
- 42 noun types (was 31): Added organism, substance + 11 others
- 127 verb types (was 40): Added affects, learns, destroys + 84 others
- Stage 3 CANONICAL taxonomy covering all major knowledge domains
NEW TYPES:
Nouns: organism (biological entities), substance (physical matter)
Verbs: destroys (lifecycle), affects (patient role), learns (cognition)
Plus 95 additional types across 24 semantic categories
REMOVED TYPES (migration recommended):
- user → person, topic → concept, content → informationContent
- createdBy, belongsTo, supervises, succeeds → use inverse relationships
PERFORMANCE:
- Memory: 676 bytes for 169 types (99.2% reduction vs Maps)
- Type embeddings: 338KB embedded, zero runtime computation
- Coverage: Natural Sciences (96%), Formal Sciences (98%), Social Sciences (97%), Humanities (96%)
DOCUMENTATION:
- Added docs/STAGE3-CANONICAL-TAXONOMY.md
- Updated README.md with new type counts
- Complete CHANGELOG entry for v5.5.0
BREAKING CHANGES (minor impact):
Removed 6 types (user, topic, content, createdBy, belongsTo, supervises, succeeds).
Migration path provided via type mapping.
Timeless design: Stable for 20+ years without changes.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-06 09:02:23 -08:00
// 42 noun types × 4 bytes = 168 bytes (vs ~20KB with Map overhead)
// 127 verb types × 4 bytes = 508 bytes (vs ~62KB with Map overhead)
// Total: 676 bytes (vs ~85KB) = 99.2% memory reduction
private entityCountsByTypeFixed = new Uint32Array ( NOUN_TYPE_COUNT ) // 168 bytes (Stage 3 CANONICAL: 42 types)
private verbCountsByTypeFixed = new Uint32Array ( VERB_TYPE_COUNT ) // 508 bytes (Stage 3 CANONICAL: 127 types)
2025-10-15 13:52:21 -07:00
2025-08-26 12:32:21 -07:00
// Unified cache for coordinated memory management
private unifiedCache : UnifiedCache
2025-10-09 13:56:45 -07:00
// File locking for concurrent write protection (prevents race conditions)
private activeLocks = new Map < string , { expiresAt : number ; lockValue : string } > ( )
private lockPromises = new Map < string , Promise < boolean > > ( )
private lockTimers = new Map < string , NodeJS.Timeout > ( ) // Track timers for cleanup
2026-01-27 15:38:21 -08:00
// Adaptive Chunked Sparse Indexing
2025-10-13 15:31:03 -07:00
// Reduces file count from 560k → 89 files (630x reduction)
// ALL fields now use chunking - no more flat files
2026-01-27 15:38:21 -08:00
// Removed sparseIndices Map - now lazy-loaded via UnifiedCache only
2025-11-14 08:26:45 -08:00
// PROJECTED: Reduces metadata memory from 35GB → 5GB @ 1B scale (86% reduction from chunking strategy, not yet benchmarked)
2025-10-13 15:31:03 -07:00
private chunkManager : ChunkManager
private chunkingStrategy : AdaptiveChunkingStrategy
2026-05-15 12:31:28 -07:00
// (Removed in 7.22.0) `dirtyChunks` and `dirtySparseIndices` Maps —
// never populated since the sparse-index write path was deleted in 7.20.0
// (commit 11be039). The associated `flushDirtyMetadata()` no-op was also
// removed. Column store is the single source of truth for indexed writes.
2026-01-31 09:09:36 -08:00
2026-01-27 15:38:21 -08:00
// Roaring Bitmap Support
2025-10-13 16:39:06 -07:00
// EntityIdMapper for UUID ↔ integer conversion
private idMapper : EntityIdMapper
2026-01-27 15:38:21 -08:00
// Field Type Inference (Production-ready value-based type detection)
feat: production-ready value-based temporal field detection
Replaces unreliable field name pattern matching with DuckDB-inspired value analysis.
### Critical Bug Fix
- Fixes 618k file explosion from false positive temporal field detection
- Field name patterns like `.endsWith('at')` incorrectly flagged non-temporal fields
- Example: "cat", "bat", "hat" were treated as timestamps, creating millions of files
### New System: FieldTypeInference
- Analyzes actual data VALUES, not field names
- Unix timestamp detection: checks if numbers fall in 2000-2100 range
- ISO 8601 datetime detection: pattern matching for date strings
- 11 field types: TIMESTAMP_MS, TIMESTAMP_S, DATE_ISO8601, DATETIME_ISO8601, BOOLEAN, INTEGER, FLOAT, UUID, ARRAY, OBJECT, STRING
- Persistent caching for O(1) lookups at billion scale
- 95%+ accuracy vs 70% with pattern matching
### Architecture
- Zero configuration required
- No fallbacks - pure value-based detection only
- Progressive refinement as more data arrives
- Production patterns from DuckDB, Apache Arrow, Parquet
### Tests
- 39 comprehensive unit tests (all passing)
- Real-world scenarios including exact bug reproduction
- Full coverage: all types, cache, edge cases
### Performance
- Cache hit: 0.1-0.5ms (O(1))
- Cache miss: 5-10ms (analyze 100 samples)
- Memory: ~500 bytes per field
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 13:58:57 -07:00
// Replaces unreliable pattern matching with DuckDB-inspired value analysis
private fieldTypeInference : FieldTypeInference
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
/ * *
* Unified Column Store — replaces sparse index internals for filtering + sorting .
* Created in the constructor ( no storage needed for writes ) , storage discovery
* happens in init ( ) . Public so brainy . ts can call sortTopK directly for
* unfiltered sort .
* /
public columnStore : ColumnStore
2026-02-01 16:23:49 -08:00
constructor ( storage : StorageAdapter , config : MetadataIndexConfig = { } , options : MetadataIndexOptions = { } ) {
2025-08-26 12:32:21 -07:00
this . storage = storage
this . config = {
maxIndexSize : config.maxIndexSize ? ? 10000 ,
rebuildThreshold : config.rebuildThreshold ? ? 0.1 ,
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
autoOptimize : config.autoOptimize ? ? true
// No name-based exclude/allow lists — the field-addressing law: every
// user field indexes, whatever its name ('content', 'data', 'id',
// 'vector', … included). Bulk payloads are kept out by uniform value-
// SHAPE rules in extractIndexableFields (arrays >10 never become
// posting scalars; >100-char values index hashed), never by name.
2025-08-26 12:32:21 -07:00
}
2025-09-22 15:45:35 -07:00
2025-08-26 12:32:21 -07:00
// Initialize metadata cache with similar config to search cache
this . metadataCache = new MetadataIndexCache ( {
maxAge : 5 * 60 * 1000 , // 5 minutes
maxSize : 500 , // 500 entries (field indexes + value chunks)
enabled : true
} )
2025-09-22 15:45:35 -07:00
2025-08-26 12:32:21 -07:00
// Get global unified cache for coordinated memory management
this . unifiedCache = getGlobalCache ( )
2025-09-22 15:45:35 -07:00
2026-07-02 15:11:41 -07:00
// Use injected EntityIdMapper (e.g., native from cor) or create JS fallback
2026-02-01 16:23:49 -08:00
this . idMapper = options . entityIdMapper ? ? new EntityIdMapper ( {
2025-10-13 16:39:06 -07:00
storage ,
storageKey : 'brainy:entityIdMapper'
} )
2026-01-27 15:38:21 -08:00
// Initialize chunking system with roaring bitmap support
2025-10-13 16:39:06 -07:00
this . chunkManager = new ChunkManager ( storage , this . idMapper )
2025-10-13 15:31:03 -07:00
this . chunkingStrategy = new AdaptiveChunkingStrategy ( )
2026-01-27 15:38:21 -08:00
// Initialize Field Type Inference
feat: production-ready value-based temporal field detection
Replaces unreliable field name pattern matching with DuckDB-inspired value analysis.
### Critical Bug Fix
- Fixes 618k file explosion from false positive temporal field detection
- Field name patterns like `.endsWith('at')` incorrectly flagged non-temporal fields
- Example: "cat", "bat", "hat" were treated as timestamps, creating millions of files
### New System: FieldTypeInference
- Analyzes actual data VALUES, not field names
- Unix timestamp detection: checks if numbers fall in 2000-2100 range
- ISO 8601 datetime detection: pattern matching for date strings
- 11 field types: TIMESTAMP_MS, TIMESTAMP_S, DATE_ISO8601, DATETIME_ISO8601, BOOLEAN, INTEGER, FLOAT, UUID, ARRAY, OBJECT, STRING
- Persistent caching for O(1) lookups at billion scale
- 95%+ accuracy vs 70% with pattern matching
### Architecture
- Zero configuration required
- No fallbacks - pure value-based detection only
- Progressive refinement as more data arrives
- Production patterns from DuckDB, Apache Arrow, Parquet
### Tests
- 39 comprehensive unit tests (all passing)
- Real-world scenarios including exact bug reproduction
- Full coverage: all types, cache, edge cases
### Performance
- Cache hit: 0.1-0.5ms (O(1))
- Cache miss: 5-10ms (analyze 100 samples)
- Memory: ~500 bytes per field
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 13:58:57 -07:00
this . fieldTypeInference = new FieldTypeInference ( storage )
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// Create column store — works immediately for writes (in-memory tail buffers).
// Storage discovery (loading existing segments) happens in init().
this . columnStore = new ColumnStore ( )
2026-01-27 15:38:21 -08:00
// Removed lazyLoadCounts() call from constructor
2025-11-26 12:06:33 -08:00
// It was a race condition (not awaited) and read from wrong source.
// Now properly called in init() after warmCache() loads the sparse index.
2025-09-22 15:45:35 -07:00
}
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
/ * *
* Get the shared EntityIdMapper instance . Used by the ColumnStore and
* other subsystems that need UUID ↔ u32 mapping without creating a
* second mapper that could diverge .
* /
getIdMapper ( ) : EntityIdMapper {
return this . idMapper
}
2025-10-13 16:39:06 -07:00
/ * *
* Initialize the metadata index manager
* This must be called after construction and before any queries
* /
async init ( ) : Promise < void > {
2026-01-06 14:09:02 -08:00
// Initialize roaring-wasm library (browser bundle requires async init)
await roaringLibraryInitialize ( )
2026-01-27 15:38:21 -08:00
// Load field registry to discover persisted indices
2025-10-23 08:47:37 -07:00
// Must run first to populate fieldIndexes directory before warming cache
await this . loadFieldRegistry ( )
2025-10-13 16:39:06 -07:00
// Initialize EntityIdMapper (loads UUID ↔ integer mappings from storage)
await this . idMapper . init ( )
2025-10-15 12:26:25 -07:00
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// Initialize column store storage discovery (load existing segment manifests).
// The column store was created in the constructor for immediate writes;
// this step loads persisted segments so queries can find existing data.
try {
await this . columnStore . init ( this . storage , this . idMapper )
} catch ( err ) {
prodLog . warn ( '[MetadataIndex] Column store storage discovery failed:' , err )
}
2026-03-24 12:57:11 -07:00
// Check if field registry was loaded successfully
2026-01-31 09:14:51 -08:00
const hasFields = this . fieldIndexes . size > 0
2025-11-26 12:06:33 -08:00
2026-03-24 12:57:11 -07:00
if ( ! hasFields ) {
// Don't trust "empty" — field registry may be missing due to interrupted flush.
// Probe storage for actual entities before concluding the workspace is empty.
try {
const probe = await this . storage . getNouns ( { pagination : { limit : 1 , offset : 0 } } )
const hasEntities = ( probe . totalCount ? ? 0 ) > 0 || probe . items . length > 0
if ( hasEntities ) {
console . warn (
` [MetadataIndex] Field registry missing but ${ probe . totalCount ? ? 'unknown' } entities exist on disk — rebuilding index `
)
await this . rebuild ( )
return // rebuild handles warmCache + lazyLoadCounts internally
}
} catch {
// Storage probe failed — genuinely empty or storage not ready
}
return // Truly empty workspace — nothing to warm
}
2025-11-26 12:06:33 -08:00
2026-03-24 12:57:11 -07:00
// Warm the cache with common fields (lazy loading optimization)
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
// This loads the type column ('system.type') needed for type counts
2026-03-24 12:57:11 -07:00
await this . warmCache ( )
2026-01-26 12:12:11 -08:00
2026-03-24 12:57:11 -07:00
// Load type counts AFTER warmCache (sparse index is now cached)
await this . lazyLoadCounts ( )
// Phase 1b: Sync loaded counts to fixed-size arrays
this . syncTypeCountsToFixed ( )
2026-01-26 12:12:11 -08:00
}
/ * *
2026-01-27 15:38:21 -08:00
* Detect index corruption and automatically repair via rebuild
2026-01-26 12:12:11 -08:00
* This catches the update ( ) field asymmetry bug that causes 7 fields to accumulate per update
2026-01-27 15:38:21 -08:00
* Corruption threshold : 100 avg metadata entries / entity , excluding __words__ ( expected ~ 30 )
2026-01-31 09:14:51 -08:00
*
* Removed from init ( ) hot path for performance . Call explicitly via :
* - brain . checkHealth ( ) — returns health status
* - brain . repairIndex ( ) — runs detection + auto - repair
2026-01-26 12:12:11 -08:00
* /
2026-01-31 09:14:51 -08:00
async detectAndRepairCorruption ( ) : Promise < void > {
2026-01-26 12:12:11 -08:00
const validation = await this . validateConsistency ( )
if ( ! validation . healthy ) {
prodLog . warn ( ` ⚠️ Index corruption detected ( ${ validation . avgEntriesPerEntity . toFixed ( 1 ) } avg entries/entity) ` )
prodLog . warn ( '🔄 Auto-rebuilding index to repair...' )
// Clear and rebuild
await this . clearAllIndexData ( )
await this . rebuild ( )
// Re-validate after rebuild
const postRebuild = await this . validateConsistency ( )
if ( postRebuild . healthy ) {
prodLog . info ( ` ✅ Index rebuilt successfully ( ${ postRebuild . avgEntriesPerEntity . toFixed ( 1 ) } avg entries/entity) ` )
} else {
prodLog . error (
` ❌ Index still appears corrupted after rebuild ( ${ postRebuild . avgEntriesPerEntity . toFixed ( 1 ) } avg entries/entity). ` +
` This may indicate a different issue. `
)
}
}
2025-10-15 12:26:25 -07:00
}
/ * *
2026-01-27 15:38:21 -08:00
* Warm the cache by preloading common field sparse indices
2025-10-15 12:26:25 -07:00
* This improves cache hit rates by loading frequently - accessed fields at startup
* Target : > 80 % cache hit rate for typical workloads
* /
async warmCache ( ) : Promise < void > {
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
// Common columns used in most queries — the frozen system keys, plus
// legacy spellings for a pre-epoch-3 brain read before its rebuild runs.
const commonFields = [ 'system.type' , 'system.service' , 'system.createdAt' , 'noun' ]
2025-10-15 12:26:25 -07:00
prodLog . debug ( ` 🔥 Warming metadata cache with common fields: ${ commonFields . join ( ', ' ) } ` )
// Preload in parallel for speed
await Promise . all (
commonFields . map ( async field = > {
try {
await this . loadSparseIndex ( field )
} catch ( error ) {
// Silently ignore if field doesn't exist yet
// This maintains zero-configuration principle
prodLog . debug ( ` Cache warming: field ' ${ field } ' not yet indexed ` )
}
} )
)
prodLog . debug ( '✅ Metadata cache warmed successfully' )
2025-10-15 13:52:21 -07:00
// Phase 1b: Also warm cache for top types (type-aware optimization)
await this . warmCacheForTopTypes ( 3 )
}
/ * *
* Phase 1b : Warm cache for top types ( type - aware optimization )
* Preloads metadata indices for the most common entity types and their top fields
* This significantly improves query performance for the most frequently accessed data
*
* @param topN Number of top types to warm ( default : 3 )
* /
async warmCacheForTopTypes ( topN : number = 3 ) : Promise < void > {
// Get top noun types by entity count
const topTypes = this . getTopNounTypes ( topN )
if ( topTypes . length === 0 ) {
prodLog . debug ( '⏭️ Skipping type-aware cache warming: no types found yet' )
return
}
prodLog . debug ( ` 🔥 Warming cache for top ${ topTypes . length } types: ${ topTypes . join ( ', ' ) } ` )
// For each top type, warm cache for its top fields
for ( const type of topTypes ) {
// Get fields with high affinity to this type
const typeFields = this . typeFieldAffinity . get ( type )
if ( ! typeFields ) continue
// Sort fields by count (most common first)
const topFields = Array . from ( typeFields . entries ( ) )
. sort ( ( a , b ) = > b [ 1 ] - a [ 1 ] )
. slice ( 0 , 5 ) // Top 5 fields per type
. map ( ( [ field ] ) = > field )
if ( topFields . length === 0 ) continue
prodLog . debug ( ` 📊 Type ' ${ type } ' - warming fields: ${ topFields . join ( ', ' ) } ` )
// Preload sparse indices for these fields in parallel
await Promise . all (
topFields . map ( async field = > {
try {
await this . loadSparseIndex ( field )
} catch ( error ) {
// Silently ignore if field doesn't exist yet
prodLog . debug ( ` ⏭️ Field ' ${ field } ' not yet indexed for type ' ${ type } ' ` )
}
} )
)
}
prodLog . debug ( '✅ Type-aware cache warming completed' )
2025-10-13 16:39:06 -07:00
}
feat: warm contract (warm/warmOnOpen/provider warm hook), configurable transact budget floor, backend-neutral vector index op names
Three pieces addressing the cold-restart-write incident where a production
deployment's first writes after every restart (33-35s each on a cold page
cache) blew the op-count-scaled transact budget mid-batch: every write is
itself a multi-op transaction, so one cold operation consumed the whole
budget, the gate before the next operation tripped, and the write rolled
back atomically - refused, retried, and refused again until the page cache
warmed passively.
- The budget's start-gating contract is now explicit and pinned: it gates
STARTING the next operation, never rolling back completed work for
elapsed time (the shipped schedule since 8.7.0, now stated in contract
JSDoc, guarded by code for operation 0, and enforced by regression
tests). The 30s floor is configurable via transactionBudgetFloorMs for
stores whose cold operations legitimately run long.
- New brain.warm() eagerly loads the vector index, metadata index, and
graph adjacency so first operations after a cold restart run at
steady-state cost. Returns a WarmReport with an honest per-surface
outcome (warmed / probed / unavailable) - never reports a probe as a
warm. warmOnOpen: true runs it during init(). New optional provider hook
warm() on the vector and graph plugin contracts.
- Vector-index transaction op classes renamed from the backend-specific
AddToHNSWOperation / RemoveFromHNSWOperation to backend-neutral
AddToVectorIndexOperation / RemoveFromVectorIndexOperation, stamping the
active backend into the emitted op-name string (AddToVectorIndex(js-hnsw)
vs a native provider's own identity) so journals never misdirect an
operator toward an index that isn't running.
2026-07-22 16:42:26 -07:00
/ * *
* Full hydration — the { @link Brainy . warm } readiness seam for the metadata
* index . Unlike { @link warmCache } / { @link warmCacheForTopTypes } ( which
* warm only a heuristic subset : common fields plus the top - N types ' top
* fields ) , this loads EVERY field ' s sparse index the field registry knows
* about — a real read through { @link loadSparseIndex } into the unified
* cache for each field , not a stat / existence check . Idempotent : an
* already - cached field ' s ` loadSparseIndex ` call is a cheap cache hit .
*
* Re - reads the field registry first when ` fieldIndexes ` is empty ( a warm ( )
* call issued before ` init() ` populated it would otherwise hydrate
* nothing ) , then loads every discovered field in parallel .
* /
async hydrateAll ( ) : Promise < void > {
if ( this . fieldIndexes . size === 0 ) {
await this . loadFieldRegistry ( )
}
const fields = Array . from ( this . fieldIndexes . keys ( ) )
if ( fields . length === 0 ) {
prodLog . debug ( '[MetadataIndex] hydrateAll: no persisted fields to hydrate' )
return
}
prodLog . debug ( ` [MetadataIndex] hydrateAll: loading ${ fields . length } field(s) — ${ fields . join ( ', ' ) } ` )
await Promise . all (
fields . map ( async field = > {
try {
await this . loadSparseIndex ( field )
} catch ( error ) {
// A single field's load failure doesn't abort the rest of the
// hydration — warm() is a best-effort readiness step, never a
// correctness gate (queries still demand-load on miss).
prodLog . debug ( ` [MetadataIndex] hydrateAll: field ' ${ field } ' failed to load: ` , error )
}
} )
)
}
2025-10-09 13:56:45 -07:00
/ * *
* Acquire an in - memory lock for coordinating concurrent metadata index writes
* Uses in - memory locks since MetadataIndexManager doesn ' t have direct file system access
* @param lockKey The key to lock on ( e . g . , 'field_noun' , 'sorted_timestamp' )
* @param ttl Time to live for the lock in milliseconds ( default : 10 seconds )
* @returns Promise that resolves to true if lock was acquired , false otherwise
* /
private async acquireLock (
lockKey : string ,
ttl : number = 10000
) : Promise < boolean > {
const lockValue = ` ${ Date . now ( ) } _ ${ Math . random ( ) } `
const expiresAt = Date . now ( ) + ttl
// Check if lock already exists and is still valid
const existingLock = this . activeLocks . get ( lockKey )
if ( existingLock && existingLock . expiresAt > Date . now ( ) ) {
// Lock exists and is still valid - wait briefly and retry once
await new Promise ( resolve = > setTimeout ( resolve , 50 ) )
// Check again after wait
const recheckLock = this . activeLocks . get ( lockKey )
if ( recheckLock && recheckLock . expiresAt > Date . now ( ) ) {
return false // Lock still held
}
}
// Acquire the lock
this . activeLocks . set ( lockKey , { expiresAt , lockValue } )
// Schedule automatic cleanup when lock expires
const timer = setTimeout ( ( ) = > {
this . releaseLock ( lockKey , lockValue ) . catch ( ( error ) = > {
prodLog . debug ( ` Failed to auto-release expired lock ${ lockKey } : ` , error )
} )
} , ttl )
this . lockTimers . set ( lockKey , timer )
return true
}
/ * *
* Release an in - memory lock
* @param lockKey The key to unlock
* @param lockValue The value used when acquiring the lock ( for verification )
* @returns Promise that resolves when lock is released
* /
private async releaseLock (
lockKey : string ,
lockValue? : string
) : Promise < void > {
// If lockValue is provided, verify it matches before releasing
if ( lockValue ) {
const existingLock = this . activeLocks . get ( lockKey )
if ( existingLock && existingLock . lockValue !== lockValue ) {
// Lock was acquired by someone else, don't release it
return
}
}
// Clear the timeout timer if it exists
const timer = this . lockTimers . get ( lockKey )
if ( timer ) {
clearTimeout ( timer )
this . lockTimers . delete ( lockKey )
}
// Remove the lock
this . activeLocks . delete ( lockKey )
}
2025-09-22 15:45:35 -07:00
/ * *
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
* Lazy load entity counts from the type column ( O ( n ) where n = number of
* types ) . The frozen key is 'system.type' ( epoch 3 ) ; the legacy 'noun'
* column is read as a fallback for a pre - epoch - 3 brain observed before its
* rebuild has run ( e . g . a reader - mode open against an old writer ) .
2026-01-27 15:38:21 -08:00
* FIX : Previously read from stats . nounCount which was SERVICE - keyed , not TYPE - keyed
2025-09-22 15:45:35 -07:00
* /
private async lazyLoadCounts ( ) : Promise < void > {
try {
2026-01-27 15:38:21 -08:00
// CRITICAL FIX - Clear counts before loading to prevent accumulation
2025-12-02 11:45:17 -08:00
// Previously, counts accumulated across restarts causing 100x inflation
this . totalEntitiesByType . clear ( )
this . entityCountsByTypeFixed . fill ( 0 )
this . verbCountsByTypeFixed . fill ( 0 )
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
// PRIMARY (8.0+): rehydrate per-type counts from the column store's
// type column — the authoritative on-disk source after a cold reopen.
// Frozen key first ('system.type', epoch 3), legacy 'noun' as the
// pre-rebuild fallback.
2026-06-19 10:55:43 -07:00
//
// The chunked sparse-index WRITE path was removed in 7.20.0 (commit
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
// 11be039): new workspaces persist the type column ONLY to the column
// store, never to a sparse-index blob. So the legacy sparse path below
// finds nothing and leaves every count at 0 — which is exactly why
// counts.byType/byTypeEnum/topTypes/allNounTypeCounts all read empty
2026-06-19 10:55:43 -07:00
// after close()+reopen while find()/getNounCount() (different sources)
// stay correct. The column store's per-value cardinality matches the warm
// `updateTypeFieldAffinity` counts EXACTLY because both are driven from the
// same `addToIndex` field set, in lockstep, with no visibility gate on
// either — so this rehydration reproduces the warm values precisely.
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
const indexedCols = this . columnStore ? this . columnStore . getIndexedFields ( ) : [ ]
const typeCol = indexedCols . includes ( 'system.type' )
? 'system.type'
: indexedCols . includes ( 'noun' )
? 'noun'
: null
if ( this . columnStore && typeCol ) {
const nounValues = await this . columnStore . getFilterValues ( typeCol )
2026-06-19 10:55:43 -07:00
for ( const value of nounValues ) {
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
const bitmap = await this . columnStore . filter ( typeCol , value )
2026-06-19 10:55:43 -07:00
if ( bitmap . size > 0 ) {
// Use the stored value directly as the key (the legacy sparse path
// did the same): it is already the normalized type string that
// getNounFromIndex/getEntityCountByType expect, so syncTypeCountsToFixed
// — called immediately after lazyLoadCounts in init() — copies it into
// entityCountsByTypeFixed without re-normalization drift.
this . totalEntitiesByType . set ( value , bitmap . size )
}
}
prodLog . debug ( ` ✅ Rehydrated type counts from column store: ${ this . totalEntitiesByType . size } types ` )
return
}
// LEGACY FALLBACK (pre-7.20.0 workspaces still on the chunked sparse index).
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
const sparseCol = ( await this . loadSparseIndex ( 'system.type' ) ) ? 'system.type' : 'noun'
const nounSparseIndex = await this . loadSparseIndex ( sparseCol )
2025-11-26 12:06:33 -08:00
if ( ! nounSparseIndex ) {
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
// No column-store type column and no sparse index yet — counts will be
2026-06-19 10:55:43 -07:00
// populated as entities are added.
2025-11-26 12:06:33 -08:00
return
}
// Iterate through all chunks and sum up bitmap sizes by type
for ( const chunkId of nounSparseIndex . getAllChunkIds ( ) ) {
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
const chunk = await this . chunkManager . loadChunk ( sparseCol , chunkId )
2025-11-26 12:06:33 -08:00
if ( chunk ) {
for ( const [ type , bitmap ] of chunk . entries ) {
const currentCount = this . totalEntitiesByType . get ( type ) || 0
this . totalEntitiesByType . set ( type , currentCount + bitmap . size )
2025-09-22 15:45:35 -07:00
}
}
}
2025-11-26 12:06:33 -08:00
prodLog . debug ( ` ✅ Loaded type counts from sparse index: ${ this . totalEntitiesByType . size } types ` )
2025-09-22 15:45:35 -07:00
} catch ( error ) {
// Silently fail - counts will be populated as entities are added
// This maintains zero-configuration principle
2026-06-19 10:55:43 -07:00
prodLog . debug ( 'Could not load type counts:' , error )
2025-09-22 15:45:35 -07:00
}
2025-08-26 12:32:21 -07:00
}
2025-10-15 13:52:21 -07:00
/ * *
* Phase 1b : Sync Map - based counts to fixed - size Uint32Arrays
* This enables gradual migration from Maps to arrays while maintaining backward compatibility
* Called periodically and on demand to keep both representations in sync
* /
private syncTypeCountsToFixed ( ) : void {
// Sync noun counts from totalEntitiesByType Map to entityCountsByTypeFixed array
for ( let i = 0 ; i < NOUN_TYPE_COUNT ; i ++ ) {
const type = TypeUtils . getNounFromIndex ( i )
const count = this . totalEntitiesByType . get ( type ) || 0
this . entityCountsByTypeFixed [ i ] = count
}
// Sync verb counts from totalEntitiesByType Map to verbCountsByTypeFixed array
// Note: Verb counts are currently tracked alongside noun counts in totalEntitiesByType
// In the future, we may want a separate Map for verb counts
for ( let i = 0 ; i < VERB_TYPE_COUNT ; i ++ ) {
const type = TypeUtils . getVerbFromIndex ( i )
const count = this . totalEntitiesByType . get ( type ) || 0
this . verbCountsByTypeFixed [ i ] = count
}
}
/ * *
* Phase 1b : Sync from fixed - size arrays back to Maps ( reverse direction )
* Used when Uint32Arrays are the source of truth and need to update Maps
* /
private syncTypeCountsFromFixed ( ) : void {
// Sync noun counts from array to Map
for ( let i = 0 ; i < NOUN_TYPE_COUNT ; i ++ ) {
const count = this . entityCountsByTypeFixed [ i ]
if ( count > 0 ) {
const type = TypeUtils . getNounFromIndex ( i )
this . totalEntitiesByType . set ( type , count )
}
}
// Sync verb counts from array to Map
for ( let i = 0 ; i < VERB_TYPE_COUNT ; i ++ ) {
const count = this . verbCountsByTypeFixed [ i ]
if ( count > 0 ) {
const type = TypeUtils . getVerbFromIndex ( i )
this . totalEntitiesByType . set ( type , count )
}
}
}
2025-09-12 12:45:32 -07:00
/ * *
* Update cardinality statistics for a field
* /
private updateCardinalityStats ( field : string , value : any , operation : 'add' | 'remove' ) : void {
// Initialize field stats if needed
if ( ! this . fieldStats . has ( field ) ) {
this . fieldStats . set ( field , {
cardinality : {
uniqueValues : 0 ,
totalValues : 0 ,
distribution : 'uniform' ,
updateFrequency : 0 ,
lastAnalyzed : Date.now ( )
} ,
queryCount : 0 ,
rangeQueryCount : 0 ,
exactQueryCount : 0 ,
avgQueryTime : 0 ,
indexType : 'hash'
} )
}
const stats = this . fieldStats . get ( field ) !
const cardinality = stats . cardinality
2026-01-27 15:38:21 -08:00
// Track unique values by checking fieldIndex counts
2025-10-13 15:31:03 -07:00
const fieldIndex = this . fieldIndexes . get ( field )
const normalizedValue = this . normalizeValue ( value , field )
const currentCount = fieldIndex ? . values [ normalizedValue ] || 0
2025-09-12 12:45:32 -07:00
if ( operation === 'add' ) {
2025-10-13 15:31:03 -07:00
// If this is a new value (count is 0), increment unique values
if ( currentCount === 0 ) {
2025-09-12 12:45:32 -07:00
cardinality . uniqueValues ++
}
cardinality . totalValues ++
} else if ( operation === 'remove' ) {
2025-10-13 15:31:03 -07:00
// If count will become 0, decrement unique values
if ( currentCount === 1 ) {
cardinality . uniqueValues = Math . max ( 0 , cardinality . uniqueValues - 1 )
2025-09-12 12:45:32 -07:00
}
cardinality . totalValues = Math . max ( 0 , cardinality . totalValues - 1 )
}
// Update frequency tracking
cardinality . updateFrequency ++
2025-10-13 15:31:03 -07:00
2025-09-12 12:45:32 -07:00
// Periodically analyze distribution
if ( ++ this . operationCount % this . cardinalityUpdateInterval === 0 ) {
this . analyzeFieldDistribution ( field )
}
// Determine optimal index type based on cardinality
this . updateIndexStrategy ( field , stats )
}
/ * *
* Analyze field distribution for optimization
* /
private analyzeFieldDistribution ( field : string ) : void {
const stats = this . fieldStats . get ( field )
if ( ! stats ) return
const cardinality = stats . cardinality
const ratio = cardinality . uniqueValues / Math . max ( 1 , cardinality . totalValues )
// Determine distribution type
if ( ratio > 0.9 ) {
cardinality . distribution = 'sparse' // High uniqueness (like IDs, timestamps)
} else if ( ratio < 0.1 ) {
cardinality . distribution = 'skewed' // Low uniqueness (like status, type)
} else {
cardinality . distribution = 'uniform' // Balanced distribution
}
cardinality . lastAnalyzed = Date . now ( )
}
/ * *
* Update index strategy based on field statistics
* /
private updateIndexStrategy ( field : string , stats : FieldStats ) : void {
const hasHighCardinality = stats . cardinality . uniqueValues > this . HIGH_CARDINALITY_THRESHOLD
2026-01-27 15:38:21 -08:00
// All fields use chunked sparse indexing with zone maps
2025-10-13 15:31:03 -07:00
stats . indexType = 'hash'
2025-09-12 12:45:32 -07:00
2025-10-13 13:16:07 -07:00
// Determine normalization strategy for high cardinality NON-temporal fields
// (Temporal fields are already bucketed in normalizeValue from the start!)
2025-09-12 12:45:32 -07:00
if ( hasHighCardinality ) {
2025-10-13 15:31:03 -07:00
// Check if field looks numeric (for float precision reduction)
const fieldLower = field . toLowerCase ( )
const looksNumeric = fieldLower . includes ( 'count' ) || fieldLower . includes ( 'score' ) ||
fieldLower . includes ( 'value' ) || fieldLower . includes ( 'amount' )
if ( looksNumeric ) {
2025-09-12 12:45:32 -07:00
stats . normalizationStrategy = 'precision' // Reduce float precision
} else {
stats . normalizationStrategy = 'none' // Keep as-is for strings
}
} else {
stats . normalizationStrategy = 'none'
}
}
2025-10-13 15:31:03 -07:00
// ============================================================================
2026-01-27 15:38:21 -08:00
// Adaptive Chunked Sparse Indexing
2025-10-13 15:31:03 -07:00
// All fields use chunking - simplified implementation
// ============================================================================
/ * *
* Load sparse index from storage
* /
private async loadSparseIndex ( field : string ) : Promise < SparseIndex | undefined > {
const indexPath = ` __sparse_index__ ${ field } `
const unifiedKey = ` metadata:sparse: ${ field } `
return await this . unifiedCache . get ( unifiedKey , async ( ) = > {
try {
const data = await this . storage . getMetadata ( indexPath )
if ( data ) {
const sparseIndex = SparseIndex . fromJSON ( data )
feat: production-ready value-based temporal field detection
Replaces unreliable field name pattern matching with DuckDB-inspired value analysis.
### Critical Bug Fix
- Fixes 618k file explosion from false positive temporal field detection
- Field name patterns like `.endsWith('at')` incorrectly flagged non-temporal fields
- Example: "cat", "bat", "hat" were treated as timestamps, creating millions of files
### New System: FieldTypeInference
- Analyzes actual data VALUES, not field names
- Unix timestamp detection: checks if numbers fall in 2000-2100 range
- ISO 8601 datetime detection: pattern matching for date strings
- 11 field types: TIMESTAMP_MS, TIMESTAMP_S, DATE_ISO8601, DATETIME_ISO8601, BOOLEAN, INTEGER, FLOAT, UUID, ARRAY, OBJECT, STRING
- Persistent caching for O(1) lookups at billion scale
- 95%+ accuracy vs 70% with pattern matching
### Architecture
- Zero configuration required
- No fallbacks - pure value-based detection only
- Progressive refinement as more data arrives
- Production patterns from DuckDB, Apache Arrow, Parquet
### Tests
- 39 comprehensive unit tests (all passing)
- Real-world scenarios including exact bug reproduction
- Full coverage: all types, cache, edge cases
### Performance
- Cache hit: 0.1-0.5ms (O(1))
- Cache miss: 5-10ms (analyze 100 samples)
- Memory: ~500 bytes per field
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 13:58:57 -07:00
// CRITICAL: Initialize chunk ID counter from existing chunks to prevent ID conflicts
this . chunkManager . initializeNextChunkId ( field , sparseIndex )
2025-10-13 15:31:03 -07:00
// Add to unified cache (sparse indices are expensive to rebuild)
const size = JSON . stringify ( data ) . length
this . unifiedCache . set ( unifiedKey , sparseIndex , 'metadata' , size , 200 )
return sparseIndex
}
} catch ( error ) {
prodLog . debug ( ` Failed to load sparse index for field ' ${ field } ': ` , error )
}
return undefined
} )
}
/ * *
* Save sparse index to storage
* /
private async saveSparseIndex ( field : string , sparseIndex : SparseIndex ) : Promise < void > {
const indexPath = ` __sparse_index__ ${ field } `
const unifiedKey = ` metadata:sparse: ${ field } `
const data = sparseIndex . toJSON ( )
await this . storage . saveMetadata ( indexPath , data )
// Update unified cache
const size = JSON . stringify ( data ) . length
this . unifiedCache . set ( unifiedKey , sparseIndex , 'metadata' , size , 200 )
}
2026-05-15 12:31:28 -07:00
// flushDirtyMetadata — DELETED in 7.22.0. The dirtyChunks / dirtySparseIndices
// accumulators it drained were never populated after the 7.20.0 column-store
// refactor (commit 11be039). Column store flush happens in flush() directly.
2026-01-31 09:09:36 -08:00
2025-10-13 15:31:03 -07:00
/ * *
2026-05-15 12:31:28 -07:00
* Get IDs for a value using the legacy chunked sparse index .
*
* * * This path is only for pre - 7.20 . 0 workspaces * * still being migrated to
* the column store . The write path for sparse indices was removed in
* commit ` 11be039 ` — new workspaces never get them .
*
* If neither the column store nor a sparse index covers the field , the
* function throws ` BrainyError(FIELD_NOT_INDEXED) ` . Returning ` [] ` for a
2026-06-11 10:42:34 -07:00
* genuinely unindexed field was a long - standing silent - empty bug class —
* an empty result indistinguishable from "the data really isn't there."
2025-10-13 15:31:03 -07:00
* /
private async getIdsFromChunks ( field : string , value : any ) : Promise < string [ ] > {
2025-10-15 12:26:25 -07:00
// Load sparse index via UnifiedCache (lazy loading)
const sparseIndex = await this . loadSparseIndex ( field )
2025-10-13 15:31:03 -07:00
if ( ! sparseIndex ) {
2026-05-15 12:31:28 -07:00
// No column store match (we'd have returned in getIds()) AND no legacy
// sparse index for this field — the field is genuinely not indexed.
// Throw so find()-evaluation can log and translate to [].
throw BrainyError . fieldNotIndexed ( field )
2025-10-13 15:31:03 -07:00
}
// Find candidate chunks using zone maps and bloom filters
const normalizedValue = this . normalizeValue ( value , field )
const candidateChunkIds = sparseIndex . findChunksForValue ( normalizedValue )
if ( candidateChunkIds . length === 0 ) {
return [ ] // No chunks contain this value
}
2025-10-13 16:39:06 -07:00
// Load chunks and collect integer IDs from roaring bitmaps
const allIntIds = new Set < number > ( )
2025-10-13 15:31:03 -07:00
for ( const chunkId of candidateChunkIds ) {
const chunk = await this . chunkManager . loadChunk ( field , chunkId )
if ( chunk ) {
2025-10-13 16:39:06 -07:00
const bitmap = chunk . entries . get ( normalizedValue )
if ( bitmap ) {
// Iterate through roaring bitmap integers
for ( const intId of bitmap ) {
allIntIds . add ( intId )
}
2025-10-13 15:31:03 -07:00
}
}
}
2025-10-13 16:39:06 -07:00
// Convert integer IDs back to UUIDs
return this . idMapper . intsIterableToUuids ( allIntIds )
2025-10-13 15:31:03 -07:00
}
/ * *
2026-01-27 15:38:21 -08:00
* Get IDs for a range using chunked sparse index with zone maps and roaring bitmaps
* Now fully lazy - loaded via UnifiedCache ( no local sparseIndices Map )
* Normalize min / max for timestamp bucketing before comparison
2025-10-13 15:31:03 -07:00
* /
private async getIdsFromChunksForRange (
field : string ,
min? : any ,
max? : any ,
includeMin : boolean = true ,
includeMax : boolean = true
) : Promise < string [ ] > {
2025-10-15 12:26:25 -07:00
// Load sparse index via UnifiedCache (lazy loading)
const sparseIndex = await this . loadSparseIndex ( field )
2025-10-13 15:31:03 -07:00
if ( ! sparseIndex ) {
2025-10-15 12:26:25 -07:00
return [ ] // No chunked index exists yet
2025-10-13 15:31:03 -07:00
}
2026-01-27 15:38:21 -08:00
// Normalize min/max for consistent comparison with indexed values
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
// (indexed values are bucketed for timestamps, so we must bucket the query bounds too)
const normalizedMin = min !== undefined ? this . normalizeValue ( min , field ) : undefined
const normalizedMax = max !== undefined ? this . normalizeValue ( max , field ) : undefined
2025-10-13 15:31:03 -07:00
// Find candidate chunks using zone maps
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
const candidateChunkIds = sparseIndex . findChunksForRange ( normalizedMin , normalizedMax )
2025-10-13 15:31:03 -07:00
if ( candidateChunkIds . length === 0 ) {
return [ ]
}
2025-10-13 16:39:06 -07:00
// Load chunks and filter by range, collecting integer IDs from roaring bitmaps
const allIntIds = new Set < number > ( )
2025-10-13 15:31:03 -07:00
for ( const chunkId of candidateChunkIds ) {
const chunk = await this . chunkManager . loadChunk ( field , chunkId )
if ( chunk ) {
2025-10-13 16:39:06 -07:00
for ( const [ value , bitmap ] of chunk . entries ) {
feat: enforce data/metadata separation, numeric range queries, improved docs
- Store data opaquely in add() and update() instead of spreading object
properties into top-level metadata. data is for semantic search (HNSW),
metadata is for structured where-filter queries (MetadataIndex).
- Fix numeric range queries in MetadataIndex — use numeric-aware comparison
instead of lexicographic string comparison for normalized values.
- Add data field to RelateParams and Relation types for relationship content.
- Add where.type → where.noun alias in metadata-only find() path.
- Rewrite README: focused ~350 lines from 791, quick start first, feature
showcase with mini-snippets, organized doc links, no version callouts.
- Add DATA_MODEL.md and QUERY_OPERATORS.md reference docs.
- Remove 10 outdated/redundant doc files consolidated into API reference.
- Improve JSDoc on Entity, Relation, AddParams, FindParams, and core methods.
- Fix tests asserting data properties appear in metadata (data model violation).
- Deprecate verb.source/target in favor of from/to (public) and sourceId/targetId (storage).
2026-02-09 12:06:59 -08:00
// Check if value is in range using numeric-aware comparison
// (normalizeValue converts numbers to strings, so we must compare numerically)
2025-10-13 15:31:03 -07:00
let inRange = true
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
if ( normalizedMin !== undefined ) {
feat: enforce data/metadata separation, numeric range queries, improved docs
- Store data opaquely in add() and update() instead of spreading object
properties into top-level metadata. data is for semantic search (HNSW),
metadata is for structured where-filter queries (MetadataIndex).
- Fix numeric range queries in MetadataIndex — use numeric-aware comparison
instead of lexicographic string comparison for normalized values.
- Add data field to RelateParams and Relation types for relationship content.
- Add where.type → where.noun alias in metadata-only find() path.
- Rewrite README: focused ~350 lines from 791, quick start first, feature
showcase with mini-snippets, organized doc links, no version callouts.
- Add DATA_MODEL.md and QUERY_OPERATORS.md reference docs.
- Remove 10 outdated/redundant doc files consolidated into API reference.
- Improve JSDoc on Entity, Relation, AddParams, FindParams, and core methods.
- Fix tests asserting data properties appear in metadata (data model violation).
- Deprecate verb.source/target in favor of from/to (public) and sourceId/targetId (storage).
2026-02-09 12:06:59 -08:00
const cmp = compareNormalizedValues ( value , normalizedMin )
inRange = inRange && ( includeMin ? cmp >= 0 : cmp > 0 )
2025-10-13 15:31:03 -07:00
}
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
if ( normalizedMax !== undefined ) {
feat: enforce data/metadata separation, numeric range queries, improved docs
- Store data opaquely in add() and update() instead of spreading object
properties into top-level metadata. data is for semantic search (HNSW),
metadata is for structured where-filter queries (MetadataIndex).
- Fix numeric range queries in MetadataIndex — use numeric-aware comparison
instead of lexicographic string comparison for normalized values.
- Add data field to RelateParams and Relation types for relationship content.
- Add where.type → where.noun alias in metadata-only find() path.
- Rewrite README: focused ~350 lines from 791, quick start first, feature
showcase with mini-snippets, organized doc links, no version callouts.
- Add DATA_MODEL.md and QUERY_OPERATORS.md reference docs.
- Remove 10 outdated/redundant doc files consolidated into API reference.
- Improve JSDoc on Entity, Relation, AddParams, FindParams, and core methods.
- Fix tests asserting data properties appear in metadata (data model violation).
- Deprecate verb.source/target in favor of from/to (public) and sourceId/targetId (storage).
2026-02-09 12:06:59 -08:00
const cmp = compareNormalizedValues ( value , normalizedMax )
inRange = inRange && ( includeMax ? cmp <= 0 : cmp < 0 )
2025-10-13 15:31:03 -07:00
}
if ( inRange ) {
2025-10-13 16:39:06 -07:00
// Iterate through roaring bitmap integers
for ( const intId of bitmap ) {
allIntIds . add ( intId )
}
2025-10-13 15:31:03 -07:00
}
}
}
}
2025-10-13 16:39:06 -07:00
// Convert integer IDs back to UUIDs
return this . idMapper . intsIterableToUuids ( allIntIds )
}
/ * *
2026-01-27 15:38:21 -08:00
* Get roaring bitmap for a field - value pair without converting to UUIDs
2025-10-13 16:39:06 -07:00
* This is used for fast multi - field intersection queries using hardware - accelerated bitmap AND
2026-01-27 15:38:21 -08:00
* Now fully lazy - loaded via UnifiedCache ( no local sparseIndices Map )
2025-10-13 16:39:06 -07:00
* @returns RoaringBitmap32 containing integer IDs , or null if no matches
* /
private async getBitmapFromChunks ( field : string , value : any ) : Promise < RoaringBitmap32 | null > {
2025-10-15 12:26:25 -07:00
// Load sparse index via UnifiedCache (lazy loading)
const sparseIndex = await this . loadSparseIndex ( field )
2025-10-13 16:39:06 -07:00
if ( ! sparseIndex ) {
2025-10-15 12:26:25 -07:00
return null // No chunked index exists yet
2025-10-13 16:39:06 -07:00
}
// Find candidate chunks using zone maps and bloom filters
const normalizedValue = this . normalizeValue ( value , field )
const candidateChunkIds = sparseIndex . findChunksForValue ( normalizedValue )
if ( candidateChunkIds . length === 0 ) {
return null // No chunks contain this value
}
// If only one chunk, return its bitmap directly
if ( candidateChunkIds . length === 1 ) {
const chunk = await this . chunkManager . loadChunk ( field , candidateChunkIds [ 0 ] )
if ( chunk ) {
const bitmap = chunk . entries . get ( normalizedValue )
return bitmap || null
}
return null
}
// Multiple chunks: collect all bitmaps and combine with OR
const bitmaps : RoaringBitmap32 [ ] = [ ]
for ( const chunkId of candidateChunkIds ) {
const chunk = await this . chunkManager . loadChunk ( field , chunkId )
if ( chunk ) {
const bitmap = chunk . entries . get ( normalizedValue )
if ( bitmap && bitmap . size > 0 ) {
bitmaps . push ( bitmap )
}
}
}
if ( bitmaps . length === 0 ) {
return null
}
if ( bitmaps . length === 1 ) {
return bitmaps [ 0 ]
}
// Combine multiple bitmaps with OR operation
2025-10-13 16:42:45 -07:00
return RoaringBitmap32 . orMany ( bitmaps )
2025-10-13 16:39:06 -07:00
}
/ * *
2026-01-27 15:38:21 -08:00
* Get IDs for multiple field - value pairs using fast roaring bitmap intersection
2025-10-13 16:39:06 -07:00
*
* This method provides 500 - 900 x faster multi - field queries by :
* - Using hardware - accelerated bitmap AND operations ( SIMD : AVX2 / SSE4 . 2 )
* - Avoiding intermediate UUID array allocations
* - Converting integers to UUIDs only once at the end
*
* Example : { status : 'active' , role : 'admin' , verified : true }
* Instead of : fetch 3 UUID arrays → convert to Sets → filter intersection
* We do : fetch 3 bitmaps → hardware AND → convert final bitmap to UUIDs
*
* @param fieldValuePairs Array of field - value pairs to intersect
* @returns Array of UUID strings matching ALL criteria
* /
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
/ * *
* Multi - field intersection query : find entities matching ALL field - value pairs .
*
* Collects roaring bitmaps for each pair via the column store , then
* intersects them using hardware - accelerated AND operations .
*
* @param fieldValuePairs - Array of { field , value } to intersect
* @returns Array of entity UUID strings matching ALL pairs
* /
2025-10-13 16:39:06 -07:00
async getIdsForMultipleFields ( fieldValuePairs : Array < { field : string ; value : any } > ) : Promise < string [ ] > {
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
if ( fieldValuePairs . length === 0 ) return [ ]
2025-10-13 16:39:06 -07:00
if ( fieldValuePairs . length === 1 ) {
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
return await this . getIds ( fieldValuePairs [ 0 ] . field , fieldValuePairs [ 0 ] . value )
2025-10-13 16:39:06 -07:00
}
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// Collect roaring bitmaps for each field-value pair via column store
2025-10-13 16:39:06 -07:00
const bitmaps : RoaringBitmap32 [ ] = [ ]
for ( const { field , value } of fieldValuePairs ) {
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
const bitmap = this . columnStore . hasField ( field )
? await this . columnStore . filter ( field , value )
: await this . getBitmapFromChunks ( field , value ) ? ? new RoaringBitmap32 ( )
if ( bitmap . size === 0 ) return [ ] // Short circuit: empty intersection
2025-10-13 16:39:06 -07:00
bitmaps . push ( bitmap )
}
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// Intersect all bitmaps (SIMD-accelerated roaring AND)
let result = bitmaps [ 0 ]
2025-10-13 16:42:45 -07:00
for ( let i = 1 ; i < bitmaps . length ; i ++ ) {
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
result = RoaringBitmap32 . and ( result , bitmaps [ i ] )
2025-10-13 16:39:06 -07:00
}
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
return result . size > 0 ? this . idMapper . intsIterableToUuids ( result ) : [ ]
2025-10-13 15:31:03 -07:00
}
2026-04-10 11:32:34 -07:00
// addToChunkedIndex — DELETED. Column store handles all writes.
2025-10-13 15:31:03 -07:00
2026-04-10 11:32:34 -07:00
// removeFromChunkedIndex — DELETED. Column store handles removes via global deleted bitmap.
2025-10-13 15:31:03 -07:00
2025-08-26 12:32:21 -07:00
/ * *
2025-10-13 15:31:03 -07:00
* Get IDs matching a range query using zone maps
2025-08-26 12:32:21 -07:00
* /
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
/ * *
* Range query : find all entity IDs where a field ' s value falls within a range .
*
* Routes through the column store for O ( log n ) binary search when available ,
* falls back to sparse index zone - map scan for fields not yet in the column store .
*
* @param field - Field name to query
* @param min - Lower bound ( undefined = no lower bound )
* @param max - Upper bound ( undefined = no upper bound )
* @param includeMin - Whether to include the lower bound ( default : true )
* @param includeMax - Whether to include the upper bound ( default : true )
* @returns Array of matching entity UUID strings
* /
2025-08-26 12:32:21 -07:00
private async getIdsForRange (
field : string ,
min? : any ,
max? : any ,
includeMin : boolean = true ,
includeMax : boolean = true
) : Promise < string [ ] > {
2025-09-12 12:45:32 -07:00
// Track range query for field statistics
if ( this . fieldStats . has ( field ) ) {
const stats = this . fieldStats . get ( field ) !
stats . rangeQueryCount ++
}
2025-10-13 15:31:03 -07:00
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// Column store path: O(log n) binary search on sorted column.
// Use raw values (no normalization) — column store stores exact values.
fix(8.0): column-store range queries honor exclusive bounds (lessThan/greaterThan)
getIdsForRange computed includeMin/includeMax correctly for every operator
(gt→false/true, lt→true/false, between→true/true) but DROPPED them when the
column store served the query — it called columnStore.rangeQuery(field,min,max)
with no flags, and the column-store path was inclusive-only. So whenever a field
lived in the column store, strict lessThan/greaterThan silently behaved as
lte/gte. The sparse-fallback path already forwarded the flags, so this was
column-store-only.
Thread includeMin/includeMax end to end:
- ColumnSegmentCursor: add textbook lowerBound/upperBound helpers and express
binarySearchRange in terms of them. Inclusive/inclusive is byte-identical to
the old impl (lowerBound(lo) == old binarySearchValue(lo).index; upperBound(hi)
== old "first position after hi"). Exclusive lower advances past ALL duplicates
of the boundary value; exclusive upper stops before them.
- ColumnStore.rangeQuery: accept the flags, apply them in the segment cursor AND
the tail-buffer linear scan (strict > / < when exclusive). A bound taken from a
segment's own min/max stays inclusive — it is a real stored value.
- VectorIndex/types interface + getIdsForRange call site updated.
Surfaced by brainy-complete dual-bound test (year/popularity exclusive both ends
→ ['Express','Vue.js']; React@95 and Angular@75 correctly excluded). Added 5
column-store unit tests: exclusive lower, exclusive upper, both, duplicate
boundary values, and the unflushed tail-buffer path. 1469 unit green.
2026-06-19 11:01:41 -07:00
// Thread includeMin/includeMax so strict lessThan/greaterThan stay strict
// (the column store is no longer inclusive-only).
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
if ( this . columnStore && this . columnStore . hasField ( field ) ) {
fix(8.0): column-store range queries honor exclusive bounds (lessThan/greaterThan)
getIdsForRange computed includeMin/includeMax correctly for every operator
(gt→false/true, lt→true/false, between→true/true) but DROPPED them when the
column store served the query — it called columnStore.rangeQuery(field,min,max)
with no flags, and the column-store path was inclusive-only. So whenever a field
lived in the column store, strict lessThan/greaterThan silently behaved as
lte/gte. The sparse-fallback path already forwarded the flags, so this was
column-store-only.
Thread includeMin/includeMax end to end:
- ColumnSegmentCursor: add textbook lowerBound/upperBound helpers and express
binarySearchRange in terms of them. Inclusive/inclusive is byte-identical to
the old impl (lowerBound(lo) == old binarySearchValue(lo).index; upperBound(hi)
== old "first position after hi"). Exclusive lower advances past ALL duplicates
of the boundary value; exclusive upper stops before them.
- ColumnStore.rangeQuery: accept the flags, apply them in the segment cursor AND
the tail-buffer linear scan (strict > / < when exclusive). A bound taken from a
segment's own min/max stays inclusive — it is a real stored value.
- VectorIndex/types interface + getIdsForRange call site updated.
Surfaced by brainy-complete dual-bound test (year/popularity exclusive both ends
→ ['Express','Vue.js']; React@95 and Angular@75 correctly excluded). Added 5
column-store unit tests: exclusive lower, exclusive upper, both, duplicate
boundary values, and the unflushed tail-buffer path. 1469 unit green.
2026-06-19 11:01:41 -07:00
const bitmap = await this . columnStore . rangeQuery ( field , min , max , includeMin , includeMax )
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
return this . idMapper . intsIterableToUuids ( bitmap )
}
// Fallback: sparse index zone-map scan (legacy path)
2025-10-13 15:31:03 -07:00
return await this . getIdsFromChunksForRange ( field , min , max , includeMin , includeMax )
2025-08-26 12:32:21 -07:00
}
/ * *
* Generate field index filename for filter discovery
* /
private getFieldIndexFilename ( field : string ) : string {
return ` field_ ${ field } `
}
2026-04-10 11:32:34 -07:00
// getValueChunkFilename, makeSafeFilename — DELETED. Sparse index file naming no longer needed.
2025-08-26 12:32:21 -07:00
/ * *
feat: production-ready value-based temporal field detection
Replaces unreliable field name pattern matching with DuckDB-inspired value analysis.
### Critical Bug Fix
- Fixes 618k file explosion from false positive temporal field detection
- Field name patterns like `.endsWith('at')` incorrectly flagged non-temporal fields
- Example: "cat", "bat", "hat" were treated as timestamps, creating millions of files
### New System: FieldTypeInference
- Analyzes actual data VALUES, not field names
- Unix timestamp detection: checks if numbers fall in 2000-2100 range
- ISO 8601 datetime detection: pattern matching for date strings
- 11 field types: TIMESTAMP_MS, TIMESTAMP_S, DATE_ISO8601, DATETIME_ISO8601, BOOLEAN, INTEGER, FLOAT, UUID, ARRAY, OBJECT, STRING
- Persistent caching for O(1) lookups at billion scale
- 95%+ accuracy vs 70% with pattern matching
### Architecture
- Zero configuration required
- No fallbacks - pure value-based detection only
- Progressive refinement as more data arrives
- Production patterns from DuckDB, Apache Arrow, Parquet
### Tests
- 39 comprehensive unit tests (all passing)
- Real-world scenarios including exact bug reproduction
- Full coverage: all types, cache, edge cases
### Performance
- Cache hit: 0.1-0.5ms (O(1))
- Cache miss: 5-10ms (analyze 100 samples)
- Memory: ~500 bytes per field
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 13:58:57 -07:00
* Normalize value for consistent indexing with VALUE - BASED temporal detection
*
2026-01-27 15:38:21 -08:00
* Replaced unreliable field name pattern matching with production - ready
feat: production-ready value-based temporal field detection
Replaces unreliable field name pattern matching with DuckDB-inspired value analysis.
### Critical Bug Fix
- Fixes 618k file explosion from false positive temporal field detection
- Field name patterns like `.endsWith('at')` incorrectly flagged non-temporal fields
- Example: "cat", "bat", "hat" were treated as timestamps, creating millions of files
### New System: FieldTypeInference
- Analyzes actual data VALUES, not field names
- Unix timestamp detection: checks if numbers fall in 2000-2100 range
- ISO 8601 datetime detection: pattern matching for date strings
- 11 field types: TIMESTAMP_MS, TIMESTAMP_S, DATE_ISO8601, DATETIME_ISO8601, BOOLEAN, INTEGER, FLOAT, UUID, ARRAY, OBJECT, STRING
- Persistent caching for O(1) lookups at billion scale
- 95%+ accuracy vs 70% with pattern matching
### Architecture
- Zero configuration required
- No fallbacks - pure value-based detection only
- Progressive refinement as more data arrives
- Production patterns from DuckDB, Apache Arrow, Parquet
### Tests
- 39 comprehensive unit tests (all passing)
- Real-world scenarios including exact bug reproduction
- Full coverage: all types, cache, edge cases
### Performance
- Cache hit: 0.1-0.5ms (O(1))
- Cache miss: 5-10ms (analyze 100 samples)
- Memory: ~500 bytes per field
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 13:58:57 -07:00
* value - based detection ( DuckDB - inspired ) . Analyzes actual data values , not names .
*
* NO FALLBACKS - Pure value - based detection only .
2025-08-26 12:32:21 -07:00
* /
2025-09-12 12:45:32 -07:00
private normalizeValue ( value : any , field? : string ) : string {
2025-08-26 12:32:21 -07:00
if ( value === null || value === undefined ) return '__NULL__'
if ( typeof value === 'boolean' ) return value ? '__TRUE__' : '__FALSE__'
2025-10-13 13:16:07 -07:00
feat: production-ready value-based temporal field detection
Replaces unreliable field name pattern matching with DuckDB-inspired value analysis.
### Critical Bug Fix
- Fixes 618k file explosion from false positive temporal field detection
- Field name patterns like `.endsWith('at')` incorrectly flagged non-temporal fields
- Example: "cat", "bat", "hat" were treated as timestamps, creating millions of files
### New System: FieldTypeInference
- Analyzes actual data VALUES, not field names
- Unix timestamp detection: checks if numbers fall in 2000-2100 range
- ISO 8601 datetime detection: pattern matching for date strings
- 11 field types: TIMESTAMP_MS, TIMESTAMP_S, DATE_ISO8601, DATETIME_ISO8601, BOOLEAN, INTEGER, FLOAT, UUID, ARRAY, OBJECT, STRING
- Persistent caching for O(1) lookups at billion scale
- 95%+ accuracy vs 70% with pattern matching
### Architecture
- Zero configuration required
- No fallbacks - pure value-based detection only
- Progressive refinement as more data arrives
- Production patterns from DuckDB, Apache Arrow, Parquet
### Tests
- 39 comprehensive unit tests (all passing)
- Real-world scenarios including exact bug reproduction
- Full coverage: all types, cache, edge cases
### Performance
- Cache hit: 0.1-0.5ms (O(1))
- Cache miss: 5-10ms (analyze 100 samples)
- Memory: ~500 bytes per field
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 13:58:57 -07:00
// VALUE-BASED temporal detection (no pattern matching!)
// Analyze the VALUE itself to determine if it's a timestamp
if ( typeof value === 'number' ) {
// Check if value looks like a Unix timestamp (2000-01-01 to 2100-01-01)
const MIN_TIMESTAMP_S = 946684800 // 2000-01-01 in seconds
const MAX_TIMESTAMP_S = 4102444800 // 2100-01-01 in seconds
const MIN_TIMESTAMP_MS = MIN_TIMESTAMP_S * 1000
const MAX_TIMESTAMP_MS = MAX_TIMESTAMP_S * 1000
const isTimestampSeconds = value >= MIN_TIMESTAMP_S && value <= MAX_TIMESTAMP_S
const isTimestampMilliseconds = value >= MIN_TIMESTAMP_MS && value <= MAX_TIMESTAMP_MS
if ( isTimestampSeconds || isTimestampMilliseconds ) {
// VALUE is a timestamp! Apply 1-minute bucketing
const bucketSize = this . TIMESTAMP_PRECISION_MS // 60000ms = 1 minute
2025-10-13 13:16:07 -07:00
const bucketed = Math . floor ( value / bucketSize ) * bucketSize
return bucketed . toString ( )
}
}
feat: production-ready value-based temporal field detection
Replaces unreliable field name pattern matching with DuckDB-inspired value analysis.
### Critical Bug Fix
- Fixes 618k file explosion from false positive temporal field detection
- Field name patterns like `.endsWith('at')` incorrectly flagged non-temporal fields
- Example: "cat", "bat", "hat" were treated as timestamps, creating millions of files
### New System: FieldTypeInference
- Analyzes actual data VALUES, not field names
- Unix timestamp detection: checks if numbers fall in 2000-2100 range
- ISO 8601 datetime detection: pattern matching for date strings
- 11 field types: TIMESTAMP_MS, TIMESTAMP_S, DATE_ISO8601, DATETIME_ISO8601, BOOLEAN, INTEGER, FLOAT, UUID, ARRAY, OBJECT, STRING
- Persistent caching for O(1) lookups at billion scale
- 95%+ accuracy vs 70% with pattern matching
### Architecture
- Zero configuration required
- No fallbacks - pure value-based detection only
- Progressive refinement as more data arrives
- Production patterns from DuckDB, Apache Arrow, Parquet
### Tests
- 39 comprehensive unit tests (all passing)
- Real-world scenarios including exact bug reproduction
- Full coverage: all types, cache, edge cases
### Performance
- Cache hit: 0.1-0.5ms (O(1))
- Cache miss: 5-10ms (analyze 100 samples)
- Memory: ~500 bytes per field
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 13:58:57 -07:00
// Check if string value is ISO 8601 datetime
if ( typeof value === 'string' ) {
// ISO 8601 pattern: YYYY-MM-DDTHH:MM:SS...
const iso8601Pattern = /^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}/
if ( iso8601Pattern . test ( value ) ) {
// VALUE is an ISO 8601 datetime! Convert to timestamp and bucket
try {
const timestamp = new Date ( value ) . getTime ( )
if ( ! isNaN ( timestamp ) ) {
const bucketSize = this . TIMESTAMP_PRECISION_MS
const bucketed = Math . floor ( timestamp / bucketSize ) * bucketSize
return bucketed . toString ( )
}
} catch {
// Not a valid date, treat as string
}
}
}
2025-10-13 13:16:07 -07:00
// Apply smart normalization based on field statistics (for non-temporal fields)
2025-09-12 12:45:32 -07:00
if ( field && this . fieldStats . has ( field ) ) {
const stats = this . fieldStats . get ( field ) !
const strategy = stats . normalizationStrategy
2025-10-13 13:16:07 -07:00
if ( strategy === 'precision' && typeof value === 'number' ) {
2025-09-12 12:45:32 -07:00
// Reduce float precision for high cardinality numeric fields
const rounded = Math . round ( value * Math . pow ( 10 , this . FLOAT_PRECISION ) ) / Math . pow ( 10 , this . FLOAT_PRECISION )
return rounded . toString ( )
}
}
2025-10-13 13:16:07 -07:00
2025-09-12 12:45:32 -07:00
// Default normalization
2025-08-26 12:32:21 -07:00
if ( typeof value === 'number' ) return value . toString ( )
if ( Array . isArray ( value ) ) {
2025-09-12 12:45:32 -07:00
const joined = value . map ( v = > this . normalizeValue ( v , field ) ) . join ( ',' )
2025-08-26 12:32:21 -07:00
// Hash very long array values to avoid filesystem limits
if ( joined . length > 100 ) {
return this . hashValue ( joined )
}
return joined
}
const stringValue = String ( value ) . toLowerCase ( ) . trim ( )
// Hash very long string values to avoid filesystem limits
if ( stringValue . length > 100 ) {
return this . hashValue ( stringValue )
}
return stringValue
}
/ * *
* Create a short hash for long values to avoid filesystem filename limits
* /
private hashValue ( value : string ) : string {
// Simple hash function to create shorter keys
let hash = 0
for ( let i = 0 ; i < value . length ; i ++ ) {
const char = value . charCodeAt ( i )
hash = ( ( hash << 5 ) - hash ) + char
hash = hash & hash // Convert to 32-bit integer
}
return ` __HASH_ ${ Math . abs ( hash ) . toString ( 36 ) } `
}
/ * *
fix(storage): v4.8.0 metadata architecture refactoring - FIXES VFS bug
CRITICAL FIX: VFS bug that persisted through v4.5.1-v4.7.4 is NOW FIXED.
Root Cause:
- Storage adapters were not properly extracting standard fields from metadata
- This caused getVerbsBySource_internal() to return 0 relationships despite relationships existing
- VFS PathResolver couldn't navigate directory structure
Solution - Metadata Architecture Refactoring:
1. Move standard fields to top-level of HNSWNounWithMetadata and HNSWVerbWithMetadata
- type, createdAt, updatedAt, confidence, weight, service, data, createdBy
2. Update all 9 storage adapters to extract standard fields from metadata on load
3. Maintain backward compatibility at storage layer (metadata files unchanged)
Changes:
- src/coreTypes.ts: Update HNSWNounWithMetadata and HNSWVerbWithMetadata interfaces
- Add top-level standard fields
- Change data type from unknown to Record<string, any>
- Add confidence field to GraphVerb
- src/storage/baseStorage.ts: Add type cast pattern for standard field extraction
- src/storage/adapters/*.ts: Fix all 9 adapters (memoryStorage, fileSystemStorage, gcsStorage,
s3CompatibleStorage, r2Storage, opfsStorage, azureBlobStorage, typeAwareStorageAdapter)
- Extract standard fields from metadata on load
- Place at top-level of returned entities
- src/api/DataAPI.ts: Read fields from top-level instead of metadata
- src/graph/graphAdjacencyIndex.ts: Convert HNSWVerbWithMetadata to GraphVerb format
- src/utils/metadataIndex.ts: Fix typo (metadata → entityOrMetadata)
- src/types/brainy.types.ts: Add createdBy field to AddParams
- src/types/graphTypes.ts: Add service field to GraphVerb
Test Results:
✅ VFS bug FIXED - vfs.readdir('/') now returns files (was returning empty array)
✅ getVerbsBySource_internal() now returns relationships correctly
✅ Build succeeds with ZERO compilation errors
✅ 95.7% of tests pass (954/997)
Breaking Changes:
- None - backward compatibility maintained at storage layer
Version: 4.8.0
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-27 15:43:49 -07:00
* Extract indexable field - value pairs from entity or metadata
*
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
* Handles BOTH entity structure ( with top - level fields ) AND record shapes
* - Record - frame system scalars index under literal 'system.<field>' keys
* - The user ' s metadata bag indexes under bare keys — EVERY name ( the
* field - addressing law : no special names ; 'level' , 'data' , 'id' ,
* 'content' , 'vector' in a bag are ordinary user fields )
* - Record - frame plumbing ( vector , connections , level , data , _rev , id )
* never indexes — that is namespace routing , not a name carve - out
* - Value - SHAPE rules apply uniformly to all names : arrays > 10 never
* become posting scalars ; purely numeric key names ( array indices )
* skip ; > 100 - char values index hashed ( normalizeValue )
2025-08-26 12:32:21 -07:00
* /
fix(storage): v4.8.0 metadata architecture refactoring - FIXES VFS bug
CRITICAL FIX: VFS bug that persisted through v4.5.1-v4.7.4 is NOW FIXED.
Root Cause:
- Storage adapters were not properly extracting standard fields from metadata
- This caused getVerbsBySource_internal() to return 0 relationships despite relationships existing
- VFS PathResolver couldn't navigate directory structure
Solution - Metadata Architecture Refactoring:
1. Move standard fields to top-level of HNSWNounWithMetadata and HNSWVerbWithMetadata
- type, createdAt, updatedAt, confidence, weight, service, data, createdBy
2. Update all 9 storage adapters to extract standard fields from metadata on load
3. Maintain backward compatibility at storage layer (metadata files unchanged)
Changes:
- src/coreTypes.ts: Update HNSWNounWithMetadata and HNSWVerbWithMetadata interfaces
- Add top-level standard fields
- Change data type from unknown to Record<string, any>
- Add confidence field to GraphVerb
- src/storage/baseStorage.ts: Add type cast pattern for standard field extraction
- src/storage/adapters/*.ts: Fix all 9 adapters (memoryStorage, fileSystemStorage, gcsStorage,
s3CompatibleStorage, r2Storage, opfsStorage, azureBlobStorage, typeAwareStorageAdapter)
- Extract standard fields from metadata on load
- Place at top-level of returned entities
- src/api/DataAPI.ts: Read fields from top-level instead of metadata
- src/graph/graphAdjacencyIndex.ts: Convert HNSWVerbWithMetadata to GraphVerb format
- src/utils/metadataIndex.ts: Fix typo (metadata → entityOrMetadata)
- src/types/brainy.types.ts: Add createdBy field to AddParams
- src/types/graphTypes.ts: Add service field to GraphVerb
Test Results:
✅ VFS bug FIXED - vfs.readdir('/') now returns files (was returning empty array)
✅ getVerbsBySource_internal() now returns relationships correctly
✅ Build succeeds with ZERO compilation errors
✅ 95.7% of tests pass (954/997)
Breaking Changes:
- None - backward compatibility maintained at storage layer
Version: 4.8.0
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-27 15:43:49 -07:00
private extractIndexableFields ( data : any ) : Array < { field : string , value : any } > {
2025-08-26 12:32:21 -07:00
const fields : Array < { field : string , value : any } > = [ ]
fix: metadata explosion bug - 69K files reduced to ~1K
Critical fix for metadata indexing that was creating 60+ chunk files per entity.
Root cause: Vector embeddings (384-dimensional arrays) were being indexed in
metadata, causing each dimension to create a separate chunk file with numeric
field names ("0", "1", "2", etc.).
Changes:
- Modified extractIndexableFields() to exclude vector/embedding fields
- Added NEVER_INDEX set: ['vector', 'embedding', 'embeddings', 'connections']
- Added safety check to skip arrays > 10 elements
- Preserves small array indexing (tags, categories, roles)
Impact:
- Reduces metadata files from 69,429 → ~1,200 (58x reduction)
- Fixes server initialization hangs
- Fixes metadata batch loading stalling at batch 23
- Fixes VFS getDescendants() hanging with large datasets
- Fixes Graph View UI not loading
Test Results:
- 7/7 integration tests passing
- Verified: 6 chunk files for 10 entities (was 7,210 before fix)
- 611/622 unit tests passing
Files Modified:
- src/utils/metadataIndex.ts - Core fix
- src/coreTypes.ts - HNSWVerb type enforcement with VerbType enum
- src/storage/adapters/* - Include core relational fields in HNSWVerb
- src/storage/adapters/baseStorageAdapter.ts - Type enforcement (HNSWNoun, GraphVerb)
- tests/integration/metadata-vector-exclusion.test.ts - Comprehensive test coverage
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 16:10:31 -07:00
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
// RECORD-FRAME-ONLY plumbing guard: on an entity/stored-record frame
// these keys are the engine's structural payloads (the 384-dim vector,
// embeddings, the adjacency list, the identity field) and never index.
// This set is NEVER applied inside the user's metadata bag — under the
// field-addressing law every user name indexes; a real vector-sized
// value in a bag is kept out by the uniform array-size shape guard, not
// by its name.
const RECORD_PLUMBING = new Set ( [ 'vector' , 'embedding' , 'embeddings' , 'connections' , 'id' ] )
fix: metadata explosion bug - 69K files reduced to ~1K
Critical fix for metadata indexing that was creating 60+ chunk files per entity.
Root cause: Vector embeddings (384-dimensional arrays) were being indexed in
metadata, causing each dimension to create a separate chunk file with numeric
field names ("0", "1", "2", etc.).
Changes:
- Modified extractIndexableFields() to exclude vector/embedding fields
- Added NEVER_INDEX set: ['vector', 'embedding', 'embeddings', 'connections']
- Added safety check to skip arrays > 10 elements
- Preserves small array indexing (tags, categories, roles)
Impact:
- Reduces metadata files from 69,429 → ~1,200 (58x reduction)
- Fixes server initialization hangs
- Fixes metadata batch loading stalling at batch 23
- Fixes VFS getDescendants() hanging with large datasets
- Fixes Graph View UI not loading
Test Results:
- 7/7 integration tests passing
- Verified: 6 chunk files for 10 entities (was 7,210 before fix)
- 611/622 unit tests passing
Files Modified:
- src/utils/metadataIndex.ts - Core fix
- src/coreTypes.ts - HNSWVerb type enforcement with VerbType enum
- src/storage/adapters/* - Include core relational fields in HNSWVerb
- src/storage/adapters/baseStorageAdapter.ts - Type enforcement (HNSWNoun, GraphVerb)
- tests/integration/metadata-vector-exclusion.test.ts - Comprehensive test coverage
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 16:10:31 -07:00
2026-08-03 15:28:24 -07:00
// THE FROZEN INDEX KEY FORMAT (cross-engine, sealed 2026-08-03; the native
// accelerator keys identically — epoch 3 rebuilds every brain onto it):
// user fields index under BARE keys exactly as the caller wrote them;
// the ten system scalars index under literal 'system.<field>' keys — the
// key IS the query address, so the two namespaces can never collide
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
// inside the index again.
// Frame kinds: 'entity-record' = entityForIndexing shape / v2 nested-bag
// stored record (user fields nested under `metadata`; stray top-level
// keys are DROPPED, not guessed); 'flat-record' = the LEGACY stored
// metadata-record shape (user fields flat beside the engine's — sound to
// split by name because the pre-law write door refused user metadata
// carrying engine names, so a flat key matching a system name IS the
// system value); 'user' = inside the metadata bag, where EVERY key is
// the user's and indexes bare — collider names included.
2026-08-03 15:28:24 -07:00
type Frame = 'entity-record' | 'flat-record' | 'user'
const extract = ( obj : any , prefix = '' , frame : Frame = 'entity-record' ) : void = > {
2025-08-26 12:32:21 -07:00
for ( const [ key , value ] of Object . entries ( obj ) ) {
2026-08-03 15:28:24 -07:00
let fullKey = prefix ? ` ${ prefix } . ${ key } ` : key
fix: metadata explosion bug - 69K files reduced to ~1K
Critical fix for metadata indexing that was creating 60+ chunk files per entity.
Root cause: Vector embeddings (384-dimensional arrays) were being indexed in
metadata, causing each dimension to create a separate chunk file with numeric
field names ("0", "1", "2", etc.).
Changes:
- Modified extractIndexableFields() to exclude vector/embedding fields
- Added NEVER_INDEX set: ['vector', 'embedding', 'embeddings', 'connections']
- Added safety check to skip arrays > 10 elements
- Preserves small array indexing (tags, categories, roles)
Impact:
- Reduces metadata files from 69,429 → ~1,200 (58x reduction)
- Fixes server initialization hangs
- Fixes metadata batch loading stalling at batch 23
- Fixes VFS getDescendants() hanging with large datasets
- Fixes Graph View UI not loading
Test Results:
- 7/7 integration tests passing
- Verified: 6 chunk files for 10 entities (was 7,210 before fix)
- 611/622 unit tests passing
Files Modified:
- src/utils/metadataIndex.ts - Core fix
- src/coreTypes.ts - HNSWVerb type enforcement with VerbType enum
- src/storage/adapters/* - Include core relational fields in HNSWVerb
- src/storage/adapters/baseStorageAdapter.ts - Type enforcement (HNSWNoun, GraphVerb)
- tests/integration/metadata-vector-exclusion.test.ts - Comprehensive test coverage
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 16:10:31 -07:00
2026-08-03 15:28:24 -07:00
if ( ! prefix && frame !== 'user' ) {
if ( key === 'metadata' && typeof value === 'object' && value !== null && ! Array . isArray ( value ) ) {
extract ( value , '' , 'user' ) // the user's namespace: bare keys
continue
}
if ( key === 'type' || key === 'noun' ) {
fullKey = 'system.type' // legacy 'noun' spelling folds into the frozen key
} else if ( SYSTEM_ENTITY_SCALARS . has ( key ) && key !== 'id' ) {
fullKey = ` system. ${ key } `
} else if (
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
key === 'data' || key === '_rev' || key === 'level' || key === '_fmt' ||
RECORD_PLUMBING . has ( key )
2026-08-03 15:28:24 -07:00
) {
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
continue // plumbing / identity / format stamp — never indexed from a record frame
2026-08-03 15:28:24 -07:00
} else if ( frame === 'entity-record' ) {
continue // stray entity-frame key: dropped, not guessed
}
// flat-record fallthrough: a non-system, non-plumbing key IS a user
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
// field (flat beside the engine's, legacy shape) — indexes bare.
2026-08-03 15:28:24 -07:00
}
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
// User frame: NO name-based skips — every user field indexes, whatever
// its name (the field-addressing law). Only the uniform value-shape
// guards below apply.
fix: v3.50.2 emergency hotfix - exclude numeric field names from metadata indexing
Critical fix for incomplete v3.50.1 release.
Problem: v3.50.1 prevented vector fields by name ('vector', 'embedding')
but missed vectors stored as objects with numeric keys: {0: 0.1, 1: 0.2, ...}
Studio team diagnostics showed:
- 212,531 chunk files with NUMERIC field names
- Examples: "field": "54716", "field": "100000", "field": "100001"
- 424,837 total files (expected ~1,200)
Root Cause: Vectors converted to objects with numeric keys were still
being indexed because field name check only caught semantic names.
Fix Applied (src/utils/metadataIndex.ts:1106):
- Added regex check: if (/^\d+$/.test(key)) continue
- Skips ANY purely numeric field name (array indices as object keys)
- Catches: "0", "1", "2", "100", "54716", "100000", etc.
Test Coverage:
- Added new test: "should NOT index objects with numeric keys (v3.50.2 fix)"
- Verifies NO chunk files have numeric field names
- All 8 integration tests passing
Impact:
- Prevents 212K+ chunk files from being created
- Reduces file count from 424K to ~1,200 (354x reduction)
- Fixes server hangs during initialization
- Completes the metadata explosion fix started in v3.50.1
2025-10-16 16:31:06 -07:00
// Skip purely numeric field names (array indices converted to object keys)
// Legitimate field names should never be purely numeric
// This catches vectors stored as objects: {0: 0.1, 1: 0.2, ...}
if ( /^\d+$/ . test ( key ) ) continue
fix: metadata explosion bug - 69K files reduced to ~1K
Critical fix for metadata indexing that was creating 60+ chunk files per entity.
Root cause: Vector embeddings (384-dimensional arrays) were being indexed in
metadata, causing each dimension to create a separate chunk file with numeric
field names ("0", "1", "2", etc.).
Changes:
- Modified extractIndexableFields() to exclude vector/embedding fields
- Added NEVER_INDEX set: ['vector', 'embedding', 'embeddings', 'connections']
- Added safety check to skip arrays > 10 elements
- Preserves small array indexing (tags, categories, roles)
Impact:
- Reduces metadata files from 69,429 → ~1,200 (58x reduction)
- Fixes server initialization hangs
- Fixes metadata batch loading stalling at batch 23
- Fixes VFS getDescendants() hanging with large datasets
- Fixes Graph View UI not loading
Test Results:
- 7/7 integration tests passing
- Verified: 6 chunk files for 10 entities (was 7,210 before fix)
- 611/622 unit tests passing
Files Modified:
- src/utils/metadataIndex.ts - Core fix
- src/coreTypes.ts - HNSWVerb type enforcement with VerbType enum
- src/storage/adapters/* - Include core relational fields in HNSWVerb
- src/storage/adapters/baseStorageAdapter.ts - Type enforcement (HNSWNoun, GraphVerb)
- tests/integration/metadata-vector-exclusion.test.ts - Comprehensive test coverage
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 16:10:31 -07:00
// Skip large arrays (> 10 elements) - likely vectors or bulk data
if ( Array . isArray ( value ) && value . length > 10 ) continue
2025-08-26 12:32:21 -07:00
if ( value && typeof value === 'object' && ! Array . isArray ( value ) ) {
2026-08-03 15:28:24 -07:00
// Recurse into nested objects (but not arrays), keeping the frame
extract ( value , fullKey , frame )
fix: metadata explosion bug - 69K files reduced to ~1K
Critical fix for metadata indexing that was creating 60+ chunk files per entity.
Root cause: Vector embeddings (384-dimensional arrays) were being indexed in
metadata, causing each dimension to create a separate chunk file with numeric
field names ("0", "1", "2", etc.).
Changes:
- Modified extractIndexableFields() to exclude vector/embedding fields
- Added NEVER_INDEX set: ['vector', 'embedding', 'embeddings', 'connections']
- Added safety check to skip arrays > 10 elements
- Preserves small array indexing (tags, categories, roles)
Impact:
- Reduces metadata files from 69,429 → ~1,200 (58x reduction)
- Fixes server initialization hangs
- Fixes metadata batch loading stalling at batch 23
- Fixes VFS getDescendants() hanging with large datasets
- Fixes Graph View UI not loading
Test Results:
- 7/7 integration tests passing
- Verified: 6 chunk files for 10 entities (was 7,210 before fix)
- 611/622 unit tests passing
Files Modified:
- src/utils/metadataIndex.ts - Core fix
- src/coreTypes.ts - HNSWVerb type enforcement with VerbType enum
- src/storage/adapters/* - Include core relational fields in HNSWVerb
- src/storage/adapters/baseStorageAdapter.ts - Type enforcement (HNSWNoun, GraphVerb)
- tests/integration/metadata-vector-exclusion.test.ts - Comprehensive test coverage
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 16:10:31 -07:00
} else if ( Array . isArray ( value ) && value . length <= 10 ) {
// Small arrays: index as multi-value field (all with same field name)
// Example: tags: ["javascript", "node"] → field="tags", value="javascript" + field="tags", value="node"
for ( const item of value ) {
// Only index primitive values (not nested objects/arrays)
if ( item !== null && typeof item !== 'object' ) {
2025-08-26 12:32:21 -07:00
fields . push ( { field : fullKey , value : item } )
}
}
fix: metadata explosion bug - 69K files reduced to ~1K
Critical fix for metadata indexing that was creating 60+ chunk files per entity.
Root cause: Vector embeddings (384-dimensional arrays) were being indexed in
metadata, causing each dimension to create a separate chunk file with numeric
field names ("0", "1", "2", etc.).
Changes:
- Modified extractIndexableFields() to exclude vector/embedding fields
- Added NEVER_INDEX set: ['vector', 'embedding', 'embeddings', 'connections']
- Added safety check to skip arrays > 10 elements
- Preserves small array indexing (tags, categories, roles)
Impact:
- Reduces metadata files from 69,429 → ~1,200 (58x reduction)
- Fixes server initialization hangs
- Fixes metadata batch loading stalling at batch 23
- Fixes VFS getDescendants() hanging with large datasets
- Fixes Graph View UI not loading
Test Results:
- 7/7 integration tests passing
- Verified: 6 chunk files for 10 entities (was 7,210 before fix)
- 611/622 unit tests passing
Files Modified:
- src/utils/metadataIndex.ts - Core fix
- src/coreTypes.ts - HNSWVerb type enforcement with VerbType enum
- src/storage/adapters/* - Include core relational fields in HNSWVerb
- src/storage/adapters/baseStorageAdapter.ts - Type enforcement (HNSWNoun, GraphVerb)
- tests/integration/metadata-vector-exclusion.test.ts - Comprehensive test coverage
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 16:10:31 -07:00
} else {
2026-08-03 15:28:24 -07:00
// Primitive value: index it under the frozen key computed above.
// (The legacy 'type'→'noun' remap is gone — 'noun' columns die at
// the epoch-3 rebuild; system.type is the one spelling.)
fields . push ( { field : fullKey , value } )
2025-08-26 12:32:21 -07:00
}
}
}
fix: metadata explosion bug - 69K files reduced to ~1K
Critical fix for metadata indexing that was creating 60+ chunk files per entity.
Root cause: Vector embeddings (384-dimensional arrays) were being indexed in
metadata, causing each dimension to create a separate chunk file with numeric
field names ("0", "1", "2", etc.).
Changes:
- Modified extractIndexableFields() to exclude vector/embedding fields
- Added NEVER_INDEX set: ['vector', 'embedding', 'embeddings', 'connections']
- Added safety check to skip arrays > 10 elements
- Preserves small array indexing (tags, categories, roles)
Impact:
- Reduces metadata files from 69,429 → ~1,200 (58x reduction)
- Fixes server initialization hangs
- Fixes metadata batch loading stalling at batch 23
- Fixes VFS getDescendants() hanging with large datasets
- Fixes Graph View UI not loading
Test Results:
- 7/7 integration tests passing
- Verified: 6 chunk files for 10 entities (was 7,210 before fix)
- 611/622 unit tests passing
Files Modified:
- src/utils/metadataIndex.ts - Core fix
- src/coreTypes.ts - HNSWVerb type enforcement with VerbType enum
- src/storage/adapters/* - Include core relational fields in HNSWVerb
- src/storage/adapters/baseStorageAdapter.ts - Type enforcement (HNSWNoun, GraphVerb)
- tests/integration/metadata-vector-exclusion.test.ts - Comprehensive test coverage
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 16:10:31 -07:00
fix(storage): v4.8.0 metadata architecture refactoring - FIXES VFS bug
CRITICAL FIX: VFS bug that persisted through v4.5.1-v4.7.4 is NOW FIXED.
Root Cause:
- Storage adapters were not properly extracting standard fields from metadata
- This caused getVerbsBySource_internal() to return 0 relationships despite relationships existing
- VFS PathResolver couldn't navigate directory structure
Solution - Metadata Architecture Refactoring:
1. Move standard fields to top-level of HNSWNounWithMetadata and HNSWVerbWithMetadata
- type, createdAt, updatedAt, confidence, weight, service, data, createdBy
2. Update all 9 storage adapters to extract standard fields from metadata on load
3. Maintain backward compatibility at storage layer (metadata files unchanged)
Changes:
- src/coreTypes.ts: Update HNSWNounWithMetadata and HNSWVerbWithMetadata interfaces
- Add top-level standard fields
- Change data type from unknown to Record<string, any>
- Add confidence field to GraphVerb
- src/storage/baseStorage.ts: Add type cast pattern for standard field extraction
- src/storage/adapters/*.ts: Fix all 9 adapters (memoryStorage, fileSystemStorage, gcsStorage,
s3CompatibleStorage, r2Storage, opfsStorage, azureBlobStorage, typeAwareStorageAdapter)
- Extract standard fields from metadata on load
- Place at top-level of returned entities
- src/api/DataAPI.ts: Read fields from top-level instead of metadata
- src/graph/graphAdjacencyIndex.ts: Convert HNSWVerbWithMetadata to GraphVerb format
- src/utils/metadataIndex.ts: Fix typo (metadata → entityOrMetadata)
- src/types/brainy.types.ts: Add createdBy field to AddParams
- src/types/graphTypes.ts: Add service field to GraphVerb
Test Results:
✅ VFS bug FIXED - vfs.readdir('/') now returns files (was returning empty array)
✅ getVerbsBySource_internal() now returns relationships correctly
✅ Build succeeds with ZERO compilation errors
✅ 95.7% of tests pass (954/997)
Breaking Changes:
- None - backward compatibility maintained at storage layer
Version: 4.8.0
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-27 15:43:49 -07:00
if ( data && typeof data === 'object' ) {
2026-08-03 15:28:24 -07:00
// Shape detection for the top frame: an object carrying a nested
// `metadata` bag is the entityForIndexing shape; anything else is the
// flat stored-record shape (user fields flat beside reserved ones).
const entityShaped =
'metadata' in data && typeof data . metadata === 'object' && data . metadata !== null
extract ( data , '' , entityShaped ? 'entity-record' : 'flat-record' )
2025-08-26 12:32:21 -07:00
}
fix: metadata explosion bug - 69K files reduced to ~1K
Critical fix for metadata indexing that was creating 60+ chunk files per entity.
Root cause: Vector embeddings (384-dimensional arrays) were being indexed in
metadata, causing each dimension to create a separate chunk file with numeric
field names ("0", "1", "2", etc.).
Changes:
- Modified extractIndexableFields() to exclude vector/embedding fields
- Added NEVER_INDEX set: ['vector', 'embedding', 'embeddings', 'connections']
- Added safety check to skip arrays > 10 elements
- Preserves small array indexing (tags, categories, roles)
Impact:
- Reduces metadata files from 69,429 → ~1,200 (58x reduction)
- Fixes server initialization hangs
- Fixes metadata batch loading stalling at batch 23
- Fixes VFS getDescendants() hanging with large datasets
- Fixes Graph View UI not loading
Test Results:
- 7/7 integration tests passing
- Verified: 6 chunk files for 10 entities (was 7,210 before fix)
- 611/622 unit tests passing
Files Modified:
- src/utils/metadataIndex.ts - Core fix
- src/coreTypes.ts - HNSWVerb type enforcement with VerbType enum
- src/storage/adapters/* - Include core relational fields in HNSWVerb
- src/storage/adapters/baseStorageAdapter.ts - Type enforcement (HNSWNoun, GraphVerb)
- tests/integration/metadata-vector-exclusion.test.ts - Comprehensive test coverage
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-16 16:10:31 -07:00
2026-01-27 15:38:21 -08:00
// Extract words for hybrid text search
// Production-scale word limit (5000 words)
2026-01-26 17:16:18 -08:00
// - Handles articles, chapters, and large documents
// - Roaring Bitmaps + Chunked Sparse Index + LRU caching
// - Int32 hashes store words as 4-byte values, not strings
//
// Memory managed by existing optimizations:
// - Roaring Bitmaps: 90%+ compression for sparse data
// - Chunked Sparse Index: ~50 values per chunk, lazy-loaded
// - UnifiedCache LRU: Only hot chunks in memory
//
2026-06-11 10:42:34 -07:00
// A Bloom-filter hybrid could lift the per-entity word cap entirely if
// full-document indexing at billion-entity scale ever becomes a need.
2026-01-26 17:16:18 -08:00
const textContent = this . extractTextContent ( data )
if ( textContent ) {
const MAX_WORDS_PER_ENTITY = 5000 // Handles articles/chapters, memory-safe at scale
const allWords = this . tokenize ( textContent )
const words = allWords . slice ( 0 , MAX_WORDS_PER_ENTITY )
if ( allWords . length > MAX_WORDS_PER_ENTITY ) {
// Log once per entity, not per word - avoids log spam
prodLog . debug (
` Entity text has ${ allWords . length } words, indexing first ${ MAX_WORDS_PER_ENTITY } for hybrid search `
)
}
for ( const word of words ) {
// Hash word to int32 for memory efficiency (saves ~10GB at 1B scale)
const wordHash = this . hashWord ( word )
fields . push ( { field : '__words__' , value : wordHash } )
}
}
2025-08-26 12:32:21 -07:00
return fields
}
2026-01-26 17:16:18 -08:00
/ * *
2026-01-27 15:38:21 -08:00
* Extract text content from entity data for word indexing
2026-01-26 17:16:18 -08:00
*
* Recursively extracts string values from data , excluding :
* - vector , embedding , connections , level , id ( internal fields )
* - Arrays with more than 10 elements ( likely vectors / bulk data )
* - Numeric - only keys ( array indices )
*
* @param data - Entity data or metadata
* @returns Concatenated text content
* /
extractTextContent ( data : any ) : string {
if ( data === null || data === undefined ) return ''
if ( typeof data === 'string' ) return data
if ( typeof data === 'number' || typeof data === 'boolean' ) return String ( data )
if ( Array . isArray ( data ) ) {
feat: add structured content extraction and batch embedding optimization to highlight()
Fix highlight() hanging on structured text input by addressing 3 root causes:
1. embedBatch() now uses native WASM batch API (single forward pass instead
of N individual embed() calls via Promise.all)
2. highlight() auto-detects content type (plain text, rich-text JSON, HTML,
Markdown) and extracts meaningful text segments. Supports TipTap, Slate.js,
Lexical, Draft.js, and Quill Delta formats. New contentType hint and
contentExtractor callback for custom parsers.
3. Semantic matching phase has 10s timeout - falls back to text-only matches
instead of hanging indefinitely.
Also fixes extractTextContent() array check: uses type-based detection
(typeof data[0] === 'number') instead of length-based (data.length > 10)
so arrays of objects are properly indexed for text search.
New types: ContentType, ContentCategory, ExtractedSegment
New fields: HighlightParams.contentType, HighlightParams.contentExtractor,
Highlight.contentCategory
2026-01-27 10:27:22 -08:00
// Skip numeric arrays (vectors/embeddings), allow object/string arrays
if ( data . length > 0 && typeof data [ 0 ] === 'number' ) return ''
2026-01-26 17:16:18 -08:00
return data . map ( d = > this . extractTextContent ( d ) ) . filter ( Boolean ) . join ( ' ' )
}
if ( typeof data === 'object' ) {
2026-07-07 12:23:36 -07:00
// Mirror of NEVER_INDEX for the text-extraction path: bulk structural
// payloads only. `level` removed for the same reason (it silently dropped
// a real user field from hybrid text search too).
const skipKeys = new Set ( [ 'vector' , 'embedding' , 'embeddings' , 'connections' , 'id' ] )
2026-01-26 17:16:18 -08:00
const texts : string [ ] = [ ]
for ( const [ key , value ] of Object . entries ( data ) ) {
// Skip internal fields and numeric keys (array indices)
if ( skipKeys . has ( key ) || /^\d+$/ . test ( key ) ) continue
const text = this . extractTextContent ( value )
if ( text ) texts . push ( text )
}
return texts . join ( ' ' )
}
return ''
}
/ * *
2026-01-27 15:38:21 -08:00
* Tokenize text into words for indexing
2026-01-26 17:16:18 -08:00
*
* - Converts to lowercase
* - Removes punctuation
* - Splits on whitespace
* - Filters by length ( 2 - 50 chars )
* - Deduplicates per entity
*
* @param text - Text content to tokenize
* @returns Array of unique words
* /
tokenize ( text : string ) : string [ ] {
if ( ! text ) return [ ]
return text
. toLowerCase ( )
. replace ( /[^\w\s]/g , ' ' ) // Remove punctuation
. split ( /\s+/ ) // Split on whitespace
. filter ( w = > w . length >= 2 && w . length <= 50 ) // Length filter
. filter ( ( w , i , arr ) = > arr . indexOf ( w ) === i ) // Dedupe per entity
}
/ * *
2026-01-27 15:38:21 -08:00
* Hash word to int32 using FNV - 1 a
2026-01-26 17:16:18 -08:00
*
* FNV - 1 a is fast with low collision rate , suitable for word hashing .
* Saves ~ 10 GB at billion scale by avoiding string storage .
*
* @param word - Word to hash
* @returns Int32 hash value
* /
hashWord ( word : string ) : number {
let hash = 2166136261 // FNV offset basis
for ( let i = 0 ; i < word . length ; i ++ ) {
hash ^= word . charCodeAt ( i )
hash = Math . imul ( hash , 16777619 ) // FNV prime
}
return hash | 0 // Convert to signed int32
}
/ * *
2026-01-27 15:38:21 -08:00
* Get entity IDs matching a text query
2026-01-26 17:16:18 -08:00
*
* Performs word - based text search using the __words__ index .
* Returns IDs ranked by match count ( entities with more matching words first ) .
*
* @param query - Text query to search for
* @returns Array of { id , matchCount } sorted by matchCount descending
* /
async getIdsForTextQuery ( query : string ) : Promise < Array < { id : string ; matchCount : number } > > {
const queryWords = this . tokenize ( query )
if ( queryWords . length === 0 ) return [ ]
// Get IDs for each word hash
const wordIdSets : Map < string , number > [ ] = [ ]
for ( const word of queryWords ) {
const wordHash = this . hashWord ( word )
2026-05-15 12:31:28 -07:00
let ids : string [ ]
try {
ids = await this . getIds ( '__words__' , wordHash )
} catch ( err ) {
// `__words__` is not yet indexed (e.g. no text content has been
// added). Treat as no matches and continue — text search against
// an empty workspace should return [], not throw.
if ( err instanceof BrainyError && err . type === 'FIELD_NOT_INDEXED' ) {
ids = [ ]
} else {
throw err
}
}
2026-01-26 17:16:18 -08:00
const idSet = new Map < string , number > ( )
for ( const id of ids ) {
idSet . set ( id , 1 )
}
wordIdSets . push ( idSet )
}
if ( wordIdSets . length === 0 ) return [ ]
// Count matches per entity
const matchCounts = new Map < string , number > ( )
for ( const idSet of wordIdSets ) {
for ( const [ id ] of idSet ) {
matchCounts . set ( id , ( matchCounts . get ( id ) || 0 ) + 1 )
}
}
// Sort by match count descending
return Array . from ( matchCounts . entries ( ) )
. map ( ( [ id , matchCount ] ) = > ( { id , matchCount } ) )
. sort ( ( a , b ) = > b . matchCount - a . matchCount )
}
2025-08-26 12:32:21 -07:00
/ * *
* Add item to metadata indexes
fix(storage): v4.8.0 metadata architecture refactoring - FIXES VFS bug
CRITICAL FIX: VFS bug that persisted through v4.5.1-v4.7.4 is NOW FIXED.
Root Cause:
- Storage adapters were not properly extracting standard fields from metadata
- This caused getVerbsBySource_internal() to return 0 relationships despite relationships existing
- VFS PathResolver couldn't navigate directory structure
Solution - Metadata Architecture Refactoring:
1. Move standard fields to top-level of HNSWNounWithMetadata and HNSWVerbWithMetadata
- type, createdAt, updatedAt, confidence, weight, service, data, createdBy
2. Update all 9 storage adapters to extract standard fields from metadata on load
3. Maintain backward compatibility at storage layer (metadata files unchanged)
Changes:
- src/coreTypes.ts: Update HNSWNounWithMetadata and HNSWVerbWithMetadata interfaces
- Add top-level standard fields
- Change data type from unknown to Record<string, any>
- Add confidence field to GraphVerb
- src/storage/baseStorage.ts: Add type cast pattern for standard field extraction
- src/storage/adapters/*.ts: Fix all 9 adapters (memoryStorage, fileSystemStorage, gcsStorage,
s3CompatibleStorage, r2Storage, opfsStorage, azureBlobStorage, typeAwareStorageAdapter)
- Extract standard fields from metadata on load
- Place at top-level of returned entities
- src/api/DataAPI.ts: Read fields from top-level instead of metadata
- src/graph/graphAdjacencyIndex.ts: Convert HNSWVerbWithMetadata to GraphVerb format
- src/utils/metadataIndex.ts: Fix typo (metadata → entityOrMetadata)
- src/types/brainy.types.ts: Add createdBy field to AddParams
- src/types/graphTypes.ts: Add service field to GraphVerb
Test Results:
✅ VFS bug FIXED - vfs.readdir('/') now returns files (was returning empty array)
✅ getVerbsBySource_internal() now returns relationships correctly
✅ Build succeeds with ZERO compilation errors
✅ 95.7% of tests pass (954/997)
Breaking Changes:
- None - backward compatibility maintained at storage layer
Version: 4.8.0
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-27 15:43:49 -07:00
*
2026-01-27 15:38:21 -08:00
* Now accepts either entity structure or plain metadata
fix(storage): v4.8.0 metadata architecture refactoring - FIXES VFS bug
CRITICAL FIX: VFS bug that persisted through v4.5.1-v4.7.4 is NOW FIXED.
Root Cause:
- Storage adapters were not properly extracting standard fields from metadata
- This caused getVerbsBySource_internal() to return 0 relationships despite relationships existing
- VFS PathResolver couldn't navigate directory structure
Solution - Metadata Architecture Refactoring:
1. Move standard fields to top-level of HNSWNounWithMetadata and HNSWVerbWithMetadata
- type, createdAt, updatedAt, confidence, weight, service, data, createdBy
2. Update all 9 storage adapters to extract standard fields from metadata on load
3. Maintain backward compatibility at storage layer (metadata files unchanged)
Changes:
- src/coreTypes.ts: Update HNSWNounWithMetadata and HNSWVerbWithMetadata interfaces
- Add top-level standard fields
- Change data type from unknown to Record<string, any>
- Add confidence field to GraphVerb
- src/storage/baseStorage.ts: Add type cast pattern for standard field extraction
- src/storage/adapters/*.ts: Fix all 9 adapters (memoryStorage, fileSystemStorage, gcsStorage,
s3CompatibleStorage, r2Storage, opfsStorage, azureBlobStorage, typeAwareStorageAdapter)
- Extract standard fields from metadata on load
- Place at top-level of returned entities
- src/api/DataAPI.ts: Read fields from top-level instead of metadata
- src/graph/graphAdjacencyIndex.ts: Convert HNSWVerbWithMetadata to GraphVerb format
- src/utils/metadataIndex.ts: Fix typo (metadata → entityOrMetadata)
- src/types/brainy.types.ts: Add createdBy field to AddParams
- src/types/graphTypes.ts: Add service field to GraphVerb
Test Results:
✅ VFS bug FIXED - vfs.readdir('/') now returns files (was returning empty array)
✅ getVerbsBySource_internal() now returns relationships correctly
✅ Build succeeds with ZERO compilation errors
✅ 95.7% of tests pass (954/997)
Breaking Changes:
- None - backward compatibility maintained at storage layer
Version: 4.8.0
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-27 15:43:49 -07:00
* - Entity structure : { id , type , confidence , weight , createdAt , metadata : { . . . } }
* - Plain metadata : { noun , confidence , weight , createdAt , . . . }
*
* @param id - Entity ID
2026-01-27 15:38:21 -08:00
* @param entityOrMetadata - Either full entity structure or plain metadata ( backward compat )
fix(storage): v4.8.0 metadata architecture refactoring - FIXES VFS bug
CRITICAL FIX: VFS bug that persisted through v4.5.1-v4.7.4 is NOW FIXED.
Root Cause:
- Storage adapters were not properly extracting standard fields from metadata
- This caused getVerbsBySource_internal() to return 0 relationships despite relationships existing
- VFS PathResolver couldn't navigate directory structure
Solution - Metadata Architecture Refactoring:
1. Move standard fields to top-level of HNSWNounWithMetadata and HNSWVerbWithMetadata
- type, createdAt, updatedAt, confidence, weight, service, data, createdBy
2. Update all 9 storage adapters to extract standard fields from metadata on load
3. Maintain backward compatibility at storage layer (metadata files unchanged)
Changes:
- src/coreTypes.ts: Update HNSWNounWithMetadata and HNSWVerbWithMetadata interfaces
- Add top-level standard fields
- Change data type from unknown to Record<string, any>
- Add confidence field to GraphVerb
- src/storage/baseStorage.ts: Add type cast pattern for standard field extraction
- src/storage/adapters/*.ts: Fix all 9 adapters (memoryStorage, fileSystemStorage, gcsStorage,
s3CompatibleStorage, r2Storage, opfsStorage, azureBlobStorage, typeAwareStorageAdapter)
- Extract standard fields from metadata on load
- Place at top-level of returned entities
- src/api/DataAPI.ts: Read fields from top-level instead of metadata
- src/graph/graphAdjacencyIndex.ts: Convert HNSWVerbWithMetadata to GraphVerb format
- src/utils/metadataIndex.ts: Fix typo (metadata → entityOrMetadata)
- src/types/brainy.types.ts: Add createdBy field to AddParams
- src/types/graphTypes.ts: Add service field to GraphVerb
Test Results:
✅ VFS bug FIXED - vfs.readdir('/') now returns files (was returning empty array)
✅ getVerbsBySource_internal() now returns relationships correctly
✅ Build succeeds with ZERO compilation errors
✅ 95.7% of tests pass (954/997)
Breaking Changes:
- None - backward compatibility maintained at storage layer
Version: 4.8.0
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-27 15:43:49 -07:00
* @param skipFlush - Skip automatic flush ( used during batch operations )
2025-08-26 12:32:21 -07:00
* /
2026-01-31 09:14:51 -08:00
async addToIndex ( id : string , entityOrMetadata : any , skipFlush : boolean = false , deferWrites : boolean = false ) : Promise < void > {
fix(storage): v4.8.0 metadata architecture refactoring - FIXES VFS bug
CRITICAL FIX: VFS bug that persisted through v4.5.1-v4.7.4 is NOW FIXED.
Root Cause:
- Storage adapters were not properly extracting standard fields from metadata
- This caused getVerbsBySource_internal() to return 0 relationships despite relationships existing
- VFS PathResolver couldn't navigate directory structure
Solution - Metadata Architecture Refactoring:
1. Move standard fields to top-level of HNSWNounWithMetadata and HNSWVerbWithMetadata
- type, createdAt, updatedAt, confidence, weight, service, data, createdBy
2. Update all 9 storage adapters to extract standard fields from metadata on load
3. Maintain backward compatibility at storage layer (metadata files unchanged)
Changes:
- src/coreTypes.ts: Update HNSWNounWithMetadata and HNSWVerbWithMetadata interfaces
- Add top-level standard fields
- Change data type from unknown to Record<string, any>
- Add confidence field to GraphVerb
- src/storage/baseStorage.ts: Add type cast pattern for standard field extraction
- src/storage/adapters/*.ts: Fix all 9 adapters (memoryStorage, fileSystemStorage, gcsStorage,
s3CompatibleStorage, r2Storage, opfsStorage, azureBlobStorage, typeAwareStorageAdapter)
- Extract standard fields from metadata on load
- Place at top-level of returned entities
- src/api/DataAPI.ts: Read fields from top-level instead of metadata
- src/graph/graphAdjacencyIndex.ts: Convert HNSWVerbWithMetadata to GraphVerb format
- src/utils/metadataIndex.ts: Fix typo (metadata → entityOrMetadata)
- src/types/brainy.types.ts: Add createdBy field to AddParams
- src/types/graphTypes.ts: Add service field to GraphVerb
Test Results:
✅ VFS bug FIXED - vfs.readdir('/') now returns files (was returning empty array)
✅ getVerbsBySource_internal() now returns relationships correctly
✅ Build succeeds with ZERO compilation errors
✅ 95.7% of tests pass (954/997)
Breaking Changes:
- None - backward compatibility maintained at storage layer
Version: 4.8.0
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-27 15:43:49 -07:00
const fields = this . extractIndexableFields ( entityOrMetadata )
2026-01-05 16:31:52 -08:00
2026-01-27 15:38:21 -08:00
// Sanity check for excessive indexed fields (indicates possible data issue)
// Separate threshold for metadata fields vs word fields
2026-01-26 17:16:18 -08:00
// - Metadata fields: warn if > 100 (indicates deeply nested metadata)
// - Word fields: expected to be many for large documents, warn only for extreme cases
const metadataFields = fields . filter ( f = > f . field !== '__words__' )
const wordFields = fields . filter ( f = > f . field === '__words__' )
if ( metadataFields . length > 100 ) {
2026-01-05 16:31:52 -08:00
prodLog . warn (
2026-01-26 17:16:18 -08:00
` Entity ${ id } has ${ metadataFields . length } metadata fields (expected ~30). ` +
` Possible deeply nested metadata. First 10 fields: ${ metadataFields . slice ( 0 , 10 ) . map ( f = > f . field ) . join ( ', ' ) } `
2026-01-05 16:31:52 -08:00
)
}
2026-01-26 17:16:18 -08:00
// Words are expected to be many for large documents - only log for extreme cases
if ( wordFields . length > 5000 ) {
prodLog . debug ( ` Entity ${ id } has ${ wordFields . length } indexed words (large document) ` )
}
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
// Sort fields to process the type column first for type-field affinity
// tracking ('system.type' is the frozen key; 'noun' died at epoch 3).
2025-09-12 13:37:24 -07:00
fields . sort ( ( a , b ) = > {
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
if ( a . field === 'system.type' ) return - 1
if ( b . field === 'system.type' ) return 1
2025-09-12 13:37:24 -07:00
return 0
} )
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// Update statistics and tracking for each field
2025-08-26 12:32:21 -07:00
for ( let i = 0 ; i < fields . length ; i ++ ) {
const { field , value } = fields [ i ]
2025-10-13 15:31:03 -07:00
this . updateCardinalityStats ( field , value , 'add' )
fix(storage): v4.8.0 metadata architecture refactoring - FIXES VFS bug
CRITICAL FIX: VFS bug that persisted through v4.5.1-v4.7.4 is NOW FIXED.
Root Cause:
- Storage adapters were not properly extracting standard fields from metadata
- This caused getVerbsBySource_internal() to return 0 relationships despite relationships existing
- VFS PathResolver couldn't navigate directory structure
Solution - Metadata Architecture Refactoring:
1. Move standard fields to top-level of HNSWNounWithMetadata and HNSWVerbWithMetadata
- type, createdAt, updatedAt, confidence, weight, service, data, createdBy
2. Update all 9 storage adapters to extract standard fields from metadata on load
3. Maintain backward compatibility at storage layer (metadata files unchanged)
Changes:
- src/coreTypes.ts: Update HNSWNounWithMetadata and HNSWVerbWithMetadata interfaces
- Add top-level standard fields
- Change data type from unknown to Record<string, any>
- Add confidence field to GraphVerb
- src/storage/baseStorage.ts: Add type cast pattern for standard field extraction
- src/storage/adapters/*.ts: Fix all 9 adapters (memoryStorage, fileSystemStorage, gcsStorage,
s3CompatibleStorage, r2Storage, opfsStorage, azureBlobStorage, typeAwareStorageAdapter)
- Extract standard fields from metadata on load
- Place at top-level of returned entities
- src/api/DataAPI.ts: Read fields from top-level instead of metadata
- src/graph/graphAdjacencyIndex.ts: Convert HNSWVerbWithMetadata to GraphVerb format
- src/utils/metadataIndex.ts: Fix typo (metadata → entityOrMetadata)
- src/types/brainy.types.ts: Add createdBy field to AddParams
- src/types/graphTypes.ts: Add service field to GraphVerb
Test Results:
✅ VFS bug FIXED - vfs.readdir('/') now returns files (was returning empty array)
✅ getVerbsBySource_internal() now returns relationships correctly
✅ Build succeeds with ZERO compilation errors
✅ 95.7% of tests pass (954/997)
Breaking Changes:
- None - backward compatibility maintained at storage layer
Version: 4.8.0
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-27 15:43:49 -07:00
this . updateTypeFieldAffinity ( id , field , value , 'add' , entityOrMetadata )
2025-08-26 12:32:21 -07:00
await this . updateFieldIndex ( field , value , 1 )
}
2026-01-31 09:09:36 -08:00
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// Write to column store — the single write path for all indexed data.
// Converts extracted fields into a map and feeds the column store.
fix(8.0): multi-valued array fields index every element (contains no longer misses)
addToIndex builds a fieldsMap from the extracted {field,value} entries, but
only __words__ accumulated — every other repeated field did fieldsMap[field]=value,
so a multi-valued field (tags:['a','b','c'] → three 'tags' entries from
extractIndexableFields) collapsed to last-value-wins. columnStore.addEntity
expands an array to one indexed entry per element, but it only ever received the
final scalar, so `contains` matched only the last element and missed the rest.
Accumulate any repeated non-__words__ field into an array before addEntity
(promote scalar→array on the second occurrence). __words__ keeps its always-array
special-case so its multiValue manifest flag stays set even for single-word docs.
find-unified-integration.test.ts → 0 failures (was 4):
- 'array contains' (A.4): now queries first/middle/last element — all match
(previously only the last-indexed element did).
- 'complete find workflow': $contains→contains (8.0 operator) AND fixed the test
premise — find() hard-ANDs vector∩graph∩metadata, and connected:{from:X} returns
X's NEIGHBOURS not X, so the graph anchor must be 'earth' (which the ML concept
relates to), not the concept itself. Multi-signal scores are reciprocal-rank
fusion (~1/61), not [0,1] cosine, so assert a positive fusion score, not >0.5.
- 'nonsense vector query': cosine search always returns nearest neighbours, so
assert the structural array/bound contract, not length===0 (a Tier-2 concern).
- 'hard-ANDs signals': a nonexistent connected.from is an empty graph signal that
zeros the intersection — assert length===0 (documented AND semantics), was >0.
1469 unit + full find-unified integration green.
2026-06-19 11:37:59 -07:00
//
// extractIndexableFields emits ONE {field,value} entry per array element for
// a multi-valued field (e.g. tags:['a','b','c'] → three 'tags' entries). We
// must accumulate every repeated field into an array, not just __words__:
// columnStore.addEntity expands an array value to one indexed entry per
// element, so a scalar overwrite (last-value-wins) would index only the final
// element and `contains` would miss the rest.
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
if ( this . columnStore ) {
const entityIntId = this . idMapper . getOrAssign ( id )
const fieldsMap : Record < string , unknown > = { }
for ( const { field , value } of fields ) {
if ( field === '__words__' ) {
fix(8.0): multi-valued array fields index every element (contains no longer misses)
addToIndex builds a fieldsMap from the extracted {field,value} entries, but
only __words__ accumulated — every other repeated field did fieldsMap[field]=value,
so a multi-valued field (tags:['a','b','c'] → three 'tags' entries from
extractIndexableFields) collapsed to last-value-wins. columnStore.addEntity
expands an array to one indexed entry per element, but it only ever received the
final scalar, so `contains` matched only the last element and missed the rest.
Accumulate any repeated non-__words__ field into an array before addEntity
(promote scalar→array on the second occurrence). __words__ keeps its always-array
special-case so its multiValue manifest flag stays set even for single-word docs.
find-unified-integration.test.ts → 0 failures (was 4):
- 'array contains' (A.4): now queries first/middle/last element — all match
(previously only the last-indexed element did).
- 'complete find workflow': $contains→contains (8.0 operator) AND fixed the test
premise — find() hard-ANDs vector∩graph∩metadata, and connected:{from:X} returns
X's NEIGHBOURS not X, so the graph anchor must be 'earth' (which the ML concept
relates to), not the concept itself. Multi-signal scores are reciprocal-rank
fusion (~1/61), not [0,1] cosine, so assert a positive fusion score, not >0.5.
- 'nonsense vector query': cosine search always returns nearest neighbours, so
assert the structural array/bound contract, not length===0 (a Tier-2 concern).
- 'hard-ANDs signals': a nonexistent connected.from is an empty graph signal that
zeros the intersection — assert length===0 (documented AND semantics), was >0.
1469 unit + full find-unified integration green.
2026-06-19 11:37:59 -07:00
// Always an array (keeps the field's multiValue manifest flag set even
// for a single-word document).
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
if ( ! fieldsMap . __words__ ) fieldsMap . __words__ = [ ]
fix(8.0): multi-valued array fields index every element (contains no longer misses)
addToIndex builds a fieldsMap from the extracted {field,value} entries, but
only __words__ accumulated — every other repeated field did fieldsMap[field]=value,
so a multi-valued field (tags:['a','b','c'] → three 'tags' entries from
extractIndexableFields) collapsed to last-value-wins. columnStore.addEntity
expands an array to one indexed entry per element, but it only ever received the
final scalar, so `contains` matched only the last element and missed the rest.
Accumulate any repeated non-__words__ field into an array before addEntity
(promote scalar→array on the second occurrence). __words__ keeps its always-array
special-case so its multiValue manifest flag stays set even for single-word docs.
find-unified-integration.test.ts → 0 failures (was 4):
- 'array contains' (A.4): now queries first/middle/last element — all match
(previously only the last-indexed element did).
- 'complete find workflow': $contains→contains (8.0 operator) AND fixed the test
premise — find() hard-ANDs vector∩graph∩metadata, and connected:{from:X} returns
X's NEIGHBOURS not X, so the graph anchor must be 'earth' (which the ML concept
relates to), not the concept itself. Multi-signal scores are reciprocal-rank
fusion (~1/61), not [0,1] cosine, so assert a positive fusion score, not >0.5.
- 'nonsense vector query': cosine search always returns nearest neighbours, so
assert the structural array/bound contract, not length===0 (a Tier-2 concern).
- 'hard-ANDs signals': a nonexistent connected.from is an empty graph signal that
zeros the intersection — assert length===0 (documented AND semantics), was >0.
1469 unit + full find-unified integration green.
2026-06-19 11:37:59 -07:00
; ( fieldsMap . __words__ as unknown [ ] ) . push ( value )
} else if ( field in fieldsMap ) {
// Repeated field → multi-valued. Promote the scalar to an array on the
// second occurrence, then accumulate.
const existing = fieldsMap [ field ]
if ( Array . isArray ( existing ) ) {
; ( existing as unknown [ ] ) . push ( value )
} else {
fieldsMap [ field ] = [ existing , value ]
}
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
} else {
fieldsMap [ field ] = value
}
}
feat(8.0): u64 BigInt graph provider contract — punch list a-d,g,h
GraphIndexProvider now speaks BigInt at the boundary (D.2 mirror):
- getNeighbors/getVerbIdsBySource/getVerbIdsByTarget take entity ints and
return entity/verb ints as bigint[]
- new REQUIRED verbIntsToIds(bigint[]) batch reverse resolver (L.7
identity-fingerprint design — verb ids are UUIDs by contract, so the
provider-side interning is losslessly reversible)
- addVerb(verb, sourceInt, targetInt) returns the interned verb int;
removeVerb(verbId) joins the contract
Coordinator (brainy.ts) owns ALL UUID <-> int conversion: getOrAssign on
writes, getInt on reads (unmapped UUID -> empty result without calling the
provider), getUuid / verbIntsToIds on returns, plus a bounded ~100k-entry
insertion-order warm cache for verb-int -> verb-id pairs fed by addVerb
returns and resolver results. GraphVerb gains derived sourceInt/targetInt
(populated at add time, never persisted). findConnectedSubtype gains a
native fast path that routes single-type single-subtype outgoing BFS
through the provider when available.
JS GraphAdjacencyIndex satisfies the contract while staying string/u32-keyed
internally: entity ints resolve through the shared entity-id mapper (threaded
in by the coordinator on init/fork/checkout), verb ints come from an
in-process append-only interning map re-derived from storage on
rebuild/cold-start. ColumnStoreProvider widens the same way: addEntity/
removeEntity take bigint, sortTopK/filteredSortTopK return bigint[].
relate() now rejects a caller-supplied id with a teaching error — verb ids
are brainy-generated UUIDs by contract in 8.0 (previously a passed id was
silently ignored). No Roaring64 provider-boundary decode site exists yet;
the JS-internal column store stays Roaring32 and the Treemap decoder lands
with the first consumer of provider-returned filter buffers.
Public brain API unchanged. 1413 tests green (+10 new BigInt contract tests).
2026-06-10 10:45:45 -07:00
this . columnStore . addEntity ( BigInt ( entityIntId ) , fieldsMap )
2026-01-31 09:14:51 -08:00
}
2026-01-31 09:09:36 -08:00
2026-01-27 15:38:21 -08:00
// Adaptive auto-flush based on usage patterns
2025-08-26 12:32:21 -07:00
if ( ! skipFlush ) {
const timeSinceLastFlush = Date . now ( ) - this . lastFlushTime
2025-10-13 15:31:03 -07:00
const shouldAutoFlush =
this . dirtyFields . size >= this . autoFlushThreshold || // Size threshold
( this . dirtyFields . size > 10 && timeSinceLastFlush > 5000 ) // Time threshold (5 seconds)
2025-08-26 12:32:21 -07:00
if ( shouldAutoFlush ) {
const startTime = Date . now ( )
await this . flush ( )
const flushTime = Date . now ( ) - startTime
2025-10-13 15:31:03 -07:00
2025-08-26 12:32:21 -07:00
// Adapt threshold based on flush performance
if ( flushTime < 50 ) {
// Fast flush, can handle more entries
this . autoFlushThreshold = Math . min ( 200 , this . autoFlushThreshold * 1.2 )
} else if ( flushTime > 200 ) {
// Slow flush, reduce batch size
this . autoFlushThreshold = Math . max ( 20 , this . autoFlushThreshold * 0.8 )
}
2025-10-13 15:31:03 -07:00
2025-08-26 12:32:21 -07:00
// Yield to event loop after flush to prevent blocking
await this . yieldToEventLoop ( )
}
}
// Invalidate cache for these fields
for ( const { field } of fields ) {
this . metadataCache . invalidatePattern ( ` field_values_ ${ field } ` )
}
}
/ * *
* Update field index with value count
* /
private async updateFieldIndex ( field : string , value : any , delta : number ) : Promise < void > {
let fieldIndex = this . fieldIndexes . get ( field )
if ( ! fieldIndex ) {
// Load from storage if not in memory
fieldIndex = await this . loadFieldIndex ( field ) ? ? {
values : { } ,
lastUpdated : Date.now ( )
}
this . fieldIndexes . set ( field , fieldIndex )
}
2025-10-13 13:16:07 -07:00
const normalizedValue = this . normalizeValue ( value , field ) // Pass field for bucketing!
2025-08-26 12:32:21 -07:00
fieldIndex . values [ normalizedValue ] = ( fieldIndex . values [ normalizedValue ] || 0 ) + delta
// Remove if count drops to 0
if ( fieldIndex . values [ normalizedValue ] <= 0 ) {
delete fieldIndex . values [ normalizedValue ]
}
fieldIndex . lastUpdated = Date . now ( )
this . dirtyFields . add ( field )
}
/ * *
* Remove item from metadata indexes
fix(storage): v4.8.0 metadata architecture refactoring - FIXES VFS bug
CRITICAL FIX: VFS bug that persisted through v4.5.1-v4.7.4 is NOW FIXED.
Root Cause:
- Storage adapters were not properly extracting standard fields from metadata
- This caused getVerbsBySource_internal() to return 0 relationships despite relationships existing
- VFS PathResolver couldn't navigate directory structure
Solution - Metadata Architecture Refactoring:
1. Move standard fields to top-level of HNSWNounWithMetadata and HNSWVerbWithMetadata
- type, createdAt, updatedAt, confidence, weight, service, data, createdBy
2. Update all 9 storage adapters to extract standard fields from metadata on load
3. Maintain backward compatibility at storage layer (metadata files unchanged)
Changes:
- src/coreTypes.ts: Update HNSWNounWithMetadata and HNSWVerbWithMetadata interfaces
- Add top-level standard fields
- Change data type from unknown to Record<string, any>
- Add confidence field to GraphVerb
- src/storage/baseStorage.ts: Add type cast pattern for standard field extraction
- src/storage/adapters/*.ts: Fix all 9 adapters (memoryStorage, fileSystemStorage, gcsStorage,
s3CompatibleStorage, r2Storage, opfsStorage, azureBlobStorage, typeAwareStorageAdapter)
- Extract standard fields from metadata on load
- Place at top-level of returned entities
- src/api/DataAPI.ts: Read fields from top-level instead of metadata
- src/graph/graphAdjacencyIndex.ts: Convert HNSWVerbWithMetadata to GraphVerb format
- src/utils/metadataIndex.ts: Fix typo (metadata → entityOrMetadata)
- src/types/brainy.types.ts: Add createdBy field to AddParams
- src/types/graphTypes.ts: Add service field to GraphVerb
Test Results:
✅ VFS bug FIXED - vfs.readdir('/') now returns files (was returning empty array)
✅ getVerbsBySource_internal() now returns relationships correctly
✅ Build succeeds with ZERO compilation errors
✅ 95.7% of tests pass (954/997)
Breaking Changes:
- None - backward compatibility maintained at storage layer
Version: 4.8.0
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-27 15:43:49 -07:00
*
2026-01-27 15:38:21 -08:00
* Now accepts either entity structure or plain metadata ( same as addToIndex )
fix(storage): v4.8.0 metadata architecture refactoring - FIXES VFS bug
CRITICAL FIX: VFS bug that persisted through v4.5.1-v4.7.4 is NOW FIXED.
Root Cause:
- Storage adapters were not properly extracting standard fields from metadata
- This caused getVerbsBySource_internal() to return 0 relationships despite relationships existing
- VFS PathResolver couldn't navigate directory structure
Solution - Metadata Architecture Refactoring:
1. Move standard fields to top-level of HNSWNounWithMetadata and HNSWVerbWithMetadata
- type, createdAt, updatedAt, confidence, weight, service, data, createdBy
2. Update all 9 storage adapters to extract standard fields from metadata on load
3. Maintain backward compatibility at storage layer (metadata files unchanged)
Changes:
- src/coreTypes.ts: Update HNSWNounWithMetadata and HNSWVerbWithMetadata interfaces
- Add top-level standard fields
- Change data type from unknown to Record<string, any>
- Add confidence field to GraphVerb
- src/storage/baseStorage.ts: Add type cast pattern for standard field extraction
- src/storage/adapters/*.ts: Fix all 9 adapters (memoryStorage, fileSystemStorage, gcsStorage,
s3CompatibleStorage, r2Storage, opfsStorage, azureBlobStorage, typeAwareStorageAdapter)
- Extract standard fields from metadata on load
- Place at top-level of returned entities
- src/api/DataAPI.ts: Read fields from top-level instead of metadata
- src/graph/graphAdjacencyIndex.ts: Convert HNSWVerbWithMetadata to GraphVerb format
- src/utils/metadataIndex.ts: Fix typo (metadata → entityOrMetadata)
- src/types/brainy.types.ts: Add createdBy field to AddParams
- src/types/graphTypes.ts: Add service field to GraphVerb
Test Results:
✅ VFS bug FIXED - vfs.readdir('/') now returns files (was returning empty array)
✅ getVerbsBySource_internal() now returns relationships correctly
✅ Build succeeds with ZERO compilation errors
✅ 95.7% of tests pass (954/997)
Breaking Changes:
- None - backward compatibility maintained at storage layer
Version: 4.8.0
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-27 15:43:49 -07:00
* - Entity structure : { id , type , confidence , weight , createdAt , metadata : { . . . } }
* - Plain metadata : { noun , confidence , weight , createdAt , . . . }
*
* @param id - Entity ID to remove
* @param metadata - Optional entity or metadata structure ( if not provided , requires scanning all fields - slow ! )
2025-08-26 12:32:21 -07:00
* /
async removeFromIndex ( id : string , metadata? : any ) : Promise < void > {
if ( metadata ) {
const fields = this . extractIndexableFields ( metadata )
2025-10-13 15:31:03 -07:00
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// Update statistics and tracking
2025-08-26 12:32:21 -07:00
for ( const { field , value } of fields ) {
2025-10-13 15:31:03 -07:00
this . updateCardinalityStats ( field , value , 'remove' )
this . updateTypeFieldAffinity ( id , field , value , 'remove' , metadata )
await this . updateFieldIndex ( field , value , - 1 )
2025-08-26 12:32:21 -07:00
this . metadataCache . invalidatePattern ( ` field_values_ ${ field } ` )
}
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
}
2026-01-31 09:09:36 -08:00
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// Remove from column store (global deleted bitmap)
if ( this . columnStore ) {
const intId = this . idMapper . getInt ( id )
if ( intId !== undefined ) {
feat(8.0): u64 BigInt graph provider contract — punch list a-d,g,h
GraphIndexProvider now speaks BigInt at the boundary (D.2 mirror):
- getNeighbors/getVerbIdsBySource/getVerbIdsByTarget take entity ints and
return entity/verb ints as bigint[]
- new REQUIRED verbIntsToIds(bigint[]) batch reverse resolver (L.7
identity-fingerprint design — verb ids are UUIDs by contract, so the
provider-side interning is losslessly reversible)
- addVerb(verb, sourceInt, targetInt) returns the interned verb int;
removeVerb(verbId) joins the contract
Coordinator (brainy.ts) owns ALL UUID <-> int conversion: getOrAssign on
writes, getInt on reads (unmapped UUID -> empty result without calling the
provider), getUuid / verbIntsToIds on returns, plus a bounded ~100k-entry
insertion-order warm cache for verb-int -> verb-id pairs fed by addVerb
returns and resolver results. GraphVerb gains derived sourceInt/targetInt
(populated at add time, never persisted). findConnectedSubtype gains a
native fast path that routes single-type single-subtype outgoing BFS
through the provider when available.
JS GraphAdjacencyIndex satisfies the contract while staying string/u32-keyed
internally: entity ints resolve through the shared entity-id mapper (threaded
in by the coordinator on init/fork/checkout), verb ints come from an
in-process append-only interning map re-derived from storage on
rebuild/cold-start. ColumnStoreProvider widens the same way: addEntity/
removeEntity take bigint, sortTopK/filteredSortTopK return bigint[].
relate() now rejects a caller-supplied id with a teaching error — verb ids
are brainy-generated UUIDs by contract in 8.0 (previously a passed id was
silently ignored). No Roaring64 provider-boundary decode site exists yet;
the JS-internal column store stays Roaring32 and the Treemap decoder lands
with the first consumer of provider-returned filter buffers.
Public brain API unchanged. 1413 tests green (+10 new BigInt contract tests).
2026-06-10 10:45:45 -07:00
this . columnStore . removeEntity ( BigInt ( intId ) )
2025-08-26 12:32:21 -07:00
}
}
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// Clean up ID mapper — must happen AFTER column store removal since it uses
// idMapper.getInt(id). Prevents deleted IDs from persisting in the mapper
// universe, which would cause ne/exists:false queries to return deleted entities.
this . idMapper . remove ( id )
await this . idMapper . flush ( )
2025-08-26 12:32:21 -07:00
}
2025-08-27 15:38:48 -07:00
/ * *
* Get all IDs in the index
* /
async getAllIds ( ) : Promise < string [ ] > {
2026-01-27 15:38:21 -08:00
// Use storage as the source of truth
2025-08-27 15:38:48 -07:00
const allIds = new Set < string > ( )
2025-10-13 15:31:03 -07:00
// Storage.getNouns() is the definitive source of all entity IDs
2026-06-11 14:51:00 -07:00
if ( this . storage && typeof this . storage . getNouns === 'function' ) {
2025-08-27 15:38:48 -07:00
try {
2026-06-11 14:51:00 -07:00
const result = await this . storage . getNouns ( {
2025-10-13 15:31:03 -07:00
pagination : { limit : 100000 }
2025-08-27 15:38:48 -07:00
} )
if ( result && result . items ) {
2026-06-11 14:51:00 -07:00
result . items . forEach ( ( item ) = > {
2025-08-27 15:38:48 -07:00
if ( item . id ) allIds . add ( item . id )
} )
}
} catch ( e ) {
2025-10-13 15:31:03 -07:00
// If storage method fails, return empty array
prodLog . warn ( 'Failed to get all IDs from storage:' , e )
return [ ]
2025-08-27 15:38:48 -07:00
}
}
2025-10-13 15:31:03 -07:00
2025-08-27 15:38:48 -07:00
return Array . from ( allIds )
}
2025-08-26 12:32:21 -07:00
/ * *
2025-10-13 15:31:03 -07:00
* Get IDs for a specific field - value combination using chunked sparse index
2025-08-26 12:32:21 -07:00
* /
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
/ * *
* Point query : find all entity IDs where a field has a specific value .
*
* Routes through the column store for O ( log n ) binary search when available ,
* falls back to sparse index scan for fields not yet in the column store .
*
* @param field - Field name to query
* @param value - Exact value to match
* @returns Array of matching entity UUID strings
* /
feat: multi-process safety + read-only inspector mode
Filesystem storage now enforces single-writer, many-reader semantics.
A second writer on the same data directory throws at init time with the
holder's PID, hostname, and heartbeat — replacing the previous silent
stale-reads failure mode.
- New: `Brainy.openReadOnly()` — coexists with a live writer, every
mutation throws clearly.
- New: writer lock at `<rootDir>/locks/_writer.lock` with 10s heartbeat
and stale-detection (PID liveness + heartbeat freshness).
- New: cross-process flush-request RPC (filesystem-based, no signals)
so inspectors can force fresh state on demand.
- New: `brain.stats()`, `brain.explain(findParams)`, `brain.health()`
for operator-facing introspection.
- New: `brainy inspect` CLI with 13 subcommands (stats, find, get,
relations, explain, health, sample, fields, dump, watch, backup,
repair, diff), all read-only by default.
- Same-PID re-opens allowed with a warning (preserves test "simulate
restart" patterns).
- Storage instances passed directly via `storage: new MemoryStorage()`
are now honoured instead of silently falling through to the
filesystem auto-detect path.
Brainy + Cortex compose under this model — the lock covers both because
they share `rootDir`, Cortex segments are immutable mmap files, and
MANIFEST updates use atomic-rename.
2026-05-15 11:25:05 -07:00
/ * *
* Report which index path a ` where ` clause on ` field ` will hit . Used by
* ` brain.explain() ` so an operator can see * before * running a query whether
* the field has any index entries at all . A ` find({ where: { someField: ... } }) `
* against a field with no index entries returns ` [] ` silently — ` explainField `
* surfaces that as ` path: 'none' ` so the empty result has an explanation .
* /
async explainField ( field : string ) : Promise < {
path : 'column-store' | 'sparse-chunked' | 'none'
notes? : string
} > {
if ( this . columnStore && this . columnStore . hasField ( field ) ) {
return {
path : 'column-store' ,
notes : 'O(log n) binary search + roaring bitmap. Best path.'
}
}
const sparse = await this . loadSparseIndex ( field )
if ( sparse ) {
return {
path : 'sparse-chunked' ,
notes : 'Chunked sparse index with zone maps and bloom filters.'
}
}
return {
path : 'none' ,
notes :
` No index entries for field " ${ field } ". A find({ where: { ${ field } : ... } }) ` +
` will return an empty result regardless of whether matching entities exist on disk. ` +
` Likely causes: (1) the writer registered the field in memory but has not flushed; ` +
` (2) the field name does not match what was written (typo or casing); ` +
` (3) the field is genuinely absent from all entities. Call requestFlush() on the ` +
` writer or call brain.flush() before relying on the result. `
}
}
2026-05-15 12:31:28 -07:00
/ * *
* Resolve a ` where: { field: value } ` clause to entity UUIDs .
*
* Lookup order :
* 1 . * * Column store * * — the post - 7.20 . 0 single source of truth . Fast .
* 2 . * * Legacy sparse index * * — only consulted for pre - 7.20 . 0 workspaces
* that haven ' t been migrated . Returns ` [] ` if no sparse data either .
*
* Throws ` BrainyError(FIELD_NOT_INDEXED) ` if the field has no entries in
* either store . Callers in find ( ) - evaluation catch this and translate to
* an empty result with a logged warning . The throw aligns the production
2026-06-11 10:42:34 -07:00
* ` find() ` path with the ` brain.explain() ` diagnostic , so a silently
* empty result for an unindexed field is no longer possible .
2026-05-15 12:31:28 -07:00
* /
2025-08-26 12:32:21 -07:00
async getIds ( field : string , value : any ) : Promise < string [ ] > {
2025-09-12 12:45:32 -07:00
// Track exact query for field statistics
if ( this . fieldStats . has ( field ) ) {
const stats = this . fieldStats . get ( field ) !
stats . exactQueryCount ++
}
2025-10-13 15:31:03 -07:00
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// Column store path: O(log n) binary search + roaring bitmap.
// Use raw value (no normalization) — the column store stores exact values,
// not the bucketed/stringified format the sparse index uses.
if ( this . columnStore && this . columnStore . hasField ( field ) ) {
const bitmap = await this . columnStore . filter ( field , value )
return this . idMapper . intsIterableToUuids ( bitmap )
}
2026-05-15 12:31:28 -07:00
// Fallback: sparse index scan (legacy path during migration). If neither
// store has the field, throw FIELD_NOT_INDEXED so the caller knows it's a
// genuine "no such index" rather than "the value isn't there".
2025-10-13 15:31:03 -07:00
return await this . getIdsFromChunks ( field , value )
2025-08-26 12:32:21 -07:00
}
/ * *
* Get all available values for a field ( for filter discovery )
* /
async getFilterValues ( field : string ) : Promise < string [ ] > {
// Check cache first
const cacheKey = ` field_values_ ${ field } `
const cachedValues = this . metadataCache . get ( cacheKey )
if ( cachedValues ) {
return cachedValues
}
// Check in-memory field indexes first
let fieldIndex = this . fieldIndexes . get ( field )
// If not in memory, load from storage
if ( ! fieldIndex ) {
const loaded = await this . loadFieldIndex ( field )
if ( loaded ) {
fieldIndex = loaded
this . fieldIndexes . set ( field , loaded )
}
}
if ( ! fieldIndex ) {
return [ ]
}
const values = Object . keys ( fieldIndex . values )
// Cache the result
this . metadataCache . set ( cacheKey , values )
return values
}
/ * *
* Get all indexed fields ( for filter discovery )
* /
async getFilterFields ( ) : Promise < string [ ] > {
// Check cache first
const cacheKey = 'all_filter_fields'
const cachedFields = this . metadataCache . get ( cacheKey )
if ( cachedFields ) {
return cachedFields
}
// Get fields from in-memory indexes and storage
const fields = new Set < string > ( this . fieldIndexes . keys ( ) )
// Also scan storage for persisted field indexes (in case not loaded)
// This would require a new storage method to list field indexes
// For now, just use in-memory fields
const fieldsArray = Array . from ( fields )
// Cache the result
this . metadataCache . set ( cacheKey , fieldsArray )
return fieldsArray
}
/ * *
* Convert Brainy Field Operator filter to simple field - value criteria for indexing
* /
private convertFilterToCriteria ( filter : any ) : Array < { field : string , values : any [ ] } > {
const criteria : Array < { field : string , values : any [ ] } > = [ ]
if ( ! filter || typeof filter !== 'object' ) {
return criteria
}
for ( const [ key , value ] of Object . entries ( filter ) ) {
// Skip logical operators for now - handle them separately
if ( key === 'allOf' || key === 'anyOf' || key === 'not' ) continue
if ( value && typeof value === 'object' && ! Array . isArray ( value ) ) {
// Handle Brainy Field Operators
for ( const [ op , operand ] of Object . entries ( value ) ) {
switch ( op ) {
case 'oneOf' :
if ( Array . isArray ( operand ) ) {
criteria . push ( { field : key , values : operand } )
}
break
case 'equals' :
case 'eq' :
criteria . push ( { field : key , values : [ operand ] } )
break
case 'contains' :
// For contains, the operand is the value we're looking for in an array field
criteria . push ( { field : key , values : [ operand ] } )
break
case 'greaterThan' :
case 'lessThan' :
case 'between' :
// Range queries will be handled separately
// Sorted index will be created/loaded when needed in getIdsForRange
break
default :
break
}
}
} else {
// Direct value or array
const values = Array . isArray ( value ) ? value : [ value ]
criteria . push ( { field : key , values } )
}
}
return criteria
}
/ * *
feat(8.0): wire the two cor-confirmed metadata-provider contract additions
Both shapes confirmed with cor for the lockstep (cor builds the native side
against these; the JS index is a no-op / unchanged):
- probeConsistency?(): Promise<boolean> — OPTIONAL O(1) cold-open consistency
sampler on MetadataIndexProvider. brainy calls it ONCE per brain on the first
read; on `false` it self-heals via detectAndRepairCorruption() — the metadata
counterpart of the 7.33.2 graph cold-load guard, completing the phantom triad's
detect-and-repair-on-open. Best-effort: a probe failure never breaks a read
(the one-shot guard resets so a transient failure retries). The JS index omits
the method, so it is simply never probed.
- getIdsForFilter(filter, opts?: { limit?; offset? }) — brainy passes a page
bound on the UNSORTED find({ type, where, limit }) path so a native provider can
early-stop and return only the [0, limit) prefix, killing the O(N) FFI marshal
at billion scale (pairs with cor #75). brainy passes offset:0 and ALWAYS
re-windows the result itself (visibility filter + slice); the JS index ignores
opts and returns all matches (behaviour unchanged).
New unit tests cover brainy's call behaviour for both (probe→repair on false,
healthy→no-repair, failure-is-best-effort, once-per-brain; opts passed with
offset 0 on the unsorted path). Full gate green: unit 1718, integration 607.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-29 12:11:00 -07:00
* Get IDs matching a Brainy Field Operator metadata filter using indexes where possible .
* The optional ` _opts ` page bound is part of the provider contract for the native
* index ( early - stop at ` offset+limit ` ) ; the JS index returns ALL matches and lets
* the caller window them , so ` _opts ` is intentionally ignored here .
2025-08-26 12:32:21 -07:00
* /
feat(8.0): wire the two cor-confirmed metadata-provider contract additions
Both shapes confirmed with cor for the lockstep (cor builds the native side
against these; the JS index is a no-op / unchanged):
- probeConsistency?(): Promise<boolean> — OPTIONAL O(1) cold-open consistency
sampler on MetadataIndexProvider. brainy calls it ONCE per brain on the first
read; on `false` it self-heals via detectAndRepairCorruption() — the metadata
counterpart of the 7.33.2 graph cold-load guard, completing the phantom triad's
detect-and-repair-on-open. Best-effort: a probe failure never breaks a read
(the one-shot guard resets so a transient failure retries). The JS index omits
the method, so it is simply never probed.
- getIdsForFilter(filter, opts?: { limit?; offset? }) — brainy passes a page
bound on the UNSORTED find({ type, where, limit }) path so a native provider can
early-stop and return only the [0, limit) prefix, killing the O(N) FFI marshal
at billion scale (pairs with cor #75). brainy passes offset:0 and ALWAYS
re-windows the result itself (visibility filter + slice); the JS index ignores
opts and returns all matches (behaviour unchanged).
New unit tests cover brainy's call behaviour for both (probe→repair on false,
healthy→no-repair, failure-is-best-effort, once-per-brain; opts passed with
offset 0 on the unsorted path). Full gate green: unit 1718, integration 607.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-29 12:11:00 -07:00
async getIdsForFilter ( filter : any , _opts ? : { limit? : number ; offset? : number } ) : Promise < string [ ] > {
2025-08-26 12:32:21 -07:00
if ( ! filter || Object . keys ( filter ) . length === 0 ) {
return [ ]
}
// Handle logical operators
if ( filter . allOf && Array . isArray ( filter . allOf ) ) {
// For allOf, we need intersection of all sub-filters
const allIds : string [ ] [ ] = [ ]
for ( const subFilter of filter . allOf ) {
const subIds = await this . getIdsForFilter ( subFilter )
allIds . push ( subIds )
}
if ( allIds . length === 0 ) return [ ]
if ( allIds . length === 1 ) return allIds [ 0 ]
2026-02-01 16:23:49 -08:00
// Set-based intersection O(n) — start with smallest set for optimal perf
const sorted = allIds . sort ( ( a , b ) = > a . length - b . length )
let result = new Set ( sorted [ 0 ] )
for ( let i = 1 ; i < sorted . length ; i ++ ) {
const current = new Set ( sorted [ i ] )
result = new Set ( [ . . . result ] . filter ( id = > current . has ( id ) ) )
}
return Array . from ( result )
2025-08-26 12:32:21 -07:00
}
2025-11-25 12:37:21 -08:00
2025-08-26 12:32:21 -07:00
if ( filter . anyOf && Array . isArray ( filter . anyOf ) ) {
// For anyOf, we need union of all sub-filters
const unionIds = new Set < string > ( )
for ( const subFilter of filter . anyOf ) {
const subIds = await this . getIdsForFilter ( subFilter )
subIds . forEach ( id = > unionIds . add ( id ) )
}
2025-11-25 12:37:21 -08:00
2026-01-27 15:38:21 -08:00
// Fix - Check for outer-level field conditions that need AND application
2025-11-25 12:37:21 -08:00
// This handles cases like { anyOf: [...], vfsType: { exists: false } }
// where the anyOf results must be intersected with other field conditions
const outerFields = Object . keys ( filter ) . filter (
( k ) = > k !== 'anyOf' && k !== 'allOf' && k !== 'not'
)
if ( outerFields . length > 0 ) {
// Build filter with just outer fields and get matching IDs
const outerFilter : any = { }
for ( const field of outerFields ) {
outerFilter [ field ] = filter [ field ]
}
const outerIds = await this . getIdsForFilter ( outerFilter )
const outerIdSet = new Set ( outerIds )
// Intersect: anyOf union AND outer field conditions
return Array . from ( unionIds ) . filter ( ( id ) = > outerIdSet . has ( id ) )
}
2025-08-26 12:32:21 -07:00
return Array . from ( unionIds )
}
2025-11-25 12:37:21 -08:00
2025-08-26 12:32:21 -07:00
// Process field filters with range support
const idSets : string [ ] [ ] = [ ]
2026-05-15 12:31:28 -07:00
// Capture field-not-indexed warnings so we log once per find() call,
// not once per AND-clause inside it.
const unindexedFields : string [ ] = [ ]
fix: one field-resolution law across aggregation hooks, source.where, removeMany, and find() spellings
Four fixes from a consumer conformance report, one root disease — two
field-resolution regimes where there must be one:
- The delete/update aggregation hooks fed the engine a partial entity
view (type/service/data/metadata only), so a reserved-field groupBy
(subtype, visibility, ...) resolved to a nonexistent group on the way
down: counts drifted upward forever after deletes, and updates moving
an entity between reserved-field groups double-counted. The hooks now
pass the full-fidelity view via entityForAggFromRawRecord (every
reserved field top-level, mirroring the add path); the update sites
pass the full get() view instead of a hand-rolled subset.
- Aggregation source.where resolved fields only against the custom
metadata bag, so where on a reserved field silently matched nothing.
The matcher now resolves each filtered field through
resolveEntityField — the same single source of truth groupBy uses.
- removeMany() with no usable selector (bare array passed positionally,
empty params, ids: []) resolved successfully having deleted nothing.
All three now throw; the two legacy tests that pinned the silent
no-op as 'graceful' now pin the refusal.
- find() where keys accept both spellings: a metadata.-prefixed key
falls back to its flattened spelling when the prefixed one is not
indexed (metadata is flattened at index time). A literal nested custom
key named metadata still wins when indexed as spelled.
Five regression pins in aggregate-reserved-fields.test.ts (4 of 5 vary
red on the unfixed code).
2026-07-19 10:54:36 -07:00
for ( const [ rawField , condition ] of Object . entries ( filter ) ) {
2025-08-26 12:32:21 -07:00
// Skip logical operators
fix: one field-resolution law across aggregation hooks, source.where, removeMany, and find() spellings
Four fixes from a consumer conformance report, one root disease — two
field-resolution regimes where there must be one:
- The delete/update aggregation hooks fed the engine a partial entity
view (type/service/data/metadata only), so a reserved-field groupBy
(subtype, visibility, ...) resolved to a nonexistent group on the way
down: counts drifted upward forever after deletes, and updates moving
an entity between reserved-field groups double-counted. The hooks now
pass the full-fidelity view via entityForAggFromRawRecord (every
reserved field top-level, mirroring the add path); the update sites
pass the full get() view instead of a hand-rolled subset.
- Aggregation source.where resolved fields only against the custom
metadata bag, so where on a reserved field silently matched nothing.
The matcher now resolves each filtered field through
resolveEntityField — the same single source of truth groupBy uses.
- removeMany() with no usable selector (bare array passed positionally,
empty params, ids: []) resolved successfully having deleted nothing.
All three now throw; the two legacy tests that pinned the silent
no-op as 'graceful' now pin the refusal.
- find() where keys accept both spellings: a metadata.-prefixed key
falls back to its flattened spelling when the prefixed one is not
indexed (metadata is flattened at index time). A literal nested custom
key named metadata still wins when indexed as spelled.
Five regression pins in aggregate-reserved-fields.test.ts (4 of 5 vary
red on the unfixed code).
2026-07-19 10:54:36 -07:00
if ( rawField === 'allOf' || rawField === 'anyOf' || rawField === 'not' ) continue
2026-08-03 15:28:24 -07:00
// THE ONE ADDRESSING LAW (sealed 2026-08-03): every filter key routes
// through parseFieldAddress — bare and 'metadata.'-prefixed spellings
// address the user's fields (indexed under BARE keys), 'system.<field>'
// addresses the ten engine scalars (indexed under their literal
// 'system.<field>' keys). A malformed address (system.<not-in-map>,
// plumbing in the system spelling) throws typed BEFORE any index read —
// an accepted name either works or refuses.
const address = parseFieldAddress ( rawField , 'entity' )
const field = address . scope === 'system' ? ` system. ${ address . field } ` : address . field
2026-05-15 12:31:28 -07:00
2025-08-26 12:32:21 -07:00
let fieldResults : string [ ] = [ ]
2026-05-15 12:31:28 -07:00
try {
// The block below evaluates one field clause. If `getIds()` throws
// FIELD_NOT_INDEXED (no column-store and no legacy sparse index for
// this field), we treat the clause as matching zero entities. This
// makes the production `find()` path consistent with the
// `brain.explain()` diagnostic: an unindexed field returns no
// results AND logs a warning, instead of silently returning [].
2025-08-26 12:32:21 -07:00
if ( condition && typeof condition === 'object' && ! Array . isArray ( condition ) ) {
2026-01-27 15:38:21 -08:00
// Handle Brainy Field Operators (canonical operators defined)
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
// See docs/api/README.md for complete operator reference
fix(8.0): real bugs surfaced by integration hardening — where-intersect, related() offset, relate() updatedAt
Three of the five bugs the rot pass surfaced (correct inputs → wrong output), fixed:
1. where-filter dropped all but the last operator on a field. getIdsForFilter()'s
per-operator loop overwrote fieldResults each iteration, so
{ year: { greaterThan: 2009, lessThan: 2020 } } kept only lessThan. Now each
operator's match set is AND-intersected (multi-operator-per-field works).
(metadataIndex.ts)
2. related({ offset }) ignored the offset — getVerbs() zeroed it and smuggled it via
an unimplemented cursor, so every page returned items [0, limit). Now the real
offset is passed through to getVerbsWithPagination (which slices [offset,+limit)).
(baseStorage.ts) — verified: get-relations-fix pagination test passes.
3. relate() never persisted updatedAt, so reads fabricated a fresh Date.now() each
call (non-idempotent). Now createdAt and updatedAt share one timestamp at create.
(brainy.ts) — verified: get-relations-fix equivalence test passes.
Follow-ups (precisely diagnosed, not papered over): exclusive range bounds —
ColumnStore.rangeQuery(field,min,max) is inclusive-only, so getIdsForRange() drops
includeMin/includeMax (metadataIndex.ts:996) and lessThan/greaterThan behave as
lte/gte when the column store is active (the dual-bound test's popularity:95 boundary
stays red); counts not rehydrating after restart; unscoped VFS path-cache.
2026-06-17 13:19:54 -07:00
//
// Multiple operators on ONE field are AND-combined (intersected): e.g.
// { greaterThan: 2009, lessThan: 2020 } requires BOTH bounds to hold. Each
// operator computes its own match set, then intersects with the running set.
let opIndex = 0
2025-08-26 12:32:21 -07:00
for ( const [ op , operand ] of Object . entries ( condition ) ) {
fix(8.0): real bugs surfaced by integration hardening — where-intersect, related() offset, relate() updatedAt
Three of the five bugs the rot pass surfaced (correct inputs → wrong output), fixed:
1. where-filter dropped all but the last operator on a field. getIdsForFilter()'s
per-operator loop overwrote fieldResults each iteration, so
{ year: { greaterThan: 2009, lessThan: 2020 } } kept only lessThan. Now each
operator's match set is AND-intersected (multi-operator-per-field works).
(metadataIndex.ts)
2. related({ offset }) ignored the offset — getVerbs() zeroed it and smuggled it via
an unimplemented cursor, so every page returned items [0, limit). Now the real
offset is passed through to getVerbsWithPagination (which slices [offset,+limit)).
(baseStorage.ts) — verified: get-relations-fix pagination test passes.
3. relate() never persisted updatedAt, so reads fabricated a fresh Date.now() each
call (non-idempotent). Now createdAt and updatedAt share one timestamp at create.
(brainy.ts) — verified: get-relations-fix equivalence test passes.
Follow-ups (precisely diagnosed, not papered over): exclusive range bounds —
ColumnStore.rangeQuery(field,min,max) is inclusive-only, so getIdsForRange() drops
includeMin/includeMax (metadataIndex.ts:996) and lessThan/greaterThan behave as
lte/gte when the column store is active (the dual-bound test's popularity:95 boundary
stays red); counts not rehydrating after restart; unscoped VFS path-cache.
2026-06-17 13:19:54 -07:00
const prevOpResults = fieldResults
fieldResults = [ ]
2025-08-26 12:32:21 -07:00
switch ( op ) {
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
// ===== EQUALITY OPERATORS =====
refactor(8.0): remove the 4 deprecated query-operator aliases (clean break)
8.0 keeps the canonical operators (eq/ne/gt/gte/lt/lte) and their clean
long-form aliases (equals/notEquals/greaterThan/greaterThanOrEqual/lessThan/
lessThanOrEqual), and drops the four redundant deprecated spellings:
is → eq, isNot → ne, greaterEqual → gte, lessEqual → lte
Removed from every evaluator (metadataIndex criteria + range switches,
metadataFilter, the db whereMatcher egress path) and from the
BrainyFieldOperators type, the unsupported-operator error message, the docs
(QUERY_OPERATORS / api README / VFS projection + semantic guides), and the
whereMatcher alias tests. Also migrated Brainy's own internal use — the VFS
TemporalProjection queried with greaterEqual/lessEqual, which would have
silently broken — to gte/lte.
Full gate green: build, unit 1512, integration 607.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-29 10:29:20 -07:00
// Canonical: 'eq' | Alias: 'equals'
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
case 'equals' : // Alias for 'eq'
2025-08-26 12:32:21 -07:00
case 'eq' :
fieldResults = await this . getIds ( field , operand )
break
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
// ===== NEGATION OPERATORS =====
refactor(8.0): remove the 4 deprecated query-operator aliases (clean break)
8.0 keeps the canonical operators (eq/ne/gt/gte/lt/lte) and their clean
long-form aliases (equals/notEquals/greaterThan/greaterThanOrEqual/lessThan/
lessThanOrEqual), and drops the four redundant deprecated spellings:
is → eq, isNot → ne, greaterEqual → gte, lessEqual → lte
Removed from every evaluator (metadataIndex criteria + range switches,
metadataFilter, the db whereMatcher egress path) and from the
BrainyFieldOperators type, the unsupported-operator error message, the docs
(QUERY_OPERATORS / api README / VFS projection + semantic guides), and the
whereMatcher alias tests. Also migrated Brainy's own internal use — the VFS
TemporalProjection queried with greaterEqual/lessEqual, which would have
silently broken — to gte/lte.
Full gate green: build, unit 1512, integration 607.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-29 10:29:20 -07:00
// Canonical: 'ne' | Alias: 'notEquals'
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
case 'notEquals' : // Alias for 'ne'
2026-02-01 16:23:49 -08:00
case 'ne' : {
2026-06-29 11:19:18 -07:00
// All ids EXCEPT those matching the value. Important for soft delete:
// `deleted !== true` must include items WITHOUT a deleted field. The
// excluded set is typically small (the matching value); compute the
// complement as a bitmap difference over the int-id universe rather
// than materializing the whole corpus as UUID strings to filter it.
const excludeInts : number [ ] = [ ]
for ( const uuid of await this . getIds ( field , operand ) ) {
const intId = this . idMapper . getInt ( uuid )
if ( intId !== undefined ) excludeInts . push ( intId )
}
fieldResults = this . complementIds ( excludeInts )
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
break
2026-02-01 16:23:49 -08:00
}
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
// ===== MULTI-VALUE OPERATORS =====
// Canonical: 'in' | Alias: 'oneOf'
case 'oneOf' : // Alias for 'in'
2025-08-26 12:32:21 -07:00
case 'in' :
if ( Array . isArray ( operand ) ) {
const unionIds = new Set < string > ( )
for ( const value of operand ) {
const ids = await this . getIds ( field , value )
ids . forEach ( id = > unionIds . add ( id ) )
}
fieldResults = Array . from ( unionIds )
}
break
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
// ===== GREATER THAN OPERATORS =====
// Canonical: 'gt' | Alias: 'greaterThan'
case 'greaterThan' : // Alias for 'gt'
2025-08-26 12:32:21 -07:00
case 'gt' :
fieldResults = await this . getIdsForRange ( field , operand , undefined , false , true )
break
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
// ===== GREATER THAN OR EQUAL OPERATORS =====
refactor(8.0): remove the 4 deprecated query-operator aliases (clean break)
8.0 keeps the canonical operators (eq/ne/gt/gte/lt/lte) and their clean
long-form aliases (equals/notEquals/greaterThan/greaterThanOrEqual/lessThan/
lessThanOrEqual), and drops the four redundant deprecated spellings:
is → eq, isNot → ne, greaterEqual → gte, lessEqual → lte
Removed from every evaluator (metadataIndex criteria + range switches,
metadataFilter, the db whereMatcher egress path) and from the
BrainyFieldOperators type, the unsupported-operator error message, the docs
(QUERY_OPERATORS / api README / VFS projection + semantic guides), and the
whereMatcher alias tests. Also migrated Brainy's own internal use — the VFS
TemporalProjection queried with greaterEqual/lessEqual, which would have
silently broken — to gte/lte.
Full gate green: build, unit 1512, integration 607.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-29 10:29:20 -07:00
// Canonical: 'gte' | Alias: 'greaterThanOrEqual'
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
case 'greaterThanOrEqual' : // Alias for 'gte'
2025-08-26 12:32:21 -07:00
case 'gte' :
fieldResults = await this . getIdsForRange ( field , operand , undefined , true , true )
break
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
// ===== LESS THAN OPERATORS =====
// Canonical: 'lt' | Alias: 'lessThan'
case 'lessThan' : // Alias for 'lt'
2025-08-26 12:32:21 -07:00
case 'lt' :
fieldResults = await this . getIdsForRange ( field , undefined , operand , true , false )
break
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
// ===== LESS THAN OR EQUAL OPERATORS =====
refactor(8.0): remove the 4 deprecated query-operator aliases (clean break)
8.0 keeps the canonical operators (eq/ne/gt/gte/lt/lte) and their clean
long-form aliases (equals/notEquals/greaterThan/greaterThanOrEqual/lessThan/
lessThanOrEqual), and drops the four redundant deprecated spellings:
is → eq, isNot → ne, greaterEqual → gte, lessEqual → lte
Removed from every evaluator (metadataIndex criteria + range switches,
metadataFilter, the db whereMatcher egress path) and from the
BrainyFieldOperators type, the unsupported-operator error message, the docs
(QUERY_OPERATORS / api README / VFS projection + semantic guides), and the
whereMatcher alias tests. Also migrated Brainy's own internal use — the VFS
TemporalProjection queried with greaterEqual/lessEqual, which would have
silently broken — to gte/lte.
Full gate green: build, unit 1512, integration 607.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-29 10:29:20 -07:00
// Canonical: 'lte' | Alias: 'lessThanOrEqual'
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
case 'lessThanOrEqual' : // Alias for 'lte'
2025-08-26 12:32:21 -07:00
case 'lte' :
fieldResults = await this . getIdsForRange ( field , undefined , operand , true , true )
break
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
// ===== RANGE OPERATOR =====
// between: [min, max] - inclusive range query
2025-08-26 12:32:21 -07:00
case 'between' :
if ( Array . isArray ( operand ) && operand . length === 2 ) {
fieldResults = await this . getIdsForRange ( field , operand [ 0 ] , operand [ 1 ] , true , true )
}
break
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
// ===== ARRAY CONTAINS OPERATOR =====
// contains: value - check if array field contains value
2025-08-26 12:32:21 -07:00
case 'contains' :
fieldResults = await this . getIds ( field , operand )
break
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
// ===== EXISTENCE OPERATOR =====
// exists: boolean - check if field exists (any value)
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
case 'exists' : {
// Column store path: rangeQuery with no bounds returns all IDs for the field
const existsBitmap = ( this . columnStore && this . columnStore . hasField ( field ) )
? await this . columnStore . rangeQuery ( field )
: await this . getExistsBitmapLegacy ( field )
2025-10-13 15:31:03 -07:00
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
if ( operand ) {
// exists: true — entities that HAVE this field
fieldResults = this . idMapper . intsIterableToUuids ( existsBitmap )
2025-11-13 11:06:59 -08:00
} else {
2026-06-29 11:19:18 -07:00
// exists: false — entities that DON'T have this field (universe \ has-field)
fieldResults = this . complementIds ( existsBitmap )
2025-11-13 11:06:59 -08:00
}
break
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
}
2025-11-13 11:06:59 -08:00
// ===== MISSING OPERATOR =====
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// missing: boolean - equivalent to exists: !boolean
case 'missing' : {
const missingBitmap = ( this . columnStore && this . columnStore . hasField ( field ) )
? await this . columnStore . rangeQuery ( field )
: await this . getExistsBitmapLegacy ( field )
2025-11-13 11:06:59 -08:00
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
if ( operand ) {
2026-06-29 11:19:18 -07:00
// missing: true — entities that DON'T have this field (universe \ has-field)
fieldResults = this . complementIds ( missingBitmap )
2025-11-13 11:06:59 -08:00
} else {
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// missing: false — entities that HAVE this field (same as exists: true)
fieldResults = this . idMapper . intsIterableToUuids ( missingBitmap )
2025-08-26 12:32:21 -07:00
}
break
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
}
2025-08-26 12:32:21 -07:00
}
fix(8.0): real bugs surfaced by integration hardening — where-intersect, related() offset, relate() updatedAt
Three of the five bugs the rot pass surfaced (correct inputs → wrong output), fixed:
1. where-filter dropped all but the last operator on a field. getIdsForFilter()'s
per-operator loop overwrote fieldResults each iteration, so
{ year: { greaterThan: 2009, lessThan: 2020 } } kept only lessThan. Now each
operator's match set is AND-intersected (multi-operator-per-field works).
(metadataIndex.ts)
2. related({ offset }) ignored the offset — getVerbs() zeroed it and smuggled it via
an unimplemented cursor, so every page returned items [0, limit). Now the real
offset is passed through to getVerbsWithPagination (which slices [offset,+limit)).
(baseStorage.ts) — verified: get-relations-fix pagination test passes.
3. relate() never persisted updatedAt, so reads fabricated a fresh Date.now() each
call (non-idempotent). Now createdAt and updatedAt share one timestamp at create.
(brainy.ts) — verified: get-relations-fix equivalence test passes.
Follow-ups (precisely diagnosed, not papered over): exclusive range bounds —
ColumnStore.rangeQuery(field,min,max) is inclusive-only, so getIdsForRange() drops
includeMin/includeMax (metadataIndex.ts:996) and lessThan/greaterThan behave as
lte/gte when the column store is active (the dual-bound test's popularity:95 boundary
stays red); counts not rehydrating after restart; unscoped VFS path-cache.
2026-06-17 13:19:54 -07:00
// Intersect this operator's matches with the running set (AND semantics
// for multiple operators on the same field).
if ( opIndex > 0 ) {
const prevSet = new Set ( prevOpResults )
fieldResults = fieldResults . filter ( ( id ) = > prevSet . has ( id ) )
}
opIndex ++
2025-08-26 12:32:21 -07:00
}
} else {
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
// Direct value match (shorthand for 'eq' operator)
2025-08-26 12:32:21 -07:00
fieldResults = await this . getIds ( field , condition )
}
2026-05-15 12:31:28 -07:00
} catch ( err ) {
if ( err instanceof BrainyError && err . type === 'FIELD_NOT_INDEXED' ) {
unindexedFields . push ( field )
fieldResults = [ ]
} else {
throw err
}
}
2025-08-26 12:32:21 -07:00
if ( fieldResults . length > 0 ) {
idSets . push ( fieldResults )
} else {
// If any field has no matches, intersection will be empty
2026-05-15 12:31:28 -07:00
if ( unindexedFields . length > 0 ) {
prodLog . warn (
` [brainy] find() where-clause referenced unindexed field(s): ` +
` ${ unindexedFields . join ( ', ' ) } . Returning []. Use ` +
` brain.explain({ where: {...} }) for diagnostics. `
)
}
2025-08-26 12:32:21 -07:00
return [ ]
}
}
2026-05-15 12:31:28 -07:00
2025-08-26 12:32:21 -07:00
if ( idSets . length === 0 ) return [ ]
2026-05-15 12:31:28 -07:00
if ( unindexedFields . length > 0 ) {
prodLog . warn (
` [brainy] find() where-clause referenced unindexed field(s) ` +
` ${ unindexedFields . join ( ', ' ) } ; their clauses contributed no rows. ` +
` Use brain.explain({ where: {...} }) for diagnostics. `
)
}
2025-08-26 12:32:21 -07:00
if ( idSets . length === 1 ) return idSets [ 0 ]
2026-02-01 16:23:49 -08:00
// Set-based intersection O(n) — start with smallest set for optimal perf
const sortedSets = idSets . sort ( ( a , b ) = > a . length - b . length )
let resultSet = new Set ( sortedSets [ 0 ] )
for ( let i = 1 ; i < sortedSets . length ; i ++ ) {
const current = new Set ( sortedSets [ i ] )
resultSet = new Set ( [ . . . resultSet ] . filter ( id = > current . has ( id ) ) )
}
return Array . from ( resultSet )
2025-08-26 12:32:21 -07:00
}
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
/ * *
* Legacy helper : get all entity int IDs that have any value for a field ,
* using the sparse index . Used by exists / missing operators when the
* column store doesn ' t have data for the field .
*
* @param field - Field name
* @returns Roaring bitmap of entity int IDs ( or iterable for compatibility )
* @private
* /
2026-06-29 11:19:18 -07:00
/ * *
* All ids EXCEPT the excluded int - id set , computed as a roaring - bitmap difference
* over the int - id universe . Used by the negation / absence operators ( ` ne ` ,
* ` exists:false ` , ` missing:true ` ) so they don ' t first materialize the ENTIRE
* corpus as an array of UUID strings ( plus a Set , plus an O ( N ) filter pass ) just
* to remove a small subset — only the final result is converted back to UUIDs .
* /
private complementIds ( excludeInts : Iterable < number > ) : string [ ] {
const universe = new RoaringBitmap32 ( )
for ( const intId of this . idMapper . getAllIntIds ( ) ) universe . add ( intId )
const exclude = new RoaringBitmap32 ( )
for ( const intId of excludeInts ) exclude . add ( intId )
return this . idMapper . intsIterableToUuids ( RoaringBitmap32 . andNot ( universe , exclude ) )
}
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
private async getExistsBitmapLegacy ( field : string ) : Promise < Iterable < number > > {
const allIntIds = new Set < number > ( )
const sparseIndex = await this . loadSparseIndex ( field )
if ( sparseIndex ) {
for ( const chunkId of sparseIndex . getAllChunkIds ( ) ) {
const chunk = await this . chunkManager . loadChunk ( field , chunkId )
if ( chunk ) {
for ( const bitmap of chunk . entries . values ( ) ) {
for ( const intId of bitmap ) {
allIntIds . add ( intId )
}
}
}
}
}
return allIntIds
}
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
/ * *
* Get filtered IDs sorted by a field ( production - scale sorting )
*
* * * Performance Characteristics * * ( designed for billions of entities ) :
* - * * Filtering * * : O ( log n ) using roaring bitmaps with SIMD acceleration
* - * * Field Loading * * : O ( k ) where k = filtered result count ( NOT O ( n ) )
* - * * Sorting * * : O ( k log k ) in - memory ( IDs + sort values only , NOT full entities )
* - * * Memory * * : O ( k ) for k filtered results , independent of total entity count
*
* * * Scalability * * :
* - Total entities : Billions ( memory usage unaffected )
* - Filtered set : Up to 10 M ( reasonable for in - memory sort of ID + value pairs )
* - Pagination : Happens AFTER sorting , so only page entities are loaded
*
* * * Example * * :
* ` ` ` typescript
* // Production-scale: 1B entities, 100K match filter, sort by createdAt
* const sortedIds = await metadataIndex . getSortedIdsForFilter (
* { status : 'published' , category : 'AI' } ,
* 'createdAt' ,
* 'desc'
* )
* // Returns: 100K sorted IDs
* // Memory: ~5MB (100K IDs + 100K timestamps)
* // Then caller paginates: sortedIds.slice(0, 20) and loads only 20 entities
* ` ` `
*
* @param filter - Metadata filter criteria ( uses roaring bitmaps )
* @param orderBy - Field name to sort by ( e . g . , 'createdAt' , 'title' )
* @param order - Sort direction : 'asc' ( default ) or 'desc'
2026-06-23 15:01:49 -07:00
* @param topK - Optional page bound : produce only the top ` K ` sorted ids
* ( ` offset + limit ` ) instead of the full sorted match set . A broad filter +
* orderBy that returns one page no longer materializes hundreds of millions of
* sorted ids at billion scale — the column store ' s top - K heap produces only the
* page . Omit for the full sorted set .
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
* @returns Promise < string [ ] > - Entity IDs sorted by specified field
*
* /
2026-08-04 16:40:48 -07:00
/ * *
* Resolve the orderBy value for MANY entities in BATCHED metadata - record
* reads — the sort path ' s one sanctioned value source ( BRAINY - PROD - LATENCY - TRIAD ) .
*
* THE ASYMPTOTIC LAW THIS ENFORCES : an ordered read never does per - row
* storage round - trips . The previous shape — ` await getFieldValueForEntity `
* per id , each opening the VECTOR record serially — cost 62 – 98 ms × N on a
* production filesystem brain : 3 , 224 rows took 199 – 317 SECONDS , silently .
* The metadata RECORD ( smaller , cached , batch - readable ) carries everything
* a sort can address : the ten system scalars top - level — EXACT values , no
* bucketing loss — and the user ' s bag ( v2 nested or legacy flat , resolved
* through the shape - aware split ) . One batched read pass serves any N .
*
* The call - shape is pinned by tests ( zero per - row reads , batch calls only )
* so the serial loop cannot quietly return .
*
* @param ids - Entity ids to resolve ( any size ; reads are chunk - batched ) .
* @param orderAddress - The parsed orderBy address ( system or metadata scope ) .
* @returns id → value map ; ids whose record is missing map to ` undefined `
* ( they sort LAST per the ordering contract — never dropped ) .
* /
private async resolveOrderValuesBatch (
ids : string [ ] ,
orderAddress : FieldAddress
) : Promise < Map < string , unknown > > {
const values = new Map < string , unknown > ( )
if ( ids . length === 0 ) return values
// Batch door, best first: BaseStorage's getNounMetadataBatch (native
// batch or parallel reads inside), then the adapter-optional
// getMetadataBatch, then chunked-parallel single reads — NEVER serial.
const storage = this . storage as StorageAdapter & {
getNounMetadataBatch ? ( ids : string [ ] ) : Promise < Map < string , NounMetadata > >
}
const CHUNK = 500
const records = new Map < string , NounMetadata > ( )
for ( let i = 0 ; i < ids . length ; i += CHUNK ) {
const chunk = ids . slice ( i , i + CHUNK )
if ( typeof storage . getNounMetadataBatch === 'function' ) {
const batch = await storage . getNounMetadataBatch ( chunk )
for ( const [ id , rec ] of batch ) records . set ( id , rec )
} else if ( typeof storage . getMetadataBatch === 'function' ) {
const batch = await storage . getMetadataBatch ( chunk )
for ( const [ id , rec ] of batch ) records . set ( id , rec )
} else {
const loaded = await Promise . all (
chunk . map ( async ( id ) = > [ id , await storage . getNounMetadata ( id ) ] as const )
)
for ( const [ id , rec ] of loaded ) if ( rec ) records . set ( id , rec )
}
}
for ( const id of ids ) {
const record = records . get ( id )
if ( ! record ) {
values . set ( id , undefined )
continue
}
// Shape-aware split serves both record eras: engine scalars from the
// reserved half (EXACT timestamps — the bucketed index is never
// consulted here), user fields from the bag.
const { reserved , custom } = splitNounMetadataRecord (
record as Record < string , unknown >
)
if ( orderAddress . scope === 'system' ) {
values . set (
id ,
orderAddress . field === 'type'
? reserved . noun
: ( reserved as Record < string , unknown > ) [ orderAddress . field ]
)
} else {
let value : unknown = custom [ orderAddress . field ]
if ( value === undefined && orderAddress . field . includes ( '.' ) ) {
// Dotted user path: traverse INSIDE the bag.
value = orderAddress . field
. split ( '.' )
. reduce < unknown > (
( o , seg ) = >
o && typeof o === 'object' ? ( o as Record < string , unknown > ) [ seg ] : undefined ,
custom
)
}
values . set ( id , value )
}
}
return values
}
/** Once-per-field flag for the fallback-degradation announcement. */
private static announcedFallbackSorts = new Set < string > ( )
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
async getSortedIdsForFilter (
filter : any ,
orderBy : string ,
2026-06-23 15:01:49 -07:00
order : 'asc' | 'desc' = 'asc' ,
topK? : number
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
) : Promise < string [ ] > {
2026-08-03 15:28:24 -07:00
// THE ONE ADDRESSING LAW — the orderBy address routes through the same
// parse the filter path uses (the historical asymmetry where the filter
// path understood 'metadata.' but the sorted path never did is dead).
// Bare / 'metadata.' → the user's bare index key; 'system.<field>' → the
// literal frozen key; malformed addresses throw typed before any read.
const orderAddress = parseFieldAddress ( orderBy , 'entity' )
const orderKey =
orderAddress . scope === 'system' ? ` system. ${ orderAddress . field } ` : orderAddress . field
2026-08-03 16:01:02 -07:00
// DATA-AWARE REFUSAL (the did-you-mean): a bare address no user field
// carries cannot mean anything as a sort key — and when the name collides
// with a system scalar the caller almost certainly meant system.<field>.
// Refusing loudly with both candidates beats silently sorting nothing.
if (
orderAddress . scope === 'metadata' &&
! ( this . columnStore && this . columnStore . hasField ( orderKey ) ) &&
! ( await this . loadSparseIndex ( orderKey ) )
) {
throw new UnresolvableFieldError ( orderAddress . raw , 'entity' )
}
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// Column store path: O(K log S) sort via k-way merge across segments.
// No per-entity storage reads, no precision loss from bucketing.
2026-08-03 15:28:24 -07:00
if ( this . columnStore && this . columnStore . hasField ( orderKey ) ) {
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// Get filtered IDs from existing roaring bitmap path
const hasFilter = filter && Object . keys ( filter ) . length > 0
const filteredIds = hasFilter ? await this . getIdsForFilter ( filter ) : [ ]
if ( hasFilter && filteredIds . length === 0 ) return [ ]
feat(8.0): u64 BigInt graph provider contract — punch list a-d,g,h
GraphIndexProvider now speaks BigInt at the boundary (D.2 mirror):
- getNeighbors/getVerbIdsBySource/getVerbIdsByTarget take entity ints and
return entity/verb ints as bigint[]
- new REQUIRED verbIntsToIds(bigint[]) batch reverse resolver (L.7
identity-fingerprint design — verb ids are UUIDs by contract, so the
provider-side interning is losslessly reversible)
- addVerb(verb, sourceInt, targetInt) returns the interned verb int;
removeVerb(verbId) joins the contract
Coordinator (brainy.ts) owns ALL UUID <-> int conversion: getOrAssign on
writes, getInt on reads (unmapped UUID -> empty result without calling the
provider), getUuid / verbIntsToIds on returns, plus a bounded ~100k-entry
insertion-order warm cache for verb-int -> verb-id pairs fed by addVerb
returns and resolver results. GraphVerb gains derived sourceInt/targetInt
(populated at add time, never persisted). findConnectedSubtype gains a
native fast path that routes single-type single-subtype outgoing BFS
through the provider when available.
JS GraphAdjacencyIndex satisfies the contract while staying string/u32-keyed
internally: entity ints resolve through the shared entity-id mapper (threaded
in by the coordinator on init/fork/checkout), verb ints come from an
in-process append-only interning map re-derived from storage on
rebuild/cold-start. ColumnStoreProvider widens the same way: addEntity/
removeEntity take bigint, sortTopK/filteredSortTopK return bigint[].
relate() now rejects a caller-supplied id with a teaching error — verb ids
are brainy-generated UUIDs by contract in 8.0 (previously a passed id was
silently ignored). No Roaring64 provider-boundary decode site exists yet;
the JS-internal column store stays Roaring32 and the Treemap decoder lands
with the first consumer of provider-returned filter buffers.
Public brain API unchanged. 1413 tests green (+10 new BigInt contract tests).
2026-06-10 10:45:45 -07:00
let sortedIntIds : bigint [ ]
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
if ( hasFilter ) {
// Build filter bitmap for the column store
const filterBitmap = new RoaringBitmap32 ( )
for ( const id of filteredIds ) {
const intId = this . idMapper . getInt ( id )
if ( intId !== undefined ) filterBitmap . add ( intId )
}
2026-06-23 15:01:49 -07:00
// Page-bounded: produce only the top `topK` (offset+limit), not every
// match, so a broad filter + orderBy returning one page stays O(matches
// log K) heap, not a full sort materialization.
const k = topK !== undefined ? Math . min ( topK , filteredIds . length ) : filteredIds . length
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
sortedIntIds = await this . columnStore . filteredSortTopK (
2026-08-03 15:28:24 -07:00
filterBitmap , orderKey , order , k
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
)
} else {
// Unfiltered sort — column store handles the full entity set efficiently
sortedIntIds = await this . columnStore . sortTopK (
2026-08-03 15:28:24 -07:00
orderKey , order , topK !== undefined ? Math . min ( topK , this . idMapper . size ) : this . idMapper . size
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
)
}
feat(8.0): u64 BigInt graph provider contract — punch list a-d,g,h
GraphIndexProvider now speaks BigInt at the boundary (D.2 mirror):
- getNeighbors/getVerbIdsBySource/getVerbIdsByTarget take entity ints and
return entity/verb ints as bigint[]
- new REQUIRED verbIntsToIds(bigint[]) batch reverse resolver (L.7
identity-fingerprint design — verb ids are UUIDs by contract, so the
provider-side interning is losslessly reversible)
- addVerb(verb, sourceInt, targetInt) returns the interned verb int;
removeVerb(verbId) joins the contract
Coordinator (brainy.ts) owns ALL UUID <-> int conversion: getOrAssign on
writes, getInt on reads (unmapped UUID -> empty result without calling the
provider), getUuid / verbIntsToIds on returns, plus a bounded ~100k-entry
insertion-order warm cache for verb-int -> verb-id pairs fed by addVerb
returns and resolver results. GraphVerb gains derived sourceInt/targetInt
(populated at add time, never persisted). findConnectedSubtype gains a
native fast path that routes single-type single-subtype outgoing BFS
through the provider when available.
JS GraphAdjacencyIndex satisfies the contract while staying string/u32-keyed
internally: entity ints resolve through the shared entity-id mapper (threaded
in by the coordinator on init/fork/checkout), verb ints come from an
in-process append-only interning map re-derived from storage on
rebuild/cold-start. ColumnStoreProvider widens the same way: addEntity/
removeEntity take bigint, sortTopK/filteredSortTopK return bigint[].
relate() now rejects a caller-supplied id with a teaching error — verb ids
are brainy-generated UUIDs by contract in 8.0 (previously a passed id was
silently ignored). No Roaring64 provider-boundary decode site exists yet;
the JS-internal column store stays Roaring32 and the Treemap decoder lands
with the first consumer of provider-returned filter buffers.
Public brain API unchanged. 1413 tests green (+10 new BigInt contract tests).
2026-06-10 10:45:45 -07:00
// Convert int IDs back to UUIDs. Number() narrowing is lossless — the
// shipped EntityIdSpaceExceeded guard caps the JS mapper at u32.
2026-08-03 16:01:02 -07:00
const sortedUuids = sortedIntIds
feat(8.0): u64 BigInt graph provider contract — punch list a-d,g,h
GraphIndexProvider now speaks BigInt at the boundary (D.2 mirror):
- getNeighbors/getVerbIdsBySource/getVerbIdsByTarget take entity ints and
return entity/verb ints as bigint[]
- new REQUIRED verbIntsToIds(bigint[]) batch reverse resolver (L.7
identity-fingerprint design — verb ids are UUIDs by contract, so the
provider-side interning is losslessly reversible)
- addVerb(verb, sourceInt, targetInt) returns the interned verb int;
removeVerb(verbId) joins the contract
Coordinator (brainy.ts) owns ALL UUID <-> int conversion: getOrAssign on
writes, getInt on reads (unmapped UUID -> empty result without calling the
provider), getUuid / verbIntsToIds on returns, plus a bounded ~100k-entry
insertion-order warm cache for verb-int -> verb-id pairs fed by addVerb
returns and resolver results. GraphVerb gains derived sourceInt/targetInt
(populated at add time, never persisted). findConnectedSubtype gains a
native fast path that routes single-type single-subtype outgoing BFS
through the provider when available.
JS GraphAdjacencyIndex satisfies the contract while staying string/u32-keyed
internally: entity ints resolve through the shared entity-id mapper (threaded
in by the coordinator on init/fork/checkout), verb ints come from an
in-process append-only interning map re-derived from storage on
rebuild/cold-start. ColumnStoreProvider widens the same way: addEntity/
removeEntity take bigint, sortTopK/filteredSortTopK return bigint[].
relate() now rejects a caller-supplied id with a teaching error — verb ids
are brainy-generated UUIDs by contract in 8.0 (previously a passed id was
silently ignored). No Roaring64 provider-boundary decode site exists yet;
the JS-internal column store stays Roaring32 and the Treemap decoder lands
with the first consumer of provider-returned filter buffers.
Public brain API unchanged. 1413 tests green (+10 new BigInt contract tests).
2026-06-10 10:45:45 -07:00
. map ( intId = > this . idMapper . getUuid ( Number ( intId ) ) )
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
. filter ( ( uuid ) : uuid is string = > uuid !== undefined )
2026-08-03 16:01:02 -07:00
// ORDERING CONTRACT (cross-engine, sealed): rows missing the field are
// NEVER dropped — they sort LAST in both directions — and ties break by
// id ascending. The column only contains rows that HAVE the field, so
2026-08-04 16:40:48 -07:00
// (1) re-sort the page deterministically (value, then id) via ONE
// batched value resolution — never per-row reads — and (2) append the
// filtered rows the column omitted, id-ascending, filling any
// remaining page budget.
const pageValues = await this . resolveOrderValuesBatch ( sortedUuids , orderAddress )
const page = sortedUuids . map ( id = > ( { id , value : pageValues.get ( id ) } ) )
2026-08-03 16:01:02 -07:00
page . sort ( ( a , b ) = > this . compareAddressedValues ( a . value , b . value , a . id , b . id , order ) )
let result = page . map ( p = > p . id )
if ( hasFilter ) {
const present = new Set ( sortedUuids )
if ( topK === undefined || result . length < topK ) {
const missing = filteredIds . filter ( id = > ! present . has ( id ) ) . sort ( )
result = result . concat ( missing )
}
}
return topK !== undefined ? result . slice ( 0 , topK ) : result
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
}
2026-08-04 16:40:48 -07:00
// Fallback: no column serves this field. BOUNDED + ANNOUNCED, never
// silent (the B2 no-silent-degradation law, BRAINY-PROD-LATENCY-TRIAD):
// O(N) in row count but served by BATCHED metadata-record reads — the
// serial per-row getNoun loop that turned 3,224 rows into a 199– 317s
// scan is dead, and the call-shape pin keeps it dead.
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
const filteredIds = await this . getIdsForFilter ( filter )
if ( filteredIds . length === 0 ) {
return [ ]
}
2026-08-04 16:40:48 -07:00
if (
filteredIds . length > 500 &&
! MetadataIndexManager . announcedFallbackSorts . has ( orderKey )
) {
MetadataIndexManager . announcedFallbackSorts . add ( orderKey )
prodLog . warn (
` [brainy] ordered read on ' ${ orderKey } ' has no column index — served by the ` +
` batched fallback over ${ filteredIds . length } rows (bounded, one batch pass; ` +
` announced once per field). A native column for this field makes it O(K). `
)
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
}
2026-08-04 16:40:48 -07:00
const fallbackValues = await this . resolveOrderValuesBatch ( filteredIds , orderAddress )
const idValuePairs = filteredIds . map ( id = > ( { id , value : fallbackValues.get ( id ) } ) )
2026-08-03 16:01:02 -07:00
idValuePairs . sort ( ( a , b ) = > this . compareAddressedValues ( a . value , b . value , a . id , b . id , order ) )
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
2026-06-23 15:01:49 -07:00
const sorted = idValuePairs . map ( p = > p . id )
return topK !== undefined ? sorted . slice ( 0 , topK ) : sorted
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
}
/ * *
* Get field value for a specific entity ( helper for sorted queries )
*
2026-04-09 16:26:38 -07:00
* Three - path lookup :
*
* 1 . * * Bucketed fields * * ( timestamps ) — the sparse index stores values
* rounded to 1 - minute buckets to keep the index compact for range
* queries . That bucketing loses precision , so sorting must read the
* actual value directly from entity storage .
*
* 2 . * * Custom fields with no sparse index * * — VFS fields like ` modified `
* and ` accessed ` , plus any user custom field whose sparse index was
* never built . Resolved from entity storage via ` resolveEntityField ` ,
* which knows the top - level - vs - metadata shape contract .
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
*
2026-04-09 16:26:38 -07:00
* 3 . * * Indexed fields * * — strings , enums , and low - cardinality ints live
* in the sparse roaring index . O ( chunks ) lookup , typically 1 - 10 chunks .
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
*
* * * Performance * * :
2026-04-09 16:26:38 -07:00
* - Paths 1 & 2 : O ( 1 ) entity load from storage ( cached )
* - Path 3 : O ( chunks ) roaring bitmap lookup
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
*
* @param entityId - Entity UUID to get field value for
* @param field - Field name to retrieve ( e . g . , 'createdAt' , 'title' )
* @returns Promise < any > - Field value or undefined if not found
*
* @public ( called from brainy . ts for sorted queries )
* /
2026-08-03 16:01:02 -07:00
/ * *
* The cross - engine ordering contract in one comparator ( sealed 2026 - 08 - 03 ) :
* missing / null values sort LAST in BOTH directions — the direction flip
* never moves them to the front — and ties break by id ascending , so an
* ordered read is deterministic and identical on both engines . Numbers
* compare numerically ; everything else by code - point ( UTF - 8 byte ) order ,
* matching the native column store exactly .
* /
private compareAddressedValues (
aVal : any ,
bVal : any ,
aId : string ,
bId : string ,
order : 'asc' | 'desc'
) : number {
const aNull = aVal == null
const bNull = bVal == null
if ( aNull || bNull ) {
if ( aNull && bNull ) return aId < bId ? - 1 : aId > bId ? 1 : 0
return aNull ? 1 : - 1
}
let comparison = 0
if ( aVal !== bVal ) {
if ( typeof aVal === 'number' && typeof bVal === 'number' ) {
comparison = aVal < bVal ? - 1 : 1
} else {
comparison = compareCodePoints ( String ( aVal ) , String ( bVal ) )
}
}
if ( comparison === 0 ) return aId < bId ? - 1 : aId > bId ? 1 : 0
return order === 'asc' ? comparison : - comparison
}
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
async getFieldValueForEntity ( entityId : string , field : string ) : Promise < any > {
2026-08-03 15:28:24 -07:00
// `field` arrives as a FROZEN INDEX KEY (bare = user metadata;
// 'system.<field>' = engine scalar). Storage fallbacks read the matching
// side of the record — a system key reads the record scalar, a bare key
// reads the user's metadata bag; the two can never shadow each other.
const systemInner = field . startsWith ( 'system.' ) ? field . slice ( 'system.' . length ) : null
// Path 1: Bucketed fields need the actual (un-bucketed) value from storage.
2026-04-09 16:26:38 -07:00
if ( BUCKETED_INDEX_FIELDS . has ( field ) ) {
const noun = await this . storage . getNoun ( entityId )
2026-08-03 15:28:24 -07:00
if ( ! noun ) return undefined
return ( noun as unknown as Record < string , unknown > ) [ systemInner as string ]
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
}
2026-04-09 16:26:38 -07:00
// Path 3 precondition: entity must be in the id mapper for bitmap lookup.
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
const intId = this . idMapper . getInt ( entityId )
if ( intId === undefined ) {
return undefined
}
2026-04-09 16:26:38 -07:00
// Load sparse index for this field (cached via UnifiedCache).
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
const sparseIndex = await this . loadSparseIndex ( field )
2026-04-09 16:26:38 -07:00
// Path 2: No sparse index exists — fall back to entity storage.
// Covers VFS custom fields (modified, accessed) and user fields not
// yet indexed. resolveEntityField handles the shape contract.
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
if ( ! sparseIndex ) {
2026-04-09 16:26:38 -07:00
const noun = await this . storage . getNoun ( entityId )
2026-08-03 15:28:24 -07:00
if ( ! noun ) return undefined
if ( systemInner !== null ) {
return ( noun as unknown as Record < string , unknown > ) [ systemInner ]
}
return ( noun as { metadata? : Record < string , unknown > } ) . metadata ? . [ field ]
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
}
2026-04-09 16:26:38 -07:00
// Path 3: Search sparse index chunks for this entity's value.
// Typically 1-10 chunks per field, so this is fast.
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
for ( const chunkId of sparseIndex . getAllChunkIds ( ) ) {
const chunk = await this . chunkManager . loadChunk ( field , chunkId )
if ( ! chunk ) continue
2026-04-09 16:26:38 -07:00
// Check each value's roaring bitmap for our entity ID.
// Roaring bitmap .has() is O(1) with SIMD optimization.
feat: add orderBy sorting and fix timestamp queries
Add production-scale sorting support with orderBy/order parameters:
- Sort by any field including createdAt, updatedAt, timestamps
- Works in both metadata-only and vector+metadata query paths
- O(k) memory complexity where k = filtered results
Fix timestamp sorting precision issue:
- Load actual timestamp values from entity metadata for sorting
- Avoids 1-minute bucketing precision loss
- Maintains bucketing for efficient range queries
Fix range query operators:
- Normalize min/max bounds before comparison with bucketed index
- Ensures gte, lte, gt, lt work correctly with timestamps
Standardize operator syntax:
- Canonical: eq, ne, gt, gte, lt, lte, in, between, contains, exists
- Deprecate: is, isNot, greaterEqual, lessEqual (remove in v5.0.0)
- Maintain backward compatibility with aliases
Test results: All sorting and range query tests pass, no regressions
2025-10-27 09:14:10 -07:00
for ( const [ value , bitmap ] of chunk . entries ) {
if ( bitmap . has ( intId ) ) {
return this . denormalizeValue ( value , field )
}
}
}
return undefined
}
/ * *
* Denormalize a value ( reverse of normalizeValue )
*
* Converts normalized / stringified values back to their original type .
* For most fields , this just parses numbers or returns strings as - is .
*
* * * NOTE * * : This is NOT used for timestamp sorting ! Timestamp fields
* ( createdAt , updatedAt ) are loaded directly from entity metadata by
* getFieldValueForEntity ( ) to avoid precision loss from bucketing .
*
* * * Timestamp Bucketing ( for range queries only ) * * :
* - Indexed as : Math . floor ( timestamp / 60000 ) * 60000
* - Used for : Range queries ( gte , lte ) where 1 - minute precision is acceptable
* - NOT used for : Sorting ( requires exact millisecond precision )
*
* @param normalized - Normalized value string from index
* @param field - Field name ( used for type inference )
* @returns Denormalized value in original type
*
* @private
* /
private denormalizeValue ( normalized : string , field : string ) : any {
// Try parsing as number (timestamps, integers, floats)
const asNumber = Number ( normalized )
if ( ! isNaN ( asNumber ) ) {
return asNumber
}
// For strings, return as-is (already denormalized)
return normalized
}
2025-08-26 12:32:21 -07:00
/ * *
* Flush dirty entries to storage ( non - blocking version )
2026-01-27 15:38:21 -08:00
* NOTE : Sparse indices are flushed immediately in add / remove operations
2025-08-26 12:32:21 -07:00
* /
async flush ( ) : Promise < void > {
2026-03-24 12:57:11 -07:00
// Always save field registry — even with no dirty fields. This tiny file
// (list of field names) is the critical link that init() needs to discover
// persisted indices. Without it, the index appears empty after restart.
if ( this . fieldIndexes . size > 0 ) {
await this . saveFieldRegistry ( )
}
// Also always flush the EntityIdMapper — prevents ID collisions on restart
await this . idMapper . flush ( )
// Check if we have anything else to flush
2025-10-13 15:31:03 -07:00
if ( this . dirtyFields . size === 0 ) {
2026-03-24 12:57:11 -07:00
return // No dirty field indexes to flush
2025-08-26 12:32:21 -07:00
}
2025-10-13 15:31:03 -07:00
2025-08-26 12:32:21 -07:00
// Process in smaller batches to avoid blocking
const BATCH_SIZE = 20
const allPromises : Promise < void > [ ] = [ ]
2025-10-13 15:31:03 -07:00
2026-01-27 15:38:21 -08:00
// Flush field indexes in batches
2025-08-26 12:32:21 -07:00
const dirtyFieldsArray = Array . from ( this . dirtyFields )
for ( let i = 0 ; i < dirtyFieldsArray . length ; i += BATCH_SIZE ) {
const batch = dirtyFieldsArray . slice ( i , i + BATCH_SIZE )
const batchPromises = batch . map ( field = > {
const fieldIndex = this . fieldIndexes . get ( field )
return fieldIndex ? this . saveFieldIndex ( field , fieldIndex ) : Promise . resolve ( )
} )
allPromises . push ( . . . batchPromises )
2025-10-13 15:31:03 -07:00
2025-08-26 12:32:21 -07:00
// Yield to event loop between batches
if ( i + BATCH_SIZE < dirtyFieldsArray . length ) {
await this . yieldToEventLoop ( )
}
}
2025-10-13 15:31:03 -07:00
2025-08-26 12:32:21 -07:00
// Wait for all operations to complete
await Promise . all ( allPromises )
2025-10-13 15:31:03 -07:00
2026-01-27 15:38:21 -08:00
// Flush EntityIdMapper (UUID ↔ integer mappings)
2025-10-13 16:39:06 -07:00
await this . idMapper . flush ( )
2026-01-27 15:38:21 -08:00
// Save field registry for fast cold-start discovery
2025-10-23 08:47:37 -07:00
await this . saveFieldRegistry ( )
2025-08-26 12:32:21 -07:00
this . dirtyFields . clear ( )
this . lastFlushTime = Date . now ( )
feat: unified column store for filtering + sorting at billion scale
Adds a per-field sorted column store (Lucene doc values + roaring bitmap
architecture) that replaces the MetadataIndex sparse index internals for
both filtering and sorting. One system for all field types with exact
precision — no bucketing, no per-entity storage reads.
Column store: binary .cidx segment format, in-memory tail buffers,
LSM-style compaction, k-way merge sort, multi-value support (__words__).
All queries (filter, range, sort, filtered sort) route through the column
store when data is available, falling back to sparse index otherwise.
Key unlocks:
- find({ orderBy: 'createdAt' }) works WITHOUT a filter (previously threw)
- find({ orderBy: 'metadata.price' }) works for custom numeric fields
- Exact timestamp precision (no 1-minute bucketing)
- O(K log S) sort independent of total entity count
New files: src/indexes/columnStore/ (types, format, tail buffer, cursor,
manifest, coordinator — ~700 lines). 101 new unit tests covering binary
format round-trips, CRC validation, sort, filter, range, deletion,
multi-segment merge, persistence, and multi-value (words) fields.
Deleted: metadataIndex-automatic-bucketing.test.ts (bucketing behavior
eliminated by exact-precision column store). Sparse index write path
removed from addToIndex/removeFromIndex. Sparse index legacy code still
present as dead code pending cleanup in next commit.
2026-04-10 11:22:19 -07:00
// Flush column store tail buffers to L0 segments
if ( this . columnStore ) {
await this . columnStore . flush ( )
}
2025-08-26 12:32:21 -07:00
}
/ * *
* Yield control back to the Node . js event loop
* Prevents blocking during long - running operations
* /
private async yieldToEventLoop ( ) : Promise < void > {
return new Promise ( resolve = > setImmediate ( resolve ) )
}
/ * *
* Load field index from storage
* /
private async loadFieldIndex ( field : string ) : Promise < FieldIndexData | null > {
const filename = this . getFieldIndexFilename ( field )
const unifiedKey = ` metadata:field: ${ filename } `
// Check unified cache first with loader function
return await this . unifiedCache . get ( unifiedKey , async ( ) = > {
try {
const cacheKey = ` field_index_ ${ filename } `
// Check old cache for migration
const cached = this . metadataCache . get ( cacheKey )
if ( cached ) {
// Add to unified cache
const size = JSON . stringify ( cached ) . length
this . unifiedCache . set ( unifiedKey , cached , 'metadata' , size , 1 ) // Low rebuild cost
return cached
}
// Load from storage
const indexId = ` __metadata_field_index__ ${ filename } `
const data = await this . storage . getMetadata ( indexId )
if ( data ) {
const fieldIndex = {
values : data.values || { } ,
lastUpdated : data.lastUpdated || Date . now ( )
}
// Add to unified cache
const size = JSON . stringify ( fieldIndex ) . length
this . unifiedCache . set ( unifiedKey , fieldIndex , 'metadata' , size , 1 )
// Also keep in old cache for now (transition period)
this . metadataCache . set ( cacheKey , fieldIndex )
return fieldIndex
}
} catch ( error ) {
// Field index doesn't exist yet
}
return null
} )
}
/ * *
2025-10-09 13:56:45 -07:00
* Save field index to storage with file locking
2025-08-26 12:32:21 -07:00
* /
private async saveFieldIndex ( field : string , fieldIndex : FieldIndexData ) : Promise < void > {
const filename = this . getFieldIndexFilename ( field )
2025-10-09 13:56:45 -07:00
const lockKey = ` field_index_ ${ field } `
const lockAcquired = await this . acquireLock ( lockKey , 5000 ) // 5 second timeout
if ( ! lockAcquired ) {
prodLog . warn (
` Failed to acquire lock for field index ' ${ field } ', proceeding without lock `
)
}
try {
const indexId = ` __metadata_field_index__ ${ filename } `
const unifiedKey = ` metadata:field: ${ filename } `
2026-01-27 15:38:21 -08:00
// Add required 'noun' property for NounMetadata
2025-10-09 13:56:45 -07:00
await this . storage . saveMetadata ( indexId , {
2025-10-17 12:29:27 -07:00
noun : 'MetadataFieldIndex' ,
2025-10-09 13:56:45 -07:00
values : fieldIndex.values ,
lastUpdated : fieldIndex.lastUpdated
2026-06-11 14:51:00 -07:00
} )
2025-10-09 13:56:45 -07:00
// Update unified cache
const size = JSON . stringify ( fieldIndex ) . length
this . unifiedCache . set ( unifiedKey , fieldIndex , 'metadata' , size , 1 )
// Invalidate old cache
this . metadataCache . invalidatePattern ( ` field_index_ ${ filename } ` )
} finally {
if ( lockAcquired ) {
await this . releaseLock ( lockKey )
}
}
2025-08-26 12:32:21 -07:00
}
2025-10-23 08:47:37 -07:00
/ * *
* Save field registry to storage for fast cold - start discovery
2026-01-27 15:38:21 -08:00
* Solves 100 x performance regression by persisting field directory
2025-10-23 08:47:37 -07:00
*
* This enables instant cold starts by discovering which fields have persisted indices
* without needing to rebuild from scratch . Similar to how HNSW persists system metadata .
*
* Registry size : ~ 4 - 8 KB for typical deployments ( 50 - 200 fields )
* Scales : O ( log N ) - field count grows logarithmically with entity count
* /
private async saveFieldRegistry ( ) : Promise < void > {
// Nothing to save if no fields indexed yet
if ( this . fieldIndexes . size === 0 ) {
return
}
try {
const registry = {
noun : 'FieldRegistry' ,
fields : Array.from ( this . fieldIndexes . keys ( ) ) ,
version : 1 ,
lastUpdated : Date.now ( ) ,
totalFields : this.fieldIndexes.size
}
await this . storage . saveMetadata ( '__metadata_field_registry__' , registry )
prodLog . debug ( ` 📝 Saved field registry: ${ registry . totalFields } fields ` )
} catch ( error ) {
// Non-critical: Log warning but don't throw
// System will rebuild registry on next cold start if needed
prodLog . warn ( 'Failed to save field registry:' , error )
}
}
/ * *
* Load field registry from storage to populate fieldIndexes directory
2026-01-27 15:38:21 -08:00
* Enables O ( 1 ) discovery of persisted sparse indices
2025-10-23 08:47:37 -07:00
*
* Called during init ( ) to discover which fields have persisted indices .
* Populates fieldIndexes Map with skeleton entries - actual sparse indices
* are lazy - loaded via UnifiedCache when first accessed .
*
* Gracefully handles missing registry ( first run or corrupted data ) .
* /
private async loadFieldRegistry ( ) : Promise < void > {
try {
const registry = await this . storage . getMetadata ( '__metadata_field_registry__' )
if ( ! registry ? . fields || ! Array . isArray ( registry . fields ) ) {
// Registry doesn't exist or is invalid - not an error, just first run
prodLog . debug ( '📂 No field registry found - will build on first flush' )
return
}
// Populate fieldIndexes Map from discovered fields
// Skeleton entries with empty values - sparse indices loaded lazily
const lastUpdated = typeof registry . lastUpdated === 'number'
? registry . lastUpdated
: Date . now ( )
for ( const field of registry . fields ) {
if ( typeof field === 'string' && field . length > 0 ) {
this . fieldIndexes . set ( field , {
values : { } ,
lastUpdated
} )
}
}
prodLog . info (
` ✅ Loaded field registry: ${ registry . fields . length } persisted fields discovered \ n ` +
` Fields: ${ registry . fields . slice ( 0 , 5 ) . join ( ', ' ) } ${ registry . fields . length > 5 ? '...' : '' } `
)
} catch ( error ) {
// Silent failure - registry not critical, will rebuild if needed
prodLog . debug ( 'Could not load field registry:' , error )
}
}
2026-01-05 16:31:52 -08:00
/ * *
* Get list of persisted fields from storage ( not in - memory )
2026-01-27 15:38:21 -08:00
* Used during rebuild to discover which chunk files need deletion
2026-01-05 16:31:52 -08:00
*
* @returns Array of field names that have persisted sparse indices
* /
private async getPersistedFieldList ( ) : Promise < string [ ] > {
try {
const registry = await this . storage . getMetadata ( '__metadata_field_registry__' )
if ( ! registry ? . fields || ! Array . isArray ( registry . fields ) ) {
return [ ]
}
return registry . fields . filter ( ( f : unknown ) = > typeof f === 'string' && f . length > 0 )
} catch ( error ) {
prodLog . debug ( 'Could not load persisted field list:' , error )
return [ ]
}
}
/ * *
* Delete all chunk files for a specific field
2026-01-27 15:38:21 -08:00
* Used during rebuild to ensure clean slate
2026-01-05 16:31:52 -08:00
*
* @param field Field name whose chunks should be deleted
* /
private async deleteFieldChunks ( field : string ) : Promise < void > {
try {
// Load sparse index to get chunk IDs
const indexPath = ` __sparse_index__ ${ field } `
const sparseData = await this . storage . getMetadata ( indexPath )
if ( sparseData ) {
const sparseIndex = SparseIndex . fromJSON ( sparseData )
// Delete all chunk files for this field
for ( const chunkId of sparseIndex . getAllChunkIds ( ) ) {
await this . chunkManager . deleteChunk ( field , chunkId )
}
2026-06-11 14:51:00 -07:00
// Delete the sparse index file itself.
// Typed boundary: the storage metadata channel doubles as the delete
// path — writing a JSON `null` tombstone clears the entry, but the
// adapter signature only models real payloads.
await this . storage . saveMetadata ( indexPath , null as unknown as NounMetadata )
2026-01-05 16:31:52 -08:00
}
} catch ( error ) {
// Silent failure - if we can't delete old chunks, rebuild will still work
// (new chunks will be created, old ones become orphaned)
prodLog . debug ( ` Could not clear chunks for field ' ${ field } ': ` , error )
}
}
/ * *
* Clear ALL metadata index data from storage ( for recovery )
2026-01-27 15:38:21 -08:00
* Nuclear option for recovering from corrupted index state
2026-01-05 16:31:52 -08:00
*
* WARNING : This deletes all indexed data - requires full rebuild after !
* Use when index is corrupted beyond normal rebuild repair .
* /
public async clearAllIndexData ( ) : Promise < void > {
prodLog . warn ( '🗑️ Clearing ALL metadata index data from storage...' )
// Get all persisted fields
const fields = await this . getPersistedFieldList ( )
// Delete chunks and sparse indices for each field
let deletedCount = 0
for ( const field of fields ) {
await this . deleteFieldChunks ( field )
deletedCount ++
}
2026-06-11 14:51:00 -07:00
// Delete field registry.
// Typed boundary: writing a JSON `null` tombstone clears the entry, but
// the adapter signature only models real payloads.
2026-01-05 16:31:52 -08:00
try {
2026-06-11 14:51:00 -07:00
await this . storage . saveMetadata ( '__metadata_field_registry__' , null as unknown as NounMetadata )
2026-01-05 16:31:52 -08:00
} catch ( error ) {
prodLog . debug ( 'Could not delete field registry:' , error )
}
// Clear in-memory state
this . fieldIndexes . clear ( )
this . dirtyFields . clear ( )
this . unifiedCache . clear ( 'metadata' )
this . totalEntitiesByType . clear ( )
this . entityCountsByTypeFixed . fill ( 0 )
this . verbCountsByTypeFixed . fill ( 0 )
this . typeFieldAffinity . clear ( )
2026-05-28 09:45:22 -07:00
// Clear EntityIdMapper. This is the explicit destructive path: the caller
// asked for nuclear recovery of a corrupted index, so renumbering UUIDs is
// intentional. Persisted int-keyed data (vector-mmap slots, graph
// link-compression encodings) is invalidated by this op — the warning
// below makes that explicit. Rebuild on its own does NOT clear the mapper.
2026-01-05 16:31:52 -08:00
await this . idMapper . clear ( )
// Clear chunk manager cache
this . chunkManager . clearCache ( )
prodLog . info ( ` ✅ Cleared ${ deletedCount } field indexes and all in-memory state ` )
2026-05-28 09:45:22 -07:00
prodLog . warn ( '⚠️ EntityIdMapper was cleared — any persisted int-keyed data ' +
'(vector mmap slots, graph link-compression encodings, etc.) is now stale ' +
'and must be rebuilt from canonical sources.' )
2026-01-05 16:31:52 -08:00
prodLog . info ( '⚠️ Run brain.index.rebuild() to recreate the index from entity data' )
}
2025-08-26 12:32:21 -07:00
/ * *
2025-09-16 11:24:20 -07:00
* Get count of entities by type - O ( 1 ) operation using existing tracking
* This exposes the production - ready counting that ' s already maintained
* /
getEntityCountByType ( type : string ) : number {
return this . totalEntitiesByType . get ( type ) || 0
}
/ * *
* Get total count of all entities - O ( 1 ) operation
* /
getTotalEntityCount ( ) : number {
let total = 0
for ( const count of this . totalEntitiesByType . values ( ) ) {
total += count
}
return total
}
/ * *
2026-06-19 10:55:43 -07:00
* Get all entity types and their counts - O ( 1 ) operation .
* ` totalEntitiesByType ` is populated by ` updateTypeFieldAffinity ` during add
* operations ( warm path ) and rehydrated from the column store 's ' noun ' field
* by ` lazyLoadCounts ` on init ( cold reopen ) , so this is accurate both within a
* session and after close ( ) + reopen .
2025-09-16 11:24:20 -07:00
* /
getAllEntityCounts ( ) : Map < string , number > {
return new Map ( this . totalEntitiesByType )
}
2025-11-25 12:37:21 -08:00
// ============================================================================
2026-01-27 15:38:21 -08:00
// VFS Statistics Methods (uses existing Roaring bitmap infrastructure)
2025-11-25 12:37:21 -08:00
// ============================================================================
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
/ * *
* Read the type column ' s bitmap for one type value — frozen key first
* ( 'system.type' , epoch 3 ) , legacy 'noun' as the pre - rebuild fallback .
* /
private async getTypeBitmap ( type : string ) : Promise < RoaringBitmap32 | null > {
return (
( await this . getBitmapFromChunks ( 'system.type' , type ) ) ? ?
( await this . getBitmapFromChunks ( 'noun' , type ) )
)
}
2025-11-25 12:37:21 -08:00
/ * *
* Get VFS entity count for a specific type using Roaring bitmap intersection
* Uses hardware - accelerated SIMD operations ( AVX2 / SSE4 . 2 )
* @param type The noun type to query
* @returns Count of VFS entities of this type
* /
async getVFSEntityCountByType ( type : string ) : Promise < number > {
const vfsBitmap = await this . getBitmapFromChunks ( 'isVFSEntity' , true )
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
const typeBitmap = await this . getTypeBitmap ( type )
2025-11-25 12:37:21 -08:00
if ( ! vfsBitmap || ! typeBitmap ) return 0
// Hardware-accelerated intersection + O(1) cardinality
const intersection = RoaringBitmap32 . and ( vfsBitmap , typeBitmap )
return intersection . size
}
/ * *
* Get all VFS entity counts by type using Roaring bitmap operations
* @returns Map of type - > VFS entity count
* /
async getAllVFSEntityCounts ( ) : Promise < Map < string , number > > {
const vfsBitmap = await this . getBitmapFromChunks ( 'isVFSEntity' , true )
if ( ! vfsBitmap || vfsBitmap . size === 0 ) {
return new Map ( )
}
const result = new Map < string , number > ( )
// Iterate through all known types and compute VFS count via intersection
for ( const type of this . totalEntitiesByType . keys ( ) ) {
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
const typeBitmap = await this . getTypeBitmap ( type )
2025-11-25 12:37:21 -08:00
if ( typeBitmap ) {
const intersection = RoaringBitmap32 . and ( vfsBitmap , typeBitmap )
if ( intersection . size > 0 ) {
result . set ( type , intersection . size )
}
}
}
return result
}
/ * *
* Get total count of VFS entities - O ( 1 ) using Roaring bitmap cardinality
* @returns Total VFS entity count
* /
async getTotalVFSEntityCount ( ) : Promise < number > {
const vfsBitmap = await this . getBitmapFromChunks ( 'isVFSEntity' , true )
return vfsBitmap ? . size ? ? 0
}
2025-10-15 13:52:21 -07:00
// ============================================================================
// Phase 1b: Type Enum Methods (O(1) access via Uint32Arrays)
// ============================================================================
/ * *
* Get entity count for a noun type using type enum ( O ( 1 ) array access )
* More efficient than Map - based getEntityCountByType
* @param type Noun type from NounTypeEnum
* @returns Count of entities of this type
* /
getEntityCountByTypeEnum ( type : NounType ) : number {
const index = TypeUtils . getNounIndex ( type )
return this . entityCountsByTypeFixed [ index ]
}
/ * *
* Get verb count for a verb type using type enum ( O ( 1 ) array access )
* @param type Verb type from VerbTypeEnum
* @returns Count of verbs of this type
* /
getVerbCountByTypeEnum ( type : VerbType ) : number {
const index = TypeUtils . getVerbIndex ( type )
return this . verbCountsByTypeFixed [ index ]
}
/ * *
* Get top N noun types by entity count ( using fixed - size arrays )
* Useful for type - aware cache warming and query optimization
* @param n Number of top types to return
* @returns Array of noun types sorted by count ( highest first )
* /
getTopNounTypes ( n : number ) : NounType [ ] {
const types : Array < { type : NounType ; count : number } > = [ ]
// Iterate through all noun types
for ( let i = 0 ; i < NOUN_TYPE_COUNT ; i ++ ) {
const count = this . entityCountsByTypeFixed [ i ]
if ( count > 0 ) {
const type = TypeUtils . getNounFromIndex ( i )
types . push ( { type , count } )
}
}
// Sort by count (descending) and return top N
return types
. sort ( ( a , b ) = > b . count - a . count )
. slice ( 0 , n )
. map ( t = > t . type )
}
/ * *
* Get top N verb types by count ( using fixed - size arrays )
* @param n Number of top types to return
* @returns Array of verb types sorted by count ( highest first )
* /
getTopVerbTypes ( n : number ) : VerbType [ ] {
const types : Array < { type : VerbType ; count : number } > = [ ]
// Iterate through all verb types
for ( let i = 0 ; i < VERB_TYPE_COUNT ; i ++ ) {
const count = this . verbCountsByTypeFixed [ i ]
if ( count > 0 ) {
const type = TypeUtils . getVerbFromIndex ( i )
types . push ( { type , count } )
}
}
// Sort by count (descending) and return top N
return types
. sort ( ( a , b ) = > b . count - a . count )
. slice ( 0 , n )
. map ( t = > t . type )
}
/ * *
* Get all noun type counts as a Map ( using fixed - size arrays )
* More efficient than getAllEntityCounts for type - aware queries
* @returns Map of noun type to count
* /
getAllNounTypeCounts ( ) : Map < NounType , number > {
const counts = new Map < NounType , number > ( )
for ( let i = 0 ; i < NOUN_TYPE_COUNT ; i ++ ) {
const count = this . entityCountsByTypeFixed [ i ]
if ( count > 0 ) {
const type = TypeUtils . getNounFromIndex ( i )
counts . set ( type , count )
}
}
return counts
}
/ * *
* Get all verb type counts as a Map ( using fixed - size arrays )
* @returns Map of verb type to count
* /
getAllVerbTypeCounts ( ) : Map < VerbType , number > {
const counts = new Map < VerbType , number > ( )
for ( let i = 0 ; i < VERB_TYPE_COUNT ; i ++ ) {
const count = this . verbCountsByTypeFixed [ i ]
if ( count > 0 ) {
const type = TypeUtils . getVerbFromIndex ( i )
counts . set ( type , count )
}
}
return counts
}
2025-09-16 11:24:20 -07:00
/ * *
2025-10-13 15:31:03 -07:00
* Get count of entities matching field - value criteria - queries chunked sparse index
2025-09-16 11:24:20 -07:00
* /
async getCountForCriteria ( field : string , value : any ) : Promise < number > {
2026-01-27 15:38:21 -08:00
// Use chunked sparse indexing
2025-10-13 15:31:03 -07:00
const ids = await this . getIds ( field , value )
return ids . length
2025-09-16 11:24:20 -07:00
}
/ * *
2026-05-15 12:31:28 -07:00
* Get index statistics .
*
* Source - of - truth precedence ( post - 7.20 . 0 column - store - first architecture ) :
* 1 . * * EntityIdMapper * * — ` idMapper.size ` is the canonical entity count .
* Every indexed entity gets a UUID → int mapping ; nothing else is
* consistent across instances .
* 2 . * * ColumnStore * * — ` getIndexedFields() ` is the canonical list of
* indexed fields . ` getFieldSizeSummary() ` provides segment / tail
* bookkeeping per field .
* 3 . * * Legacy sparse - index registry * * — only for pre - 7.20 . 0 workspaces
* whose data hasn ' t been migrated . ` getPersistedFieldList() ` may know
* fields the column store doesn ' t yet , so we union them in .
*
* Prior implementation read from ` this.fieldIndexes ` + lazy - loaded sparse
* indices , which silently returned ` 0 ` entries for any workspace written
2026-06-11 10:42:34 -07:00
* after sparse - index writes were deleted in commit ` 11be039 ` . That
* silent - zero defect is why this reads the column store first .
2025-08-26 12:32:21 -07:00
* /
async getStats ( ) : Promise < MetadataIndexStats > {
2026-05-15 12:31:28 -07:00
const entityCount = this . idMapper . size
2025-10-13 15:31:03 -07:00
2026-05-15 12:31:28 -07:00
// Field set: union of column-store fields and any legacy sparse-index
// fields registered on disk. Exclude the `__words__` text index by
// convention (it's not a metadata field in the public sense).
const fields = new Set < string > ( )
if ( this . columnStore ) {
for ( const f of this . columnStore . getIndexedFields ( ) ) {
if ( f !== '__words__' ) fields . add ( f )
}
}
// Legacy fallback: pre-7.20.0 workspaces may have sparse-index registry
// entries the column store doesn't know about yet. Surfacing them in the
// field list lets the rest of the system migrate them on read.
try {
const legacyFields = await this . getPersistedFieldList ( )
for ( const f of legacyFields ) {
if ( f !== '__words__' ) fields . add ( f )
2025-10-13 15:31:03 -07:00
}
2026-05-15 12:31:28 -07:00
} catch {
// Registry missing — nothing to add.
2025-10-13 15:31:03 -07:00
}
2026-05-15 12:31:28 -07:00
// `totalEntries` semantically means "distinct entities tracked by this
// index". That's `idMapper.size`. `totalIds` is the sum of all
// (field, value) → entityId postings — proxied by the segment/tail size
// summary so we don't have to scan every bitmap.
let totalIds = 0
if ( this . columnStore ) {
for ( const summary of this . columnStore . getFieldSizeSummary ( ) ) {
if ( summary . field === '__words__' ) continue
totalIds += summary . tailSize
// Segment count is a proxy; for a coarser-grained number we'd open
// each segment cursor. Avoided here because stats() is on the hot
// path for `brain.stats()` / health checks.
totalIds += summary . segmentCount * 1 // segments contribute at least 1 posting
2026-01-05 16:31:52 -08:00
}
}
2025-08-26 12:32:21 -07:00
return {
2026-05-15 12:31:28 -07:00
totalEntries : entityCount ,
2025-08-26 12:32:21 -07:00
totalIds ,
2026-05-15 12:31:28 -07:00
fieldsIndexed : Array.from ( fields ) . sort ( ) ,
2025-09-11 16:23:32 -07:00
lastRebuild : Date.now ( ) ,
2026-05-15 12:31:28 -07:00
indexSize : entityCount * 100 // rough estimate
2025-08-26 12:32:21 -07:00
}
}
2026-01-26 12:12:11 -08:00
/ * *
2026-01-27 15:38:21 -08:00
* Validate index consistency and detect corruption
2026-01-26 12:12:11 -08:00
* Returns health status and recommendations for repair
*
2026-01-27 15:38:21 -08:00
* Counts metadata field entries only ( excludes __words__ keyword index ) .
2026-01-26 12:12:11 -08:00
* Corruption typically manifests as high avg entries / entity ( expected ~ 30 , corrupted can be 100 + )
2026-01-27 15:38:21 -08:00
* caused by the update ( ) field asymmetry bug
2026-01-26 12:12:11 -08:00
* /
async validateConsistency ( ) : Promise < {
healthy : boolean
avgEntriesPerEntity : number
entityCount : number
indexEntryCount : number
recommendation : string | null
} > {
const entityCount = this . idMapper . size
// If no entities, index is trivially healthy
if ( entityCount === 0 ) {
return {
healthy : true ,
avgEntriesPerEntity : 0 ,
entityCount : 0 ,
indexEntryCount : 0 ,
recommendation : null
}
}
2026-01-27 15:38:21 -08:00
// Count total index entries across all fields (excluding keyword index)
2026-01-26 12:12:11 -08:00
let indexEntryCount = 0
for ( const field of this . fieldIndexes . keys ( ) ) {
2026-01-27 15:38:21 -08:00
if ( field === '__words__' ) continue // Keyword entries are expected to be high-volume
2026-01-26 12:12:11 -08:00
const sparseIndex = await this . loadSparseIndex ( field )
if ( sparseIndex ) {
for ( const chunkId of sparseIndex . getAllChunkIds ( ) ) {
const chunk = await this . chunkManager . loadChunk ( field , chunkId )
if ( chunk ) {
for ( const ids of chunk . entries . values ( ) ) {
indexEntryCount += ids . size
}
}
}
}
}
const avgEntriesPerEntity = indexEntryCount / entityCount
2026-01-27 15:38:21 -08:00
// Threshold: 100 metadata entries/entity is clearly corrupted (expected ~30)
// __words__ keyword entries are excluded from this count since they can be 50-5000 per entity
2026-01-26 12:12:11 -08:00
// This catches the update() asymmetry bug which causes 7 fields to accumulate per update
const CORRUPTION_THRESHOLD = 100
const healthy = avgEntriesPerEntity <= CORRUPTION_THRESHOLD
let recommendation : string | null = null
if ( ! healthy ) {
recommendation = ` Index corruption detected ( ${ avgEntriesPerEntity . toFixed ( 1 ) } avg entries/entity, expected ~30). ` +
` Run brain.index.clearAllIndexData() followed by brain.index.rebuild() to repair. `
}
return {
healthy ,
avgEntriesPerEntity ,
entityCount ,
indexEntryCount ,
recommendation
}
}
2025-08-26 12:32:21 -07:00
/ * *
* Rebuild entire index from scratch using pagination
* Non - blocking version that yields control back to event loop
2026-01-27 15:38:21 -08:00
* Sparse indices now lazy - loaded via UnifiedCache ( no need to clear Map )
2025-08-26 12:32:21 -07:00
* /
async rebuild ( ) : Promise < void > {
if ( this . isRebuilding ) return
2025-10-15 12:26:25 -07:00
2025-08-26 12:32:21 -07:00
this . isRebuilding = true
try {
2025-10-23 09:02:37 -07:00
prodLog . info ( '🔄 Starting non-blocking metadata index rebuild with batch processing...' )
2025-10-23 08:47:37 -07:00
prodLog . info ( ` 📊 Storage adapter: ${ this . storage . constructor . name } ` )
prodLog . info ( ` 🔧 Batch processing available: ${ ! ! this . storage . getMetadataBatch } ` )
2025-10-13 15:31:03 -07:00
2026-01-27 15:38:21 -08:00
// Clear existing indexes
// No sparseIndices Map to clear - UnifiedCache handles eviction
2025-08-26 12:32:21 -07:00
this . fieldIndexes . clear ( )
this . dirtyFields . clear ( )
2025-10-15 12:26:25 -07:00
2026-01-27 15:38:21 -08:00
// CRITICAL FIX - Clear type counts to prevent accumulation
2025-12-02 11:45:17 -08:00
// Previously, counts accumulated across rebuilds causing incorrect values
this . totalEntitiesByType . clear ( )
this . entityCountsByTypeFixed . fill ( 0 )
this . verbCountsByTypeFixed . fill ( 0 )
this . typeFieldAffinity . clear ( )
2025-10-15 12:26:25 -07:00
// Clear all cached sparse indices in UnifiedCache
2026-01-27 15:38:21 -08:00
// This ensures rebuild starts fresh
2025-10-15 12:26:25 -07:00
this . unifiedCache . clear ( 'metadata' )
2025-10-23 08:07:07 -07:00
2026-03-24 12:57:11 -07:00
// Clear existing chunk files from storage to prevent overcounting.
// Chunks are deleted first, then rebuilt. The field registry is NOT deleted
// here — it's always saved at the end of rebuild via flush(). This ensures
// that if rebuild fails partway, the next init() can still discover fields
// and trigger another rebuild attempt.
prodLog . info ( 'Clearing existing metadata index chunks from storage...' )
2026-01-05 16:31:52 -08:00
const existingFields = await this . getPersistedFieldList ( )
if ( existingFields . length > 0 ) {
for ( const field of existingFields ) {
await this . deleteFieldChunks ( field )
}
2026-03-24 12:57:11 -07:00
prodLog . info ( ` Cleared ${ existingFields . length } field indexes from storage ` )
2026-01-05 16:31:52 -08:00
}
2026-05-28 09:45:22 -07:00
// EntityIdMapper is intentionally NOT cleared here. Rebuild re-iterates
// every entity in storage and calls idMapper.getOrAssign(uuid), which
// returns the existing int for known UUIDs (no renumbering). This is the
// foundational stability guarantee — vector-mmap slot indices, graph
// link-compression encodings, and any other persisted int-keyed data
// remain valid across a rebuild. Previously this line reset nextId to 1
// and renumbered every UUID by re-insertion order, silently breaking
// any consumer that had persisted int-keyed data against the old map.
// Stale entries for UUIDs no longer in storage persist (harmless memory
// overhead); a dedicated prune step can be added if it ever matters.
// The destructive wipe is still available via clearAllIndexData() →
// idMapper.clear(), which is the explicit "recovery" path with the
// appropriate warning about invalidating persisted int-keyed data.
2026-01-05 16:31:52 -08:00
// Clear chunk manager cache
this . chunkManager . clearCache ( )
2026-06-09 15:05:02 -07:00
// Brainy 8.0 ships filesystem + memory storage only. Load all nouns
// at once — the cloud-storage paginated branch was deleted alongside
// the cloud adapters in step 7.
2025-08-26 12:32:21 -07:00
let totalNounsProcessed = 0
2025-09-16 10:35:07 -07:00
2026-06-09 15:05:02 -07:00
{
prodLog . info ( ` ⚡ Loading all nouns at once (local storage) ` )
2025-08-26 12:32:21 -07:00
const result = await this . storage . getNouns ( {
2025-10-23 09:19:17 -07:00
pagination : { offset : 0 , limit : 1000000 } // Effectively unlimited
2025-08-26 12:32:21 -07:00
} )
2025-09-16 10:35:07 -07:00
2025-10-23 09:19:17 -07:00
prodLog . info ( ` 📦 Loading ${ result . items . length } nouns with metadata... ` )
// Get all metadata in one batch if available
const nounIds = result . items . map ( noun = > noun . id )
let metadataBatch : Map < string , any >
if ( this . storage . getMetadataBatch ) {
metadataBatch = await this . storage . getMetadataBatch ( nounIds )
prodLog . info ( ` ✅ Loaded ${ metadataBatch . size } / ${ nounIds . length } metadata objects ` )
} else {
metadataBatch = new Map ( )
for ( const id of nounIds ) {
try {
const metadata = await this . storage . getNounMetadata ( id )
if ( metadata ) metadataBatch . set ( id , metadata )
} catch ( error ) {
prodLog . debug ( ` Failed to read metadata for ${ id } : ` , error )
}
}
}
for ( const noun of result . items ) {
const metadata = metadataBatch . get ( noun . id )
if ( metadata ) {
2026-01-31 09:14:51 -08:00
await this . addToIndex ( noun . id , metadata , true , true )
2025-10-23 09:19:17 -07:00
}
}
totalNounsProcessed = result . items . length
prodLog . info ( ` ✅ Indexed ${ totalNounsProcessed } nouns ` )
2025-08-26 12:32:21 -07:00
}
2025-10-23 09:19:17 -07:00
2026-06-09 15:05:02 -07:00
// Rebuild verb metadata indexes — same single-pass local strategy.
2025-08-26 12:32:21 -07:00
let totalVerbsProcessed = 0
2025-09-16 10:35:07 -07:00
2026-06-09 15:05:02 -07:00
{
2025-10-23 09:19:17 -07:00
prodLog . info ( ` ⚡ Loading all verbs at once (local storage) ` )
2025-08-26 12:32:21 -07:00
const result = await this . storage . getVerbs ( {
2025-10-23 09:19:17 -07:00
pagination : { offset : 0 , limit : 1000000 } // Effectively unlimited
2025-08-26 12:32:21 -07:00
} )
2025-09-16 10:35:07 -07:00
2025-10-23 09:19:17 -07:00
prodLog . info ( ` 📦 Loading ${ result . items . length } verbs with metadata... ` )
const verbIds = result . items . map ( verb = > verb . id )
2026-06-11 14:51:00 -07:00
let verbMetadataBatch : Map < string , VerbMetadata >
2025-10-23 09:19:17 -07:00
2026-06-11 14:51:00 -07:00
// Optional adapter capability: batched verb-metadata reads. Not part of
// the StorageAdapter contract, so it is probed structurally.
const batchCapableStorage = this . storage as StorageAdapter & {
getVerbMetadataBatch ? : ( ids : string [ ] ) = > Promise < Map < string , VerbMetadata > >
}
if ( batchCapableStorage . getVerbMetadataBatch ) {
verbMetadataBatch = await batchCapableStorage . getVerbMetadataBatch ( verbIds )
2025-10-23 09:19:17 -07:00
prodLog . info ( ` ✅ Loaded ${ verbMetadataBatch . size } / ${ verbIds . length } verb metadata objects ` )
} else {
verbMetadataBatch = new Map ( )
for ( const id of verbIds ) {
try {
const metadata = await this . storage . getVerbMetadata ( id )
if ( metadata ) verbMetadataBatch . set ( id , metadata )
} catch ( error ) {
prodLog . debug ( ` Failed to read verb metadata for ${ id } : ` , error )
}
}
}
for ( const verb of result . items ) {
const metadata = verbMetadataBatch . get ( verb . id )
if ( metadata ) {
2026-01-31 09:14:51 -08:00
await this . addToIndex ( verb . id , metadata , true , true )
2025-10-23 09:19:17 -07:00
}
}
totalVerbsProcessed = result . items . length
prodLog . info ( ` ✅ Indexed ${ totalVerbsProcessed } verbs ` )
2025-09-16 10:35:07 -07:00
}
2026-06-09 15:05:02 -07:00
// Flush to storage. The column store's flush() handles tail-buffer-to-
// segment promotion + manifest persistence.
2025-08-26 12:32:21 -07:00
prodLog . debug ( '💾 Flushing metadata index to storage...' )
await this . flush ( )
2025-09-16 10:35:07 -07:00
2025-08-26 12:32:21 -07:00
prodLog . info ( ` ✅ Metadata index rebuild completed! Processed ${ totalNounsProcessed } nouns and ${ totalVerbsProcessed } verbs ` )
2026-06-09 15:05:02 -07:00
2025-08-26 12:32:21 -07:00
} finally {
this . isRebuilding = false
}
}
2025-09-12 12:45:32 -07:00
/ * *
* Get field statistics for optimization and discovery
* /
async getFieldStatistics ( ) : Promise < Map < string , FieldStats > > {
// Initialize stats for fields we haven't seen yet
for ( const field of this . fieldIndexes . keys ( ) ) {
if ( ! this . fieldStats . has ( field ) ) {
this . fieldStats . set ( field , {
cardinality : {
uniqueValues : 0 ,
totalValues : 0 ,
distribution : 'uniform' ,
updateFrequency : 0 ,
lastAnalyzed : Date.now ( )
} ,
queryCount : 0 ,
rangeQueryCount : 0 ,
exactQueryCount : 0 ,
avgQueryTime : 0 ,
indexType : 'hash'
} )
}
}
return new Map ( this . fieldStats )
}
/ * *
* Get field cardinality information
* /
async getFieldCardinality ( field : string ) : Promise < CardinalityInfo | null > {
const stats = this . fieldStats . get ( field )
return stats ? stats.cardinality : null
}
/ * *
* Get all field names with their cardinality ( for query optimization )
* /
async getFieldsWithCardinality ( ) : Promise < Array < { field : string ; cardinality : number ; distribution : string } > > {
const fields : Array < { field : string ; cardinality : number ; distribution : string } > = [ ]
for ( const [ field , stats ] of this . fieldStats ) {
fields . push ( {
field ,
cardinality : stats.cardinality.uniqueValues ,
distribution : stats.cardinality.distribution
} )
}
// Sort by cardinality (low cardinality fields are better for filtering)
fields . sort ( ( a , b ) = > a . cardinality - b . cardinality )
return fields
}
/ * *
* Get optimal query plan based on field statistics
* /
async getOptimalQueryPlan ( filters : Record < string , any > ) : Promise < {
strategy : 'exact' | 'range' | 'hybrid'
fieldOrder : string [ ]
estimatedCost : number
} > {
const fieldOrder : string [ ] = [ ]
let hasRangeQueries = false
let totalEstimatedCost = 0
// Analyze each filter
for ( const [ field , value ] of Object . entries ( filters ) ) {
const stats = this . fieldStats . get ( field )
if ( ! stats ) continue
// Check if this is a range query
if ( typeof value === 'object' && value !== null && ! Array . isArray ( value ) ) {
hasRangeQueries = true
}
// Estimate cost based on cardinality
const cardinality = stats . cardinality . uniqueValues
const estimatedCost = Math . log2 ( Math . max ( 1 , cardinality ) )
totalEstimatedCost += estimatedCost
fieldOrder . push ( field )
}
// Sort fields by cardinality (process low cardinality first)
fieldOrder . sort ( ( a , b ) = > {
const statsA = this . fieldStats . get ( a )
const statsB = this . fieldStats . get ( b )
if ( ! statsA || ! statsB ) return 0
return statsA . cardinality . uniqueValues - statsB . cardinality . uniqueValues
} )
return {
strategy : hasRangeQueries ? 'hybrid' : 'exact' ,
fieldOrder ,
estimatedCost : totalEstimatedCost
}
}
/ * *
* Export field statistics for analysis
* /
async exportFieldStats ( ) : Promise < any > {
const stats : any = {
fields : { } ,
summary : {
totalFields : this.fieldStats.size ,
highCardinalityFields : 0 ,
sparseFields : 0 ,
skewedFields : 0 ,
uniformFields : 0
}
}
for ( const [ field , fieldStats ] of this . fieldStats ) {
stats . fields [ field ] = {
cardinality : fieldStats.cardinality ,
queryStats : {
total : fieldStats.queryCount ,
exact : fieldStats.exactQueryCount ,
range : fieldStats.rangeQueryCount ,
avgTime : fieldStats.avgQueryTime
} ,
indexType : fieldStats.indexType ,
normalization : fieldStats.normalizationStrategy
}
// Update summary
if ( fieldStats . cardinality . uniqueValues > this . HIGH_CARDINALITY_THRESHOLD ) {
stats . summary . highCardinalityFields ++
}
switch ( fieldStats . cardinality . distribution ) {
case 'sparse' :
stats . summary . sparseFields ++
break
case 'skewed' :
stats . summary . skewedFields ++
break
case 'uniform' :
stats . summary . uniformFields ++
break
}
}
return stats
}
2025-09-12 13:24:47 -07:00
/ * *
* Update type - field affinity tracking for intelligent NLP
* Tracks which fields commonly appear with which entity types
* /
2025-10-13 15:31:03 -07:00
private updateTypeFieldAffinity ( entityId : string , field : string , value : any , operation : 'add' | 'remove' , metadata? : any ) : void {
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
// Only track affinity for user fields (plus the type column itself,
// which drives detection). Engine columns carry the literal 'system.'
// prefix under the frozen key format.
if ( field . startsWith ( 'system.' ) && field !== 'system.type' ) return
2025-10-13 15:31:03 -07:00
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
// For the type column ('system.type'), the value IS the entity type
2025-09-12 13:24:47 -07:00
let entityType : string | null = null
2025-10-13 15:31:03 -07:00
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
if ( field === 'system.type' ) {
2025-09-12 13:37:24 -07:00
// This is the type definition itself
2025-10-13 13:16:07 -07:00
entityType = this . normalizeValue ( value , field ) // Pass field for bucketing!
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
} else if ( metadata && ( metadata . noun ? ? metadata . type ) ) {
// Extract entity type from the source shape: stored records carry it
// under 'noun', entity-for-indexing views under 'type'.
entityType = this . normalizeValue ( metadata . noun ? ? metadata . type , 'system.type' )
2025-09-12 13:37:24 -07:00
} else {
2025-10-13 15:31:03 -07:00
// No type information available, skip affinity tracking
return
2025-09-12 13:24:47 -07:00
}
2025-10-13 15:31:03 -07:00
2025-09-12 13:24:47 -07:00
if ( ! entityType ) return // No type found, skip affinity tracking
// Initialize affinity tracking for this type
if ( ! this . typeFieldAffinity . has ( entityType ) ) {
this . typeFieldAffinity . set ( entityType , new Map ( ) )
}
if ( ! this . totalEntitiesByType . has ( entityType ) ) {
this . totalEntitiesByType . set ( entityType , 0 )
}
const typeFields = this . typeFieldAffinity . get ( entityType ) !
if ( operation === 'add' ) {
// Increment field count for this type
const currentCount = typeFields . get ( field ) || 0
typeFields . set ( field , currentCount + 1 )
2025-10-15 13:52:21 -07:00
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
// Update total entities of this type (only count once per entity —
// the type column appears exactly once per entity)
if ( field === 'system.type' ) {
2025-10-15 13:52:21 -07:00
const newCount = this . totalEntitiesByType . get ( entityType ) ! + 1
this . totalEntitiesByType . set ( entityType , newCount )
// Phase 1b: Also update fixed-size array
// Try to parse as noun type - if it matches a known type, update the array
try {
const nounTypeIndex = TypeUtils . getNounIndex ( entityType as NounType )
this . entityCountsByTypeFixed [ nounTypeIndex ] = newCount
} catch {
// Not a recognized noun type, skip fixed-size array update
}
2025-09-12 13:24:47 -07:00
}
} else if ( operation === 'remove' ) {
// Decrement field count for this type
const currentCount = typeFields . get ( field ) || 0
if ( currentCount > 1 ) {
typeFields . set ( field , currentCount - 1 )
} else {
typeFields . delete ( field )
}
2025-10-15 13:52:21 -07:00
2025-09-12 13:24:47 -07:00
// Update total entities of this type
feat(namespace): NO SPECIAL NAMES + storage fidelity — the ruled completion of the field-addressing law
The write side of the law, ruled 2026-08-03: data is either in main space
where developers can use anything, or it is in system.*.
- The reserved-name write door DIES: add/update/relate/updateRelation
metadata bags accept EVERY name (confidence, type, id, data, level,
content, ...) as ordinary user fields — indexed, filterable, sortable,
aggregatable, identical to any other field. The remap/enforce/warn
machinery, the reservedFieldPolicy config (now a typed init refusal),
and the compile-time metadata key bans are all removed. The one write
refusal left: keys spelled 'system.*' (namespace forgery), now enforced
on all four write doors.
- STORED RECORDS GO NESTED (v2): engine fields top-level, the user bag
nested verbatim under 'metadata', sealed by a format stamp — by-name
storage discrimination is unsound once colliders are admitted. Legacy
flat records stay readable forever through the shape-aware splitters
(sound for them: the old door refused colliders). Time travel rides the
same split (generation store snapshots whole records).
- Name-based index exclusions DIE: user frame indexes every name; the
excludeFields/indexedFields knobs and their silent-[] holes are gone;
bulk-payload protection is value-shape only, uniform across names.
- Consumer-sweep findings fixed in the same wave: per-type counts read
the frozen 'system.type' column (addToIndex sort, affinity tracking,
cold-count rehydration, VFS type bitmaps — legacy 'noun' fallback for
pre-rebuild reads); resolveHiddenIds addresses 'system.visibility'
(bare 'visibility' was a silent no-op under the law — VFS/system
entities leaked into default reads).
- Fidelity fallout fixed in the owning layers: readEntityFieldAddress
reads the bag first (colliders were absent-shadowed by its own guard)
and never serves system addresses from the bag; blob history refs read
the bag shape-aware; migration transforms now receive ONE normalized
view (engine fields + nested bag) regardless of stored era, and stray
flat-habit keys refuse with the fix in the message.
- THE REOPEN-COLLIDER CONFORMANCE CASE (required before any RC counts as
gates-green): all ten collider names + plumbing names written as user
fields, verified verbatim + queryable across live reads, flush+reopen,
a forced epoch rebuild, and asOf time travel; relation mirror; forgery
refusals; legacy flat-record compat. 8/8 green.
Gates: unit 1901/1901 (exit 0) · integration 758 (exit 0) · conformance
27/27 (exit 0) · consumer test sweep migrated (10 files).
2026-08-03 16:59:13 -07:00
if ( field === 'system.type' ) {
2025-09-12 13:24:47 -07:00
const total = this . totalEntitiesByType . get ( entityType ) !
if ( total > 1 ) {
2025-10-15 13:52:21 -07:00
const newCount = total - 1
this . totalEntitiesByType . set ( entityType , newCount )
// Phase 1b: Also update fixed-size array
try {
const nounTypeIndex = TypeUtils . getNounIndex ( entityType as NounType )
this . entityCountsByTypeFixed [ nounTypeIndex ] = newCount
} catch {
// Not a recognized noun type, skip fixed-size array update
}
2025-09-12 13:24:47 -07:00
} else {
this . totalEntitiesByType . delete ( entityType )
this . typeFieldAffinity . delete ( entityType )
2025-10-15 13:52:21 -07:00
// Phase 1b: Also zero out fixed-size array
try {
const nounTypeIndex = TypeUtils . getNounIndex ( entityType as NounType )
this . entityCountsByTypeFixed [ nounTypeIndex ] = 0
} catch {
// Not a recognized noun type, skip fixed-size array update
}
2025-09-12 13:24:47 -07:00
}
}
}
}
/ * *
* Get fields that commonly appear with a specific entity type
* Returns fields with their affinity scores ( 0 - 1 )
* /
2025-09-12 14:37:39 -07:00
async getFieldsForType ( nounType : NounType ) : Promise < Array < {
2025-09-12 13:24:47 -07:00
field : string
affinity : number
occurrences : number
totalEntities : number
} >> {
const typeFields = this . typeFieldAffinity . get ( nounType )
const totalEntities = this . totalEntitiesByType . get ( nounType )
if ( ! typeFields || ! totalEntities ) {
return [ ]
}
const fieldsWithAffinity : Array < {
field : string
affinity : number
occurrences : number
totalEntities : number
} > = [ ]
for ( const [ field , count ] of typeFields . entries ( ) ) {
const affinity = count / totalEntities // 0-1 score
fieldsWithAffinity . push ( {
field ,
affinity ,
occurrences : count ,
totalEntities
} )
}
// Sort by affinity (most common fields first)
fieldsWithAffinity . sort ( ( a , b ) = > b . affinity - a . affinity )
return fieldsWithAffinity
}
/ * *
* Get type - field affinity statistics for analysis
* /
async getTypeFieldAffinityStats ( ) : Promise < {
totalTypes : number
averageFieldsPerType : number
typeBreakdown : Record < string , {
totalEntities : number
uniqueFields : number
topFields : Array < { field : string ; affinity : number } >
} >
} > {
const typeBreakdown : Record < string , any > = { }
let totalFields = 0
2025-10-15 17:48:26 -07:00
2025-09-12 13:24:47 -07:00
for ( const [ nounType , fieldsMap ] of this . typeFieldAffinity . entries ( ) ) {
const totalEntities = this . totalEntitiesByType . get ( nounType ) || 0
const fields = Array . from ( fieldsMap . entries ( ) )
2025-10-15 17:48:26 -07:00
2025-09-12 13:24:47 -07:00
// Get top 5 fields for this type
const topFields = fields
. map ( ( [ field , count ] ) = > ( { field , affinity : count / totalEntities } ) )
. sort ( ( a , b ) = > b . affinity - a . affinity )
. slice ( 0 , 5 )
2025-10-15 17:48:26 -07:00
2025-09-12 13:24:47 -07:00
typeBreakdown [ nounType ] = {
totalEntities ,
uniqueFields : fieldsMap.size ,
topFields
}
2025-10-15 17:48:26 -07:00
2025-09-12 13:24:47 -07:00
totalFields += fieldsMap . size
}
2025-10-15 17:48:26 -07:00
2025-09-12 13:24:47 -07:00
return {
totalTypes : this.typeFieldAffinity.size ,
averageFieldsPerType : totalFields / Math . max ( 1 , this . typeFieldAffinity . size ) ,
typeBreakdown
}
}
2025-08-26 12:32:21 -07:00
}