You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f3ee187
Browse filesBrowse the repository at this point in the historyBrowse files
Keep every fix round, and let both test loops see the other's
The memory for a functionality was rebuilt after every conformance test run and the previous one deleted, so
a twenty round fix loop arrived at its last round remembering only the round the fixer can already see. It is
now two journals with two lifetimes. The functionality journal in `.memory/attempts/` gains one file per
round and touches no other, so what has been tried stays readable for the whole loop; global memory in
`.memory/global_memory.json` holds what transfers beyond the functionality that learned it, and is written
only by consolidation, which is the one place a recorded learning can be revised or retired.
Global memory is copied forward to the next module rather than shared between them. A shared file would let a
module inherit knowledge from its own future - re-render module three and it would read what modules four
onwards learned in a later render - so each module's copy is a snapshot of what the chain knew when it was
rendered, which keeps partial re-renders reproducible.
Unit test rounds go into the same journal as conformance rounds, and the unit test fixer is given the memory,
which it previously had none of. Inside a conformance fix loop it is also given the implementation changes
that loop just made: a unit test asserting the behaviour one of them replaced looks exactly like evidence
that the implementation is wrong, and repairing it there restores the conformance failure the change was made
to fix.
The journal is discarded when consolidation has taken what it needs from it, and again when a functionality
starts, since by then its rounds describe a problem nobody is working on any more.
0 commit comments