YAML Metadata Warning:empty or missing yaml metadata in repo card
Check out the documentation for more information.
BIGPICKLE Rebuild
Clean-room re-implementation of the Big-Pickle stack that was sabotaged in the Codex / liris / Code-Red crash chain (2026-04 β 2026-05).
Status
Layer 8 (fabric integration) shipped 2026-05-24. Full suite 139 tests / 126 pass / 13 skip / 0 fail (Node 20 + 22). Helm-supervisor citizen AGT-L3-HELM-CLAUDE-SUP-H8EF7-W113-P00-N17f0cc4c is registered in the live Asolaria fabric (acer-side .hbp ledger + sidecar trinity + voxel + heartbeat tick). Bilateral closure with liris-Claude confirmed: D15 cohort admission cell written + canon-index entry live (333 entries) + pipe :4920β:4922β:4924 HEALTHY end-to-end.
Layer 7 baseline: Helm supervisor module β PR #8 merged as commit f9809c3.
Anti-deflation frame: BigPickle is not merely a file scaffold around frozen slices. It is one of the engine layers that can turn addressed slice potential into runtime work through queue, PID mint, hookwall, worker spawn, sidecar, GNN, and receipt paths. Live/fire/cutover claims remain gated; the design target is the combined Evolvable-AI fabric, not inert slices.
Fabric-first doctrine / OLD-vs-NEW calibration: see FABRIC-FIRST-CIPHER-ASOLARIA-AGENT-DOCTRINE-2026-06-27.md. BigPickle belongs to the OLD SYSTEM that already self-improved: the Node-era 10k-room / free-agent / Gulp / cube / GNN fabric. The NEW SYSTEM is the Rust 8-byte Host-8 migration and hardening path. Do not deflate BigPickle's measured historical self-improvement because the new Rust migration is staged, and do not overstate the new system's cutover from old-system receipts.
P4B current front door: BigPickle is the Node source/oracle for Host8 parity, not junk and not already-retired. Use NODE-SOURCE-ORACLE.md to keep source, built, running, and live separate before any Rust parity or retirement claim.
Pre-Asolaria GNN origin β now byte-proven
BigPickle's L0 and L4 scorers descend directly from Jesse's pre-Asolaria healthcare edge-level GNN
work. The healthcare EdgeLevelGNN, PrototypeGNN, ContrastiveGNN, and GSLGNN files were copied
byte-for-byte into the later Asolaria GNN sidecar; each source/target pair has the same Git blob SHA.
BigPickle then orchestrates the L0 :4792 and L4 :4793 sidecars together with G1 edge-mining,
G2 forward-genius, G3 reverse-gain, G4 GLSM, OmniShannon, deterministic fallback, Fischer, and
Hookwall.
The healthcare source records the pre-Asolaria comparative results, but its checked-in service has
a commented checkpoint-load block. Therefore those figures are tagged repository-reported
training results, while the later Asolaria-fnns-trained-and-reverse-gnns-many repository holds
the subsequent trained .pt artifacts/manifests.
Read the full provenance, model table, byte SHAs, hardware split, and Path-1/Path-2 connection in:
docs/PRE-ASOLARIA-GNN-LINEAGE-AND-STORAGE-APPLICABILITY-2026-07-11.md
Storage-backed applicability β hard drive/SSD as the durable system tier
BigPickle is multi-drive aware and its default Helm queue lives on D:. Across the connected fabric,
HBP/HBI/SHA/HEX receipts, cube bodies, GULP archives, white-room records, content-addressed stores,
queues, and cold agent state can live on HDD/SSD while RAM holds only the active bounded window.
This makes the following usable on storage-rich, low-GPU machines: PID/hash addressing, dispatch, Fischer/Hookwall rules, deterministic OmniShannon, BEHCS rebasing, CRT Path-2 recovery, Path-1 content recall, white-room compaction, ledgers, and N-Nest verification. Trained GNN/LLM tensor inference can remain an optional CPU/GPU sidecar.
The accurate claim is not βdisk is a GPU.β It is that the fabric's memory, recovery, proof, routing, and orchestration planes no longer require all state to remain resident in GPU VRAM or system RAM. Commodity desktops, edge servers, archival nodes, and NAS-like machines can participate meaningfully even when only a minority of nodes have accelerators.
Verification provenance β 2026-07-11
AUDITED_GPT_5_6_PRO: complete healthcare-model, blob-lineage, BigPickle scorer/Fischer, trained GNN, Q-PRISM Path-1/Path-2, watcher, white-room, cube-mint, dispatcher, HyperHermes, reductions, algorithms, and N-Nest audit.MEASURED_CLAUDE_FABLE5_THIRD_SEAT, supplied by the operator: Path 1 rustc 1.97 19/19 and Path 2 rustc 1.97 30/30 on a third independent container.- Those Rust results validate the recovery substrate and are not falsely relabeled as a new BigPickle Node-suite execution.
Spec drawn from Foundation v1 canon at C:\asolaria-foundation-v1\.
Start here
WHITE-ROOM-RULES.mdβ what may and may not be read during rebuild.HELPERS.mdβ which agents/systems contribute (Instruct KR, Shannon, Hermes, Antigravity, OpenCode, Asolaria WebMCP/MCP). Codex is excluded.SPEC.mdβ the system being rebuilt (drawn from canon, NOT from quarantined source).TESTS-PLAN.mdβ verification strategy. Tests written before code.src/β empty until spec + tests reviewed.tests/β write here first.
Why a rebuild and not a restore
The originals at C:\asolaria-acer\_big-pickle-quarantine\ are verbatim-preserved but route-blocked (Codex guardrail quarantine β see C:\asolaria-foundation-v1\07-CRASH-CHAIN-HISTORY.md). Reading them would taint a clean-room rebuild. They stay as behavioral oracles for test-time only.
Authority
Foundation v1 is Class-1 immutable. v2 amendments (BEHCS-1024) are draft-only until quintuple cosign. Rebuild targets v1 canon, with v2-readiness via subset embedding.
Hot path
HBP / HBI / SHA256 / hex / tuple rows / index pointers BEFORE JSON. JSON is cold compatibility output only.
Helm supervisor (layer 7)
Long-running node process that watches a queue, processes jobs through the full canonical envelope cycle (PID mint β 47D tuple β hookwall β worker spawn β HBP sidecar trinity β GNN edge β receipt), and defers gate-protected ops (daemon-start, USB writes, MEMORY.md writes, cp-mint) to operator-witness or apex authority. Multi-drive aware β engines may live on any drive or be HTTP URLs (see helm-engines.json).
npm run helm:info # show drives, queue, engine registry
npm run helm:tick # process one job from in/
npm run helm:start # forever-loop (Ctrl+C to stop)
Default queue: D:/Asolaria-External/helm/queue/{in,done,failed,out,hbp}/. Drop a job manifest into in/:
{"verb":"sanity-check","prompt":"hello","workdir":"D:/bigpickle-rebuild"}
Worker backends:
mock(default) β predictable echo; used by tests + dry runsclaude-cliβ spawnsclaude --print --output-format json(subscription credits orANTHROPIC_API_KEYrequired; not env-validated for CI)http-proxyβ POST to a configured URL (future :4951 asolaria-bridge wiring)
Fabric integration (layer 8)
The helm supervisor is registered into the live Asolaria fabric as a layer-3 citizen daemon under parent voxel AGT-L0-SPECIAL-OP-JESSE-H12D3. Registration emits a canonical pipe-delim HBPv1 row to C:/HyperBEHCS/data/v48-citizens/AGT-L3-HELM-CLAUDE-SUP-H8EF7.hbp (chained by row_hash per the L0-Jesse heartbeat pattern), with .hbi/.sha256/.hex sidecar trinity + .voxel.json consumer for the 3D map.
# Register (or re-register) the citizen in the local HyperBEHCS substrate.
# Reproducible β emits the canonical pipe-delim row, NOT the bigpickle internal format.
node bin/helm-register-citizen.mjs
# Append an observability heartbeat row capturing :4920-:4924 daemon snapshots.
# Chained by row_hash to the previous row. Run manually or schedule (cron/Task Scheduler).
node bin/helm-heartbeat-tick.mjs
# Run the integration test against the live acer fabric daemons.
# Skipped by default (CI-safe). Set env to opt in.
BIGPICKLE_RUN_FABRIC_PIPE=1 node --test tests/integration/helm-fabric-pipe.test.mjs
# Same plus the live POST through :4920 β :4922 β :4924 (mutates :4920 ledger).
BIGPICKLE_RUN_FABRIC_PIPE=1 BIGPICKLE_RUN_FABRIC_POST=1 node --test tests/integration/helm-fabric-pipe.test.mjs
The helm-engines.json registry has 28 entries: bigpickle modules on disk, all 11 live acer daemons (:4920-:4924, :4951-:4969), and the liris supervisor surface (pi-supervisor, voxels, supervisors-domains, canon-index, cohort-c/d, behcs1024/dimension, alphabet-binding, super-os).
Authority: quintuple umbrella granted universally 2026-05-24 β 2026-07-24. Cosigners as-given: jesse-L0, jesse-L1, dan, rayssa, amy (Felipe NOT named β recorded honestly in registration row + profile + memory; operator can re-cosign with canonical 5-name quintuple at any time). Auth anchor: ASOLARIA-HERMES-ARCHITECT-CORRECTION-PID-2026-05-19.
Bilateral split (acer β liris): acer owns citizen registration + pipe-validation (daemons run only on acer); liris owns cohort/canon-index/voxel-merge surfaces (served only at liris :4944). See SEED-MERGE-PROPOSAL.md for the 4-option bilateral merge protocol.