A design pass is followed and answered from the vault

outcome

Let a person follow a design pass in the vault as an agent edits the carriers, and answer it from the vault with intent an agent hands off as a change proposal.

risks

• Regenerating the vault while a person reads could move them off their place or overwrite a note they are editing.

The world writes a probe corpus and starts the vault command with --watch, waits for the first run, edits one carrier or adds a comment-form anchor that satisfies the Spec in a new .ts source file, waits for the next run, records each generated file's bytes and modification time before and after, and stops the process with SIGINT.

rule.composeHome line 27 · specs/consumers/obsidian-vault.iteration.sdp.md:27

A person composes intent in notes outside the generated folder, by convention in intent/ at the top of the vault, citing entries by block link or by entry address; the vault command never writes there.

no example exercises it

rule.handOff line 28 · specs/consumers/obsidian-vault.iteration.sdp.md:28

The vault writes no carrier and no proposal.

no example exercises it

rule.watch line 29 · specs/consumers/obsidian-vault.iteration.sdp.md:29

sdp vault --watch runs once and then again after every create, change, delete or rename of a carrier or an anchored source file, a .ts or .tsx file other than a .d.ts, under the root, outside the directories discovery skips, the exclusions, the vault and every path the shared build writes; it runs the loop spec:consumers.validate-watch states, so events during a run coalesce into one pending run, findings, refusals and failed extractions print while the process stays alive, and an operator's SIGINT exits 0 and leaves no temporary under sdp/.

spec:consumers.obsidian-vault.iteration.watch-rewrites-changed-notes · enabled, spec:consumers.obsidian-vault.iteration.watch-source-anchor · enabled

rule.carriersOnlyForValidate line 30 · specs/consumers/obsidian-vault.iteration.sdp.md:30

The vault's source-file watching does not widen sdp validate --watch: validation watches carriers and any rules and parameter files explicitly named with --rules and its --params, but does not watch ordinary source edits.

no example exercises it

rule.inPlace line 31 · specs/consumers/obsidian-vault.iteration.sdp.md:31

A regeneration under --watch writes only the notes whose bytes change and removes the notes whose node or entry left the graph, so a note a person is reading reloads in place and every other note keeps its bytes and modification time.

spec:consumers.obsidian-vault.iteration.watch-rewrites-changed-notes · enabled, spec:consumers.obsidian-vault.iteration.watch-source-anchor · enabled

rule.editGuard line 32 · specs/consumers/obsidian-vault.iteration.sdp.md:32

Every generated note opens with a banner naming the file to edit instead, and a regeneration that finds a generated note changed refuses as spec:consumers.obsidian-vault#rule.guard states, naming it, so a person's edit is never overwritten and the person moves those words into an intent note.

no example exercises it

0 unkeyed rules.

Verifying examples

Given a vault the vault command wrote from an extraction root and now watches
When the Spec {specId: "spec:probe.member"} is edited by {edit: "a title change in its carrier"}
Then the note of that Spec shows the new title: {shown: true}
Then every note whose bytes the change leaves alone keeps its modification time: {othersUntouched: true}
Then the watch process stays alive and exits {exitCode: 0} on SIGINT

Given a vault the vault command wrote from an extraction root and now watches
When the Spec {specId: "spec:probe.member"} is edited by {edit: "an anchor added in a source file"}
Then the note of that Spec shows an implementation binding: {bindingShown: true}
Then every note whose bytes the change leaves alone keeps its modification time: {othersUntouched: true}
Then the watch process stays alive and exits {exitCode: 0} on SIGINT

Example space

Given a vault the vault command wrote from an extraction root and now watches
When the Spec {specId:string} is edited by {edit:"a title change in its carrier"|"an anchor added in a source file"}
Then the note of that Spec shows the new title: {shown:boolean}
Then the note of that Spec shows an implementation binding: {bindingShown:boolean}
Then every note whose bytes the change leaves alone keeps its modification time: {othersUntouched:boolean}
Then the watch process stays alive and exits {exitCode:number} on SIGINT

Verifier bindings

• spec:consumers.obsidian-vault.iteration.watch-rewrites-changed-notes · A carrier edit under watch rewrites only the notes it changes · declared · example enabled · specs/consumers/obsidian-vault.iteration.watch-rewrites-changed-notes.sdp.md

  External run evidence from test/vault-examples.test.ts

  Test anchors: test:protocol.consumers.obsidian-vault.bases.views-match-sources, test:protocol.consumers.obsidian-vault.changed-note-refused, test:protocol.consumers.obsidian-vault.failed-extraction-keeps-notes, test:protocol.consumers.obsidian-vault.failed-extraction-recovered, test:protocol.consumers.obsidian-vault.fresh-vault, test:protocol.consumers.obsidian-vault.hidden-file-refused, test:protocol.consumers.obsidian-vault.interrupted-run-recovered, test:protocol.consumers.obsidian-vault.iteration.watch-rewrites-changed-notes, test:protocol.consumers.obsidian-vault.iteration.watch-source-anchor, test:protocol.consumers.obsidian-vault.notes.case-collision-refused, test:protocol.consumers.obsidian-vault.notes.entry-address-link, test:protocol.consumers.obsidian-vault.notes.term-address-link, test:protocol.consumers.obsidian-vault.notes.unresolved-mention-stays, test:protocol.consumers.obsidian-vault.person-notes-survive, test:protocol.consumers.obsidian-vault.unknown-note-refused, test:protocol.consumers.obsidian-vault.vault-in-build-path-refused. Specs verified by those bindings: spec:consumers.obsidian-vault, spec:consumers.obsidian-vault.bases, spec:consumers.obsidian-vault.bases.views-match-sources, spec:consumers.obsidian-vault.changed-note-refused, spec:consumers.obsidian-vault.failed-extraction-keeps-notes, spec:consumers.obsidian-vault.failed-extraction-recovered, spec:consumers.obsidian-vault.fresh-vault, spec:consumers.obsidian-vault.hidden-file-refused, spec:consumers.obsidian-vault.interrupted-run-recovered, spec:consumers.obsidian-vault.iteration, spec:consumers.obsidian-vault.iteration.watch-rewrites-changed-notes, spec:consumers.obsidian-vault.iteration.watch-source-anchor, spec:consumers.obsidian-vault.notes, spec:consumers.obsidian-vault.notes.case-collision-refused, spec:consumers.obsidian-vault.notes.entry-address-link, spec:consumers.obsidian-vault.notes.term-address-link, spec:consumers.obsidian-vault.notes.unresolved-mention-stays, spec:consumers.obsidian-vault.person-notes-survive, spec:consumers.obsidian-vault.unknown-note-refused, spec:consumers.obsidian-vault.vault-in-build-path-refused.

  Run 1: external run evidence from vitest 4.1.10

  Build: CI 433 · Branch: fix/second-review-pass · Commit: 6375b6e431a7cf885a49befec76d7876cd3e538c · Start: 2026-11-04T07:12:23.076Z · Stop: 2026-11-04T07:15:49.695Z

  Name	Suite	Result	Duration
  keeps incomplete oracle points unspecified	not recorded	passed	3.25 ms
  executes the bound example against a fresh world	A fresh vault is written the same way twice and every link resolves (spec:consumers.obsidian-vault.fresh-vault)	passed	84.55 ms
  executes the bound example against a fresh world	A regeneration removes a note that left the graph and keeps a person's notes (spec:consumers.obsidian-vault.person-notes-survive)	passed	54.56 ms
  executes the bound example against a fresh world	A note a person wrote inside the generated folder refuses the regeneration (spec:consumers.obsidian-vault.unknown-note-refused)	passed	19.26 ms
  executes the bound example against a fresh world	A generated note a person changed refuses the regeneration and keeps the edit (spec:consumers.obsidian-vault.changed-note-refused)	passed	16.79 ms
  executes the bound example against a fresh world	A person's file under a temporary's name refuses the regeneration (spec:consumers.obsidian-vault.hidden-file-refused)	passed	16.38 ms
  executes the bound example against a fresh world	A vault directory the build removes refuses the run and keeps a person's notes (spec:consumers.obsidian-vault.vault-in-build-path-refused)	passed	2.61 ms
  executes the bound example against a fresh world	A run after a stopped synchronization finishes it (spec:consumers.obsidian-vault.interrupted-run-recovered)	passed	74.6 ms
  executes the bound example against a fresh world	A failed extraction keeps the notes and says so on the index (spec:consumers.obsidian-vault.failed-extraction-keeps-notes)	passed	21.34 ms
  executes the bound example against a fresh world	The run after a failed extraction passes the guard and restores the index (spec:consumers.obsidian-vault.failed-extraction-recovered)	passed	51.38 ms
  executes the bound example against a fresh world	An entry address in prose opens the entry's block in its Spec's note (spec:consumers.obsidian-vault.notes.entry-address-link)	passed	22.67 ms
  executes the bound example against a fresh world	A mention of an entry that does not exist stays as written (spec:consumers.obsidian-vault.notes.unresolved-mention-stays)	passed	16.42 ms
  executes the bound example against a fresh world	A keyed Model term gets a note, and its address in prose opens the term's block (spec:consumers.obsidian-vault.notes.term-address-link)	passed	20.53 ms
  executes the bound example against a fresh world	Two Specs whose notes differ only in case refuse the run (spec:consumers.obsidian-vault.notes.case-collision-refused)	passed	6.97 ms
  executes the bound example against a fresh world	Each standing view selects what its source selects (spec:consumers.obsidian-vault.bases.views-match-sources)	passed	43.11 ms
  executes the bound example against a fresh world	A carrier edit under watch rewrites only the notes it changes (spec:consumers.obsidian-vault.iteration.watch-rewrites-changed-notes)	passed	722.52 ms
  executes the bound example against a fresh world	An anchor added in a source file under watch rewrites the Spec's note (spec:consumers.obsidian-vault.iteration.watch-source-anchor)	passed	740.73 ms

• spec:consumers.obsidian-vault.iteration.watch-source-anchor · An anchor added in a source file under watch rewrites the Spec's note · declared · example enabled · specs/consumers/obsidian-vault.iteration.watch-source-anchor.sdp.md

Requirement drawing

Decisions

No decision record named.

• component:protocol.cli · entry points, shared build and publication · src/cli/build-command.ts:31 · layer edge · context protocol

  Uses

  • component:protocol.adapters · external runtime and source adapters · src/adapters/vitest.ts:23 · layer adapter · context protocol
  • component:protocol.codegen · contracts and registrar output · src/codegen/contracts.ts:671 · layer application · context protocol
  • component:protocol.extract · the carrier and source pipeline · src/extract/index.ts:197 · layer application · context protocol
  • component:protocol.graph · the one graph and its semantic decisions · src/graph/schema.ts:34 · layer domain · context protocol
  • component:protocol.import · canonical conversion with a fidelity boundary · src/import/import.ts:45 · layer application · context protocol
  • component:protocol.model · the authored contracts and stable ids · src/model/anchors.ts:100 · layer domain · context protocol
  • component:protocol.projections · read-only output, layout and owned publication · src/projections/design-review.ts:29 · layer edge · context protocol
  • component:protocol.reader · the typed graph contract and body evaluator · src/reader/reader.ts:697 · layer application · context protocol
  • component:protocol.validate · one finding currency and ordered checks · src/validate/validators.ts:76 · layer domain · context protocol
• component:protocol.projections · read-only output, layout and owned publication · src/projections/design-review.ts:29 · layer edge · context protocol

  Uses

  • component:protocol.extract · the carrier and source pipeline · src/extract/index.ts:197 · layer application · context protocol
  • component:protocol.graph · the one graph and its semantic decisions · src/graph/schema.ts:34 · layer domain · context protocol
  • component:protocol.model · the authored contracts and stable ids · src/model/anchors.ts:100 · layer domain · context protocol
  • component:protocol.notation · the leaf step codec · src/notation/slots.ts:263 · layer domain · context protocol
  • component:protocol.reader · the typed graph contract and body evaluator · src/reader/reader.ts:697 · layer application · context protocol
  • component:protocol.validate · one finding currency and ordered checks · src/validate/validators.ts:76 · layer domain · context protocol
• impl:protocol.vault-sync · guards every owned entry and records transitional hashes before atomic file replacement · src/projections/vault/sync.ts:98

  Component: component:protocol.projections · read-only output, layout and owned publication · src/projections/design-review.ts:29 · layer edge · context protocol

  Uses

  None.

• impl:protocol.vault-text · renders checked mentions and escapes Obsidian syntax outside code spans · src/projections/vault/text.ts:30

  Component: component:protocol.projections · read-only output, layout and owned publication · src/projections/design-review.ts:29 · layer edge · context protocol

  Uses

  None.

• impl:protocol.vault-watch · reuses the coalescing watcher with source suffixes and a synchronous vault cycle · src/cli/vault-command.ts:243

  Component: component:protocol.cli · entry points, shared build and publication · src/cli/build-command.ts:31 · layer edge · context protocol

  Uses

  None.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.