Problem
Long-running coding or content projects fail when the next agent cannot tell which notes are current, which files are evidence, which tasks are pending, and which constraints are protected. Flat memory files become stale. Chat history disappears. The next agent restarts by guessing.
ModelBreeder.com uses a file-backed memory pattern instead of a database. Typed .uai files carry current operating truth. /docs carries durable source reports. Active handoff buckets carry new material waiting for review.
Current package choice
This package uses UAIX Agent File Handoff only. It does not use a memory wiki. The reason is simple: all original reports are already preserved in /docs, and curated pages promote selected ideas into the public curriculum.
Intake lifecycle
| Step | Action | Evidence |
|---|---|---|
| scan | list Content and Improvement buckets | bucket count and filenames |
| inspect | read safe files without executing them | review notes |
| decide | incorporated, rejected, preserved, or kept active | ledger entry |
| use | update content, code, tests, docs, or memory | changed files |
| clear | remove processed active file or record keep-active reason | ledger outcome |
PROCEDURE process_file_handoff()
files <- SCAN(["agent-file-handoff/Content", "agent-file-handoff/Improvement"])
FOR each file IN files
IF file.is_placeholder
CONTINUE
END IF
inspection <- SAFE_INSPECT(file)
outcome <- DECIDE_DISPOSITION(inspection)
IF outcome == "incorporated"
APPLY_TO_PROJECT(file)
ELSE IF outcome == "preserved-to-durable-memory"
COPY_TO_APPROVED_DURABLE_TARGET(file)
END IF
APPEND_LEDGER(file, outcome, proof_of_use)
REMOVE_OR_KEEP_ACTIVE(file, outcome)
END FOR
END PROCEDURECode beading connection
Code beading treats work items as discrete, linked units instead of unstructured notes. File Handoff does the same for incoming files: each item has a disposition and proof trail. The result is a project that can survive short agent sessions without pretending one context window is permanent memory.
Operational rule
Do not put long essays into hot .uai memory. Keep hot files concise and route to /docs, content pages, manifests, or archives when more detail is needed.
Source reports used for this guide
These reports are preserved verbatim in the site archive. The guide above is an editorial synthesis and may narrow, qualify, or reorganize claims from the source material.