UAI File Handoff for Model Ecologies
This release adds a repository-local .uai memory package so a future human, coding agent, or audit session can understand what was changed, which source reports were used, what remains uncertain, and what boundaries must not be crossed.
The memory package mirrors the practical shape of a Project Handoff: current truth in short-term memory, durable source pointers in long-term memory, source-intake dispositions in a ledger, architecture notes, safety constraints, coding standards, test plans, and a receiver brief.
Why this matters for Cognivirus.com
The site studies adaptive ecologies. The site itself should not become an undocumented ecology. New reports should not float in the repository as unreviewed influence. They should be scanned, summarized, preserved, dispositioned, and linked to the pages they changed.
Files added or expanded
.uai/file-handoff.uai.uai/intake-outcome-ledger.uai.uai/short-term-memory.uai.uai/long-term-memory.uai.uai/source-report-corpus.uai.uai/memory/source-reports/*.uai.uai/receiver-brief.uai.uai/next-recursive-prompt.uai.uai/exports/llms.uai.uai/exports/llms-full.uai
Operational boundary
The .uai files are local handoff memory. They do not install a runtime, write to a hosted site, certify the research, or synchronize with an external memory system. They are review artifacts for continuity.