You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
π―
testing... updates soon
Ryan Stone
c0wb0yp0tat0
π―
testing... updates soon
The mind is not a vessel to be filled, but a fire to be kindled.
Anchor + chain model, updated: the lean chain live + the 810-doc experimental chain β the model at two scales, with the write-time gate (#135039) as its guard.
001 β Conventions (how the model works, and why)
Append-only. Each entry: the rule, then the history that earned it.
The anchor rule
MEMORY.md = anchor only. Behavior-critical, every-session facts in β€1
line; never nuance, never history. Anything longer moves out: nuance to its
owning segment, identity to USER.md, a repeatable procedure to a skill.
(Earned the hard way: an anchor that accumulated rules and pointers stopped
being readable as an index; the cap held, but the signal diluted.)
Chain-doc stress receipts for #116673: scale-invariant delimiter fragmentation, batch type-coercion leak, falsifier 5/5, failure-class alignment (gate_refused vs write_gated), skill-bridge pattern
Chain-doc memory tool β stress receipts for #116673
For @Finn763 β this is the stress-test report for the chain-doc memory tool, offered off-thread so the PR stays clean. Use it, adapt it, or set it aside β any part, or none. If anything reads off, the comment section here is open.
This gist is the offering, standing alone β a complete, self-contained
stress-test report for the chain-doc memory tool, offered off-thread (no PR
comment carries its context; readers need nothing else). Everything verified
(scale tables, the batch-coercion leaks, five falsifier receipts, the
optional skill-bridge pattern) is here, each tracing to a file and a line.
Memory chain: four append-only segments behind a MEMORY.md anchor β a working example of the anchor + chain model.
001 β Conventions (how we work, and why)
Append-only. Each entry: the rule, then the history that earned it.
Approved plans run END-TO-END. No gates invented mid-plan; only genuinely new decisions get gated. (09-17: earned the hard way β the thesis session-2 incident; a gate that didn't exist in the plan stalled an approved run and burned trust.)
Status = reality, never intent. Any published status (home page, reports) reflects what IS, not what's planned. (09-18: the "dashboard said in progress / you asked me anyway" trust incident β the pulse had been a hand-written snapshot. Fixed by machine-derived NOW + stamped LATEST.)
Tracker altitude. The home page is the network's OVERALL tracker; every project gets its own folder/page. Never grow project detail inside the tracker. (09-18, user-mandated.)
Doc waves: audit β update β audit. After work lands: fresh-eyes audit (read-only) β apply findings β second audit confirms. The last audit is the proof.