docs: reconcile layered-memory contracts and docs index #110
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/layered-memory-reconcile"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #109 (
docs/layered-memory-authority-lifecycle, merged). The newcontract is accurate, but it landed unwired: its
system_opsrecord-classlist disagreed with
layered-memory-fabric.md, and none of the newer plans werediscoverable from the docs index.
Changes
with an accurate curated-index description, and add the five missing plan rows
(
COLIBRI-SIMPLIFICATION,JEV-DECISION-GATE,LAYERED-MEMORY-AUTHORITY-LIFECYCLE,PATH-ENV-IDENTITY-UNIFICATION,SYSTEM1-WIKI-INVENTORY).system_opsbullet to the canonicalsix record classes in the lifecycle contract (was a divergent
“freshness, approvals, conflicts, …” list) and link it.
system_brainauthority is out of scope and remains governed byshared-memory-architecture; record co-verification.system_skills/system_brain/system_opsmemory planes.okfsemantics and clarify thatstale_afterand
decision_stateare informational annotations (no gate enforces them).Gates (on the branch)
check-format.sh— passwiki-lint --strict— clean (761 pass / 0 fail; +10 from the new terms/links)check-dates.sh --strict— cleancheck-okf.sh— advisory exit 0Targeted
last_verifiedrefresh on the five edited files only — no bulkrefresh (cf. open #105, which is such a bulk refresh).
Closes nothing; prepares the ground for the #104/#105 disposition discussion.