PROCESS EVIDENCE
Memory changes the next action after the writer is gone.
The actual production controller stores the earlier observation through the Sibyl SDK, acknowledges its durable write, and is terminated. A separate process reads the native store. The observation’s UUID and payload survive.
| Evidence available | First bin | Additional counts on selected truth |
|---|---|---|
| Sibyl history, fresh process | B | 1 |
| Earlier history removed | A | 2 |
| Equivalent JSON history | B | 1 |
| Complete external count archive | B | 1 |
All quantities in this test are disclosed synthetic responses. The solver receives only the requested bin’s response, after selecting that bin. Removing history preserves the opening, transfer model and solver. Substitution restores the advantage: the evidence proves dependence on retained observations, not exclusive algorithmic capability of the Sibyl SDK.
Inspect fresh run records
Forced termination and fresh SDK reader · Full four-arm controller traces · Separate fresh-controller MCP protocol evidence
Storage locations
The default local database is .countback/memory.db, configurable through COUNTBACK_DB. Countback uses Sibyl WARM entities for case data, COLD events for the authoritative ordered journal, and HOT state for the journal head and task projection. Reconstruction replays validated evidence; it does not trust a cached answer.