You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
4 months ago | |
|---|---|---|
| .. | ||
| CONTINUE-docs-corpus.md | 4 months ago | |
| README.md | 4 months ago | |
| active-architecture-snapshot-2026-05.md | 4 months ago | |
| arts-audit-2026-06.md | 4 months ago | |
| handoffs-2026-05.md | 4 months ago | |
README.md
Process docs
Ephemeral, time-stamped artifacts — not part of the permanent reference corpus. Session hand-offs, audits, migration plans, "continue next time" notes.
They are kept for history and traceability only. The source of truth for how the
framework works lives in the reference / architecture / canon docs (the layer
READMEs, active_architecture.md, GUIA_IMPLEMENTACION_SEMAUIX.md, the RFCs),
never here.
Rule of thumb: anything written as "as of <date>", "handoff", "estado actual",
or "continue next session" belongs here, not inside a reference doc. A reference
doc should read as if it were always true.
Contents
handoffs-2026-05.md— session hand-off blocks that used to be embedded inline in the layer READMEs and architecture docs. Pulled out so the reference docs stay timeless.arts-audit-2026-06.md— audit of thearts/artifacts (ex-sium): contract / barrel / diagnostics findings, what was fixed and what was deliberately left.