docs(soul): design recipe placeholders backed by vault capability classes #237
Loading…
Reference in a new issue
No description provided.
Delete branch "clawdie/docs/layered-soul-recipe"
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?
Add a design note and a spec-check pack for turning layered-soul guardrails
into Agent Vault placeholders.
guardrail->class table, an additive clawdie.layered-soul.v1 recipe schema
(requires/provides, ph./cap./gen. ids, registry membership), the vault
report shape with redaction rules, and the class-aware decision table
30-row class-aware matrix B, five recipe fixtures, a mutant-table negative
control, and a sentinel proving a blocked recipe never invokes install()
one label and was unstable across runs (confidence 0.19-0.57), so it is
treated as no evidence; the class-aware matrix agreed on write-only
requirements (0.83/0.88) and was overruled on circular custody, where the
deterministic table wins (refuse, not blocked)
Design only: no live vault, Tarsnap, jail, or ZFS operation. The replayer is a
spec check, not production binding.
Gates: ci-checks.sh PASS; check-okf.sh --changed clean; wiki-lint --strict 583
PASS; leak-guard clean; replay PASS.
Pull request closed