Version localizada en revision
Esta pagina aun no esta disponible como norma localizada revisada. Use la fuente inglesa autoritativa para lenguaje normativo, interpretacion de esquemas, obligaciones de implementacion y limites de soporte.
Cómo usar esta página
Use this guide to record research-harness outcomes, memory-mediated self-learning, evidence ledgers, reproducibility notes, static completeness sweeps, and .uai memory strategy without making UAIX a runtime.
Research Harnesses
Turn harness lessons into reviewed memory
Use this guide to capture memory-mediated self-learning, evidence ledgers, claim ledgers, reproducibility notes, static completeness sweeps, and state hygiene without making UAIX the runtime.
Runtime
Harnesses own execution
Tool calls, retries, approvals, traces, scratchpads, and checkpointers stay in the research harness or runtime layer.
Memory
UAIX keeps reviewed state
Only accepted facts, evidence pointers, claim status, tests, blockers, and next actions belong in hot .uai memory.
Review
No evidence, no claim
Source leads become current guidance only after page copy, machine records, tests, roadmap state, and support boundaries agree.
Use beside
Agentic Harness StrategiesBroader runtime-versus-evidence split.Memoria de IACompact reviewed memory.Traspaso de proyectoDurable project state after the run.Context BudgetHot and cold memory placement.Memory FirewallQuarantine imported memory before promotion.ValidadorValidate candidate UAI-1 packets before claims.
A research-harness result becomes UAIX memory only after review, redaction, provenance check, conflict check, and a named promotion target.Use this line when reviewing harness-derived guidance, reports, or generated memory.