[valentinyanakiev]

What changed

The operator accepted two decisions on 2026-10-31, and both are built and merged. This PR records the acceptances in the records. Documents only.

• 0099 (the tracker's tick reads the engine's own tree; An idle run driver re-reads the whole host's process table every 100 ms: on Linux, walk its own tree instead #918, built in protocol: an idle run driver walks its own tree to detect, and one full snapshot attributes (#918) #931) is accepted as built.

• 0102 (a stop with no ending stands as stopping; A stop accepted while no driver runs is never applied, so the run reads as running forever, and the trail hides the stop #909, built in readouts: a run whose accepted stop has no ending reads as stopping, and its trail shows the stop (#909) #926) is accepted as built, with ruling 3 widened:

  • the summary row carries a second nullable column, stop_folded_seq, the stamp that the stop columns were written at the folded head;
  • the run_summary_stopping trigger sends behind a row an older writer folded, so the open's backfill refolds it.

  A closing "Ruled" section records the widening. No ruling's text moves.

Each Status line and index row moves to accepted, with the trailing acceptance sentence 0091, 0095 and 0096 carry. This follows the shape of #901, the records PR for 0096. Both PRs said in their text that a records PR would follow their merge.

Brokkr-Run: landing-pr-the-records-of-two-ac-51798121

How it's held

The landing landing-pr-the-records-of-two-ac-51798121 closed RESIDUAL-OK at LOW: no security residual, no specification defect, no new ask. Its chief confirmed:

• the Status lines, the Ruled section and the index rows agree, each quoting its ruling verbatim with the link;
• 0102's Ruled section is true at HEAD (crates/brokkr-store/src/summary/stop.rs's columns, stale() and the trigger; summary.rs:311 writes the stamp in the same statement as folded_seq);
• DATABASE_SCHEMA is 1 at HEAD and before readouts: a run whose accepted stop has no ending reads as stopping, and its trail shows the stop (#909) #926;
• no other line cites either decision as proposed (the one grep hit, landing_shape.rs:244, is a synthetic fixture).

Gates: decisions_index::, doc_truth:: and doc_samples:: (66 passed), typos, the file and clone ratchets, and git diff --check.

The one LOW, carried without an edit: 0099:252-253 keeps its proposal-time line "Only the operator accepts this decision; this document claims no acceptance." The chief ruled no edit, by house precedent: accepted 0077, 0087, 0091 and 0096 keep the same disclaimer, and #901 changed only 0096's Status line. The task also forbids moving ruling text.

Ruling: operator 2026-10-31, in chat, "go with recommended everywhere" (#918, #918 (comment)): decision 0099 accepted (proposed, built), recorded by a records PR after #931 merges
Ruling: operator 2026-10-31, in chat, "go with recommended on all the rulings" (#909, #909 (comment)): PR #926's asks as recommended, including (c), the second column and the trigger beyond 0102 ruling 3's one-column text, and (f), decision 0102
Ruling: operator 2026-10-31, in chat, "go with recommended everywhere" (#909, #909 (comment)): 0102's acceptance recorded in its status line by a records PR after #926 merges

Part of #918. Part of #909. Part of #330.

🤖 Generated with Claude Code