diff --git a/.claude/skills/architecture.md b/.claude/skills/architecture.md
index 4de3c287..de046b17 100644
--- a/.claude/skills/architecture.md
+++ b/.claude/skills/architecture.md
@@ -2,7 +2,7 @@
## What Is Brainy
-@soulcraftlabs/brainy (v7.17.0) is a Universal Knowledge Protocol -- a Triple Intelligence database combining vector search, graph traversal, and metadata filtering in a single library. Published to npm as a public MIT-licensed package.
+@soulcraft/brainy (v7.17.0) is a Universal Knowledge Protocol -- a Triple Intelligence database combining vector search, graph traversal, and metadata filtering in a single library. Published to npm as a public MIT-licensed package.
## Core Architecture
diff --git a/.forgejo/workflows/ci.yml b/.forgejo/workflows/ci.yml
index da5887f6..fec679a8 100644
--- a/.forgejo/workflows/ci.yml
+++ b/.forgejo/workflows/ci.yml
@@ -5,10 +5,6 @@ name: CI
# sequential, so tag-triggered matrix jobs (~22 min) would queue AHEAD of the
# tag's publish-source run and starve every release (observed on 8.10.3 and
# 9.0.0: the publish sat behind the tag's own redundant CI).
-concurrency:
- group: ci-${{ github.ref }}
- cancel-in-progress: true
-
on:
push:
branches: ['**']
@@ -31,22 +27,6 @@ jobs:
- run: npm ci
- run: npm run test:unit
- # The correctness plant's full gate: integration + conformance run here on
- # dedicated iron, on every push, so a release never depends on any other
- # machine being up. Verdicts live in this run's log (never inferred).
- integration:
- name: Integration + conformance (Node 22)
- runs-on: ubuntu-latest
- steps:
- - uses: actions/checkout@v4
- - uses: actions/setup-node@v4
- with:
- node-version: '22'
- cache: npm
- - run: npm ci
- - run: npm run test:ci-integration
- - run: npx vitest run tests/conformance
-
bun:
name: Bun (latest)
runs-on: ubuntu-latest
diff --git a/.forgejo/workflows/delta-gate.yml b/.forgejo/workflows/delta-gate.yml
deleted file mode 100644
index c320594e..00000000
--- a/.forgejo/workflows/delta-gate.yml
+++ /dev/null
@@ -1,148 +0,0 @@
-name: Delta Gate
-
-# On-demand candidate-vs-control gate on the capped functional CI lane
-# (label: gate-functional). That lane is Bun-only host-mode — there is no
-# Node.js runtime available to it, so this workflow deliberately avoids every
-# JS-based action (checkout/setup-node/setup-bun/upload-artifact all require
-# one) and does everything with plain git + bun in shell steps instead.
-#
-# Verdict lines a caller should grep for in the run log:
-# COLLECTED patch= control= — collection-truncation guard inputs
-# NEW-RED-COUNT: — failures on candidate absent from control
-# DELTA-GATE: CLEAN | NEW REDS | INVALID | STOPPED-BY-REGISTRY-TRIPWIRE
-#
-# The lane's own housekeeping stops the runner and drops a marker file when
-# host pressure (I/O, registry latency, disk budget) trips — never ours to
-# interpret as a red or a green. The final step checks for that marker before
-# it says anything about pass/fail.
-
-on:
- workflow_dispatch:
- inputs:
- candidate:
- description: 'Candidate ref (branch or sha) to gate'
- required: true
- type: string
- control:
- description: 'Control sha to diff against'
- required: true
- type: string
- # workflow_dispatch needs Actions-unit write on the dispatching credential;
- # push does not (it runs from the pushed ref's own tree), so a plain push
- # to a release or CI branch is the fallback trigger while that grant is
- # outstanding — see the ref-resolution step below for what it gates against.
- push:
- branches: ['rel/**', 'ci/**']
-
-concurrency:
- group: delta-gate
- cancel-in-progress: false
-
-jobs:
- delta-gate:
- name: Delta gate — candidate vs control
- runs-on: gate-functional
- timeout-minutes: 120
- steps:
- - name: Resolve candidate/control refs
- id: refs
- run: |
- candidate="${{ github.event.inputs.candidate }}"
- control="${{ github.event.inputs.control }}"
- # workflow_dispatch supplies both explicitly; a push event carries
- # neither — fall back to the pushed commit as candidate and the
- # last released, known-good tip (10.4.9) as control, so a plain
- # push still produces a meaningful gate instead of an empty ref.
- if [ -z "$candidate" ]; then candidate="${{ github.sha }}"; fi
- if [ -z "$control" ]; then control="eec90bdd"; fi
- echo "candidate=$candidate" >> "$GITHUB_OUTPUT"
- echo "control=$control" >> "$GITHUB_OUTPUT"
- echo "Resolved (trigger=${{ github.event_name }}): candidate=$candidate control=$control"
-
- - name: Clean any residue from a prior run
- run: rm -rf "ob-cand-${{ github.run_id }}" "ob-ctrl-${{ github.run_id }}" "/tmp/ob-${{ github.run_id }}-"*
-
- - name: Clone + test — candidate
- id: patch
- run: |
- set -o pipefail
- git clone --quiet "https://source.soulcraft.com/soulcraftlabs/open-brainy.git" "ob-cand-${{ github.run_id }}"
- cd "ob-cand-${{ github.run_id }}"
- git checkout --quiet "${{ steps.refs.outputs.candidate }}"
- git log --oneline -1
- bun install
- rc=0
- bun x vitest run > "/tmp/ob-${{ github.run_id }}-patch.log" 2>&1 || rc=$?
- echo "PATCH-RC:$rc"
- grep -aE "Tests .*(passed|failed)" "/tmp/ob-${{ github.run_id }}-patch.log" | tail -1
- grep -aE "^ FAIL |^\s+×" "/tmp/ob-${{ github.run_id }}-patch.log" | sed -E "s/ [0-9]+ms$//" | sed -E "s/^\s+//" | sort -u > "/tmp/ob-${{ github.run_id }}-patch.fail"
- echo "PATCH-FAILING:$(wc -l < "/tmp/ob-${{ github.run_id }}-patch.fail")"
-
- - name: Clone + test — control
- id: control
- run: |
- set -o pipefail
- git clone --quiet "https://source.soulcraft.com/soulcraftlabs/open-brainy.git" "ob-ctrl-${{ github.run_id }}"
- cd "ob-ctrl-${{ github.run_id }}"
- git checkout --quiet "${{ steps.refs.outputs.control }}"
- git log --oneline -1
- bun install
- rc=0
- bun x vitest run > "/tmp/ob-${{ github.run_id }}-control.log" 2>&1 || rc=$?
- echo "CONTROL-RC:$rc"
- grep -aE "Tests .*(passed|failed)" "/tmp/ob-${{ github.run_id }}-control.log" | tail -1
- grep -aE "^ FAIL |^\s+×" "/tmp/ob-${{ github.run_id }}-control.log" | sed -E "s/ [0-9]+ms$//" | sed -E "s/^\s+//" | sort -u > "/tmp/ob-${{ github.run_id }}-control.fail"
- echo "CONTROL-FAILING:$(wc -l < "/tmp/ob-${{ github.run_id }}-control.fail")"
-
- - name: Delta gate verdict
- if: always()
- run: |
- set -o pipefail
-
- # The lane's own tripwire wins over anything we would otherwise say:
- # a bare failure/timeout above with this marker present is host
- # pressure, never a real red and never a real green.
- if [ -f /srv/gate-lane/TRIPWIRE-STOPPED ]; then
- echo "DELTA-GATE: STOPPED-BY-REGISTRY-TRIPWIRE"
- head -1 /srv/gate-lane/TRIPWIRE-STOPPED
- exit 3
- fi
-
- patch_log="/tmp/ob-${{ github.run_id }}-patch.log"
- control_log="/tmp/ob-${{ github.run_id }}-control.log"
- patch_fail="/tmp/ob-${{ github.run_id }}-patch.fail"
- control_fail="/tmp/ob-${{ github.run_id }}-control.fail"
-
- if [ ! -s "$patch_log" ] || [ ! -s "$control_log" ]; then
- echo "DELTA-GATE: INVALID — a leg produced no log (see the two steps above for the real cause)"
- exit 2
- fi
-
- pt=$(grep -aoE "\(([0-9]+)\)$" "$patch_log" | tail -1 | tr -d "()")
- ct=$(grep -aoE "\(([0-9]+)\)$" "$control_log" | tail -1 | tr -d "()")
- echo "COLLECTED patch=${pt:-0} control=${ct:-0}"
- if [ "${pt:-0}" -lt 3000 ] || [ "${ct:-0}" -lt 3000 ]; then
- echo "DELTA-GATE: INVALID — truncated collection"
- exit 2
- fi
-
- echo "=== NEW REDS ==="
- comm -23 "$patch_fail" "$control_fail"
- new=$(comm -23 "$patch_fail" "$control_fail" | wc -l)
- echo "NEW-RED-COUNT:$new"
-
- echo "=== full candidate fail list ==="
- cat "$patch_fail"
- echo "=== full control fail list ==="
- cat "$control_fail"
-
- if [ "$new" -eq 0 ]; then
- echo "DELTA-GATE: CLEAN"
- else
- echo "DELTA-GATE: NEW REDS"
- exit 1
- fi
-
- - name: Clean up (mind the lane's disk budget)
- if: always()
- run: rm -rf "ob-cand-${{ github.run_id }}" "ob-ctrl-${{ github.run_id }}" "/tmp/ob-${{ github.run_id }}-"*
diff --git a/.forgejo/workflows/publish-source.yml b/.forgejo/workflows/publish-source.yml
index 6bd42b2a..8220bac9 100644
--- a/.forgejo/workflows/publish-source.yml
+++ b/.forgejo/workflows/publish-source.yml
@@ -12,11 +12,6 @@ on:
push:
tags:
- 'v*'
- workflow_dispatch:
- inputs:
- ref_reason:
- description: 'why this manual run (e.g. tag event dropped)'
- required: false
jobs:
publish:
@@ -37,31 +32,22 @@ jobs:
run: |
set -eo pipefail
- SOURCE_NPM_REG="https://source.soulcraft.com/api/packages/soulcraftlabs/npm/"
+ SOURCE_NPM_REG="https://source.soulcraft.com/api/packages/soulcraft/npm/"
VERSION="$(node -p "require('./package.json').version")"
- # The dist-tag follows the version: a prerelease (any hyphen —
- # 10.4.0-rc.1) publishes under 'rc' and must NEVER move 'latest' —
- # every consumer resolving 'latest' from this registry would otherwise
- # be handed a release candidate. Same rule scripts/release.sh applies
- # to the storefront leg.
- NPM_TAG="latest"
- case "$VERSION" in
- *-*) NPM_TAG="rc" ;;
- esac
- echo "Publishing @soulcraftlabs/brainy@${VERSION} to The Source registry (dist-tag: ${NPM_TAG})..."
+ echo "Publishing @soulcraft/brainy@${VERSION} to The Source registry..."
TMPRC="$(mktemp)"
chmod 600 "$TMPRC"
{
- echo "@soulcraftlabs:registry=${SOURCE_NPM_REG}"
- echo "//source.soulcraft.com/api/packages/soulcraftlabs/npm/:_authToken=${FORGE_NPM_TOKEN}"
+ echo "@soulcraft:registry=${SOURCE_NPM_REG}"
+ echo "//source.soulcraft.com/api/packages/soulcraft/npm/:_authToken=${FORGE_NPM_TOKEN}"
} > "$TMPRC"
# The release script bumps package.json's version before it tags, so
# this tag's checkout already carries the version being published —
# nothing here re-derives it from the tag name.
PUBLISH_OK=true
- if ! npm publish --tag "$NPM_TAG" --userconfig "$TMPRC"; then
+ if ! npm publish --tag latest --userconfig "$TMPRC"; then
PUBLISH_OK=false
fi
@@ -69,7 +55,7 @@ jobs:
# exit code: a benign duplicate publish (a prior run, or a mirror, already
# landed this exact version) reports failure even though the registry
# already holds the right content.
- LANDED_VERSION="$(npm view "@soulcraftlabs/brainy@${VERSION}" version --userconfig "$TMPRC" 2>/dev/null || echo "")"
+ LANDED_VERSION="$(npm view "@soulcraft/brainy@${VERSION}" version --userconfig "$TMPRC" 2>/dev/null || echo "")"
rm -f "$TMPRC"
if [ "$LANDED_VERSION" != "$VERSION" ]; then
@@ -78,7 +64,7 @@ jobs:
fi
if [ "$PUBLISH_OK" = true ]; then
- echo "Published and verified @soulcraftlabs/brainy@${VERSION} on The Source registry."
+ echo "Published and verified @soulcraft/brainy@${VERSION} on The Source registry."
else
- echo "::warning::npm publish reported failure, but readback confirms @soulcraftlabs/brainy@${VERSION} is already live on The Source (a prior run or mirror landed it) — treating this run as successful, since the registry content is correct. Any OTHER failure mode would have failed the readback check above instead."
+ echo "::warning::npm publish reported failure, but readback confirms @soulcraft/brainy@${VERSION} is already live on The Source (a prior run or mirror landed it) — treating this run as successful, since the registry content is correct. Any OTHER failure mode would have failed the readback check above instead."
fi
diff --git a/CHANGELOG.md b/CHANGELOG.md
index fc577c1d..5482bf3f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,212 +2,7 @@
All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
-
-### [10.4.12](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.4.11...v10.4.12) (2026-09-03)
-
-- Mixed-kind fields index exactly, arrays to 256, a drained loop is not a shutdown, and finds project from the column store
-- fix(index): a metadata field holds every value kind it was written with — one posting column per (field, kind); an equality filter reads the query value's own kind, a range routes by its bounds; nothing is refused and nothing is silently dropped; an index written by the old shape opens unchanged (a128f0ed)
-- fix(metadata): metadata arrays index up to 256 elements; a longer array refuses at write time by name (MetadataArrayTooLargeError) — a vector parked in metadata now throws; move it to `vector` (e435da78)
-- fix(shutdown): beforeExit runs a non-closing flush only — a script that never calls close() exits with the writer lock on disk and no clean-shutdown marker, and the next open evicts the stale lock and folds the log, bounded; SIGTERM and SIGINT are unchanged (6baa4d7f)
-- feat(find): field projection — find({fields}) and get({fields}) resolve scalars from the column store on every leg, including vector-leg finds; absent fields stay absent (ad0f493f)
-- fix(find): orderBy is the order on every find path, not only the metadata-only one (5e720d17)
-- fix(metadata): the legacy sparse range path orders values, or refuses by name — never ranks by hash (a7eb7f52)
-- fix(close): a read-only brain writes nothing under `_system/` (f27a7776)
-- fix(contract): the flush gate's internals are private, not doors (72c8ee6a)
-- test(hygiene): the triple-intelligence correctness cases sit in the gate; the idle and connected-find pins name the brain they measure (28083981)
-- ci(release): the rail writes its own wall entry into the shared releases repo — never hand-written again (adcb883e)
-
-### [10.4.11](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.4.9...v10.4.11) (2026-09-02)
-
-- ci: superseded pushes cancel their own runs (concurrency per ref) (6053f6d4)
-- test(batch): the batch-size-limit tests add unvectored items — they test batching, not embedding (a1423c6d)
-- fix(flush): the gate settles its waiter from the machine, never from a chain (dea3ec20)
-- test(batch): the batch-vs-individual timing assertion runs in the perf lane, not the correctness gate (ebb3a4bf)
-- test(gate): the coverage guard counts the perf lane's config as a gate (2c5e3474)
-- chore(contract): emit the 10.4.11 manifest (4142f368)
-- fix(close): a read-only brain writes no clean-shutdown evidence — the marker is the writer's word about itself (367ca721)
-- fix(generation-store): commitTransaction refuses while single-ops are pending — the order invariant is enforced, not assumed (a79db434)
-- test(shutdown): pin one owner per brain — real processes, real signals (da951990)
-- fix(shutdown): one owner per brain — the signal handler defers to close(), and flush is single-flight (ec644bde)
-- fix(vfs): a path-scoped search is a served range over the path, not a refused prefix match (65493ba2)
-- ci(test): perf and scale benchmarks leave the correctness gate (dee46b35)
-- test(open): pin the pending-embed checkpoint — stuck id, crash matrix, torn fallback (1fb51093)
-- perf(open): the pending-embed fold is bounded by a checkpoint of the SET, not an empty-only mark (15d4f65d)
-- perf(open): a sealed segment the manifest proves is below the bound is never read (bc70c43d)
-- fix(find): a page the metadata block already cut is not cut again (905c267c)
-- fix(find): the hybrid legs rank inside the filter, and only the page is read (b1c70544)
-- ci(delta-gate): add a push fallback trigger alongside workflow_dispatch (67ae0046)
-- ci: add the delta-gate workflow for the capped functional lane (9922631d)
-- docs(plugin): the planner door's hiddenIds contract is the answer, not the mechanism (2633e8d5)
-- feat(engine): a protected factory for the generation store — a subclass may substitute one that keeps the contract (f763317a)
-- fix(find): near() searches around the anchor's own vector, and refuses by name without one (a8c5fbf9)
-- Merge remote-tracking branches 'origin/fix/planner-provider-door' and 'origin/fix/containment-batching' into rel/10.4.10-candidate (34f1886f)
-- feat(plugin): an optional planFindPage door — an index that can plan a find answers it in one call (4d5f823f)
-- perf(vfs): repairContainment's reconcile is one paged edge walk, not one graph call per file (3e60aded)
-
-
-### [10.4.9](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.4.6...v10.4.9) (2026-09-02)
-
-- Merge branch 'fix/pending-embed-low-water' into rel/10.4.9-candidate (2648f56d)
-- fix(open): pending-embed recovery keeps the crash-recovery contract — foreground, bounded by the mark (8a2ebacf)
-- Merge branches 'fix/connected-find-order', 'fix/pending-embed-low-water' and 'fix/related-verb-array' into rel/10.4.9-candidate (d5147ed6)
-- fix(graph): the verb fast paths honour every requested type, source, and target (6a89adc4)
-- perf(open): pending-embed recovery is bounded by a low-water mark and runs behind the doors (88e79729)
-- fix(find): connected finds are graph-first — neighbours, then the filter over those ids, then the page (077cbc0b)
-- fix(storage): counts persistence is single-flight, coalesced, and never races its own temp file (5e3b343a)
-
-
-### [10.4.6](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.4.5...v10.4.6) (2026-08-31)
-
-- fix(transact): metadata-index ops take their JSON-safe view at the crossing, not at construction (73500e7d)
-
-
-### [10.4.5](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.4.4...v10.4.5) (2026-08-31)
-
-- build(release): the docs-push step retires — this engine documents itself in its own repository (d6bcb14f)
-- fix(generations): a sealed segment may only declare the generations it holds (a963a744)
-- fix(recovery): a torn generation-log tail is a terminal verdict, never a wait (c9930871)
-
-
-### [10.4.4](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.4.3...v10.4.4) (2026-08-28)
-
-- fix(vfs): the old-root sweep narrates only when it has something to say (d49148e1)
-- fix(tests): the health-gate pin follows the verdict, and the VFS suite uses its own store (42e2da25)
-- Merge branch 'next/open-lazy-open-and-counts' (5ebd3b40)
-- docs: the contract manifest stands alone; public docs describe this engine only (a8c724a2)
-- docs(releases): 10.4.4 consumer notes — correctness and observability, with the performance line stated exactly (61a46927)
-- docs: measurements in public history carry numbers, not provenance (02c61636)
-- feat(open): name the two steps that hold the vfs-bootstrap phase (2cf38010)
-- fix(storage): a dead flush watch falls back to the 500ms poll, not the 30s sweep (5c22f950)
-- fix(storage): the flush watcher cannot arm twice in its async window (16d2e1a9)
-- perf(idle): the flush-request watch is event-driven; the heartbeat is observability (fb1da1c5)
-- perf(open): answer "are there any entities?" with one directory read (417ddb51)
-- perf(generations): discover generations by directory name, not by walking the log (9dd39921)
-- fix(flush): clear() and repairIndex() set the dirty witness themselves (e4c27fbc)
-- feat(open): the open names the STEP that cost the time, not just the phase (5a091cca)
-- perf(vfs): the old-root sweep runs once per store, not once per open (4a67aa0f)
-- chore: keep the generated neural stamps at main's values (c1f09723)
-- feat(contract): declare contract 1, serve three operators, refuse four by name (48802ba3)
-- fix(open): a provider rebuilding itself is a third state, not a CRITICAL (50676c02)
-- feat(open): open never waits for a provider that is rebuilding itself (131daa08)
-- perf(flush): an idle brain does no work — no periodic flush without a write (f5a6cb3f)
-- feat(repair): repairIndex narrates every phase and its receipt carries the walls (3fffd9c6)
-- fix(storage): a suspect count ledger heals itself, and counts.json is written atomically (f4e2d34b)
-- feat(open): the open narrates itself, on a channel production cannot clamp (afe08a1f)
-- fix(storage): a clean close is recorded, and the writer lock is always given up (e652162c)
-- docs: repository links point at soulcraftlabs/open-brainy — the soulcraft/brainy path becomes the native engine's repo tonight (38c3397b)
-
-
-### [10.4.3](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.4.2...v10.4.3) (2026-08-27)
-
-- Merge branch 'next/open-brainy-rename' (a58372f0)
-- chore: rename to @soulcraftlabs/brainy for Open Brainy on The Source (a99b1e83)
-- docs(releases): 10.4.3 — Open Brainy's first release under the new name, same engine as 10.4.2; The Source is the one registry (9f248b24)
-
-
-### [10.4.2](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.4.2-rc.1...v10.4.2) (2026-08-27)
-
-- docs(releases): 10.4.1 and 10.4.2 consumer notes; 10.4.2 is the last MIT release under this name, Open Brainy continues at @soulcraftlabs/brainy (a082e0ef)
-
-
-### [10.4.2-rc.1](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.4.1...v10.4.2-rc.1) (2026-08-27)
-
-- Merge branch 'next/zero-norm-unvector-door' (9b84ef5b)
-- fix(vectors): a zero-norm vector is not a vector, canonical side included, plus the sanctioned unvector door (0de76659)
-- fix(hnsw): skip unvectored rows on rebuild; refuse empty vectors in the index (8fc553b1)
-- fix(storage): derive the canonical count ledger from identity records, stamp the derivation rule, and mark legacy-derived ledgers suspect at load (fd6b4ce4)
-- Merge branch 'next/enumeration-identity-rekey' (204d74c1)
-- fix(storage): enumeration re-keys on the identity record, not the vector leg (f8d8ce16)
-- fix(init): rethrow plugin activation failures with the original error as cause so the originating frame survives to the caller (2496e09a)
-- Merge branch 'next/vfs-root-zero-norm' (4c7b0fab)
-- fix(vfs): the VFS root never persists a zero-norm vector (c6cc0de9)
-- build: derive generated-file stamps from git commit time, not wall clock (8a5c1245)
-- Merge remote-tracking branch 'origin/release/10.4.1' (aad9e2ee)
-- docs(concepts): the serving law — a failure is graded by whether an answer could be wrong, never by the cost of the fix; reads refuse per family (2914e0eb)
-- chore(release): 10.4.1-rc.1 (7870dc40)
-
-
-### [10.4.1](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.4.0...v10.4.1) (2026-08-26)
-
-- fix(reads): the read gate is per-family; a write carrying unchanged data never re-embeds (c039411e)
-- docs(guide): the docs pipeline publishes through the ingest API — the separate deploy step is retired (21e506e8)
-
-
-### [10.4.0](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.4.0-rc.4...v10.4.0) (2026-08-26)
-
-- docs(releases): the 10.4.0 entry catches up to the late trains — repair routing, the vector ledger and open-gate leg, the loud config guard, the JSON-safe crossing (834149ed)
-
-
-### [10.4.0-rc.4](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.4.0-rc.3...v10.4.0-rc.4) (2026-08-25)
-
-- feat(vector): the vectored-noun scalar joins the count ledger; the open gate closes the vector leg (9730835b)
-
-
-### [10.4.0-rc.3](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.4.0-rc.2...v10.4.0-rc.3) (2026-08-25)
-
-- fix(update-seam): the metadata crossing never carries BigInt endpoint ints (f4780c8e)
-- Merge branch 'worktree-agent-ad3aff0dffd17a6eb' (f14da34b)
-- fix(add): empty string is real data, not a missing field (258e9042)
-- feat(vfs): implement readdir's recursive option — typed since 7.30, never read (fc516da6)
-- feat(open-path): init never gates on the embedding model; open goes concurrent; slow opens narrate (96624f40)
-
-
-### [10.4.0-rc.2](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.4.0-rc.1...v10.4.0-rc.2) (2026-08-25)
-
-- test(readiness): the report helper's clock freezes — two independently-built reports compared across a millisecond tick made the plant lane red (39b916a3)
-- feat(repair): a heal:'repair' verdict routes to the provider's own incremental repair() (553e0d97)
-- fix(storage): an unknown nested storage config can never silently land on the shared default root (ddd5e719)
-- docs(release): the 10.4.0 entry, the index-health concept doc, and the API surfaces — written from the tree, not the plan (8cced871)
-- fix(plugins): the silent-degrade doors close — a broken accelerator install can never read as absent (b9ba50fb)
-- feat(recovery): the catchup verdict is consumed; verb rows go live; the metadata rebuild goes online (18f172e0)
-- feat(health): the gate reads the named report — reads refuse loudly, never rebuild; open serves before it returns; the ceremony door (f8f64780)
-
-
-### [10.4.0-rc.1](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.3.1...v10.4.0-rc.1) (2026-08-24)
-
-- ci(publish): the home dist-tag follows the version — a prerelease publishes under 'rc' and never moves 'latest' (a1376e4a)
-- chore(release): --source-only — a home-only prerelease mode (The Source, never the storefront) (dcbad176)
-- test(fold-checkpoint): the ARM-AT-FLIP pin arms its crash instead of racing the pending-flush timer (4176439b)
-- fix(health): one contract for a throwing probe — heal is none, serving is not withheld; repair report gains missing/rebuilt/reason (116550eb)
-- feat(storage): the canonical count ledger — ALL-visibility scalars, unclamped totals, suspect-on-unprovable-delete (7c8c8be3)
-- fix(delete): the null-metadata skip closes — index legs run id-keyed or narrate, never silently strand postings (607e9f54)
-- feat(repair): repairIndex returns the per-family receipt and narrates its summary (8d45f964)
-- fix(reads): the readiness gate guards every index read surface — serving empty from a not-ready provider is unrepresentable (40e7119b)
-- ci(gate): the machine-health preflight and the truncation verdict guard (1e046aa1)
-
-
-### [10.3.1](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.3.0...v10.3.1) (2026-08-18)
-
-- docs(releases): the 10.3.1 consumer entry — the fold that behaves (900cc895)
-- fix(recovery): the fold streams and narrates; the checkpoint chain arms at the flip (ed7d1db9)
-
-
-### [10.3.0](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.2.0...v10.3.0) (2026-08-18)
-
-- docs(releases): the 10.3.0 consumer entry — the trust-and-provenance release (97d75649)
-- fix(locks): the fence keys ownership on pid+hostname — a same-process re-open never fences its predecessor (0991cf28)
-- test(budgets): iron-honest wall-clock budgets — 3x the worst honest-iron measurement (314e0e6c)
-- fix(locks): live writers are never auto-evicted; evicted writers are fenced at every commit barrier (292e7c04)
-- feat(log): system commits carry their origin; the attested per-id reconcile door (9ac9e706)
-
-
-### [10.2.0](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.1.0...v10.2.0) (2026-08-17)
-
-- docs(releases): the 10.2.0 consumer entry — adoption completes in one call (97538e1f)
-- ci: the correctness plant runs integration + conformance on every push — a release never waits on a second machine (b17fdc8e)
-- fix(adoption): the baseline backfill runs to completion — one call adopts a pre-log baseline of any size (a5a18838)
-
-
-### [10.1.0](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v10.0.0...v10.1.0) (2026-08-13)
-
-- docs(releases): the 10.1.0 consumer entry — bounded recovery, restore founding, the two write-path cures (7d3c8696)
-- fix(restore): a restore is an unclean event — the swap runs quiesced and the snapshot's durability stamps never survive it (9ca80667)
-- feat(recovery): the fold-checkpoint bound — crash folds (checkpoint, head], never the whole log twice (ff43de1a)
-- fix(log): pad-frame construction is total; the at-ack sync-failure compensation splits by phase — a production adoption's two write-path defects, cured at their roots (cbe34d11)
-- feat(query): the sparse-store cut — where on a never-carried field serves operator truth, never a refusal (7b67db4d)
-
-
-### [10.0.0](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v9.0.0...v10.0.0) (2026-08-12)
+### [10.0.0](https://source.soulcraft.com/soulcraft/brainy/compare/v9.0.0...v10.0.0) (2026-08-12)
- fix(adoption): the baseline backfill cures hydration-law drift — existing brains reach the crash-safe default with zero operator steps (25f0dd96)
- fix(adoption): the reserved-root mint exemption — int 0 is legitimate for exactly one id (2abe8b38)
@@ -239,7 +34,7 @@ All notable changes to this project will be documented in this file. See [standa
- test: version-coupling pins go major-agnostic — the 8.x literals broke at the 9.0.0 bump while the coupling law itself behaved correctly (8a6807e8)
-### [9.0.0](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v8.11.0...v9.0.0) (2026-08-04)
+### [9.0.0](https://source.soulcraft.com/soulcraft/brainy/compare/v8.11.0...v9.0.0) (2026-08-04)
- docs: 9.0 namespace-migration guide — the simple story + the mechanical sweep checklist, published for humans and tooling alike (61ab9db2)
- fix(release): storefront leg republishes CI's exact forge artifact — byte-identity by construction, verified by cross-registry shasum before the ceremony reports success (d89df2ed)
@@ -274,7 +69,7 @@ All notable changes to this project will be documented in this file. See [standa
- feat: scanFacts liveness contract — first batch or loud failure within a documented bound (f8e6da2b)
-### [8.11.0](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v8.10.1...v8.11.0) (2026-07-27)
+### [8.11.0](https://source.soulcraft.com/soulcraft/brainy/compare/v8.10.1...v8.11.0) (2026-07-27)
- docs: the last two archived-host links point home (91ef1c8b)
- feat: includeHidden — export carries every visibility tier for migration-grade canon completeness (63c1eeb9)
@@ -283,19 +78,19 @@ All notable changes to this project will be documented in this file. See [standa
- ci: run the pipeline on the forge (999d0ebb)
-### [8.10.3](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v8.10.2...v8.10.3) (2026-08-03)
+### [8.10.3](https://source.soulcraft.com/soulcraft/brainy/compare/v8.10.2...v8.10.3) (2026-08-03)
- docs: dedupe the 8.10.2 release-notes entry the cherry doubled onto the branch (8c956608)
- fix: user metadata named 'level' is a real field everywhere — the engine-internal node layer no longer shadows it in sort/filter/aggregation, and the indexing views stop stamping a phantom 0 into its column; index epoch 2 rebuilds existing brains at first open (958a0859)
-### [8.10.2](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v8.10.1...v8.10.2) (2026-07-29)
+### [8.10.2](https://source.soulcraft.com/soulcraft/brainy/compare/v8.10.1...v8.10.2) (2026-07-29)
- docs: 8.10.2 consumer release notes — update() write granularity, PathResolver idle-log fix, graph-lsm key recognition (a0123b5b)
- fix: metadata-only update() never rewrites the noun record — the unconditional whole-vector save turned per-entity stat touches into full rewrites+fsync, amplifying read-heavy sweeps into disk saturation on a production deployment (5b65eb82)
-### [8.10.1](https://source.soulcraft.com/soulcraftlabs/open-brainy/compare/v8.10.0...v8.10.1) (2026-07-24)
+### [8.10.1](https://source.soulcraft.com/soulcraft/brainy/compare/v8.10.0...v8.10.1) (2026-07-24)
- refactor: remove the orphaned transaction-result type left behind by the dead-path removal (edf123a5)
- fix: warm() metadata surface routes through the active provider (warm hook added to the metadata contract); add maintenanceDebt() observability surface (5b2cbf74)
diff --git a/CLAUDE.md b/CLAUDE.md
index 56df0b72..c7336a18 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -12,13 +12,13 @@ Handoff file: `/home/dpsifr/.strategy/PLATFORM-HANDOFF.md`
**Brainy's current open actions:** None. MIT open-source — no platform-specific actions.
-**Current version:** run `npm view @soulcraftlabs/brainy version --registry https://source.soulcraft.com/api/packages/soulcraftlabs/npm/` (never trust a hardcoded number here — this line went stale for months); consumer-facing changes tracked in `RELEASES.md`
+**Current version:** run `npm view @soulcraft/brainy version` (never trust a hardcoded number here — this line went stale for months); consumer-facing changes tracked in `RELEASES.md`
---
## Project Overview
-Brainy is a Universal Knowledge Protocol -- a Triple Intelligence database that combines vector similarity search, graph traversal, and metadata filtering into a single TypeScript library. Published as `@soulcraftlabs/brainy` on The Source (source.soulcraft.com registry) under the MIT license.
+Brainy is a Universal Knowledge Protocol -- a Triple Intelligence database that combines vector similarity search, graph traversal, and metadata filtering into a single TypeScript library. Published as `@soulcraft/brainy` on npm under the MIT license.
## Getting Started
@@ -91,7 +91,7 @@ test: add/update tests (patch version bump)
## Docs Pipeline — soulcraft.com/docs
-Docs in `docs/**/*.md` are published with the npm package (included in `files`) and go live on soulcraft.com/docs via the docs ingest API: the release script's `scripts/push-docs.js` step POSTs every public doc to `https://soulcraft.com/api/docs/ingest` (auth: `DOCS_INGEST_SECRET` in the environment). No separate deploy step is involved (the old deploy-to-publish flow was retired in a platform change, 2026-08). Frontmatter controls what appears publicly.
+Docs in `docs/**/*.md` are published with the npm package (included in `files`) and synced to soulcraft.com/docs on every portal deploy. Frontmatter controls what appears publicly.
### Docs check triggers
@@ -161,9 +161,9 @@ npm run release:major # Breaking changes (rare, manual decision)
The script: verifies clean git state, builds, tests, bumps version, updates CHANGELOG.md, commits, tags, pushes, publishes to npm, and creates a GitHub release.
After a successful release, remind the user:
-> "Published. Docs are live on soulcraft.com/docs (pushed via the ingest API during the release) — spot-check a changed page with curl."
+> "Published. Deploy portal to pick up the new docs → go to the portal project and deploy."
-There is no separate deploy step anymore. If the docs push failed (the script warns loudly), re-run `node scripts/push-docs.js` with `DOCS_INGEST_SECRET` set.
+Do NOT deploy portal from here. Portal is always deployed separately from within the portal project.
## Closed-Source Product Names — HARD RULE
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index c58520b7..d277091d 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -6,7 +6,7 @@ may find elsewhere in the repo's history.
## Where the project lives
-The source of truth is a self-hosted forge: **source.soulcraft.com/soulcraftlabs/open-brainy**.
+The source of truth is a self-hosted forge: **source.soulcraft.com/soulcraft/brainy**.
It's anonymously readable and cloneable — no account needed to browse, clone,
or build.
@@ -31,7 +31,7 @@ fine) to talk through the approach saves everyone rework.
## Development setup
```bash
-git clone https://source.soulcraft.com/soulcraftlabs/open-brainy.git
+git clone https://source.soulcraft.com/soulcraft/brainy.git
cd brainy
npm install
npm run build
@@ -41,20 +41,6 @@ npm test
Tests run on [Vitest](https://vitest.dev/). `npm test` runs the unit suite;
see `package.json` for `test:integration`, `test:coverage`, and friends.
-## Test gate
-
-The release gate is a bare `vitest run` (no `--config` flag) — the same
-command the delta gate and CI's checks invoke. It carries the full
-correctness suite and nothing else: wall-clock/scale benchmarks
-(`tests/performance/**`, `tests/critical-performance-benchmark.test.ts`,
-`tests/api/performance-benchmarks.test.ts`) and the two tests whose outcome
-depends on the host machine or network rather than the code
-(`tests/package-size-limit.test.ts` shells out to the `npm` CLI;
-`tests/model-loading.test.ts` makes a real network call to download a model)
-are excluded from it, because a timing threshold or a flaky network call has
-no business failing a correctness check. That whole family runs on demand,
-in its own exclusive slot, via `npm run test:perf`.
-
## Standards
- **Strict TypeScript.** No `any` escape hatches to dodge the type checker.
@@ -71,17 +57,6 @@ in its own exclusive slot, via `npm run test:perf`.
description states a number, cite the benchmark that produced it (see
[docs/performance-envelopes.md](docs/performance-envelopes.md) for the
pattern). Don't state an estimate as if it were measured.
-- **Measurements carry numbers, not provenance.** Public commit messages and
- docs give the SHAPE a number was taken at and never where it was taken: no
- hostnames, no store or deployment identities, no operational anecdotes about
- someone's running system. "A 14,056-noun / 72,679-verb production-shaped
- store, measured solo under an exclusive lock" tells a reader everything the
- number depends on; the machine it ran on and whose data it was tell them
- nothing except where somebody's infrastructure lives.
-- **Documents that answer or reference a confidential specification never enter
- this repository, even summarized.** The public docs describe THIS engine and
- the published contract, and nothing else — a summary of a private document is
- still that document's contents.
## License
diff --git a/README.md b/README.md
index 762c9ec3..ca558340 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,5 @@
-
+
Brainy
@@ -11,9 +11,9 @@
-
-
-
+
+
+
@@ -30,8 +30,6 @@
---
-**Open Brainy** is the MIT engine — the open API, client library, types, and protocol; an openly specified canonical on-disk format; and this TypeScript reference engine, scoped as a single-node engine for stores up to roughly one million rows. `@soulcraft/brainy` 10.4.2 was the last release under the old package name — the name passes to the native engine, **Brainy**, at 11.0.0: the same API over the same open format at production scale, and it requires a license.
-
Built because we were tired of stitching a vector store to a graph database to a document store — and spending weeks on plumbing before writing a line of business logic. Brainy indexes every fact **three ways at once** and lets one call query them together:
| You write | Brainy indexes it as | You query it with |
@@ -47,14 +45,12 @@ It runs **inside your process** — no server, no Docker, nothing to operate —
## Quick start
```bash
-bun add @soulcraftlabs/brainy # Bun ≥ 1.1 — recommended
-npm install @soulcraftlabs/brainy # Node.js ≥ 22
+bun add @soulcraft/brainy # Bun ≥ 1.1 — recommended
+npm install @soulcraft/brainy # Node.js ≥ 22
```
-> **Registry**: add `@soulcraftlabs:registry=https://source.soulcraft.com/api/packages/soulcraftlabs/npm/` to your `.npmrc` (anonymous read).
-
```javascript
-import { Brainy, NounType, VerbType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType, VerbType } from '@soulcraft/brainy'
const brain = new Brainy() // in-memory; one line swaps to disk
await brain.init()
diff --git a/RELEASES.md b/RELEASES.md
index c875cb26..df05a81e 100644
--- a/RELEASES.md
+++ b/RELEASES.md
@@ -1,14 +1,7 @@
# @soulcraft/brainy — Release Notes for Consumers
-Machine-readable release notes are published at
-https://source.soulcraft.com/soulcraftlabs/releases/raw/branch/main/open-brainy.json
-(this engine) and
-https://source.soulcraft.com/soulcraftlabs/releases/raw/branch/main/brainy.json
-(the product engine) — read by HQ's `/hq/releases` door, and the source of
-truth ahead of this file.
-
This file is the **quick reference for downstream sessions** tracking Brainy changes.
-Full auto-generated changelog: `CHANGELOG.md` · Releases: https://source.soulcraft.com/soulcraftlabs/open-brainy/releases
+Full auto-generated changelog: `CHANGELOG.md` · Releases: https://source.soulcraft.com/soulcraft/brainy/releases
**How to use:** Brainy is the underlying data engine for downstream applications. Read this when:
- Upgrading `@soulcraft/brainy` in your application
@@ -38,455 +31,6 @@ is sometimes cited as a 7.x removal — those methods never existed on 7.x; the
---
-## v10.4.4 — 2026-08-28
-
-**A correctness and observability release.** The headline is not speed: it is that a
-restart now tells you the truth about itself, a store stops lying about how much it
-holds, and the engine stops doing work nobody asked for. There is a performance
-improvement and it is modest; it is stated exactly below rather than rounded up.
-
-### The dark restart — fixed at the root
-
-A service could stop cleanly, exit 0, having awaited `close()` on every store it held,
-and its next boot would announce `Overwriting stale writer lock … appears dead` for
-every one of them. Nothing had crashed. Two deployments hit this; the same defect also
-made those boots pay a crash-recovery fold they did not owe.
-
-The cause was not the lock. `close()` released it correctly — when it got there. A
-failure part-way through close skipped both the release AND the clean-shutdown marker,
-and "the recorded pid is gone" reads identically for an orderly restart and a crash.
-
-- `close()` is now two parts and the second is unconditional: the flush-request watcher,
- the **writer lock**, the VFS timers and the terminal `closed` flag are released whether
- the durable steps succeeded or not. The original failure is narrated with what it costs
- the next open, then rethrown.
-- Releasing the lock writes a **clean-close record** naming the lock generation it gave
- up. The next open reads that record instead of guessing: recorded → nothing to recover;
- absent → it says so, and names the recovery it is about to run. This also ends two
- long-standing false alarms — a recycled pid locking a store out of its own reopen, and
- `Re-acquiring writer lock … this is a bug` after a perfectly clean close.
-- The signal path stopped failing in a batch. One store's failing flush used to strand
- every remaining store's lock and markers — at exit code 0. Now: per-store isolation, the
- generation store's close (the marker) is part of shutdown, the lock goes in a `finally`,
- and the handler no longer calls `process.exit()` when the host application has its own
- signal handler, a race that truncated the host's own shutdown mid-flight.
-
-### The count ledger stops lying, and `counts.json` is written atomically
-
-The all-tier scalars are the denominator a coverage check subtracts against. A ledger
-derived under the old rule — one entity per id DIRECTORY — counted ghost and scar
-containers as rows, and was only FLAGGED suspect: it went on serving wrong numbers for
-the life of the store. Two copies of one archive could disagree, and a downstream index
-heal reported remaining work that did not exist.
-
-- Such a ledger now derives itself honestly **in the background** after the open, counting
- identity records, and persists the correction stamped. Nothing waits for it, because no
- read is served from a denominator.
-- A derivation that raced a write refuses to stamp its number: one retry on a quiet store,
- then the ledger stays SUSPECT and names `repairIndex()` as the door that recounts under
- a barrier.
-- `counts.json` is written temp+rename. A truncating write left a window in which a
- concurrent reader saw the file EMPTY — and an unparseable ledger sends the next open
- down the full-rescan path, so the cheapest file in the store was buying the most
- expensive recovery.
-
-### An open and a repair narrate themselves — on a channel a log level cannot silence
-
-A store could open for three minutes and print nothing at all. The phase timings existed;
-they were written to a channel that every production-looking environment clamps away.
-
-- Narration moved to an always-visible channel. An open now heartbeats the phase it is in,
- names each phase as it ends with what it was paying for, and names the expensive STEP
- inside a phase. `repairIndex()` does the same and its receipt carries a per-family
- `durationMs` — a repair that ran for half an hour with no output could only be watched
- through `top`.
-- A brain nobody has written to now does nothing: a flush over a clean store is a no-op
- and says nothing, the graph index's auto-flush asks before it acts, and the
- cross-process flush-request watch is **event-driven** (`fs.watch`) instead of polling a
- directory every 500 ms per store forever, with a slow safety sweep behind it and a
- narrated fall back to polling where a filesystem cannot be watched.
-- A provider that is REBUILDING ITSELF is no longer confused with a broken one. `init()`
- does not wait for it, every other family serves, and that family's doors refuse **by
- name, carrying the provider's own progress**, saying plainly that they open by
- themselves and no action is needed. Health narration dedupes by content, so an unchanged
- verdict is silent however a provider's generation counter moves.
-
-### For operators — one behaviour change
-
-**Four `where` operators that previously returned an empty page now raise
-`INVALID_QUERY`:** `startsWith`, `endsWith`, `matches` and `length`. An equality/range
-posting index cannot evaluate a substring, a pattern or an array length without reading
-every row, and it now refuses by name instead of answering with an empty result that
-looks like an answer.
-
-**Three that previously returned an empty page are now SERVED:** `hasAll`, `noneOf` and
-`excludes`. All 25 accepted operator tokens now agree between this engine and its
-accelerated counterpart.
-
-### Performance — stated exactly
-
-Measured on a 14,056-noun / 72,679-verb production-shaped store, both builds solo under
-an exclusive lock:
-
-- **Warm reopen after a clean close: 85.7 s → 77.0 s (−10.2%).** The whole of that gain is
- one fix — generation discovery reads directory NAMES instead of recursively walking the
- entire generation log (−9.2 s, and it scales with history rather than row count). The
- VFS phase is **unchanged**.
-- **Cold open: −31.4 s** (518.1 s → 486.7 s), of which the count-ledger derivation moving
- off the critical path accounts for storage-init dropping 5,941 ms → 25 ms.
-- **A dominant ~38 s remains, diagnosed and NOT fixed.** It is not the VFS — the VFS's own
- init is under 2 s of that phase. It is the log-authority adoption and/or the
- pending-embed log recovery, both now instrumented so the next measurement names the
- culprit outright.
-
-Continuing work, named so nobody has to rediscover it: that ~38 s term; making the
-generation store's committed-range set lazy; the hydration path that substitutes
-`Date.now()` for an unreadable stored timestamp (inventing data); and a VFS path-prefix
-filter built with a `$startsWith` spelling no operator set accepts, so
-`searchFiles({ path })` throws today.
-
----
-
-## v10.4.3 — 2026-08-27 (Open Brainy's first release)
-
-**`@soulcraftlabs/brainy` 10.4.3 is the same engine as `@soulcraft/brainy` 10.4.2, byte for
-byte — only the name, the registry, and the pointers changed.** Install:
-
-```bash
-npm install @soulcraftlabs/brainy
-```
-
-with the registry line in your `.npmrc` (anonymous read):
-
-```
-@soulcraftlabs:registry=https://source.soulcraft.com/api/packages/soulcraftlabs/npm/
-```
-
-- **The Source is the one registry.** Open Brainy publishes to source.soulcraft.com only; the
- npmjs republish step is retired from the release rail. Existing npmjs versions of
- `@soulcraft/brainy` stay as they are and receive no new versions.
-- **The repository moved** to `soulcraftlabs/open-brainy` on The Source; the old path redirects.
-- **No engine change.** Everything in the 10.4.2 notes applies unchanged; adoption is one
- install-line change (`@soulcraft/brainy` → `@soulcraftlabs/brainy`), which downstream
- applications make together with their native-engine bump.
-
-## v10.4.2 — 2026-08-27 (a zero-norm vector is not a vector)
-
-**This is the last release of the MIT engine under the `@soulcraft/brainy` name.**
-The MIT package continues as **Open Brainy** — `@soulcraftlabs/brainy`: the open API,
-client library, types and protocol, an openly specified canonical format, and the TypeScript
-reference engine, scoped honestly as a single-node engine for stores up to roughly one
-million rows. The `@soulcraft/brainy` name passes to the native engine, **Brainy**, at a
-major version bump; that engine implements the same API over the same open format at
-production scale, requires a license, and refuses loudly without one. Nothing changes
-for existing installs until that major ships; the move is announced with it.
-
-Six fixes, one law: a vector with no magnitude carries no information, so it must
-never reach a vector index — in any engine — and the canonical store must say so.
-
-- **The permanently-unvectored row.** `add({ ..., vector: [] })` (and the same item
- shape in `addMany` / `transact`) is now the sanctioned "no vector" row: persisted
- with an empty vector leg, never embedded, never indexed, counted as unvectored in
- the canonical ledger. Metadata-only rows — telemetry tallies, counters, plumbing —
- no longer need a placeholder vector and never enter the vector leg. `vector: []`
- together with `deferEmbedding: true` is refused with a typed error (a supplied
- vector has nothing to defer). Previously `vector: []` threw a dimension error.
-- **The unvector door.** `update({ id, vector: [] })` (and its `transact()` twin) is
- the sanctioned way to strip a vector from an existing row: canonical vector → `[]`,
- removal from the vector index, the vectored ledger decremented exactly once — and
- idempotent, so a resumed cleanup pass may simply re-issue. It never re-embeds, and
- it clears a pending deferred-embed marker durably so the background worker cannot
- re-vector the row later. Note that a rebuild never sheds vectors (it re-derives the
- index from canonical rows); shedding historical vectors needs this door.
-- **Zero-norm vectors are normalized at the write.** An explicit all-zero vector on
- any write path is persisted as unvectored (`[]`) with one warning naming the row;
- the vector-index operations keep their own refusal as a second line. The engine's
- own VFS root, which used to persist a deliberate all-zero placeholder (harmless
- under cosine distance, a false attractor under a downstream engine's
- squared-euclidean serving — a production incident this week), is now created
- unvectored, and an existing store's legacy root is migrated on open by a single
- fixed-path read before the health gate runs — never a walk.
-- **Enumeration keys on the identity record.** `getNouns()` / `getVerbs()` and the
- cursor walks behind them enumerate by the metadata record, the same key the
- canonical ledger counts by — previously the walk keyed on the vector file, so a
- row holding metadata but no vector was counted yet never yielded (a permanent
- "missing" phantom in coverage math), while an orphaned vector-only directory
- could be yielded as a phantom id. The recovery fold also never deletes an existing
- vector when it replays a metadata-only after-image (preserve-if-absent). One
- documented gap remains: a verb's endpoints live only in its vector leg, so a
- metadata-only verb is counted and loudly skipped, never fabricated — the fix is a
- canonical-format change and lands with the open format.
-- **The ledger's one-time derivation counts identity records.** Stores upgraded from
- pre-ledger versions derived their ALL-visibility scalars once by counting id
- directories, which included ghost and scar containers left by an old partial-delete
- defect — an inflated denominator whose coverage row could never reach exact. The
- derivation now counts only directories holding a metadata record, `counts.json`
- carries a derivation-rule stamp, and a ledger derived under the old rule is marked
- `suspect` at open (one O(1) field read, one warning) so the online `repairIndex()`
- path clears it with a real recount.
-- **The vector index refuses what it cannot hold.** `rebuild()` skips unvectored and
- zero-norm rows (one summary line), re-pins the vector dimension from the first real
- vector after a restart (previously a restart left the pin unset, so a wrong-length
- insert became the new pin instead of being rejected), and `addItem` / `updateItem`
- throw a typed `EmptyVectorIndexError` on a length-0 vector instead of ever storing
- a vector-less node.
-- **Smaller:** a failing plugin activation now rethrows with the original error as
- `cause` (the originating file and line survive to the caller's log); build
- generators stamp from the repository history of their inputs instead of wall clock,
- so two builds of the same tree are byte-identical.
-
-Adoption: one restart, paired with its native-engine release. The first open of an
-existing store runs the legacy-root migration (one narrated line) and, on stores that
-upgraded from pre-ledger versions, marks the ledger suspect until the next sanctioned
-recount — no rebuild in either case.
-
-## v10.4.1 — 2026-08-26 (reads refuse per family; an unchanged write never re-embeds)
-
-Two production defects from the same week, fixed together as a patch to 10.4.0.
-
-- **The read gate is per family.** A read now refuses only when the index family it
- actually consults is unhealthy: a metadata filter is served while the vector leg is
- rebuilding; a semantic query is refused only by the vector family; a graph
- traversal only by the graph family. Previously any unhealthy family refused every
- read on the brain — under a long vector rebuild, a production deployment's
- metadata-only reads were refused for the duration, and the retries became a write
- pump of their own.
-- **Unchanged data never re-embeds.** `update()` compares the incoming `data`
- structurally with the stored record; an update carrying identical data (a common
- shape for periodic upserts) no longer embeds again and no longer churns the vector
- leg. Previously every such update re-embedded and re-inserted, which under load
- saturated the vector index with near-identical vectors.
-
-Adoption: one restart, paired with its native-engine release.
-
-## v10.4.0 — 2026-08-25 (the health report has a name)
-
-Three related cures, one root cause: an index deciding whether it could be trusted
-by sampling itself instead of by exact accounting. This release replaces every
-sampled self-probe with ledger-derived truth, and a read against an unhealthy index
-now refuses loudly instead of guessing.
-
-- **The canonical count ledger.** Storage now tracks two scalars per family
- (nouns/verbs) on the write path: the user-facing `counted` total — unchanged,
- still what `getNounCount()` / `getVerbCount()` return — and a new ALL-visibility
- `all` total covering every tier, the real denominator a derived index's own
- coverage math needs. The unfiltered storage-level `totalCount` returned by
- `getNouns()` / `getVerbs()` is now this unclamped ALL scalar; previously it could
- only ever move up (`Math.max(scalar, scanned)`), so an inflated counter could
- never self-correct. A delete that cannot prove the record it removed actually
- existed (no canonical read, no prior image available) no longer decrements on
- faith — it marks the ledger `suspect` (narrated once per session) instead of
- silently drifting, and the next `repairIndex()` clears the flag with a real
- recount.
-- **One contract for a throwing health probe.** A provider's `validateInvariants()`
- is documented to never throw — but if one does anyway (a bug, a transient fault),
- it is now read the same way everywhere: `heal: 'none'`, the error named in the
- report, never synthesized into a rebuild trigger and never swallowed into "looks
- fine." A flaky check can no longer buy itself a rebuild. `repairIndex()`'s
- per-family receipt also gains `missing` (an exact count plus a capped id sample),
- `rebuilt` (a full rebuild ran, vs. an incremental heal), and `reason`.
-- **The named health report; reads refuse instead of rebuilding.** Any index
- provider may now expose a synchronous, O(1) `healthReport()` — composed from the
- provider's own exact ledgers, never a sample — and this is the one signal
- Brainy's read gate trusts. The first-query lazy-build path is gone: `brain.init()`
- now runs every needed rebuild to completion before it returns, always, regardless
- of dataset size. A read that lands on a provider whose health report says it
- isn't serving throws a typed error instead of triggering a rebuild mid-query —
- `GraphIndexNotReadyError`, `MetadataIndexNotReadyError`, or
- `VectorIndexNotReadyError` (all exported from `@soulcraft/brainy`), naming the
- reasons. `repairIndex({ rebuild: ['metadata' | 'graph' | 'vector'] | 'all' })` is
- the new explicit operator door: it rebuilds the named family unconditionally, no
- health check consulted — reach for it when you have independent reason to
- distrust a family regardless of what it self-reports. Bare `repairIndex()` is
- unchanged in spirit: report-driven, heals only what its own checks say needs it.
-- New concept doc: [Index Health](docs/concepts/index-health.md) walks the whole
- story from a consumer's side — degraded-but-serving vs. not-ready, what
- `repairIndex()` checks and heals per family, what `suspect` counts mean.
-
-**Nothing to change to adopt this.** No API removed, no signature narrowed —
-`repairIndex()` gains an optional options bag and its return value gains fields,
-both additive. The honest notes: if your code ever relied on a `find()` against a
-cold/not-yet-built index quietly triggering a rebuild and returning results a beat
-later, that behavior is gone — it now throws one of the three typed
-`*NotReadyError` classes instead (catch them if you need to distinguish "not ready
-yet" from "no results"). And `disableAutoRebuild: true` no longer defers index
-construction to the first query — a needed rebuild always runs at `open()` now;
-the flag has no effect on timing. Full manual control still lives in
-`repairIndex({ rebuild: [...] })`.
-
-- **Crash-reopen catchup.** After an unclean shutdown, the metadata index now
- folds the exact fact window it missed — `find()` serves every acked write on
- reopen, closing the gap where canonical reads and counts recovered a
- crash-window write but the index kept serving its pre-crash state until the
- next full rebuild. Related root-cause fixed alongside: `close()` never
- stamped the index watermarks (only `flush()` did), so a close without a
- prior flush caused a needless full rescan verdict on the next open.
-- **Relation rows are live in the metadata index.** Previously verb rows
- entered the metadata index only during a rebuild — so a rebuilt store's
- relation postings went stale from the first `relate()` after it. Relations
- are now posted and retracted on the live write path (relate / unrelate /
- updateRelation / remove's cascade, and their `transact()` forms), in the
- same commit as the graph leg.
-- **The metadata rebuild is online.** `rebuild()` for the metadata family no
- longer clears and rebuilds in place (reads went empty for the duration): it
- builds a complete replacement beside the serving index, mirrors concurrent
- writes to both, swaps atomically, and persists once after the swap. Reads
- never observe a partial index. `repairIndex({ rebuild: ['metadata'] })` uses
- it automatically.
-- **Incremental heal is routed.** A provider invariant that asks for the
- incremental heal (`heal: 'repair'`) now routes to the provider's own
- `repair()` when it exposes one — re-posting exactly what its ledger names,
- never a store-sized rebuild — and the post-heal re-read of the report decides
- success; a repair that doesn't converge is recorded with the escalation named.
-- **The vector family joins the count ledger.** `getCanonicalCounts()` gains
- `vectors: { all }` — the count of canonical entities holding a real vector
- (deferred-embed entities count when their vector lands). And the open gate
- closes the vector leg: a store whose canonical rows hold vectors but whose
- derived vector index is empty now builds at `open()` (or refuses with the
- typed error) instead of silently serving empty vector-search results.
-- **An unknown storage config shape fails loudly.** A nested `config` object
- carrying a path-shaped key (a shape that was never supported) used to fall
- through silently to the default shared directory — every instance writing one
- store while callers believed each had its own. It now throws, naming the
- canonical `path` key.
-- **Relation index rows are JSON-safe.** Internal endpoint identifiers can no
- longer ride the metadata-index crossing (a native provider serializes it);
- they stay on the graph operations where they belong.
-- **A broken accelerator install can never read as "not installed."** The
- auto-detection free pass now requires the resolution error to name the
- accelerator package itself, exactly — a missing platform-binary sibling
- package, an inner file path, or a dependency failure is a broken install and
- `init()` throws loudly. And a plugin that declines activation is narrated on
- the always-on log channel, so `silent: true` can no longer hide a fallback
- to the default engines.
-
----
-
-## v10.3.1 — 2026-08-18 (the fold that behaves)
-
-Three recovery cures from one production first-boot incident (a brain's first
-process restart after a live storage-authority flip looked hung and was
-restarted three times mid-recovery). **Adopt this version before flipping
-brains with existing history** — it is the intended adoption target for
-fleets moving to the crash-safe authority.
-
-- **Recovery streams.** The boot-time log fold now consumes the generation
- log one segment-batch at a time — memory stays bounded at one segment for
- any log size. Previously it materialized every fact into one array, which
- on a ~7k-fact log produced multi-GB allocation pressure and a process that
- looked wedged while it worked.
-- **Recovery narrates.** The fold announces itself before the work begins
- ("recovery fold beginning — do not restart, the fold is finite") and prints
- progress every thousand facts. A visible fold gets to finish; a silent one
- gets killed by a well-meaning operator, and each kill makes the next boot
- pay the whole fold again.
-- **Bounded recovery from the flip itself.** Adopting the log authority now
- founds the recovery checkpoint at the moment of the flip (one paged
- canonical sync, bounded memory, then the stamp) — so even the FIRST unclean
- shutdown after a flip replays only the log's tail. Previously the bound
- could only establish itself at a completed crash recovery, which is exactly
- the recovery the incident kept interrupting.
-
----
-
-## v10.3.0 — 2026-08-18 (the trust-and-provenance release)
-
-Four consumer-driven cures. Pairs with the same native accelerator line
-(>=4.1.0); adopt alongside the accelerator's 4.2.0 for its paired fixes.
-
-- **Writer-lock fencing.** A live writer is never auto-evicted (staleness now
- requires the holding process to be dead — a >60s stall is a slow writer, not
- a dead one); the lock claim is atomic (no empty-file window a racer can
- misread as torn); and every flush commit and transact barrier verifies lock
- ownership first, so a forced-out or lock-deleted writer fails typed
- (`BRAINY_WRITER_FENCED`) instead of writing on unaware — the split-brain
- class a shared dev store hit is dead at all three roots. The documented
- same-process re-open ("warn and take over") stays benign: ownership is
- per-process. Consumers that raised stop-timeouts as mitigation can retire
- them.
-- **Transaction-log provenance.** `TxLogEntry` gains an optional `origin`
- field — absent means a user write (existing consumers unchanged);
- engine-originated commits stamp themselves (`system:embed-landing`,
- `system:adoption-backfill`, `system:reconcile`), and the same stamp rides
- the commit fact's meta. Activity feeds filter on fact instead of guessing;
- a reported "double tick" (the deferred vector landing indistinguishable from
- a user save) is cured without collapsing genuine rapid saves.
-- **The attested reconcile door.** `reconcileLogDivergence(id, {attest})`
- resolves the one adoption-refusing divergence class
- (`log-live-canonical-absent`) with a human's word: `'deleted'` mints the
- tombstone the log always lacked; `'restore'` folds the log's only copy back
- into canonical; wrong-class calls refuse typed with nothing written. Loud,
- narrated, single-row.
-- **Iron-honest test budgets.** The wall-clock micro-budgets are recalibrated
- as order-of-magnitude guards (3x the worst measurement across three machine
- classes) so honest hardware differences can never again read as failures;
- real performance enforcement lives in the dedicated perf lanes.
-
----
-
-## v10.2.0 — 2026-08-17 (adoption completes in one call)
-
-One fix, headline-sized for large stores. Pairs with the same native accelerator
-version as 10.1.0 — no accelerator bump needed.
-
-- **The adoption backfill runs to completion.** Adopting the crash-safe storage
- authority first re-commits every row the log never saw (a one-time baseline
- backfill). That backfill had a fixed ceiling of 800 rows per
- `adoptLogAuthority()` call — sized for small drift, not for a large pre-existing
- store — so a store with a 12,700-row baseline advanced 800 rows per call and
- stayed on the prior authority across restarts (a production deployment's
- report). Now one call adopts a baseline of any size: the backfill sees the
- entire curable set at once, cures all of it, and loops only until green — the
- no-progress guard is the sole stop. Pace rides the write path (~100 rows/s
- measured end to end, versus ~1.7 rows/s under the old page-per-scan shape),
- and progress is narrated so an operator watching a live service sees motion.
- Stores that already adopted are unaffected; stores still on the prior authority
- flip in a single call on their next open or on an explicit
- `adoptLogAuthority()`.
-- Verification report unchanged on the wire (still lists at most 200 mismatches;
- counts remain complete) — only the adoption path reads the full set.
-
----
-
-## v10.1.0 — 2026-08-13 (the bounded-recovery and write-path-cure release)
-
-The theme: **crash recovery is bounded, restores are durably founded, and two
-production-reported write-path defects are cured at their roots.** Ships together
-with the matching native accelerator version; adopt as a pair.
-
-- **Bounded crash recovery (the fold-checkpoint bound).** Recovery after an unclean
- shutdown now replays only the log segment above a durably-stamped checkpoint
- instead of the whole log. The checkpoint advances only after a canonical-sync
- barrier makes every touched record durable (deletes included), so the bound can
- lag but can never overstate durability. Existing stores converge automatically at
- their first recovery — zero operator steps; recovery cost stops scaling with
- store age.
-- **Restores are unclean events, by construction.** `restore()` now runs its swap
- fully quiesced (no background flush can race the directory replacement — a
- consumer-reported `ENOTEMPTY` crash class is dead), and a snapshot's durability
- stamps never survive the restore: the reopen folds the restored log, re-syncs
- what it re-applied, and stamps fresh. Restored state is durably founded at
- restore time instead of inheriting assertions about bytes the disk never synced.
-- **Write-path cures from a production report.** (1) Log pad-frame construction is
- total — a size-class boundary hole could previously kill a sync with "pad frame
- not constructible". (2) The at-ack sync-failure compensation now splits by phase:
- the generation counter can never re-mint a number the log may already carry, so
- the non-monotonic append refusal loop reported by a downstream deployment cannot
- recur. Both pinned with the reporter's exact shapes.
-- **Operator-truthful sparse queries.** `where` on a field no store row has ever
- carried now serves the honest answer (`eq`/`in`/range → empty; `ne`/`exists:false`
- → all rows; `exists:true` → empty) with a throttled did-you-mean warning, instead
- of refusing. `orderBy` on unknown fields and ambiguous spellings keep their typed
- refusals.
-- **Cross-package error identity.** `UnresolvableFieldError` thrown across package
- boundaries is re-normalized so `instanceof` checks in consuming applications
- match regardless of duplicated dependency trees.
-- Release tooling: publishes now push the tag before the branch (the publish
- workflow can no longer queue behind a redundant CI run) and verify registry
- byte-identity with a propagation-tolerant raw-registry probe.
-
----
-
## v10.0.0 — 2026-08-10 (the write-path and lifecycle release)
The theme: **writes ack fast and honestly, startup adopts instead of rebuilding, and
diff --git a/SECURITY.md b/SECURITY.md
index 91d40d49..1f3c4732 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -30,7 +30,7 @@ commit to backporting fixes to unsupported lines.
## Scope
-This policy covers the `@soulcraftlabs/brainy` package itself — the code in
+This policy covers the `@soulcraft/brainy` package itself — the code in
this repository. If you're evaluating a deployment that also uses
`@soulcraft/cor`, report issues in that package the same way, to the same
address; we'll route internally.
diff --git a/bin/brainy-ts.js b/bin/brainy-ts.js
index 90a35e98..4e9aedb8 100644
--- a/bin/brainy-ts.js
+++ b/bin/brainy-ts.js
@@ -3,7 +3,7 @@
/**
* Modern TypeScript CLI Runner
*
- * This is the entry point after npm install @soulcraftlabs/brainy
+ * This is the entry point after npm install @soulcraft/brainy
* It runs the compiled TypeScript CLI code
*/
diff --git a/bun.lock b/bun.lock
index 1e3e66e2..c31b3865 100644
--- a/bun.lock
+++ b/bun.lock
@@ -3,7 +3,7 @@
"configVersion": 0,
"workspaces": {
"": {
- "name": "@soulcraftlabs/brainy",
+ "name": "@soulcraft/brainy",
"dependencies": {
"@aws-sdk/client-s3": "^3.540.0",
"@azure/identity": "^4.0.0",
diff --git a/docs/DEVELOPER_LEARNING_PATH.md b/docs/DEVELOPER_LEARNING_PATH.md
index b2d22fb1..4134ae63 100644
--- a/docs/DEVELOPER_LEARNING_PATH.md
+++ b/docs/DEVELOPER_LEARNING_PATH.md
@@ -25,13 +25,13 @@
### Prerequisites
```bash
-npm install @soulcraftlabs/brainy
+npm install @soulcraft/brainy
```
### Your First Neural Database
```typescript
-import { Brainy, NounType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType } from '@soulcraft/brainy'
// Step 1: Create and initialize Brainy
const brain = new Brainy({
@@ -143,7 +143,7 @@ Once you're comfortable with basic operations, move to **Level 2** to learn abou
### Building a Knowledge Graph
```typescript
-import { Brainy, NounType, VerbType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType, VerbType } from '@soulcraft/brainy'
const brain = new Brainy({ storage: { type: 'memory' } })
await brain.init()
@@ -314,7 +314,7 @@ Ready for AI-powered search and clustering? Move to **Level 3**.
### Triple Intelligence in Action
```typescript
-import { Brainy, NounType, VerbType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType, VerbType } from '@soulcraft/brainy'
const brain = new Brainy({ storage: { type: 'memory' } })
await brain.init()
@@ -529,7 +529,7 @@ Want to treat files as intelligent entities? Learn the **Virtual Filesystem** in
### Files as Intelligent Entities
```typescript
-import { Brainy, NounType, VerbType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType, VerbType } from '@soulcraft/brainy'
const brain = new Brainy({ storage: { type: 'memory' } })
await brain.init()
@@ -832,7 +832,7 @@ Ready for production deployment? Level 5 covers **planet-scale architecture**.
### Production-Ready Deployment
```typescript
-import { Brainy, NounType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType } from '@soulcraft/brainy'
// 1. PRODUCTION STORAGE - Filesystem with off-site snapshots
console.log('Initializing production storage...\n')
diff --git a/docs/FIND_SYSTEM.md b/docs/FIND_SYSTEM.md
index 6aa33515..1cc38ce9 100644
--- a/docs/FIND_SYSTEM.md
+++ b/docs/FIND_SYSTEM.md
@@ -369,71 +369,6 @@ return results.slice(offset, offset + limit)
// → Auto-correction: Use most likely alternative based on affinity data
```
-## Field Projection (`fields`)
-
-`find()` and `get()` accept a `fields` list. Without it they return the whole
-record; with it they return only the fields you name — and, where the index can
-supply them, without opening the canonical record at all.
-
-```ts
-// A list page: two user fields and one engine scalar. No document bodies.
-await brain.find({
- where: { kind: 'post' },
- fields: ['title', 'slug', 'system.createdAt'],
- limit: 50
-})
-
-await brain.get(id, { fields: ['title'] })
-```
-
-### Why it exists
-
-A list view that renders a title and a date does not need the body, but without
-a projection every row hydrates its full record and throws almost all of it
-away. On a posts list that is the dominant cost of the query.
-
-### The rules
-
-| | |
-|---|---|
-| **`fields` absent** | The full record, byte-identical to before. Nothing changes. |
-| **Field names** | The one addressing law: a bare name is user metadata (`'title'`), `system.*` is an engine scalar (`'system.createdAt'`). |
-| **A field the row lacks** | Simply **absent** from the result. Never an error. |
-| **Identity** | Every row keeps its `id` (and `score` on `find`) regardless — a row you cannot identify is not a row. |
-| **Where values come from** | The **column store**, which holds raw values. Never the sparse index, which buckets timestamps for range queries. |
-| **A field the column cannot serve** | The canonical record is read for that field only. Correct, just not free. |
-
-### Missing fields are absent, not errors
-
-This is deliberate and differs from `orderBy`, which throws
-`UnresolvableFieldError` for an unknown field. A typo in `orderBy` silently
-changes the ordering, so it must be loud. A projection asks "give me these if
-you have them", and an optional field must not turn a list into a failure — so
-`fields` uses the permissive path.
-
-### Cost
-
-When every named field is column-served, a projected page performs **zero**
-canonical reads. When one is not, only that read happens and the rest still come
-from the index. Both are pinned by counting reads rather than timing them, in
-`tests/integration/find-fields-projection.test.ts`.
-
-### `related()` takes no `fields`
-
-A `Relation` carries `from` and `to` as **ids** and hydrates no entity record,
-so there is nothing for a projection to trim. Projecting the endpoints would be
-a new capability rather than a projection of an existing one.
-
-### For engine implementers
-
-Projection is served through an optional provider door,
-`getScalarsForIds(ids, fields)` on `MetadataIndexProvider`. The contract is in
-`src/plugin.ts`; the short version is **return only what you can serve exactly,
-and say what you served**. The caller diffs the answer against the request and
-reads records for the remainder, so omission costs a read while a wrong value is
-a wrong answer nobody can see. An engine without the door still works — every
-field falls back to the record.
-
## Performance Characteristics
### Query Performance by Type
@@ -1282,7 +1217,7 @@ where: {
await brain.find({ type: 'Document' })
// ✅ Correct: Use NounType enum
-import { NounType } from '@soulcraftlabs/brainy'
+import { NounType } from '@soulcraft/brainy'
await brain.find({ type: NounType.Document })
// ❌ Error: Operator not recognized
diff --git a/docs/MIGRATION-V3-TO-V4.md b/docs/MIGRATION-V3-TO-V4.md
index 680b6928..29c409ac 100644
--- a/docs/MIGRATION-V3-TO-V4.md
+++ b/docs/MIGRATION-V3-TO-V4.md
@@ -153,13 +153,13 @@ brainy-data/
### Step 1: Update Brainy Package
```bash
-npm install @soulcraftlabs/brainy@latest
+npm install @soulcraft/brainy@latest
```
**Check your version:**
```bash
-npm list @soulcraftlabs/brainy
-# Should show: @soulcraftlabs/brainy@4.0.0
+npm list @soulcraft/brainy
+# Should show: @soulcraft/brainy@4.0.0
```
### Step 2: No Code Changes Required! ✅
@@ -374,7 +374,7 @@ If you encounter issues, you can rollback:
```bash
# Reinstall v3
-npm install @soulcraftlabs/brainy@^3.50.0
+npm install @soulcraft/brainy@^3.50.0
# Restart application
```
@@ -389,7 +389,7 @@ rm -rf ./data
cp -r ./data-backup ./data
# Reinstall v3
-npm install @soulcraftlabs/brainy@^3.50.0
+npm install @soulcraft/brainy@^3.50.0
```
## Common Migration Scenarios
@@ -539,7 +539,7 @@ console.log('Storage type:', status.type)
**Migration Checklist:**
- ✅ Backup data
-- ✅ Update npm package (`npm install @soulcraftlabs/brainy@latest`)
+- ✅ Update npm package (`npm install @soulcraft/brainy@latest`)
- ✅ Restart application (automatic migration)
- ✅ Verify data integrity
- ✅ Enable lifecycle policies
diff --git a/docs/PERFORMANCE.md b/docs/PERFORMANCE.md
index b543e84a..248a2c70 100644
--- a/docs/PERFORMANCE.md
+++ b/docs/PERFORMANCE.md
@@ -323,24 +323,58 @@ Only the graph adjacency index carries a committed scale assertion:
- ✅ **Single-Node by Design**: One process owns one `path`; scale out at the service layer
- ✅ **Zero Stubs**: Every line of code is production-ready
-## Index Build at Open (10.4+)
+## Lazy Loading Performance
-As of 10.4, `brain.init()` runs every needed index rebuild to completion before
-it returns — always, regardless of dataset size. There is no lazy,
-first-query rebuild path: a brain either finishes opening healthy, or `init()`
-fails loudly. `disableAutoRebuild` no longer defers index construction to a
-first query; it has no effect on *when* a rebuild runs. Manual control over
-rebuilds is `repairIndex({ rebuild: [...] })`. See
-[Index Health](concepts/index-health.md) for the full read-gate contract
-(providers self-report readiness via `healthReport()`; a read against a
-not-serving provider throws a typed `*NotReadyError` rather than rebuilding
-mid-query).
+Brainy supports two initialization modes for optimal performance across different use cases:
-
+### Mode 1: Auto-Rebuild (Default)
+
+```javascript
+const brain = new Brainy()
+await brain.init() // Rebuilds indexes during init (~500ms-3s for 10K entities)
+```
+
+**Performance:**
+- Init time: 500ms-3s (depends on dataset size)
+- First query: Instant (indexes already loaded)
+- Use case: Traditional applications, long-running servers
+
+### Mode 2: Lazy Loading
+
+```javascript
+const brain = new Brainy({ disableAutoRebuild: true })
+await brain.init() // Returns instantly (0-10ms)
+
+const results = await brain.find({ limit: 10 }) // First query triggers rebuild (~50-200ms)
+const more = await brain.find({ limit: 100 }) // Subsequent queries instant (0ms check)
+```
+
+**Performance:**
+- Init time: 0-10ms (instant)
+- First query: 50-200ms (includes index rebuild for 1K-10K entities)
+- Subsequent queries: 0ms check (instant)
+- Concurrent queries: Wait for same rebuild (mutex prevents duplicates)
+
+**Concurrency Safety:**
+```javascript
+// 100 concurrent queries immediately after init
+await brain.init()
+
+const promises = Array.from({ length: 100 }, () =>
+ brain.find({ limit: 10 })
+)
+
+const results = await Promise.all(promises)
+// ✅ Only 1 rebuild triggered (mutex)
+// ✅ All 100 queries return correct results
+// ✅ Total time: ~60ms (not 6000ms!)
+```
+
+**Use Cases for Lazy Loading:**
+- **Serverless/Edge**: Minimize cold start time (0-10ms init)
+- **Development**: Faster restarts during development
+- **Large datasets**: Defer index loading until needed
+- **Read-heavy workloads**: Writes don't wait for index rebuild
## Zero Configuration Required
@@ -350,6 +384,10 @@ Brainy is designed to be **smart enough to tune itself dynamically**. No configu
// That's it. Brainy handles everything.
const brain = new Brainy()
await brain.init()
+
+// Or with lazy loading for serverless
+const brain = new Brainy({ disableAutoRebuild: true })
+await brain.init() // Instant (0-10ms)
```
### Automatic Self-Tuning
@@ -357,6 +395,7 @@ await brain.init()
- **Metadata Index**: Auto-builds sorted indices for range queries on first use
- **Graph Index**: Auto-flushes every 30 seconds
- **Default Tuning**: Research-based vector index defaults
+- **Lazy Loading**: Indices built only when needed
- **Cache Management**: LRU caches with TTL
### Intelligent Defaults
diff --git a/docs/PLUGINS.md b/docs/PLUGINS.md
index 238d2252..d9a4d3e7 100644
--- a/docs/PLUGINS.md
+++ b/docs/PLUGINS.md
@@ -10,7 +10,7 @@ next:
- guides/storage-adapters
---
-# Plugin System
+# Plugin Development Guide
Brainy has a plugin system that allows third-party packages to replace internal subsystems with custom implementations. This is how `@soulcraft/cor` provides optional native acceleration, and it's the same system available to any developer.
@@ -46,7 +46,7 @@ If no plugin provides a given key, brainy uses its built-in JavaScript implement
### 1. Implement the `BrainyPlugin` interface
```typescript
-import type { BrainyPlugin, BrainyPluginContext } from '@soulcraftlabs/brainy/plugin'
+import type { BrainyPlugin, BrainyPluginContext } from '@soulcraft/brainy/plugin'
const myPlugin: BrainyPlugin = {
name: 'my-brainy-plugin', // Must be unique (typically your npm package name)
@@ -90,7 +90,7 @@ await brain.init()
**Programmatic registration:** For plugins not installed as npm packages, use `brain.use()`:
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
import myPlugin from './my-plugin.js'
const brain = new Brainy()
@@ -200,30 +200,15 @@ members so a warm reopen never pays a redundant rebuild-from-canonical:
- **`init?(): Promise`** — eager cold-load. Brainy awaits it once during
`brain.init()`, after the metadata provider's `init()` (the id-mapper hydrates first)
and **before the rebuild gate**.
-- **`healthReport?(): HealthReport`** — the PREFERRED signal (10.4+). A named,
- synchronous, O(1) verdict derived from the provider's own exact ledgers — never a
- sample, never I/O, must never throw for a well-formed provider. Brainy's read gate
- (`assessProviderHealth()`) reads this INSTEAD of `isReady()` / size heuristics when
- present: `serving: false` refuses the read with a typed `*NotReadyError` rather than
- triggering a rebuild — a read never starts a store walk. `healthy` marks every
- *verified* invariant holding; a family named in `unledgered` counts as neither
- healthy nor broken. See `HealthReport` / `LedgerInvariantResult` /
- `InvariantSource` in `src/plugin.ts`, and
- [Index Health](concepts/index-health.md) for the consumer-facing story.
-- **`isReady?(): boolean`** — honest durability signal, the fallback when
- `healthReport()` is absent. `true` ⇔ the persisted index is loaded (or cheaply
- demand-loadable) and consistent with what was last persisted. When exposed, the
- gate defers to this signal **instead of** the `size() === 0` / `totalEntries === 0`
- heuristics — a disk-native index may report 0 resident entries while fully durable.
- Never return `true` if the durable state failed to load: the signal is honest in
- both directions, and a not-ready provider gets its rebuild even when `size() > 0`.
+- **`isReady?(): boolean`** — honest durability signal. `true` ⇔ the persisted index is
+ loaded (or cheaply demand-loadable) and consistent with what was last persisted. When
+ exposed, the rebuild gate defers to this signal **instead of** the `size() === 0` /
+ `totalEntries === 0` heuristics — a disk-native index may report 0 resident entries
+ while fully durable. Never return `true` if the durable state failed to load: the
+ signal is honest in both directions, and a not-ready provider gets its rebuild even
+ when `size() > 0`.
- **`isMigrating?(): boolean`** — while `true`, the provider owns its index (background
migration); brainy skips its rebuild entirely.
-- **`validateInvariants?(): Promise`** — the async DEEP
- diagnostic (full scans allowed), distinct from the bounded, sync `healthReport()`.
- Must never throw — a failure is `healthy: false` data, not an exception; a provider
- that throws anyway is read as a loud, unverified failure (never as "healthy") by
- every caller, never silently retried into a rebuild.
Providers that implement none of these keep the size/count heuristics — correct for
engines whose `rebuild()` *is* their load path (like brainy's built-in JS vector index).
@@ -272,10 +257,10 @@ When provided by an optional native acceleration plugin (such as `@soulcraft/cor
#### `cache`
**Type:** `UnifiedCache`
-Replaces the global `UnifiedCache` singleton used for VFS path resolution, semantic caching, and vector index caching. Must implement the `UnifiedCache` interface (available from `@soulcraftlabs/brainy/internals`).
+Replaces the global `UnifiedCache` singleton used for VFS path resolution, semantic caching, and vector index caching. Must implement the `UnifiedCache` interface (available from `@soulcraft/brainy/internals`).
```typescript
-import type { UnifiedCache } from '@soulcraftlabs/brainy/internals'
+import type { UnifiedCache } from '@soulcraft/brainy/internals'
context.registerProvider('cache', myNativeCache)
```
@@ -325,8 +310,8 @@ Plugins can register custom storage backends that users reference by name.
### Implementing a Storage Adapter
```typescript
-import type { StorageAdapterFactory } from '@soulcraftlabs/brainy/plugin'
-import type { StorageAdapter } from '@soulcraftlabs/brainy'
+import type { StorageAdapterFactory } from '@soulcraft/brainy/plugin'
+import type { StorageAdapter } from '@soulcraft/brainy'
class MyStorageAdapter implements StorageAdapter {
async init(): Promise { /* ... */ }
@@ -360,9 +345,9 @@ Brainy provides three entry points for plugin developers:
| Import Path | Contents | Stability |
|-------------|----------|-----------|
-| `@soulcraftlabs/brainy` | Public API, types, StorageAdapter | Stable (semver) |
-| `@soulcraftlabs/brainy/plugin` | BrainyPlugin, BrainyPluginContext, StorageAdapterFactory | Stable (semver) |
-| `@soulcraftlabs/brainy/internals` | UnifiedCache, EntityIdMapper, logger utilities | Internal (may change between minor versions) |
+| `@soulcraft/brainy` | Public API, types, StorageAdapter | Stable (semver) |
+| `@soulcraft/brainy/plugin` | BrainyPlugin, BrainyPluginContext, StorageAdapterFactory | Stable (semver) |
+| `@soulcraft/brainy/internals` | UnifiedCache, EntityIdMapper, logger utilities | Internal (may change between minor versions) |
## Diagnostics
@@ -440,7 +425,7 @@ A minimal but useful plugin that provides SIMD-accelerated distance calculations
```typescript
// simd-distance-plugin/src/plugin.ts
-import type { BrainyPlugin, BrainyPluginContext } from '@soulcraftlabs/brainy/plugin'
+import type { BrainyPlugin, BrainyPluginContext } from '@soulcraft/brainy/plugin'
// Hypothetical native module
import { simdCosineDistance } from './native.js'
@@ -470,7 +455,7 @@ export default simdDistancePlugin
"main": "./dist/plugin.js",
"types": "./dist/plugin.d.ts",
"peerDependencies": {
- "@soulcraftlabs/brainy": ">=7.0.0"
+ "@soulcraft/brainy": ">=7.0.0"
}
}
```
@@ -478,7 +463,7 @@ export default simdDistancePlugin
Usage:
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const brain = new Brainy({ plugins: ['brainy-simd-distance'] })
await brain.init()
diff --git a/docs/PRODUCTION_SERVICE_ARCHITECTURE.md b/docs/PRODUCTION_SERVICE_ARCHITECTURE.md
index ad4a4a40..4568cd31 100644
--- a/docs/PRODUCTION_SERVICE_ARCHITECTURE.md
+++ b/docs/PRODUCTION_SERVICE_ARCHITECTURE.md
@@ -54,7 +54,7 @@ After 40 API calls:
```typescript
// server.ts
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
// SINGLETON INSTANCE
let brainInstance: Brainy | null = null
@@ -174,7 +174,7 @@ process.on('SIGTERM', async () => {
```typescript
// server.ts - Clean Bun implementation
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
let brain: Brainy | null = null
diff --git a/docs/README.md b/docs/README.md
index ddb37d20..3290001f 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -5,7 +5,7 @@
## Quick Start
```typescript
-import { Brainy, NounType, VerbType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType, VerbType } from '@soulcraft/brainy'
const brain = new Brainy()
await brain.init()
diff --git a/docs/RELEASE-GUIDE.md b/docs/RELEASE-GUIDE.md
index 4b120bd8..94c6a6cb 100644
--- a/docs/RELEASE-GUIDE.md
+++ b/docs/RELEASE-GUIDE.md
@@ -99,7 +99,7 @@ Examples:
```bash
# 1. Deprecate wrong version on npm
-npm deprecate @soulcraftlabs/brainy@X.X.X "Incorrect version - use Y.Y.Y"
+npm deprecate @soulcraft/brainy@X.X.X "Incorrect version - use Y.Y.Y"
# 2. Fix version in package.json
# 3. Republish correct version
diff --git a/docs/SCALING.md b/docs/SCALING.md
index 054d2096..e9ae1136 100644
--- a/docs/SCALING.md
+++ b/docs/SCALING.md
@@ -13,7 +13,7 @@
### In-Memory
```typescript
-import Brainy from '@soulcraftlabs/brainy'
+import Brainy from '@soulcraft/brainy'
const brain = new Brainy({ storage: { type: 'memory' } })
```
@@ -43,7 +43,7 @@ The native vector provider (via the optional `@soulcraft/cor` package) extends t
Numbers below are **measured** by `tests/benchmarks/find-composition-scale.js` (a single
Node 22 process, in-memory storage, 384-dim vectors, `balanced` recall). They are the
-open-core (pure-TypeScript) path — what you get from `@soulcraftlabs/brainy` with no native
+open-core (pure-TypeScript) path — what you get from `@soulcraft/brainy` with no native
provider installed. Run it yourself: `node --max-old-space-size=8192 tests/benchmarks/find-composition-scale.js 100000`.
`find()` query latency, p50 / p95 (200 queries each):
diff --git a/docs/api-contract.json b/docs/api-contract.json
deleted file mode 100644
index c4f4e056..00000000
--- a/docs/api-contract.json
+++ /dev/null
@@ -1,1633 +0,0 @@
-{
- "contractVersion": 1,
- "engine": "@soulcraftlabs/brainy",
- "compatibility": {
- "minor": "additive — a new optional door, a new served operator, a new error class; every existing implementation still conforms",
- "major": "breaking — a door removed, an answer narrowed, an ordering law changed, an optional door promoted to required, or an operator moved from served to refused"
- },
- "doors": [
- {
- "name": "adaptiveHistoryBudgetBytes",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "add",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "addMany",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "adoptLogAuthority",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "adoptLogAuthorityInner",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "aggViewFromEntity",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "anyProviderMigrating",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "applyFusionScoring",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "applyGraphConstraints",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "armIdleFlushTimer",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "asOf",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "assertGenerationStoreReady",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "assertWritable",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "audit",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "auditGraph",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "autoAdoptLegacyVfsBlobsIfNeeded",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "autoAlpha",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "autoCompactHistory",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "awaitMigrationLock",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "awaitPendingEmbeds",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "backfillAggregateIfNeeded",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "batchGet",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "brainWideStrictRequiresSubtype",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "bridgeLegacyPendingEmbedSidecars",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "buildAtGenerationVectors",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "buildGraphView",
- "kind": "method",
- "arity": 4
- },
- {
- "name": "buildMetadataFilter",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "buildMigrationUpdate",
- "kind": "method",
- "arity": 5
- },
- {
- "name": "buildRelationMigrationUpdate",
- "kind": "method",
- "arity": 5
- },
- {
- "name": "cacheVerbInt",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "canServeVectorAtGeneration",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "captureEmbedCheckpoint",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "checkHealth",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "checkMigrations",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "clear",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "clearPendingEmbed",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "close",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "closeDurableSteps",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "cluster",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "collectProviderInvariants",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "compactHistory",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "consumeMetadataWatermarkVerdict",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "convertMetadataToEntity",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "convertNounToEntity",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "counts",
- "kind": "accessor"
- },
- {
- "name": "createGenerationStore",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "createIndex",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "createMigrationBackupIfNeeded",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "createPinnedDb",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "createResult",
- "kind": "method",
- "arity": 4
- },
- {
- "name": "dbFinalizationRegistry",
- "kind": "accessor"
- },
- {
- "name": "dbHost",
- "kind": "accessor"
- },
- {
- "name": "defineAggregate",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "demoteTornEntityTreeStamp",
- "kind": "method",
- "arity": 4
- },
- {
- "name": "detectIdKind",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "diagnostics",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "diff",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "embed",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "embedBatch",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "emitCommitted",
- "kind": "method",
- "arity": 4
- },
- {
- "name": "enforceSubtypeOnAdd",
- "kind": "method",
- "arity": 4
- },
- {
- "name": "enforceSubtypeOnRelate",
- "kind": "method",
- "arity": 4
- },
- {
- "name": "enforceTrackedFieldValues",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "enhanceNLPResult",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "enqueuePendingEmbed",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "ensureAggregationIndex",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "ensureIndexesLoaded",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "ensureInitialized",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "entityForAggFromRawRecord",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "entityFromGenerationRecord",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "entityIntsToUuids",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "entityViewFromRawRecord",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "excludedVisibilityTiers",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "executeProximitySearch",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "executeTextSearch",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "executeTextSearchScored",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "executeVectorSearch",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "executeVectorSearchScored",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "explain",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "export",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "extract",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "extractConcepts",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "extractEntities",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "factSegmentPaths",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "fieldCountsAggregateName",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "fillSubtypes",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "filterIdsBelted",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "filterIdsWithinBelted",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "find",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "findAggregate",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "findDuplicates",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "findMatchingWords",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "flush",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "formatInfo",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "formatSubtypeError",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "generation",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "generationDigest",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "get",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "getActivePlugins",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "getAvailableFields",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "getBackgroundDeduplicator",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "getFieldsForType",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "getFieldStatistics",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "getFieldsWithCardinality",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "getFieldValues",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "getIndexStats",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "getIndexStatus",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "getMemoryStats",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "getNeighborUuids",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "getNounCount",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "getOptimalQueryPlan",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "getStats",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "getStorageType",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "getSubtypeRule",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "getTripleIntelligence",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "getTypedNeighbors",
- "kind": "method",
- "arity": 4
- },
- {
- "name": "getVerbCount",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "graph",
- "kind": "accessor"
- },
- {
- "name": "graphAccelerationProvider",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "graphCommunities",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "graphCommunitiesFallback",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "graphCommunitiesNative",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "graphEntityInt",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "graphExport",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "graphExportFallback",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "graphExportNative",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "graphPath",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "graphPathFallback",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "graphPathNative",
- "kind": "method",
- "arity": 4
- },
- {
- "name": "graphRank",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "graphRankFallback",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "graphRankNative",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "graphSubgraph",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "graphSubgraphFallback",
- "kind": "method",
- "arity": 4
- },
- {
- "name": "graphSubgraphFromQuery",
- "kind": "method",
- "arity": 5
- },
- {
- "name": "graphSubgraphNative",
- "kind": "method",
- "arity": 5
- },
- {
- "name": "groupByLabel",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "hasStorageMethod",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "hasVectorOrTextCriteria",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "health",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "highlight",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "highlightSemanticPhase",
- "kind": "method",
- "arity": 5
- },
- {
- "name": "history",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "historyStats",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "hub",
- "kind": "accessor"
- },
- {
- "name": "hydrateIdMapperForGraphRebuild",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "hydrateNativeSubgraph",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "hydrateResultPage",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "import",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "importPluginPackage",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "incidentEdges",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "indexStats",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "init",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "insights",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "isClosed",
- "kind": "accessor"
- },
- {
- "name": "isClosing",
- "kind": "accessor"
- },
- {
- "name": "isEmbeddingReady",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "isInfrastructureWrite",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "isInitialized",
- "kind": "accessor"
- },
- {
- "name": "isReadOnly",
- "kind": "accessor"
- },
- {
- "name": "kickBackgroundFlush",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "kickEmbedWorker",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "legacyLayoutMigrationPhase",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "loadAnalyticsGraph",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "loadPlugins",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "logAuthority",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "maintenanceDebt",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "materializeAtGeneration",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "maybeWriteEmbedCheckpoint",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "maybeWriteEmbedLowWater",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "metadataIndexRetractionOp",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "migrate",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "migrateField",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "migrateInternal",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "migrateLegacyZeroNormVfsRootIfNeeded",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "migrationSnapshot",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "neededFamiliesMigrating",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "neighbors",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "newId",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "nlp",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "normalizeConfig",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "noteEmbedCheckpointCadence",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "noteWriteForPersistence",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "now",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "onChange",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "pageConnectedIds",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "pagination",
- "kind": "accessor"
- },
- {
- "name": "parseMigrationPath",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "parseNaturalQuery",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "pathExists",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "pendingEmbedCount",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "pendingResult",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "performInit",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "persistPinnedGeneration",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "persistSingleOp",
- "kind": "method",
- "arity": 6
- },
- {
- "name": "pickMetadataProbe",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "pickVectorProbe",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "pinGeneration",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "planGetEntity",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "planTransact",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "planTxAdd",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "planTxRelate",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "planTxRemove",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "planTxUnrelate",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "planTxUpdate",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "projectionGauges",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "providerForFamily",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "providerIsMigrating",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "providerMigrationStatus",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "queryAggregate",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "queryIndexFamilies",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "readPath",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "readPendingEmbedBound",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "ready",
- "kind": "accessor"
- },
- {
- "name": "rebuildIndexesIfNeeded",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "rebuildMetadataIndexOnline",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "reconcileLogDivergence",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "reconstructPath",
- "kind": "method",
- "arity": 4
- },
- {
- "name": "recordStateAt",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "recoverPendingEmbedsFromLog",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "registerShutdownHooks",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "relate",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "related",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "relateMany",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "relationFromGenerationRecord",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "relationshipSubtypesOf",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "releaseGeneration",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "remove",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "removeAggregate",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "removeMany",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "removeMigrationBackupSafe",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "repackHistory",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "repairIndex",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "requestFlush",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "requireProviders",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "requireSubtype",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "resolveAsOfGeneration",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "resolveConnectedIds",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "resolveDiffEndpoint",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "resolveHiddenIds",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "resolveHNSWPersistMode",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "resolveRawGeneration",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "resolveRetentionPolicy",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "resolveVerbEndpointInts",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "resolveVerbIntsToIds",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "restore",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "rrfFusion",
- "kind": "method",
- "arity": 3
- },
- {
- "name": "runAggregationBackfillWalk",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "runAggregationCatchUp",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "runEmbedWorker",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "runOracle",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "runRepairIndexPhases",
- "kind": "method",
- "arity": 5
- },
- {
- "name": "scanFacts",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "seedIdsToInts",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "selectorToSeedIds",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "setRetentionBudget",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "setupEmbedder",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "setupIndex",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "setupStorage",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "similar",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "similarity",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "splitForHighlighting",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "stampBrainFormat",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "stampBrainFormatIfNeeded",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "stampEntityTree",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "stampProjectionWatermarks",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "stats",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "storageAdapter",
- "kind": "accessor"
- },
- {
- "name": "stream",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "streaming",
- "kind": "accessor"
- },
- {
- "name": "subtypesOf",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "textIdsWithinBelted",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "trackField",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "transact",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "transactionLog",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "unrelate",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "unvectorNounForRootMigration",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "update",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "updateMany",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "updateRelation",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "upsertMergeParams",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "use",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "usesDefaultWasmEmbedder",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "validateIndexConsistency",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "vectorSearchAtGeneration",
- "kind": "method",
- "arity": 4
- },
- {
- "name": "verbsToRelations",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "verbToRelationLike",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "verifyEntityTreeStamp",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "verifyGraphAdjacencyLive",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "verifyLogAuthority",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "verifyMetadataLive",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "verifyVectorLive",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "versionedIndexProviders",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "vfs",
- "kind": "accessor"
- },
- {
- "name": "waitForIndexed",
- "kind": "method",
- "arity": 2
- },
- {
- "name": "warm",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "warmupEmbeddings",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "warnIfReadsDegraded",
- "kind": "method",
- "arity": 1
- },
- {
- "name": "wireConnectionsCodec",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "wireGraphIdResolver",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "writeEmbedCheckpoint",
- "kind": "method",
- "arity": 0
- },
- {
- "name": "writeEmbedLowWater",
- "kind": "method",
- "arity": 0
- }
- ],
- "errors": [
- "BrainyError",
- "DerivedArtifactMissingError",
- "GraphIndexNotReadyError",
- "MetadataArrayTooLargeError",
- "MetadataIndexNotReadyError",
- "MigrationInProgressError",
- "ProtectedArtifactError",
- "VectorIndexNotReadyError"
- ],
- "operators": {
- "accepted": [
- "between",
- "contains",
- "endsWith",
- "eq",
- "equals",
- "excludes",
- "exists",
- "greaterThan",
- "greaterThanOrEqual",
- "gt",
- "gte",
- "hasAll",
- "in",
- "length",
- "lessThan",
- "lessThanOrEqual",
- "lt",
- "lte",
- "matches",
- "missing",
- "ne",
- "noneOf",
- "notEquals",
- "oneOf",
- "startsWith"
- ],
- "servedOnIndexPath": [
- "between",
- "contains",
- "eq",
- "equals",
- "excludes",
- "exists",
- "greaterThan",
- "greaterThanOrEqual",
- "gt",
- "gte",
- "hasAll",
- "in",
- "lessThan",
- "lessThanOrEqual",
- "lt",
- "lte",
- "missing",
- "ne",
- "noneOf",
- "notEquals",
- "oneOf"
- ],
- "refusedByIndexPath": [
- "endsWith",
- "length",
- "matches",
- "startsWith"
- ],
- "combinators": [
- "allOf",
- "anyOf",
- "not"
- ]
- },
- "fieldAddressing": {
- "systemKeyPrefix": "system.",
- "systemEntityScalars": [
- "confidence",
- "createdAt",
- "createdBy",
- "id",
- "service",
- "subtype",
- "type",
- "updatedAt",
- "visibility",
- "weight"
- ],
- "systemRelationScalars": [
- "confidence",
- "createdAt",
- "createdBy",
- "service",
- "sourceId",
- "subtype",
- "targetId",
- "updatedAt",
- "verb",
- "visibility",
- "weight"
- ],
- "plumbingFields": [
- "_rev",
- "connections",
- "data",
- "level",
- "vector"
- ]
- },
- "health": {
- "verdicts": [
- "pass",
- "warn",
- "fail"
- ],
- "healKinds": [
- "none",
- "repair",
- "rebuild"
- ],
- "servingWithholdingInvariants": [
- "index-initialized",
- "durable-state-present",
- "manifest-residency",
- "replay-clean",
- "strand-latch"
- ]
- }
-}
diff --git a/docs/api/README.md b/docs/api/README.md
index ba49ff48..4ca84364 100644
--- a/docs/api/README.md
+++ b/docs/api/README.md
@@ -24,7 +24,7 @@ next:
## Quick Start
```typescript
-import { Brainy, NounType, VerbType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType, VerbType } from '@soulcraft/brainy'
const brain = new Brainy() // Zero config!
await brain.init() // VFS auto-initialized!
@@ -1010,7 +1010,7 @@ await db.release() // unpin + free cached materialization
### Db API errors
-All exported from `@soulcraftlabs/brainy`:
+All exported from `@soulcraft/brainy`:
| Error | Thrown by | Meaning |
|---|---|---|
@@ -1451,34 +1451,6 @@ const count = await brain.getVerbCount()
---
-### The canonical count ledger (`StorageAdapter.getCanonicalCounts()`)
-
-An OPTIONAL method on the `StorageAdapter` interface (implemented by both
-built-in adapters), not a method on `Brainy` itself — relevant if you're
-writing a custom storage adapter or composing a provider's own
-`healthReport()`. O(1), no I/O. Per family (`nouns`/`verbs`):
-
-```typescript
-interface CanonicalCounts {
- nouns: { counted: number; all: number }
- verbs: { counted: number; all: number }
- suspect: boolean
-}
-```
-
-- `counted` mirrors `getNounCount()` / `getVerbCount()` (public + internal tiers).
-- `all` is the ALL-visibility scalar — every tier, including system/internal
- records — the denominator a derived index's own coverage math is measured
- against.
-- `suspect` is `true` when an unprovable delete has left `all` unverified since
- the last recount; `brain.repairIndex()` clears it with a real canonical walk.
-
-Adapters without the ledger omit the method; treat absence as "no
-denominator," never as zero. See
-**[Index Health](../concepts/index-health.md)** for the full story.
-
----
-
### Subtype & facet APIs
Full guide: **[Subtypes & Facets](../guides/subtypes-and-facets.md)**.
@@ -1859,104 +1831,6 @@ const semanticOnly = await brain.getStats({ excludeVFS: true })
---
-### `repairIndex(options?)` → `Promise`
-
-The ceremony door for index repair. Bare `repairIndex()` is report-driven: it
-prunes orphaned containers, recomputes count rollups, reconciles VFS
-containment, and rebuilds only a derived-index family whose own health check
-asks for it. Pass `options.rebuild` to force one or more families to rebuild
-UNCONDITIONALLY — no health check is consulted — when an operator has
-independent reason to reconcile a family regardless of what it self-reports.
-
-```typescript
-// Report-driven: only heals what actually needs it
-const report = await brain.repairIndex()
-console.log(report.healedTotal, report.families)
-
-// Explicit: force the graph adjacency to rebuild from canonical, unconditionally
-await brain.repairIndex({ rebuild: ['graph'] })
-
-// Explicit: force all three derived indexes to rebuild
-await brain.repairIndex({ rebuild: 'all' })
-```
-
-**`RepairReport`:**
-- `families: RepairFamilyReport[]` — one row per family checked
-- `healedTotal: number` — items healed across every family
-- `durationMs: number`
-
-**`RepairFamilyReport`** (one row):
-- `family: string` — e.g. `'orphaned-containers'`, `'count-rollups'`,
- `'vfs-containment'`, `'metadata-corruption'`, `'provider:metadata'`,
- `'provider:graph'`, `'provider:vector'`
-- `checked: boolean` — was this family actually examined (`false` ⇒ see `skipped`)
-- `healed: number` — items re-posted/corrected in place (the incremental heal count)
-- `missing?: { count: number; sample: string[] }` — exact count plus a capped id
- sample when the check can name what diverged (never the full list)
-- `rebuilt?: boolean` — a full generational rebuild ran (vs. an incremental heal)
-- `detail?: string` / `reason?: string` — narration
-- `skipped?: string` — why the family wasn't checked
-
-Full walkthrough — what each family checks, degraded-but-serving vs. not-ready,
-and what `suspect` counts mean — in
-**[Index Health](../concepts/index-health.md)**.
-
----
-
-### Index readiness: typed errors, `healthReport()`, `disableAutoRebuild`
-
-Every derived-index provider (vector, graph, metadata) may expose a named,
-synchronous, O(1) `healthReport()` composed from its own exact ledgers — the
-signal Brainy's read gate trusts over sampling or size heuristics. `init()`
-brings every provider to serving before it returns; there is no first-query
-lazy-rebuild path. A read that reaches a provider whose health report says it
-isn't serving throws instead of rebuilding mid-query:
-
-| Error | Thrown by | Meaning |
-|---|---|---|
-| `GraphIndexNotReadyError` | `find({ connected })`, `neighbors()`, `related()` | Graph adjacency isn't serving |
-| `MetadataIndexNotReadyError` | `find({ where })` | Metadata/field index isn't serving |
-| `VectorIndexNotReadyError` | `find({ query })`, `similar()` | Vector index isn't serving |
-
-All three are exported from `@soulcraftlabs/brainy`. Catch them to distinguish
-"index not ready" from a genuine empty result:
-
-```typescript
-import { MetadataIndexNotReadyError } from '@soulcraftlabs/brainy'
-
-try {
- const rows = await brain.find({ where: { status: 'active' } })
-} catch (err) {
- if (err instanceof MetadataIndexNotReadyError) {
- // reconcile: await brain.repairIndex(), then retry
- } else {
- throw err
- }
-}
-```
-
-**`disableAutoRebuild`** no longer defers index construction to the first
-query. A needed rebuild always runs at `open()`, regardless of this flag or
-dataset size; the flag has no effect on *when* a rebuild runs. Full manual
-control lives in `repairIndex({ rebuild: [...] })`, above.
-
-### `validateIndexConsistency()` → `Promise<...>`
-
-The deep, async diagnostic counterpart to `healthReport()` — safe to run on a
-live brain, but does more work (a provider's `validateInvariants()` may run a
-full scan, not just read a ledger). Aggregates the JS metadata index's own
-consistency check with every derived-index provider's invariant report.
-
-```typescript
-const validation = await brain.validateIndexConsistency()
-if (!validation.healthy) {
- console.log(validation.recommendation) // what to run, e.g. repairIndex()
- console.log(validation.providers) // each provider's own invariant report, when exposed
-}
-```
-
----
-
## Lifecycle
### Initialization
@@ -2208,7 +2082,7 @@ For the full taxonomy with all 169 types and their descriptions, see:
- **📖 Documentation:** [Full Documentation](../)
- **🐛 Issues:** [GitHub Issues](https://github.com/soulcraftlabs/brainy/issues)
- **💬 Discussions:** [GitHub Discussions](https://github.com/soulcraftlabs/brainy/discussions)
-- **📦 NPM:** [@soulcraftlabs/brainy](https://www.npmjs.com/package/@soulcraftlabs/brainy)
+- **📦 NPM:** [@soulcraft/brainy](https://www.npmjs.com/package/@soulcraft/brainy)
- **⭐ GitHub:** [Star us](https://github.com/soulcraftlabs/brainy)
---
diff --git a/docs/architecture/data-storage-architecture.md b/docs/architecture/data-storage-architecture.md
index 12398747..48064757 100644
--- a/docs/architecture/data-storage-architecture.md
+++ b/docs/architecture/data-storage-architecture.md
@@ -217,40 +217,6 @@ membership queries at scale:
`__words__` for tokenized text…).
- `_blobs/_column_index/{field}/L0-NNNNNN.bin` — the actual level-0 run
segments, stored through the shared `_blobs/.bin` binary convention.
-- `_column_index/{field}/k/{kind}/…` — the same two files again, for a
- **second value kind** on the same field (see below). Absent for a field that
- holds one kind, which is nearly all of them.
-
-### One posting column per (field, kind)
-
-A field is not obliged to hold one type of value. `category` may carry
-`'electronics'` on some rows and `5` on others, and both are real values of
-that field. A segment, though, has one encoding — i64, f64, UTF-8, or boolean
-— so a field that holds several kinds gets **one column per kind**:
-
-- The first kind a field ever sees owns the plain `_column_index/{field}/`
- layout above. A single-kind field is therefore byte-identical to what earlier
- versions wrote, and an index written before typed postings opens unchanged.
-- Every later kind gets its own column beside it at
- `_column_index/{field}/k/{kind}/`, where `{kind}` is `number`, `string` or
- `boolean`.
-
-What that buys at query time:
-
-| | |
-|---|---|
-| **Equality** | Answered from the column matching the **query value's own kind**. `where {category: 5}` reads the number postings; `where {category: '5'}` reads the string postings. Neither borrows the other's rows — a row written with the number `5` is not a row whose category is the text `'5'`. |
-| **A kind the field never held** | Matches nothing. That is the true answer, not a coerced one. |
-| **Ranges** | Routed by the kind of the bounds: numeric bounds read the numeric postings and ignore the field's strings. An **unbounded** range is the "has any value here" probe behind `exists`, and reads every kind. |
-| **`orderBy`** | A number and a string have no order between them, so a mixed field orders by kind first (number, string, boolean) and by value within a kind. A single-kind field sorts exactly as it always did. |
-| **Numbers** | One kind, one column: an integer column is written as i64 and widens to f64 the first time a non-integer arrives, so `4.5` is stored as itself rather than rounded. |
-
-`null` and `undefined` are not kinds and are never posted; their absence is
-what the `exists` / `missing` operators read.
-
-Older readers are unaffected by the additional columns: they see the field's
-primary column exactly where it has always been, and a `k/{kind}` directory is
-simply a name they never query.
Sparse per-field indexes, roaring-bitmap chunks, and zone-map/bloom segments
additionally live as bucketed keys under `_system/idx/` (see §3). Which path
@@ -302,7 +268,7 @@ locks/_flush_responses/ # writer answers with .ack
| **Counts/statistics** | Per-type and per-subtype maps | `_system/{type,subtype,verb-subtype}-statistics.json.gz`, `counts.json` | Recomputable by scanning entities (`brainy inspect repair`) |
A pluggable index provider (the 8.0 plugin contract in
-`@soulcraftlabs/brainy/plugin`) may replace any of the JS implementations; the
+`@soulcraft/brainy/plugin`) may replace any of the JS implementations; the
persisted formats above are contract-bound so JS and native implementations
can interleave on the same directory.
diff --git a/docs/architecture/finite-type-system.md b/docs/architecture/finite-type-system.md
index 48a8b1fe..76492ee5 100644
--- a/docs/architecture/finite-type-system.md
+++ b/docs/architecture/finite-type-system.md
@@ -126,7 +126,7 @@ class TypeAwareMetadataIndex {
**The Design**: Specify types clearly in your API calls:
```typescript
-import { Brainy, NounType, VerbType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType, VerbType } from '@soulcraft/brainy'
// Add entity with explicit type
await brain.add({
@@ -231,7 +231,7 @@ class OrgEnrichmentAugmentation {
**Brainy's Approach**: Extract **typed** concepts:
```typescript
-import { NaturalLanguageProcessor } from '@soulcraftlabs/brainy'
+import { NaturalLanguageProcessor } from '@soulcraft/brainy'
const nlp = new NaturalLanguageProcessor()
const concepts = await nlp.extractConcepts("Alice works at Google in San Francisco")
@@ -382,7 +382,7 @@ import {
getVerbTypes,
BrainyTypes,
suggestType
-} from '@soulcraftlabs/brainy'
+} from '@soulcraft/brainy'
// Get all available noun types
const nounTypes = getNounTypes()
diff --git a/docs/architecture/index-architecture.md b/docs/architecture/index-architecture.md
index 6a754b56..8b3dc540 100644
--- a/docs/architecture/index-architecture.md
+++ b/docs/architecture/index-architecture.md
@@ -723,14 +723,6 @@ async stats(): Promise {
### 5. Index Rebuilding (Lazy Loading Support)
-> **Stale as of 10.4 — "Mode 2: Lazy Loading on First Query" below is
-> RETIRED.** `disableAutoRebuild` no longer defers index construction to a
-> first query; `brain.init()` now runs every needed rebuild to completion
-> before it returns, unconditionally, and a read against a not-serving
-> provider throws a typed `*NotReadyError` instead of rebuilding mid-query.
-> See `docs/concepts/index-health.md` for the current contract. Left below
-> as historical background on the rebuild mechanics.
-
**Two modes of index loading:**
#### Mode 1: Auto-Rebuild on init() (default)
diff --git a/docs/architecture/initialization-and-rebuild.md b/docs/architecture/initialization-and-rebuild.md
index e19bdd9f..a1645744 100644
--- a/docs/architecture/initialization-and-rebuild.md
+++ b/docs/architecture/initialization-and-rebuild.md
@@ -1,15 +1,5 @@
# Initialization and Rebuild Processes
-> **Stale as of 10.4 — "Mode 2: Lazy Loading on First Query" below is RETIRED.**
-> `disableAutoRebuild` no longer defers index construction to a first query;
-> `brain.init()` now runs every needed rebuild to completion before it
-> returns, unconditionally. A read against a not-serving provider throws a
-> typed `*NotReadyError` instead of rebuilding mid-query. See
-> `docs/concepts/index-health.md` for the current contract; this document's
-> line-number references to `src/brainy.ts` also predate the file's current
-> size and are unreliable. Left as historical background on the rebuild
-> mechanics, not as a current API description.
-
This document explains how Brainy's four indexes (MetadataIndex, vector index, GraphAdjacencyIndex, DeletedItemsIndex) initialize and rebuild from persisted storage.
## Core Principle: All Indexes Are Disk-Based
diff --git a/docs/architecture/multiprocess-storage-mixin.md b/docs/architecture/multiprocess-storage-mixin.md
index 1593bf8f..46f98398 100644
--- a/docs/architecture/multiprocess-storage-mixin.md
+++ b/docs/architecture/multiprocess-storage-mixin.md
@@ -127,7 +127,7 @@ For reference, a clean migration path:
`isMultiProcessSafe` type-guard. Keep `hasStorageMethod` for
build/install artifact protection.
5. Document the new contract in `concepts/storage-adapters.md`.
-6. Major-version-bump the `@soulcraftlabs/brainy` peerDep range expected by
+6. Major-version-bump the `@soulcraft/brainy` peerDep range expected by
plugins.
Estimated work: ~half a day of code, ~2 hours of doc/example updates,
diff --git a/docs/architecture/noun-verb-taxonomy.md b/docs/architecture/noun-verb-taxonomy.md
index 3dac6892..286464be 100644
--- a/docs/architecture/noun-verb-taxonomy.md
+++ b/docs/architecture/noun-verb-taxonomy.md
@@ -20,7 +20,7 @@ next:
Every example on this page is written against the real Brainy 8.0 API. The setup is always the same:
```typescript
-import { Brainy, NounType, VerbType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType, VerbType } from '@soulcraft/brainy'
const brain = new Brainy()
await brain.init()
@@ -40,7 +40,7 @@ Brainy's **Noun-Verb Taxonomy** achieves broad coverage of human knowledge throu
- **Multi-hop Graph Traversals = Relationship Complexity**
- **Result: Model data across virtually any industry**
-Every piece of information can be represented as entities (nouns) connected by relationships (verbs) carrying properties (metadata). The standardized type system from `@soulcraftlabs/brainy` (`NounType`, `VerbType`) gives those nouns and verbs a stable, shared name.
+Every piece of information can be represented as entities (nouns) connected by relationships (verbs) carrying properties (metadata). The standardized type system from `@soulcraft/brainy` (`NounType`, `VerbType`) gives those nouns and verbs a stable, shared name.
## The Power of Standardization: Universal Interoperability
diff --git a/docs/architecture/zero-config.md b/docs/architecture/zero-config.md
index a35e6416..d42d6784 100644
--- a/docs/architecture/zero-config.md
+++ b/docs/architecture/zero-config.md
@@ -35,7 +35,7 @@ constructor and `init()`.
## Instant Start
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
// That's it. No config needed.
const brain = new Brainy()
diff --git a/docs/concepts/field-addressing.md b/docs/concepts/field-addressing.md
index d24dd66b..c459021b 100644
--- a/docs/concepts/field-addressing.md
+++ b/docs/concepts/field-addressing.md
@@ -167,7 +167,7 @@ await brain.find({ orderBy: 'createdAt' })
`UnresolvableFieldError` is exported from the package root:
```typescript
-import { UnresolvableFieldError } from '@soulcraftlabs/brainy'
+import { UnresolvableFieldError } from '@soulcraft/brainy'
try {
await brain.find({ orderBy: 'createdAt' })
diff --git a/docs/concepts/index-health.md b/docs/concepts/index-health.md
deleted file mode 100644
index 923267df..00000000
--- a/docs/concepts/index-health.md
+++ /dev/null
@@ -1,217 +0,0 @@
----
-title: Index Health
-slug: concepts/index-health
-public: true
-category: concepts
-template: concept
-order: 8
-description: How Brainy knows whether a derived index can be trusted — exact accounting instead of sampling, the named health report, degraded-but-serving vs. not-ready, and what repairIndex() checks, heals, and rebuilds.
-next:
- - concepts/generation-fact-log
- - guides/inspection
----
-
-# Index Health
-
-Brainy keeps one **canonical** copy of every entity and relationship, and three
-**derived** indexes built from it — vector, metadata, and graph — so `find()` can
-answer semantically, by filter, and by traversal without re-deriving the answer from
-scratch on every query. A derived index is a cache with a serving structure: it can
-be present but stale, present but only partially loaded, or fully out of sync with
-canonical after a crash. This page is about how Brainy decides whether to trust one,
-what it does when it can't, and how you reconcile the two.
-
-## Exact accounting instead of sampling
-
-Older health checks worked by inference: does `size()` return something greater
-than zero, does a spot-check on one known item come back correct. Both are proxies.
-A cold index can report a nonzero count while its actual serving structure never
-loaded, and a spot-check only proves the one item it happened to ask about.
-
-Every derived-index provider may now expose a named, synchronous, O(1)
-`healthReport()` — composed from the provider's own **exact ledgers** (real counters
-it already maintains on the write path), never a sample or a walk. This is the one
-signal Brainy's read gate consults. A provider that doesn't yet expose one falls
-back to an honest `isReady()` boolean, and finally to a size heuristic for engines
-with neither — but wherever a `healthReport()` exists, it wins.
-
-Underneath, storage itself keeps an analogous **canonical count ledger**: a
-`counted` scalar (the user-facing total — what `getNounCount()` / `getVerbCount()`
-return) and an `all` scalar (every tier, including internal records a derived
-index's own coverage math needs to compare against). This is the real denominator
-a provider's `healthReport()` measures itself by, rather than a total that can only
-ever ratchet upward. See [What `suspect` counts mean](#what-suspect-counts-mean)
-below for the one case that ledger can't stay exact through on its own.
-
-## The named report
-
-A `HealthReport` carries, per provider (`'vector'` / `'graph'` / `'metadata'`):
-
-- **`healthy`** — `true` iff every *verified* invariant holds. An invariant whose
- family has no ledger yet is `unledgered`, never counted either way — unknown,
- not passing.
-- **`serving`** — can this provider answer a query right now. A failing invariant
- graded `heal: 'repair'` or `heal: 'none'` still leaves `serving: true` — this is
- **degraded-but-serving**: something is off (say, a stale rollup on an
- `employee` record's relationship count) but reads keep working. Only a failure
- graded `heal: 'rebuild'` flips `serving` to `false` — **not-ready** — because the
- provider itself is telling you its serving structure cannot answer correctly.
-- **`invariants`** — each checked condition, with its provenance
- (`source: 'ledger'` — an exact count; `'deep'` — a full scan, diagnostic-only;
- `'unledgered'` — not yet tracked) and, for a failing one, an exact `missing`
- count plus a capped sample of the affected ids — a verdict, never a dump.
-- **`generation`** — bumps on every ledger mutation and rebuild, so a caller can
- cache a verdict per generation instead of re-deriving it.
-
-The distinction that matters day to day: `healthy: false` can be entirely benign —
-a maintenance window, a divergence `repairIndex()` will clean up on its own
-schedule. `serving: false` is not benign. It means this provider is refusing to
-answer, on its own word, right now.
-
-**How a failure gets its grade — the serving law.** A provider grades `heal` by
-one question only: *could an answer be wrong?* — never *how expensive is the
-fix?* A missing-postings shortfall, however large, is `heal: 'repair'` (re-post
-exactly what the ledger names, reads serving throughout); it can never withhold
-serving just because healing it takes work. `serving` is withheld only by a
-small, named set of rebuild-graded conditions — the index not initialized, its
-durable state absent, a manifest naming files that are not resident, a replay
-that did not complete cleanly — the states in which an answer could genuinely be
-wrong. And a read is only ever refused by the family it actually consults: a
-metadata filter is answered by the metadata index alone, vector search by the
-vector index, traversal by the graph index — one family's refusal never blocks
-another family's reads.
-
-## Reads refuse — they never rebuild
-
-A query that reaches a not-serving provider does not trigger a rebuild from inside
-the read. Brainy retired that path deliberately: a rebuild kicked off by an ordinary
-`find({ where: { status: 'active' } })` call is a dark, unpredictable cost hiding
-behind a request that looks like a cheap read. Instead, the read throws a typed,
-catchable error naming the reason:
-
-| Error | Thrown when | Meaning |
-|---|---|---|
-| `GraphIndexNotReadyError` | `find({ connected })`, `neighbors()`, `related()` | The graph adjacency index isn't serving — traversal would otherwise return `[]` indistinguishable from "no relationships" |
-| `MetadataIndexNotReadyError` | `find({ where })` | The metadata/field index isn't serving — a filtered read would otherwise return `[]` indistinguishable from "no matches" |
-| `VectorIndexNotReadyError` | `find({ query })`, `similar()` | The vector index isn't serving — a semantic search would otherwise return `[]` indistinguishable from "nothing similar" |
-
-All three are exported from `@soulcraftlabs/brainy`. Catch them where your application
-needs to distinguish "this index isn't ready yet" from "there's genuinely nothing
-here" — a health dashboard, a retry policy, an operator alert. The fix is always
-the same: reconcile the index, either by reopening the brain (which brings every
-provider to serving before `init()` returns — see the next section) or by calling
-`repairIndex()` explicitly.
-
-```typescript
-try {
- const active = await brain.find({ where: { status: 'active' } })
-} catch (err) {
- if (err instanceof MetadataIndexNotReadyError) {
- // not a "no results" — the index itself refused; alert or retry after repair
- } else {
- throw err
- }
-}
-```
-
-### Rebuilds happen at open, not on first query
-
-`brain.init()` runs every needed rebuild to completion **before it returns**,
-unconditionally, regardless of dataset size. There is no lazy, first-query
-rebuild path anymore — a brain either finishes opening healthy, or it fails
-open loudly. `disableAutoRebuild: true` no longer defers index construction to
-the first query: it has no effect on *when* a needed rebuild runs. Full manual
-control over rebuilds is `repairIndex({ rebuild: [...] })` (below), not this flag.
-
-## `repairIndex()` — checking and healing
-
-Bare `repairIndex()` is **report-driven**: it only heals what its own checks say
-actually needs it, and it always returns a full per-family receipt.
-
-```typescript
-const report = await brain.repairIndex()
-report.healedTotal // total items healed across every family
-report.durationMs
-report.families // one row per family checked
-```
-
-Each `RepairFamilyReport` row names what happened:
-
-- **`checked`** — was this family actually examined (`false` means skipped —
- see `skipped` for why).
-- **`healed`** — items re-posted or corrected in place.
-- **`missing`** — when the check can name what diverged: an exact `count` plus a
- capped `sample` of ids.
-- **`rebuilt`** — a full generational rebuild ran (as opposed to an incremental
- heal).
-- **`detail`** / **`reason`** / **`skipped`** — the receipt's narration; a row is
- always either checked or explains why it wasn't. Nothing is silent.
-
-On every call, bare `repairIndex()`:
-
-1. Prunes orphaned canonical containers left by a partial delete.
-2. Recomputes the count rollups from one canonical walk (unconditional — this is
- also what clears a `suspect` ledger; see below).
-3. Reconciles VFS containment edges, if the VFS is initialized.
-4. Runs the metadata index's own corruption detection pass.
-5. Consults each of the three derived-index providers' own health check and
- rebuilds only a family whose failing invariant actually asks for it
- (`heal: 'rebuild'`) — never a provider that reports `healthy` or a lesser
- grade.
-
-### The explicit rebuild door
-
-`options.rebuild` skips the health check and rebuilds one or more families
-**unconditionally** — the operator override for when you have independent reason
-to distrust a family regardless of what it self-reports (a suspicious deploy, a
-storage-layer incident, a support ticket that doesn't match what the health report
-says):
-
-```typescript
-// Force the graph adjacency to rebuild from canonical, no invariant consulted
-await brain.repairIndex({ rebuild: ['graph'] })
-
-// Force all three derived indexes
-await brain.repairIndex({ rebuild: 'all' })
-```
-
-A family named this way is recorded with `rebuilt: true` and
-`reason: 'explicit rebuild requested'`, and is skipped by the normal
-health-driven pass in the same call — it was already rebuilt unconditionally.
-
-Reach for the explicit door when you need certainty regardless of self-report;
-reach for bare `repairIndex()` for routine maintenance and after any incident
-where you're not sure which family (if any) needs it.
-
-## What `suspect` counts mean
-
-Storage's canonical count ledger increments the ALL-visibility total on every new
-record and decrements it on every *proven* delete — one where the record was read,
-or the caller supplied its prior image. A delete that cannot prove what it removed
-existed doesn't guess: it flags the ledger `suspect` (an operator-visible
-`console.warn`, narrated once per session, not once per delete) rather than risk
-decrementing a total that was never incremented for that record in the first
-place. This is intentionally rare — it's a defensive fallback for callers on an
-unusual removal path, not a per-delete cost.
-
-`suspect` is not directly exposed on any `Brainy` method today — it lives on the
-`StorageAdapter`'s optional `getCanonicalCounts()`, primarily consulted by
-`repairIndex()`'s recount step and by custom storage adapters composing their own
-`healthReport()`. What matters for an application: a `suspect` ledger is not
-incorrect, just *unverified since the last recount* — and `repairIndex()`'s
-unconditional count-rollup step (step 2, above) recomputes the ALL scalars from a
-real canonical walk on every call, clearing the flag with proof either way.
-
-## Practical guidance
-
-- **On a normal restart**, do nothing — `init()` brings every provider to
- serving before it returns, or fails loudly.
-- **On a `*NotReadyError`** from a live read, reconcile with `repairIndex()`
- (report-driven is almost always sufficient) and retry.
-- **After an incident** where you distrust a specific family regardless of what
- it reports healthy — a storage-layer fault, a suspicious restore — use the
- explicit door: `repairIndex({ rebuild: ['metadata' | 'graph' | 'vector'] })`.
-- **To audit before trusting a report**, `brain.auditGraph()` walks every stored
- relationship and proves (or disproves) that reads return canonical truth,
- independent of what any provider self-reports — see
- [Inspecting a Live Brainy](../guides/inspection.md).
diff --git a/docs/concepts/multi-process.md b/docs/concepts/multi-process.md
index d698eee8..8fda315f 100644
--- a/docs/concepts/multi-process.md
+++ b/docs/concepts/multi-process.md
@@ -95,15 +95,8 @@ The heartbeat interval rewrites the lock file every 10 seconds. The timer
is unref'd, so it does not keep the event loop alive on its own.
On normal shutdown the writer releases the lock in `close()`. The shutdown
-hooks Brainy registers for `SIGTERM` and `SIGINT` close every live brain by
-that same `close()`, so a container restart doesn't strand the directory.
-
-`beforeExit` is not one of them. Node emits it whenever the event loop has
-no ref'd work left — a state a healthy script reaches routinely, because
-Brainy's own idle and cadence timers are unref'd — and a drained event loop
-is not a shutdown. That hook only persists derived state with a non-closing
-`flush()`: it closes nothing, releases no lock, and leaves every brain open
-and usable. If you want a shutdown, call `close()` or send `SIGTERM`.
+hooks Brainy registers for `SIGTERM`, `SIGINT`, and `beforeExit` also
+release the lock so a container restart doesn't strand the directory.
## How to inspect a live writer
diff --git a/docs/concepts/storage-adapters.md b/docs/concepts/storage-adapters.md
index 82aa01e8..af6d068f 100644
--- a/docs/concepts/storage-adapters.md
+++ b/docs/concepts/storage-adapters.md
@@ -61,7 +61,7 @@ The only required override is the capability flag. Returning `true` from
to call `acquireWriterLock()` at init.
```typescript
-import { FileSystemStorage } from '@soulcraftlabs/brainy'
+import { FileSystemStorage } from '@soulcraft/brainy'
export class MmapFileSystemStorage extends FileSystemStorage {
public supportsMultiProcessLocking(): boolean {
@@ -79,7 +79,7 @@ If your storage is **not filesystem-backed** (a custom
network backend), extend `BaseStorage` directly:
```typescript
-import { BaseStorage } from '@soulcraftlabs/brainy'
+import { BaseStorage } from '@soulcraft/brainy'
export class MyCloudStorage extends BaseStorage {
// BaseStorage's default no-op implementations of the multi-process
@@ -101,7 +101,7 @@ The defensive check at every new-storage-method call site (`brainy.ts`,
`hasStorageMethod(name)`) does **not** exist to handle "plugin bundles a
stale BaseStorage." Plugins ship a dist that preserves the dynamic ESM
import (verify in your plugin's `dist/`: `import { FileSystemStorage } from
-'@soulcraftlabs/brainy'` is not rewritten to a vendored copy). The prototype
+'@soulcraft/brainy'` is not rewritten to a vendored copy). The prototype
chain at runtime resolves to whatever Brainy version your consumer has
installed.
@@ -109,8 +109,8 @@ installed.
the prototype chain at the consumer-app level:
- **Stale `node_modules`** — a lingering install from before the consumer
- upgraded Brainy. The package.json says `@soulcraftlabs/brainy@7.22.0` but
- `node_modules/@soulcraftlabs/brainy` is still 7.20.x.
+ upgraded Brainy. The package.json says `@soulcraft/brainy@7.22.0` but
+ `node_modules/@soulcraft/brainy` is still 7.20.x.
- **Lockfile drift** — `bun.lockb` / `package-lock.json` pins a brainy
version older than the package.json range, and `bun install` honors the
lockfile.
@@ -131,7 +131,7 @@ and the warning names the adapter class plus a remediation hint:
methods on its prototype chain. Writer locking and the flush-request RPC are
disabled for this directory. Likely fix: clean install (`rm -rf node_modules
bun.lockb && bun install`) or rebuild your container image to refresh
-`@soulcraftlabs/brainy` to ≥7.21. See docs/concepts/storage-adapters.md.
+`@soulcraft/brainy` to ≥7.21. See docs/concepts/storage-adapters.md.
```
## Authoring a new storage adapter — minimum checklist
@@ -168,7 +168,7 @@ bun.lockb && bun install`) or rebuild your container image to refresh
install time — fix install, not your plugin.
6. **Pin your peer dep generously.** `"peerDependencies": {
- "@soulcraftlabs/brainy": "^7.21.0" }` accepts any compatible 7.x. Don't pin
+ "@soulcraft/brainy": "^7.21.0" }` accepts any compatible 7.x. Don't pin
to an exact patch unless you're tracking a known regression.
## Future direction
@@ -185,5 +185,5 @@ follow-up; consumers don't need to anticipate the change.
heartbeat semantics, what the lock protects.
- [`guides/inspection`](../guides/inspection.md) — `brainy inspect` and the
read-only mode.
-- `node_modules/@soulcraftlabs/brainy/dist/storage/baseStorage.d.ts` — the
+- `node_modules/@soulcraft/brainy/dist/storage/baseStorage.d.ts` — the
authoritative type signatures for every method this page references.
diff --git a/docs/guides/aggregation.md b/docs/guides/aggregation.md
index 616c8fc4..11d86ec8 100644
--- a/docs/guides/aggregation.md
+++ b/docs/guides/aggregation.md
@@ -22,7 +22,7 @@ they share a single scan.
## Quick Start
```typescript
-import { Brainy, NounType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType } from '@soulcraft/brainy'
const brain = new Brainy()
await brain.init()
diff --git a/docs/guides/framework-integration.md b/docs/guides/framework-integration.md
index 8f85da00..984466c5 100644
--- a/docs/guides/framework-integration.md
+++ b/docs/guides/framework-integration.md
@@ -8,7 +8,7 @@ Brainy is **framework-friendly** - designed to drop into the server side of any
Brainy embeds an HNSW vector index, a graph engine, and a filesystem-backed persistence layer. These belong on the server:
-- **Zero configuration**: Just `import { Brainy } from '@soulcraftlabs/brainy'`
+- **Zero configuration**: Just `import { Brainy } from '@soulcraft/brainy'`
- **Auto storage detection**: `new Brainy()` auto-selects filesystem persistence on Node
- **Cleaner code**: No browser polyfills, no conditional client/server imports
- **Better DX**: One instance shared across your server routes
@@ -18,13 +18,13 @@ Brainy embeds an HNSW vector index, a graph engine, and a filesystem-backed pers
### Install Brainy
```bash
-npm install @soulcraftlabs/brainy
+npm install @soulcraft/brainy
```
### Basic Integration
```javascript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
// Run on the server (API route, server component, backend service)
// new Brainy() auto-detects filesystem persistence on Node
@@ -105,7 +105,7 @@ On the server, create one Brainy instance and reuse it across requests. This mod
```javascript
// lib/brain.server.js
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
let brainPromise
@@ -163,7 +163,7 @@ On the server, create one Brainy instance and reuse it across requests:
```javascript
// server/brain.js (server-only module)
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
let brainPromise
@@ -248,7 +248,7 @@ The matching backend endpoint uses Brainy directly (Node/Bun):
```typescript
// server: api/search
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const brain = new Brainy() // auto-detects filesystem persistence on Node
await brain.init()
@@ -266,7 +266,7 @@ In Next.js, Brainy lives in server code only: API routes, server components, or
```javascript
// lib/brain.server.js (imported only by server code)
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
let brainPromise
@@ -318,7 +318,7 @@ Brainy runs in a server-only module (`*.server.js`); the component fetches resul
```javascript
// src/lib/server/brain.js (server-only — note the .server suffix)
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
let brainPromise
@@ -432,7 +432,7 @@ import { defineConfig } from 'vite'
export default defineConfig({
ssr: {
- external: ['@soulcraftlabs/brainy']
+ external: ['@soulcraft/brainy']
}
})
```
@@ -440,7 +440,7 @@ export default defineConfig({
```javascript
// rollup.config.js (server bundle)
export default {
- external: ['@soulcraftlabs/brainy', 'node:fs', 'node:path', 'node:crypto']
+ external: ['@soulcraft/brainy', 'node:fs', 'node:path', 'node:crypto']
}
```
@@ -466,7 +466,7 @@ export async function load({ url }) {
```javascript
// For build-time usage (runs in Node during the build)
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
export async function generateStaticProps() {
const brain = new Brainy({
@@ -513,7 +513,7 @@ export async function generateStaticProps() {
### Issue: Large client bundle size
**Cause**: A client module is pulling in Brainy.
-**Solution**: Move the `import { Brainy } from '@soulcraftlabs/brainy'` into a server-only module so it never reaches the browser bundle.
+**Solution**: Move the `import { Brainy } from '@soulcraft/brainy'` into a server-only module so it never reaches the browser bundle.
### Issue: SSR hydration mismatch
**Solution**: Run the search on the server (loader / server action / API route) and pass the results down as props, so server and client render the same markup.
diff --git a/docs/guides/import-anything.md b/docs/guides/import-anything.md
index ffabe55c..b1bb15ef 100644
--- a/docs/guides/import-anything.md
+++ b/docs/guides/import-anything.md
@@ -9,7 +9,7 @@ Brainy's import is **ONE magical method** that understands EVERYTHING:
## The Ultimate Simplicity
```javascript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const brain = new Brainy()
await brain.init()
diff --git a/docs/guides/import-progress-examples.md b/docs/guides/import-progress-examples.md
index 18c3cb9a..66f50713 100644
--- a/docs/guides/import-progress-examples.md
+++ b/docs/guides/import-progress-examples.md
@@ -13,7 +13,7 @@ Brainy provides real-time progress tracking for **all 7 supported file formats**
### Basic Progress Tracking
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
import * as fs from 'fs'
const brain = await Brainy.create()
diff --git a/docs/guides/import-quick-reference.md b/docs/guides/import-quick-reference.md
index 3bc26dae..7837d49e 100644
--- a/docs/guides/import-quick-reference.md
+++ b/docs/guides/import-quick-reference.md
@@ -7,7 +7,7 @@
## Basic Import
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const brain = new Brainy()
await brain.init()
@@ -187,7 +187,7 @@ await brain.import(file, {
## Complete Example
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
import * as fs from 'fs'
async function importCatalog() {
diff --git a/docs/guides/inspection.md b/docs/guides/inspection.md
index 8560b543..240e81ae 100644
--- a/docs/guides/inspection.md
+++ b/docs/guides/inspection.md
@@ -108,7 +108,7 @@ check fails — useful for piping into monitoring or CI.
## Programmatic inspection
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const reader = await Brainy.openReadOnly({
storage: { type: 'filesystem', path: '/data/brain' }
diff --git a/docs/guides/installation.md b/docs/guides/installation.md
index 20d40ea2..0a36f632 100644
--- a/docs/guides/installation.md
+++ b/docs/guides/installation.md
@@ -21,21 +21,21 @@ next:
## Install
```bash
-npm install @soulcraftlabs/brainy
+npm install @soulcraft/brainy
```
Or with your preferred package manager:
```bash
-bun add @soulcraftlabs/brainy
-yarn add @soulcraftlabs/brainy
-pnpm add @soulcraftlabs/brainy
+bun add @soulcraft/brainy
+yarn add @soulcraft/brainy
+pnpm add @soulcraft/brainy
```
## Verify
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const brain = new Brainy()
await brain.init()
@@ -52,7 +52,7 @@ npm install @soulcraft/cor
```
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const brain = new Brainy({ plugins: ['@soulcraft/cor'] })
await brain.init() // native providers registered during init
@@ -71,7 +71,7 @@ remains available on npm if you need it.
Brainy ships with full TypeScript types. No `@types/` package needed:
```typescript
-import { Brainy, NounType, VerbType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType, VerbType } from '@soulcraft/brainy'
const brain = new Brainy()
await brain.init()
diff --git a/docs/guides/migration-3.36.0.md b/docs/guides/migration-3.36.0.md
index 5f00534a..8b1f239e 100644
--- a/docs/guides/migration-3.36.0.md
+++ b/docs/guides/migration-3.36.0.md
@@ -66,7 +66,7 @@ const results = await brain.search("query")
**New diagnostics for capacity planning and performance tuning.**
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const brain = new Brainy()
await brain.init()
@@ -112,7 +112,7 @@ Recommendations: ${stats.recommendations.join(', ')}
### Step 1: Update Package
```bash
-npm install @soulcraftlabs/brainy@latest
+npm install @soulcraft/brainy@latest
```
### Step 2: Restart Your Application
@@ -134,7 +134,7 @@ npm run start
### Check Adaptive Sizing is Working
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const brain = new Brainy()
await brain.init()
@@ -218,7 +218,7 @@ For debugging or compatibility testing:
If you need to rollback to v3.35.0:
```bash
-npm install @soulcraftlabs/brainy@3.35.0
+npm install @soulcraft/brainy@3.35.0
```
**Note:** We don't anticipate any issues, but rollback is straightforward if needed.
@@ -367,7 +367,7 @@ if (stats.fairness.fairnessViolation) {
## Next Steps
-1. ✅ **Upgrade:** `npm install @soulcraftlabs/brainy@latest`
+1. ✅ **Upgrade:** `npm install @soulcraft/brainy@latest`
2. 📊 **Monitor:** Use `getCacheStats()` to verify performance improvements
3. 🎯 **Tune:** Adjust based on recommendations (if needed)
4. 📖 **Read:** [Operations Guide](../operations/capacity-planning.md) for capacity planning
diff --git a/docs/guides/model-loading.md b/docs/guides/model-loading.md
index cc1b2b6a..e5b7b1d6 100644
--- a/docs/guides/model-loading.md
+++ b/docs/guides/model-loading.md
@@ -37,7 +37,7 @@ This single WASM file contains everything needed for sentence embeddings.
```bash
# Bun as a runtime — supported and recommended
-bun add @soulcraftlabs/brainy
+bun add @soulcraft/brainy
bun run server.ts
```
diff --git a/docs/guides/namespace-migration.md b/docs/guides/namespace-migration.md
index f7d2c7f7..fad3c766 100644
--- a/docs/guides/namespace-migration.md
+++ b/docs/guides/namespace-migration.md
@@ -80,7 +80,7 @@ If you read raw stored records (fact-log scanners, export tooling), use
the exported shape-aware splitters — they handle both record eras:
```typescript
-import { splitNounMetadataRecord } from '@soulcraftlabs/brainy'
+import { splitNounMetadataRecord } from '@soulcraft/brainy'
const { reserved, custom } = splitNounMetadataRecord(rawRecord)
// reserved = engine fields · custom = the user's bag, ANY names
```
@@ -88,7 +88,7 @@ const { reserved, custom } = splitNounMetadataRecord(rawRecord)
Feature detection (never version-sniff):
```typescript
-import * as brainy from '@soulcraftlabs/brainy'
+import * as brainy from '@soulcraft/brainy'
const lawActive = 'FIELD_ADDRESSING_CAPABILITY' in brainy // 'field-addressing/v1'
```
diff --git a/docs/guides/nextjs-integration.md b/docs/guides/nextjs-integration.md
index 25d6062d..ab55e51f 100644
--- a/docs/guides/nextjs-integration.md
+++ b/docs/guides/nextjs-integration.md
@@ -9,7 +9,7 @@ Complete guide to integrating Brainy with Next.js applications, covering App Rou
```bash
npx create-next-app@latest my-brainy-app
cd my-brainy-app
-npm install @soulcraftlabs/brainy
+npm install @soulcraft/brainy
```
### Basic Setup
@@ -18,7 +18,7 @@ npm install @soulcraftlabs/brainy
// app/components/BrainyProvider.jsx
'use client'
import { createContext, useContext, useEffect, useState } from 'react'
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const BrainyContext = createContext()
@@ -271,7 +271,7 @@ export default function SearchPage() {
```javascript
// app/api/search/route.js (App Router)
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
let brain = null
@@ -332,7 +332,7 @@ export async function GET() {
```javascript
// pages/api/search.js (Pages Router)
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
let brain = null
@@ -374,7 +374,7 @@ export default async function handler(req, res) {
```javascript
// app/api/data/route.js
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
let brain = null
@@ -418,7 +418,7 @@ export async function POST(request) {
```jsx
// app/actions/brainy.js
'use server'
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
let brain = null
@@ -630,7 +630,7 @@ CMD ["npm", "start"]
/** @type {import('next').NextConfig} */
const nextConfig = {
experimental: {
- serverComponentsExternalPackages: ['@soulcraftlabs/brainy']
+ serverComponentsExternalPackages: ['@soulcraft/brainy']
},
webpack: (config, { isServer }) => {
if (!isServer) {
@@ -797,7 +797,7 @@ export function rateLimit(req, limit = 100, window = 60000) {
// app/contexts/BrainyContext.jsx
'use client'
import { createContext, useContext, useReducer, useEffect } from 'react'
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const BrainyContext = createContext()
@@ -873,7 +873,7 @@ import { BrainyProvider } from '../app/components/BrainyProvider'
import { Search } from '../app/components/Search'
// Mock Brainy
-jest.mock('@soulcraftlabs/brainy', () => ({
+jest.mock('@soulcraft/brainy', () => ({
Brainy: jest.fn().mockImplementation(() => ({
init: jest.fn().mockResolvedValue(undefined),
find: jest.fn().mockResolvedValue([
diff --git a/docs/guides/optimistic-concurrency.md b/docs/guides/optimistic-concurrency.md
index 2984998b..268bc5fa 100644
--- a/docs/guides/optimistic-concurrency.md
+++ b/docs/guides/optimistic-concurrency.md
@@ -32,7 +32,7 @@ Brainy 7.31.0 adds a per-entity revision counter so multiple writers can coordin
Every distributed-job scheduler eventually wants this exact loop:
```ts
-import { Brainy, RevisionConflictError } from '@soulcraftlabs/brainy'
+import { Brainy, RevisionConflictError } from '@soulcraft/brainy'
const LOCK_ID = '...uuid for this job slot...'
@@ -137,7 +137,7 @@ await brain.addIfMissing({ // ← not a real API
It's race-prone as a plain read-then-write: two concurrent imports both see "not found," both insert, you get duplicates. Without a unique-index primitive (which Brainy doesn't have today), close the race with whole-store CAS — read at a pinned generation, then commit only if nothing moved:
```ts
-import { GenerationConflictError } from '@soulcraftlabs/brainy'
+import { GenerationConflictError } from '@soulcraft/brainy'
async function addIfMissingByEmail(email: string, data: string) {
for (let attempt = 0; attempt < 5; attempt++) {
diff --git a/docs/guides/quick-start.md b/docs/guides/quick-start.md
index d9a4e896..097c55fe 100644
--- a/docs/guides/quick-start.md
+++ b/docs/guides/quick-start.md
@@ -18,13 +18,13 @@ Get Brainy running in under a minute.
## 1. Install
```bash
-npm install @soulcraftlabs/brainy
+npm install @soulcraft/brainy
```
## 2. Initialize
```typescript
-import { Brainy, NounType, VerbType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType, VerbType } from '@soulcraft/brainy'
const brain = new Brainy()
await brain.init()
@@ -67,7 +67,7 @@ await brain.relate({
## 5. Query with Triple Intelligence
```typescript
-import type { Result } from '@soulcraftlabs/brainy'
+import type { Result } from '@soulcraft/brainy'
// All three search paradigms in one call
const results: Result[] = await brain.find({
diff --git a/docs/guides/standard-import-progress.md b/docs/guides/standard-import-progress.md
index 27dabe75..9f2e2e5b 100644
--- a/docs/guides/standard-import-progress.md
+++ b/docs/guides/standard-import-progress.md
@@ -11,7 +11,7 @@
### One Interface for Everything
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const brain = await Brainy.create()
@@ -78,7 +78,7 @@ interface ImportProgress {
```typescript
import { useState } from 'react'
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
function UniversalImportProgress({ file }: { file: File }) {
const [progress, setProgress] = useState({
@@ -177,7 +177,7 @@ function UniversalImportProgress({ file }: { file: File }) {
```typescript
import ora from 'ora'
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
async function importWithProgress(filePath: string) {
const spinner = ora('Starting import...').start()
diff --git a/docs/guides/storage-adapters.md b/docs/guides/storage-adapters.md
index a4224bc8..06ec9f3a 100644
--- a/docs/guides/storage-adapters.md
+++ b/docs/guides/storage-adapters.md
@@ -28,7 +28,7 @@ on-disk layout (memory's "disk" is a JS Map).
## Quick start
```ts
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
// Filesystem (recommended for any persistent workload):
const brain = new Brainy({
@@ -134,7 +134,7 @@ config; the `type` is optional.
If you want to skip the factory:
```ts
-import { FileSystemStorage, MemoryStorage } from '@soulcraftlabs/brainy'
+import { FileSystemStorage, MemoryStorage } from '@soulcraft/brainy'
const fsStorage = new FileSystemStorage('./brainy-data')
const memStorage = new MemoryStorage()
diff --git a/docs/guides/subtypes-and-facets.md b/docs/guides/subtypes-and-facets.md
index 74311528..ff5de320 100644
--- a/docs/guides/subtypes-and-facets.md
+++ b/docs/guides/subtypes-and-facets.md
@@ -34,7 +34,7 @@ Three layers solve this:
### Write
```typescript
-import { Brainy, NounType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType } from '@soulcraft/brainy'
const brain = new Brainy()
await brain.init()
@@ -240,7 +240,7 @@ await brain.migrateField({
A realistic adoption sequence for a brain that started without these primitives:
```typescript
-import { Brainy, NounType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType } from '@soulcraft/brainy'
const brain = new Brainy({ storage: { type: 'filesystem', path: './brain-data' } })
await brain.init()
diff --git a/docs/guides/upgrading-7-to-8.md b/docs/guides/upgrading-7-to-8.md
index 53aa2a5c..a3c64fb9 100644
--- a/docs/guides/upgrading-7-to-8.md
+++ b/docs/guides/upgrading-7-to-8.md
@@ -25,7 +25,7 @@ content — and how 8.0 recovers it for you.
## TL;DR
-- **Just upgrade to `@soulcraftlabs/brainy@8.0.12` (or later) and open the store.**
+- **Just upgrade to `@soulcraft/brainy@8.0.12` (or later) and open the store.**
If a previous upgrade left VFS content stranded, 8.0.12 **heals it on open**,
with no operator action.
- Want to force or script it? Call **`await brain.vfs.adoptOrphanedBlobs()`**.
@@ -90,7 +90,7 @@ So the operator action for a stranded store is simply: **upgrade to 8.0.12 and
open it.**
```ts
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
// Opening the store is all that is required — recovery runs during init().
const brain = new Brainy({ storage: { type: 'filesystem', path: '/data/my-store' } })
@@ -182,5 +182,5 @@ and opening each store is sufficient.
The recovery is copy-only, so no rollback of the recovery itself is ever needed.
If you need to roll back the **whole** 7→8 upgrade, restore the directory from
your pre-upgrade backup (retained automatically while recovery is incomplete, or
-your own snapshot) and pin `@soulcraftlabs/brainy@7.x`. 8.0 does not keep the old
+your own snapshot) and pin `@soulcraft/brainy@7.x`. 8.0 does not keep the old
branch layout in place, so a directory-level restore is the rollback path.
diff --git a/docs/guides/vue-integration.md b/docs/guides/vue-integration.md
index 34d18ebf..7f7c6a06 100644
--- a/docs/guides/vue-integration.md
+++ b/docs/guides/vue-integration.md
@@ -12,7 +12,7 @@ Complete guide to integrating Brainy with Vue.js applications, covering Vue 3, N
npm create vue@latest my-brainy-app
cd my-brainy-app
npm install
-npm install @soulcraftlabs/brainy
+npm install @soulcraft/brainy
```
### Basic Setup
@@ -574,7 +574,7 @@ Nuxt's server engine (Nitro) is the natural home for Brainy: it runs on Node/Bun
```javascript
// server/utils/brain.js (server-only — Nitro never bundles this into the client)
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
let brainPromise
@@ -1201,7 +1201,7 @@ import vue from '@vitejs/plugin-vue'
export default defineConfig({
plugins: [vue()],
ssr: {
- external: ['@soulcraftlabs/brainy']
+ external: ['@soulcraft/brainy']
}
})
```
diff --git a/docs/neural-extraction.md b/docs/neural-extraction.md
index cfb6d764..989b1b60 100644
--- a/docs/neural-extraction.md
+++ b/docs/neural-extraction.md
@@ -24,7 +24,7 @@ Brainy's neural extraction system uses a **4-signal ensemble architecture** to c
### Method 1: Brain Instance (Recommended)
```typescript
-import { Brainy, NounType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType } from '@soulcraft/brainy'
const brain = new Brainy()
await brain.init()
@@ -62,9 +62,9 @@ const people = await brain.extractEntities('...', {
import {
SmartExtractor,
SmartRelationshipExtractor
-} from '@soulcraftlabs/brainy'
+} from '@soulcraft/brainy'
// Or use subpath imports:
-import { SmartExtractor } from '@soulcraftlabs/brainy/neural/SmartExtractor'
+import { SmartExtractor } from '@soulcraft/brainy/neural/SmartExtractor'
const brain = new Brainy()
await brain.init()
@@ -176,7 +176,7 @@ const withVectors = await brain.extractEntities(text, {
**Direct entity type classifier.** Use when you have pre-detected candidates or need custom configuration.
```typescript
-import { SmartExtractor, FormatContext } from '@soulcraftlabs/brainy'
+import { SmartExtractor, FormatContext } from '@soulcraft/brainy'
const extractor = new SmartExtractor(brain, {
minConfidence: 0.7, // Threshold
@@ -229,7 +229,7 @@ interface ExtractionResult {
**Relationship type classifier.** Determines verb/relationship types between entities.
```typescript
-import { SmartRelationshipExtractor } from '@soulcraftlabs/brainy'
+import { SmartRelationshipExtractor } from '@soulcraft/brainy'
const relExtractor = new SmartRelationshipExtractor(brain, {
minConfidence: 0.6,
@@ -286,7 +286,7 @@ const rel = await relExtractor.infer(
**Full extraction orchestrator.** Handles candidate detection, classification, and deduplication.
```typescript
-import { NeuralEntityExtractor } from '@soulcraftlabs/brainy'
+import { NeuralEntityExtractor } from '@soulcraft/brainy'
const extractor = new NeuralEntityExtractor(brain)
@@ -607,7 +607,7 @@ const locations = entities.filter(e => e.type === NounType.Location)
### Example 2: Excel Data Classification
```typescript
-import { SmartExtractor } from '@soulcraftlabs/brainy'
+import { SmartExtractor } from '@soulcraft/brainy'
const extractor = new SmartExtractor(brain)
@@ -629,7 +629,7 @@ for (let i = 0; i < cells.length; i++) {
### Example 3: Relationship Extraction
```typescript
-import { SmartRelationshipExtractor } from '@soulcraftlabs/brainy'
+import { SmartRelationshipExtractor } from '@soulcraft/brainy'
const relExtractor = new SmartRelationshipExtractor(brain)
diff --git a/docs/transactions.md b/docs/transactions.md
index cbea39c0..fce7d10e 100644
--- a/docs/transactions.md
+++ b/docs/transactions.md
@@ -204,8 +204,8 @@ await brain.add({ data: { name: 'Entity' }, type: NounType.Thing })
### Basic Add Operation
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
-import { NounType } from '@soulcraftlabs/brainy/types'
+import { Brainy } from '@soulcraft/brainy'
+import { NounType } from '@soulcraft/brainy/types'
const brain = new Brainy()
await brain.init()
@@ -428,7 +428,7 @@ await brain.relate({ ... }) // a crash here leaves the entity unlinked
```typescript
import { describe, it, expect } from 'vitest'
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
describe('Transaction Tests', () => {
it('should rollback on failure', async () => {
diff --git a/docs/universal-display-augmentation.md b/docs/universal-display-augmentation.md
index 464b91fb..da42874c 100644
--- a/docs/universal-display-augmentation.md
+++ b/docs/universal-display-augmentation.md
@@ -23,7 +23,7 @@ The Universal Display Augmentation is a powerful AI-powered system that automati
### Basic Usage
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const brainy = new Brainy()
await brainy.init()
diff --git a/docs/vfs/PROJECTION_STRATEGY_API.md b/docs/vfs/PROJECTION_STRATEGY_API.md
index f1319d5b..380862e1 100644
--- a/docs/vfs/PROJECTION_STRATEGY_API.md
+++ b/docs/vfs/PROJECTION_STRATEGY_API.md
@@ -71,9 +71,9 @@ Let's build a projection that organizes files by priority (high, medium, low):
### Step 1: Create the Strategy Class
```typescript
-import { BaseProjectionStrategy } from '@soulcraftlabs/brainy/vfs/semantic'
-import { Brainy } from '@soulcraftlabs/brainy'
-import { VirtualFileSystem, VFSEntity } from '@soulcraftlabs/brainy/vfs'
+import { BaseProjectionStrategy } from '@soulcraft/brainy/vfs/semantic'
+import { Brainy } from '@soulcraft/brainy'
+import { VirtualFileSystem, VFSEntity } from '@soulcraft/brainy/vfs'
export class PriorityProjection extends BaseProjectionStrategy {
readonly name = 'priority'
@@ -141,7 +141,7 @@ export class PriorityProjection extends BaseProjectionStrategy {
### Step 2: Register the Strategy
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
import { PriorityProjection } from './PriorityProjection'
const brain = new Brainy()
@@ -537,7 +537,7 @@ Use the projection's resolve cache:
```typescript
import { describe, it, expect, beforeAll } from 'vitest'
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
import { PriorityProjection } from './PriorityProjection'
describe('PriorityProjection', () => {
@@ -714,7 +714,7 @@ async resolve(brain, vfs, value: string) {
3. Use appropriate limits: Don't fetch more than needed
### Type errors
-1. Import correct types: `import { Brainy, VirtualFileSystem } from '@soulcraftlabs/brainy'`
+1. Import correct types: `import { Brainy, VirtualFileSystem } from '@soulcraft/brainy'`
2. Use `as VFSEntity` when mapping results
3. Check BaseProjectionStrategy import
diff --git a/docs/vfs/QUICK_START.md b/docs/vfs/QUICK_START.md
index 4a1f83dc..8b0efce6 100644
--- a/docs/vfs/QUICK_START.md
+++ b/docs/vfs/QUICK_START.md
@@ -14,11 +14,11 @@ A file explorer that:
## ⚡ Step 1: Basic Setup (1 minute)
```bash
-npm install @soulcraftlabs/brainy
+npm install @soulcraft/brainy
```
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
// ✅ CORRECT: Use filesystem storage for production
const brain = new Brainy({
@@ -115,7 +115,7 @@ Here's a complete React component using the correct patterns:
```tsx
import React, { useState, useEffect } from 'react'
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
export function FileExplorer() {
const [brain, setBrain] = useState(null)
@@ -288,8 +288,8 @@ Your file explorer is now working! Here's what to explore next:
### "Module not found" errors
```bash
# Make sure you're using the right import
-npm ls @soulcraftlabs/brainy # Check version
-npm install @soulcraftlabs/brainy@latest # Update if needed
+npm ls @soulcraft/brainy # Check version
+npm install @soulcraft/brainy@latest # Update if needed
```
### "VFS not initialized" errors
diff --git a/docs/vfs/README.md b/docs/vfs/README.md
index a94910c9..b95f0d7b 100644
--- a/docs/vfs/README.md
+++ b/docs/vfs/README.md
@@ -24,7 +24,7 @@ Brainy VFS is a revolutionary virtual filesystem that runs on top of Brainy's ne
## Quick Start
```javascript
-import { VirtualFileSystem } from '@soulcraftlabs/brainy/vfs'
+import { VirtualFileSystem } from '@soulcraft/brainy/vfs'
// Initialize the VFS
const vfs = new VirtualFileSystem({
@@ -381,7 +381,7 @@ Brainy VFS fully leverages Brainy's revolutionary Triple Intelligence system:
## Installation
```bash
-npm install @soulcraftlabs/brainy
+npm install @soulcraft/brainy
```
## Requirements
diff --git a/docs/vfs/ROADMAP.md b/docs/vfs/ROADMAP.md
index c8d15cd2..93c5b901 100644
--- a/docs/vfs/ROADMAP.md
+++ b/docs/vfs/ROADMAP.md
@@ -135,7 +135,7 @@ Mount VFS as a native filesystem on Linux/Mac/Windows.
```typescript
// Planned (research phase)
-import { mountVFS } from '@soulcraftlabs/brainy/vfs/fuse'
+import { mountVFS } from '@soulcraft/brainy/vfs/fuse'
await mountVFS(vfs, {
mountPoint: '/mnt/brainy',
@@ -160,7 +160,7 @@ These features would benefit from community contributions. If you're interested
### Express.js Static Middleware
```typescript
// Wanted: Community contribution
-import { createStaticMiddleware } from '@soulcraftlabs/brainy/vfs/express'
+import { createStaticMiddleware } from '@soulcraft/brainy/vfs/express'
app.use('/files', createStaticMiddleware(vfs, {
index: ['index.html', 'index.md'],
@@ -172,7 +172,7 @@ app.use('/files', createStaticMiddleware(vfs, {
### VSCode Extension
```typescript
// Wanted: Community contribution
-import { VFSProvider } from '@soulcraftlabs/brainy/vfs/vscode'
+import { VFSProvider } from '@soulcraft/brainy/vfs/vscode'
const provider = new VFSProvider(vfs)
vscode.workspace.registerFileSystemProvider('brainy', provider)
diff --git a/docs/vfs/SEMANTIC_VFS.md b/docs/vfs/SEMANTIC_VFS.md
index f34ee9ae..9298c822 100644
--- a/docs/vfs/SEMANTIC_VFS.md
+++ b/docs/vfs/SEMANTIC_VFS.md
@@ -327,7 +327,7 @@ console.log(id1 === id2 && id2 === id3) // true
Create your own semantic dimensions:
```typescript
-import { BaseProjectionStrategy } from '@soulcraftlabs/brainy/vfs/semantic'
+import { BaseProjectionStrategy } from '@soulcraft/brainy/vfs/semantic'
class PriorityProjection extends BaseProjectionStrategy {
readonly name = 'priority'
diff --git a/docs/vfs/VFS_API_GUIDE.md b/docs/vfs/VFS_API_GUIDE.md
index 5dcaaeb8..e0c6a94c 100644
--- a/docs/vfs/VFS_API_GUIDE.md
+++ b/docs/vfs/VFS_API_GUIDE.md
@@ -7,7 +7,7 @@ Brainy's Virtual Filesystem (VFS) provides a POSIX-like filesystem interface tha
## Quick Start
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
// Initialize Brainy
const brain = new Brainy({
@@ -598,7 +598,7 @@ const user = await store.findById('users', 'user123')
VFS uses standard POSIX-style errors:
```typescript
-import { VFSError, VFSErrorCode } from '@soulcraftlabs/brainy'
+import { VFSError, VFSErrorCode } from '@soulcraft/brainy'
try {
await vfs.readFile('/nonexistent.txt')
diff --git a/docs/vfs/VFS_CORE.md b/docs/vfs/VFS_CORE.md
index c1d502c0..1eeaf9f8 100644
--- a/docs/vfs/VFS_CORE.md
+++ b/docs/vfs/VFS_CORE.md
@@ -280,7 +280,7 @@ GitBridge provides Git import/export capabilities:
#### GitBridge Usage
```javascript
// Import and instantiate GitBridge
-import { GitBridge } from '@soulcraftlabs/brainy'
+import { GitBridge } from '@soulcraft/brainy'
const gitBridge = new GitBridge(vfs, brain)
// Export VFS to Git repository structure
@@ -452,7 +452,7 @@ This ordering prevents race conditions where file writes might fail because pare
## Complete Example
```javascript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
async function vfsExample() {
// Initialize
diff --git a/docs/vfs/VFS_GRAPH_TYPES.md b/docs/vfs/VFS_GRAPH_TYPES.md
index 478bef7f..3c1f30f0 100644
--- a/docs/vfs/VFS_GRAPH_TYPES.md
+++ b/docs/vfs/VFS_GRAPH_TYPES.md
@@ -196,5 +196,5 @@ await brain.relate({
Always import and use the type enums:
```javascript
-import { NounType, VerbType } from '@soulcraftlabs/brainy'
+import { NounType, VerbType } from '@soulcraft/brainy'
```
\ No newline at end of file
diff --git a/docs/vfs/VFS_INITIALIZATION.md b/docs/vfs/VFS_INITIALIZATION.md
index fd12fc71..97e6b0bf 100644
--- a/docs/vfs/VFS_INITIALIZATION.md
+++ b/docs/vfs/VFS_INITIALIZATION.md
@@ -5,7 +5,7 @@
The Brainy VFS is automatically initialized during `brain.init()`. No separate initialization needed!
```javascript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
// Create and initialize Brainy
const brain = new Brainy({
@@ -71,7 +71,7 @@ VFS stores files as entities and relationships in the same graph as everything e
## Complete Example
```javascript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
async function useVFS() {
// Initialize Brainy
@@ -100,7 +100,7 @@ useVFS().catch(console.error)
## TypeScript Usage
```typescript
-import { Brainy, VirtualFileSystem } from '@soulcraftlabs/brainy'
+import { Brainy, VirtualFileSystem } from '@soulcraft/brainy'
class FileManager {
private brain: Brainy
diff --git a/docs/vfs/building-file-explorers.md b/docs/vfs/building-file-explorers.md
index 7514c12e..6bb31871 100644
--- a/docs/vfs/building-file-explorers.md
+++ b/docs/vfs/building-file-explorers.md
@@ -37,7 +37,7 @@ Brainy VFS provides safe, tree-aware methods that prevent these issues:
### Method 1: Use `getDirectChildren()` (Recommended)
```typescript
-import { Brainy, VirtualFileSystem } from '@soulcraftlabs/brainy'
+import { Brainy, VirtualFileSystem } from '@soulcraft/brainy'
const brain = new Brainy()
await brain.init()
@@ -97,7 +97,7 @@ Here's a complete example using React:
```tsx
import React, { useState, useEffect } from 'react'
-import { VirtualFileSystem } from '@soulcraftlabs/brainy'
+import { VirtualFileSystem } from '@soulcraft/brainy'
interface FileNode {
name: string
@@ -177,7 +177,7 @@ function TreeView({ node, onToggle, expanded }) {
If you must build trees manually from flat lists, use the `VFSTreeUtils`:
```typescript
-import { VFSTreeUtils } from '@soulcraftlabs/brainy/vfs'
+import { VFSTreeUtils } from '@soulcraft/brainy/vfs'
// Get all entities somehow
const allEntities = await vfs.getDescendants('/root')
diff --git a/examples/bluesky-distributed-setup.js b/examples/bluesky-distributed-setup.js
index e3b33506..9e83cf25 100644
--- a/examples/bluesky-distributed-setup.js
+++ b/examples/bluesky-distributed-setup.js
@@ -7,7 +7,7 @@
* the Bluesky firehose with Brainy's distributed architecture
*/
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
import { WebSocket } from 'ws'
// =====================================================
diff --git a/examples/monitor-cache-performance.ts b/examples/monitor-cache-performance.ts
index 87c965a2..9d50d476 100644
--- a/examples/monitor-cache-performance.ts
+++ b/examples/monitor-cache-performance.ts
@@ -14,7 +14,7 @@
* ts-node examples/monitor-cache-performance.ts
*/
-import { Brainy, NounType } from '@soulcraftlabs/brainy'
+import { Brainy, NounType } from '@soulcraft/brainy'
// ANSI color codes for pretty output
const colors = {
diff --git a/integrations/README.md b/integrations/README.md
index de156623..aa3d795b 100644
--- a/integrations/README.md
+++ b/integrations/README.md
@@ -5,7 +5,7 @@ Connect Brainy to spreadsheets, BI tools, and external systems with zero configu
## Quick Start
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const brain = new Brainy({ integrations: true })
await brain.init()
@@ -178,7 +178,7 @@ Webhooks include `X-Brainy-Signature` header with HMAC-SHA256 signature.
### Minimal (in-memory):
```typescript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const brain = new Brainy({ integrations: true })
await brain.init()
@@ -194,7 +194,7 @@ console.log(brain.hub.getInstructions())
```typescript
import express from 'express'
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const app = express()
const brain = new Brainy({
@@ -232,7 +232,7 @@ app.listen(3000, () => {
```typescript
import { Hono } from 'hono'
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const app = new Hono()
diff --git a/integrations/google-sheets/README.md b/integrations/google-sheets/README.md
index 8309a30a..b2b0af3a 100644
--- a/integrations/google-sheets/README.md
+++ b/integrations/google-sheets/README.md
@@ -99,7 +99,7 @@ Add the `BRAINY_URL` script property in Apps Script settings.
The simplest way to enable all integrations:
```javascript
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const brain = new Brainy({ integrations: true })
await brain.init()
@@ -112,7 +112,7 @@ With Express:
```javascript
import express from 'express'
-import { Brainy } from '@soulcraftlabs/brainy'
+import { Brainy } from '@soulcraft/brainy'
const app = express()
const brain = new Brainy({ integrations: true })
diff --git a/package-lock.json b/package-lock.json
index c4757030..6193a630 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
{
- "name": "@soulcraftlabs/brainy",
- "version": "10.4.12",
+ "name": "@soulcraft/brainy",
+ "version": "10.0.0",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
- "name": "@soulcraftlabs/brainy",
- "version": "10.4.12",
+ "name": "@soulcraft/brainy",
+ "version": "10.0.0",
"license": "MIT",
"dependencies": {
"@msgpack/msgpack": "^3.1.2",
diff --git a/package.json b/package.json
index 649f2aaf..7b93cdd7 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,6 @@
{
- "name": "@soulcraftlabs/brainy",
- "version": "10.4.12",
- "brainyContract": 1,
+ "name": "@soulcraft/brainy",
+ "version": "10.0.0",
"description": "Universal Knowledge Protocol™ - World's first Triple Intelligence database unifying vector, graph, and document search in one API. Stage 3 CANONICAL: 42 nouns × 127 verbs covering 96-97% of all human knowledge.",
"main": "dist/index.js",
"module": "dist/index.js",
@@ -88,7 +87,7 @@
"test:watch": "NODE_OPTIONS='--max-old-space-size=8192' vitest --config tests/configs/vitest.unit.config.ts",
"test:coverage": "NODE_OPTIONS='--max-old-space-size=8192' vitest run --config tests/configs/vitest.unit.config.ts --coverage",
"test:unit": "NODE_OPTIONS='--max-old-space-size=8192' vitest run --config tests/configs/vitest.unit.config.ts",
- "test:perf": "vitest run --config tests/configs/vitest.perf.config.ts",
+ "test:perf": "vitest run tests/unit/performance --reporter=basic",
"test:integration": "NODE_OPTIONS='--max-old-space-size=8192' vitest run --config tests/configs/vitest.integration.config.ts",
"test:semantic": "NODE_OPTIONS='--max-old-space-size=8192' vitest run --config tests/configs/vitest.semantic.config.ts",
"test:all": "npm run test:unit && npm run test:integration",
@@ -127,16 +126,15 @@
"license": "MIT",
"private": false,
"publishConfig": {
- "access": "public",
- "registry": "https://source.soulcraft.com/api/packages/soulcraftlabs/npm/"
+ "access": "public"
},
- "homepage": "https://source.soulcraft.com/soulcraftlabs/open-brainy",
+ "homepage": "https://source.soulcraft.com/soulcraft/brainy",
"bugs": {
- "url": "https://source.soulcraft.com/soulcraftlabs/open-brainy/issues"
+ "url": "https://source.soulcraft.com/soulcraft/brainy/issues"
},
"repository": {
"type": "git",
- "url": "git+https://source.soulcraft.com/soulcraftlabs/open-brainy.git"
+ "url": "git+https://source.soulcraft.com/soulcraft/brainy.git"
},
"files": [
"dist/**/*.js",
diff --git a/scripts/buildEmbeddedPatterns.ts b/scripts/buildEmbeddedPatterns.ts
index c046df45..73e51224 100644
--- a/scripts/buildEmbeddedPatterns.ts
+++ b/scripts/buildEmbeddedPatterns.ts
@@ -10,7 +10,6 @@ import { TransformerEmbedding } from '../src/utils/embedding.js'
import * as fs from 'fs/promises'
import * as path from 'path'
import { fileURLToPath } from 'url'
-import { resolveDeterministicStamp } from './lib/deterministicStamp.js'
const __dirname = path.dirname(fileURLToPath(import.meta.url))
@@ -98,22 +97,13 @@ async function buildEmbeddedPatterns() {
// Convert to base64 for embedding in TypeScript
const uint8 = new Uint8Array(buffer)
const base64 = Buffer.from(uint8).toString('base64')
-
- // Deterministic stamp: derived from the git commit time of this
- // generator's inputs, never from wall-clock time — two builds of the
- // same source tree must produce byte-identical output.
- const outputPath = path.join(__dirname, '..', 'src', 'neural', 'embeddedPatterns.ts')
- const generatedStamp = resolveDeterministicStamp(
- [path.join(__dirname, 'buildEmbeddedPatterns.ts'), libraryPath],
- outputPath
- )
-
+
// Generate TypeScript file with everything embedded
const tsContent = `/**
* 🧠 BRAINY EMBEDDED PATTERNS
*
* AUTO-GENERATED - DO NOT EDIT
- * Generated: ${generatedStamp}
+ * Generated: ${new Date().toISOString()}
* Patterns: ${libraryData.patterns.length}
* Coverage: 94-98% of all queries
*
@@ -207,6 +197,7 @@ prodLog.info(\`🧠 Brainy Pattern Library loaded: \${EMBEDDED_PATTERNS.length}
`
// Write the TypeScript file
+ const outputPath = path.join(__dirname, '..', 'src', 'neural', 'embeddedPatterns.ts')
await fs.writeFile(outputPath, tsContent)
// Report statistics
diff --git a/scripts/buildTypeEmbeddings.ts b/scripts/buildTypeEmbeddings.ts
index 688d6ac1..61bcf238 100644
--- a/scripts/buildTypeEmbeddings.ts
+++ b/scripts/buildTypeEmbeddings.ts
@@ -11,7 +11,6 @@ import * as fs from 'fs/promises'
import * as path from 'path'
import { fileURLToPath } from 'url'
import { NounType, VerbType } from '../src/types/graphTypes.js'
-import { resolveDeterministicStamp } from './lib/deterministicStamp.js'
const __dirname = path.dirname(fileURLToPath(import.meta.url))
@@ -374,24 +373,12 @@ async function buildTypeEmbeddings() {
const uint8 = new Uint8Array(buffer)
const base64 = Buffer.from(uint8).toString('base64')
- // Deterministic stamp: derived from the git commit time of this
- // generator's inputs, never from wall-clock time — two builds of the
- // same source tree must produce byte-identical output.
- const outputPath = path.join(__dirname, '..', 'src', 'neural', 'embeddedTypeEmbeddings.ts')
- const generatedStamp = resolveDeterministicStamp(
- [
- path.join(__dirname, 'buildTypeEmbeddings.ts'),
- path.join(__dirname, '..', 'src', 'types', 'graphTypes.ts')
- ],
- outputPath
- )
-
// Generate TypeScript file
const tsContent = `/**
* 🧠 BRAINY EMBEDDED TYPE EMBEDDINGS
*
* AUTO-GENERATED - DO NOT EDIT
- * Generated: ${generatedStamp}
+ * Generated: ${new Date().toISOString()}
* Noun Types: ${nounTypes.length}
* Verb Types: ${verbTypes.length}
*
@@ -408,7 +395,7 @@ export const TYPE_METADATA = {
verbTypes: ${verbTypes.length},
totalTypes: ${totalTypes},
embeddingDimensions: ${embeddingDim},
- generatedAt: "${generatedStamp}",
+ generatedAt: "${new Date().toISOString()}",
sizeBytes: {
embeddings: ${buffer.byteLength},
base64: ${base64.length}
@@ -507,6 +494,7 @@ prodLog.info(\`🧠 Brainy Type Embeddings loaded: \${TYPE_METADATA.nounTypes} n
`
// Write the TypeScript file
+ const outputPath = path.join(__dirname, '..', 'src', 'neural', 'embeddedTypeEmbeddings.ts')
await fs.writeFile(outputPath, tsContent)
// Report statistics
diff --git a/scripts/emit-contract-manifest.mjs b/scripts/emit-contract-manifest.mjs
deleted file mode 100644
index be73d4ca..00000000
--- a/scripts/emit-contract-manifest.mjs
+++ /dev/null
@@ -1,128 +0,0 @@
-#!/usr/bin/env node
-/**
- * Emit this build's API-contract manifest to docs/api-contract.json.
- *
- * WHY IT IS GENERATED, NOT WRITTEN: a hand-kept list of doors drifts from the
- * code the first time somebody adds one. This reads the surface the build
- * actually exposes — the prototype's own methods and accessors, the exported
- * error classes, the `where` operator sets, the field-addressing vocabulary,
- * the health verdicts — so a diff between two engines' manifests is a diff
- * between two engines, never between two authors.
- *
- * Requirement marking (required / optional per door) is NOT derivable from the
- * surface — it is a commitment, recorded with the contract's owner rather than
- * here. This manifest carries the surface; the promise lives with the contract.
- *
- * Usage: node scripts/emit-contract-manifest.mjs [--check]
- * --check exits non-zero when the committed manifest is stale.
- */
-
-import { writeFileSync, readFileSync, existsSync } from 'node:fs'
-import { join, dirname } from 'node:path'
-import { fileURLToPath } from 'node:url'
-
-const ROOT = join(dirname(fileURLToPath(import.meta.url)), '..')
-const OUT = join(ROOT, 'docs', 'api-contract.json')
-
-const { Brainy } = await import(join(ROOT, 'dist', 'brainy.js'))
-const errorsModule = await import(join(ROOT, 'dist', 'errors', 'brainyError.js'))
-const versionModule = await import(join(ROOT, 'dist', 'utils', 'version.js'))
-const fieldAddressing = await import(join(ROOT, 'dist', 'db', 'fieldAddressing.js'))
-
-/** Every own method and accessor on the class's prototype, minus the private ones. */
-function surfaceOf(ctor) {
- const doors = []
- for (const name of Object.getOwnPropertyNames(ctor.prototype)) {
- if (name === 'constructor' || name.startsWith('_')) continue
- const descriptor = Object.getOwnPropertyDescriptor(ctor.prototype, name)
- if (!descriptor) continue
- if (typeof descriptor.value === 'function') {
- doors.push({ name, kind: 'method', arity: descriptor.value.length })
- } else if (descriptor.get) {
- doors.push({ name, kind: 'accessor' })
- }
- }
- return doors.sort((a, b) => a.name.localeCompare(b.name))
-}
-
-const errors = Object.entries(errorsModule)
- .filter(([name, value]) => typeof value === 'function' && /Error$/.test(name))
- .map(([name]) => name)
- .sort()
-
-// The operator sets, read from the engine's own refusal message so the
-// manifest can never disagree with the validator.
-const filterSource = readFileSync(join(ROOT, 'src', 'utils', 'metadataFilter.ts'), 'utf-8')
-const acceptedMatch = filterSource.match(/const VALUE_OPERATORS = new Set\(\[([\s\S]*?)\]\)/)
-if (!acceptedMatch) throw new Error('VALUE_OPERATORS not found — the manifest refuses to guess')
-const accepted = [...acceptedMatch[1].matchAll(/'([^']+)'/g)].map((m) => m[1]).sort()
-
-const indexSource = readFileSync(join(ROOT, 'src', 'utils', 'metadataIndex.ts'), 'utf-8')
-const refusedByIndex = ['endsWith', 'length', 'matches', 'startsWith'].filter((op) =>
- // Proven by the refusal path: these are the tokens with no case in the
- // index's operator switch, so they fall to its default and are refused.
- !new RegExp(`case '${op}':`).test(indexSource)
-)
-const servedOnIndex = accepted.filter((op) => !refusedByIndex.includes(op))
-
-const manifest = {
- contractVersion: versionModule.contractVersion(),
- engine: '@soulcraftlabs/brainy',
- compatibility: {
- minor:
- 'additive — a new optional door, a new served operator, a new error class; every existing implementation still conforms',
- major:
- 'breaking — a door removed, an answer narrowed, an ordering law changed, an optional door promoted to required, or an operator moved from served to refused'
- },
- doors: surfaceOf(Brainy),
- errors,
- operators: {
- accepted,
- servedOnIndexPath: servedOnIndex,
- refusedByIndexPath: refusedByIndex,
- combinators: ['allOf', 'anyOf', 'not']
- },
- fieldAddressing: {
- systemKeyPrefix: 'system.',
- systemEntityScalars: [...(fieldAddressing.SYSTEM_ENTITY_SCALARS ?? [])].sort(),
- systemRelationScalars: [...(fieldAddressing.SYSTEM_RELATION_SCALARS ?? [])].sort(),
- plumbingFields: [...(fieldAddressing.PLUMBING_FIELDS ?? [])].sort()
- },
- health: {
- verdicts: ['pass', 'warn', 'fail'],
- healKinds: ['none', 'repair', 'rebuild'],
- servingWithholdingInvariants: [
- 'index-initialized',
- 'durable-state-present',
- 'manifest-residency',
- 'replay-clean',
- 'strand-latch'
- ]
- }
-}
-
-const rendered = `${JSON.stringify(manifest, null, 2)}\n`
-
-if (process.argv.includes('--check')) {
- if (!existsSync(OUT)) {
- console.error(`docs/api-contract.json is missing — run: node scripts/emit-contract-manifest.mjs`)
- process.exit(1)
- }
- if (readFileSync(OUT, 'utf-8') !== rendered) {
- console.error(
- `docs/api-contract.json is STALE — the public surface changed. Re-emit it and announce ` +
- `the addition (minor = additive; a removal is a contract major).`
- )
- process.exit(1)
- }
- console.log(`docs/api-contract.json is current (${manifest.doors.length} doors, contract ${manifest.contractVersion}).`)
- process.exit(0)
-}
-
-writeFileSync(OUT, rendered)
-console.log(
- `Wrote docs/api-contract.json — contract ${manifest.contractVersion}, ` +
- `${manifest.doors.length} doors, ${manifest.errors.length} error classes, ` +
- `${manifest.operators.accepted.length} operators ` +
- `(${manifest.operators.refusedByIndexPath.length} refused by the index path).`
-)
diff --git a/scripts/gate/README.md b/scripts/gate/README.md
deleted file mode 100644
index 0a8afab0..00000000
--- a/scripts/gate/README.md
+++ /dev/null
@@ -1,85 +0,0 @@
-# Gate Guards
-
-Two standalone scripts that stand between a test/build gate and a false
-verdict: one refuses to let the gate start on a noisy machine, the other
-refuses to let a truncated or crashed vitest run be read as green.
-
-## Why these exist
-
-Both guards exist because of the 2026-08-13 lost-day ledger: a gate ran on
-a machine under load, and separately a vitest worker pool died mid-suite
-while still printing a plausible-looking summary line, and in both cases
-the bad result was trusted and acted on for the better part of a day before
-anyone noticed. Neither failure mode announces itself — a loaded machine
-still finishes and reports numbers, and a truncated test run still prints a
-`Test Files` / `Tests` line — so both guards check the evidence explicitly
-rather than trusting that a gate finishing means the gate was valid.
-
-## gate-preflight.sh
-
-Run before any gate lane starts. Exits 1 the moment the machine isn't
-gate-clean, with one `FATAL:` line per violation naming the exact offender
-(the pid and command, the path, the measured value). Prints one `OK:` line
-per check that passes. `WARNING:` lines mark checks that were skipped, not
-failures.
-
-Checks:
-
-| # | Check | Default threshold | Override |
-|---|-------|--------------------|----------|
-| a | 1-minute load average | `nproc / 2` | `GATE_MAX_LOAD` |
-| b | any non-allowlisted process over 50% of one core | 50% | `GATE_ALLOW_REGEX` (extra pattern matched against the process's args) |
-| c | cpu0 scaling governor must be `performance` | — | none (warns and skips if the sysfs path is absent) |
-| d | free space on `/` and `/tmp` | 10G each | `GATE_SKIP_DISK_CHECK=1` to skip entirely |
-
-The allowlist for check (b) is always: this script's own process tree
-(its ancestors and its direct child processes), `sshd`, `systemd`, and
-kernel threads (recognizable by args wrapped in brackets, e.g.
-`[kworker/0:1]`). `GATE_ALLOW_REGEX` extends it — it does not replace it.
-
-## vitest-verdict-check.sh
-
-Run after every vitest lane, against that lane's captured log. Fails
-loudly, quoting the exact line or string that tripped it, when the log's
-own summary can't be trusted:
-
-- no `Test Files` (or, in `--count-tests` mode, `Tests`) summary line is
- present at all
-- the parenthesized total in that line doesn't match what was expected
-- fewer files/tests are accounted for (passed + failed + skipped) than the
- total claims — a truncated run
-- the log contains `Unhandled Error` or `Timeout calling` anywhere — a dead
- worker pool, regardless of what the summary line claims
-
-```
-vitest-verdict-check.sh
-vitest-verdict-check.sh --count-tests
-```
-
-The first form checks `Test Files` for an exact match. The second checks
-`Tests` for a minimum (a floor, not an exact count, since the total number
-of individual tests moves more often than the number of test files).
-
-## Wiring into a CI lane
-
-```sh
-# Before any lane that will report a verdict:
-scripts/gate/gate-preflight.sh || exit 1
-
-# Run the suite, capturing its output:
-npx vitest run tests/unit 2>&1 | tee /tmp/unit.log
-
-# After every vitest lane, check the log against the actual file count:
-EXPECTED_FILES=$(ls tests/unit/**/*.test.ts | wc -l)
-scripts/gate/vitest-verdict-check.sh /tmp/unit.log "$EXPECTED_FILES" || exit 1
-```
-
-## Exit-code contract
-
-| Script | Exit 0 | Exit 1 |
-|--------|--------|--------|
-| `gate-preflight.sh` | machine is gate-clean | one or more `FATAL:` violations printed |
-| `vitest-verdict-check.sh` | log's summary is trustworthy and matches | usage error, missing/unreadable log, or one or more `FATAL:` violations printed |
-
-Non-zero from either script means: do not trust the gate that was about to
-run, or the result of the one that just ran.
diff --git a/scripts/gate/gate-preflight.sh b/scripts/gate/gate-preflight.sh
deleted file mode 100755
index c6208f49..00000000
--- a/scripts/gate/gate-preflight.sh
+++ /dev/null
@@ -1,206 +0,0 @@
-#!/bin/bash
-set -euo pipefail
-
-# Brainy Gate Preflight
-# Refuses to let a test/build gate run on a machine that isn't clean enough
-# to trust the numbers it produces. See scripts/gate/README.md for why (the
-# 2026-08-13 lost-day ledger).
-#
-# Checks: 1-minute load average, any non-allowlisted process pinning a core,
-# the cpu0 scaling governor, and free space on / and /tmp.
-#
-# Exit 0 and print one OK line per passing check when the machine is clean.
-# Exit 1 and print one FATAL line per violation, naming the offender, when
-# it is not.
-#
-# Known trap: a helper function whose last executed statement is a `while`
-# (or any command whose own exit status happens to be nonzero) hands that
-# status back as the function's return value. Called as a plain statement,
-# that silently kills this script under `set -e`. Every helper below ends
-# on an explicit `return 0` as its own statement, never on a loop or test.
-#
-# The same failure mode hides in plainer-looking lines too: `var=$(cmd)` is
-# a bare assignment, so `set -e` DOES treat a nonzero `cmd` (or, under
-# `pipefail`, a nonzero stage anywhere in `cmd`'s pipeline) as a failure of
-# that statement and kills the script right there — even mid-loop, even
-# when the "failure" is routine (a process that exited before a second
-# lookup, a path that doesn't exist). Every such assignment below is paired
-# with an explicit `|| var=""` fallback so a routine miss degrades to an
-# empty value instead of an exit.
-
-VIOLATIONS=0
-ANCESTOR_PIDS=""
-
-fatal() {
- echo "FATAL: $1"
- VIOLATIONS=$((VIOLATIONS + 1))
-}
-
-ok() {
- echo "OK: $1"
-}
-
-# Walks this process's parent chain up to pid 1, then takes one snapshot of
-# its direct children (the ps/read pipeline in check_processes), and
-# records both in ANCESTOR_PIDS — so the process-scan below can recognize
-# its own tree (the shell/terminal/session that launched it, plus its own
-# helper commands) instead of flagging it. Children are captured once, up
-# front, rather than re-queried per row later, so a helper command that has
-# already exited by the time it's looked up can't be mistaken for a miss.
-build_ancestor_pids() {
- local pid="$$"
- local ppid child
- ANCESTOR_PIDS=" $pid "
- while [ "$pid" != "1" ]; do
- ppid=$(ps -o ppid= -p "$pid" 2>/dev/null | tr -d ' ') || ppid=""
- if [ -z "$ppid" ]; then
- break
- fi
- ANCESTOR_PIDS="${ANCESTOR_PIDS}${ppid} "
- pid="$ppid"
- done
-
- while IFS= read -r child; do
- [ -z "$child" ] && continue
- ANCESTOR_PIDS="${ANCESTOR_PIDS}${child} "
- done < <(ps --ppid "$$" -o pid= 2>/dev/null || true)
-
- return 0
-}
-
-# (a) 1-minute load average vs. threshold (default: nproc / 2).
-check_load() {
- local max_load="${GATE_MAX_LOAD:-}"
- if [ -z "$max_load" ]; then
- max_load=$(( $(nproc) / 2 ))
- if [ "$max_load" -lt 1 ]; then
- max_load=1
- fi
- fi
-
- local load_1m
- load_1m=$(cut -d' ' -f1 /proc/loadavg)
-
- if awk -v l="$load_1m" -v m="$max_load" 'BEGIN { exit !(l > m) }'; then
- fatal "1-minute load average ${load_1m} exceeds threshold ${max_load} (GATE_MAX_LOAD=${max_load})"
- else
- ok "1-minute load average ${load_1m} is within threshold ${max_load}"
- fi
- return 0
-}
-
-# (b) any process outside the allowlist pinning more than half a core.
-# Parsed with `read` into named fields, not an awk/cut chain — a fixed-column
-# awk/cut split on `ps` output duplicated fields the first time this was
-# tried, because process args vary in word count. `read` with a fixed list
-# of variables dumps everything left over into the last one (args), which
-# handles that correctly.
-check_processes() {
- local max_pcpu=50
- local extra_regex="${GATE_ALLOW_REGEX:-}"
- local violation_found=0
- local line pcpu pid args pcpu_int
-
- while IFS= read -r line; do
- [ -z "$line" ] && continue
- read -r pcpu pid args <<< "$line"
-
- # Kernel threads report their comm in brackets, e.g. "[kworker/0:1]".
- case "$args" in
- \[*\]) continue ;;
- esac
-
- # This script's own tree: its ancestors (shell, terminal, session) and
- # its direct children, both captured once by build_ancestor_pids.
- case " $ANCESTOR_PIDS " in
- *" $pid "*) continue ;;
- esac
-
- case "$args" in
- *sshd*|*systemd*) continue ;;
- esac
-
- if [ -n "$extra_regex" ] && [[ "$args" =~ $extra_regex ]]; then
- continue
- fi
-
- pcpu_int="${pcpu%.*}"
- if [ -z "$pcpu_int" ]; then
- pcpu_int=0
- fi
- if [ "$pcpu_int" -gt "$max_pcpu" ]; then
- fatal "pid ${pid} ('${args}') is using ${pcpu}% of one core"
- violation_found=1
- fi
- done < <(ps -eo pcpu,pid,args --sort=-pcpu | tail -n +2)
-
- if [ "$violation_found" -eq 0 ]; then
- ok "no process outside the allowlist exceeds ${max_pcpu}% of one core"
- fi
- return 0
-}
-
-# (c) cpu0 scaling governor must be "performance". Skipped with a warning
-# (not a violation) when the sysfs path doesn't exist on this machine.
-check_governor() {
- local gov_path="/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor"
- if [ ! -r "$gov_path" ]; then
- echo "WARNING: ${gov_path} not present; skipping governor check"
- return 0
- fi
-
- local governor
- governor=$(cat "$gov_path" 2>/dev/null) || governor=""
- if [ "$governor" != "performance" ]; then
- fatal "cpu0 governor is '${governor}', not 'performance'"
- else
- ok "cpu0 governor is 'performance'"
- fi
- return 0
-}
-
-# (d) free-space floors on / and /tmp (default 10G each). Skip entirely via
-# GATE_SKIP_DISK_CHECK=1.
-check_disk() {
- if [ "${GATE_SKIP_DISK_CHECK:-0}" = "1" ]; then
- echo "WARNING: disk free-space check skipped (GATE_SKIP_DISK_CHECK=1)"
- return 0
- fi
-
- local floor_gb=10
- local floor_bytes=$((floor_gb * 1024 * 1024 * 1024))
- local path avail_bytes avail_gb
-
- for path in / /tmp; do
- avail_bytes=$(df --output=avail -B1 "$path" 2>/dev/null | tail -n 1 | tr -d ' ') || avail_bytes=""
- if [ -z "$avail_bytes" ]; then
- echo "WARNING: could not determine free space on ${path}; skipping"
- continue
- fi
- if [ "$avail_bytes" -lt "$floor_bytes" ]; then
- avail_gb=$((avail_bytes / 1024 / 1024 / 1024))
- fatal "${path} has only ${avail_gb}G free, below the ${floor_gb}G floor"
- else
- ok "${path} has enough free space (floor ${floor_gb}G)"
- fi
- done
- return 0
-}
-
-echo "Brainy gate preflight"
-echo "----------------------"
-
-build_ancestor_pids
-check_load
-check_processes
-check_governor
-check_disk
-
-echo "----------------------"
-if [ "$VIOLATIONS" -gt 0 ]; then
- echo "FATAL: gate preflight failed with ${VIOLATIONS} violation(s) — machine is not gate-clean"
- exit 1
-fi
-
-echo "gate preflight passed — machine is gate-clean"
-exit 0
diff --git a/scripts/gate/vitest-verdict-check.sh b/scripts/gate/vitest-verdict-check.sh
deleted file mode 100755
index 36243a1d..00000000
--- a/scripts/gate/vitest-verdict-check.sh
+++ /dev/null
@@ -1,158 +0,0 @@
-#!/bin/bash
-set -euo pipefail
-
-# Brainy Vitest Verdict Check
-# Confirms a vitest run's own summary line is trustworthy before anything
-# downstream treats a green run as green. See scripts/gate/README.md for why
-# (the 2026-08-13 lost-day ledger).
-#
-# Usage:
-# vitest-verdict-check.sh
-# vitest-verdict-check.sh --count-tests
-#
-# The first form checks the "Test Files" summary line's total against an
-# exact expected count. The second checks the "Tests" summary line's total
-# against a minimum. Both also fail on any sign the worker pool died
-# mid-run, whether or not a summary line still made it into the log.
-#
-# Exit 0 and print one OK line per passing check when the log is clean.
-# Exit 1 and print one FATAL line per violation, quoting the exact line or
-# string that tripped it, when it is not.
-#
-# Known trap (shared with gate-preflight.sh): every helper below ends on an
-# explicit `return 0` as its own statement, never on a loop or test, so a
-# helper's last command can never hand its own exit status back as the
-# function's under `set -e`. The same applies to `var=$(cmd)` assignments
-# mid-helper: a bare assignment IS checked by `set -e`, so a `grep` that
-# legitimately finds nothing (exit 1) would otherwise kill the script
-# instead of just leaving the variable empty — every such assignment below
-# is paired with an explicit `|| true` inside the substitution.
-
-usage() {
- echo "Usage: $0 "
- echo " $0 --count-tests "
- exit 1
-}
-
-MODE="files"
-if [ "${1:-}" = "--count-tests" ]; then
- MODE="tests"
- shift
-fi
-
-LOG_FILE="${1:-}"
-THRESHOLD="${2:-}"
-
-if [ -z "$LOG_FILE" ] || [ -z "$THRESHOLD" ]; then
- usage
-fi
-
-if [ ! -f "$LOG_FILE" ]; then
- echo "FATAL: log file '${LOG_FILE}' does not exist"
- exit 1
-fi
-
-if ! [[ "$THRESHOLD" =~ ^[0-9]+$ ]]; then
- echo "FATAL: threshold '${THRESHOLD}' is not a non-negative integer"
- exit 1
-fi
-
-VIOLATIONS=0
-
-fatal() {
- echo "FATAL: $1"
- VIOLATIONS=$((VIOLATIONS + 1))
-}
-
-ok() {
- echo "OK: $1"
-}
-
-# Vitest colorizes its summary with ANSI escapes; strip them before parsing
-# anything, or the color codes end up embedded in the fields we grep for.
-CLEAN_LOG="$(sed 's/\x1b\[[0-9;]*m//g' "$LOG_FILE")"
-
-# Worker-pool death: if either string appears, the run's own summary line —
-# even if present and even if its numbers look fine — cannot be trusted,
-# because the process died mid-suite and vitest's own accounting is what
-# died with it.
-check_worker_death() {
- if echo "$CLEAN_LOG" | grep -q "Unhandled Error"; then
- fatal "log contains 'Unhandled Error' — worker pool died mid-run"
- fi
- if echo "$CLEAN_LOG" | grep -q "Timeout calling"; then
- fatal "log contains 'Timeout calling' — worker pool died mid-run"
- fi
- return 0
-}
-
-# Shared shape between the "Test Files" and "Tests" summary lines:
-#