I3914 — A standing approval is one owner-attributed record in the repository, each machine reports whether it carries it, and only the owner writes it

✕BLOKOVÁNO vlna 1 · p1 · profil implementation · běží samostatně

Part of landing-survives-any-session — Landing green work survives any session, any restart and any machine.

Cíl

The owner's standing approvals are declared as dated, owner-attributed records under .ai/repo/autonomy, each with the owner's words and its bounds. majordomus autonomy status reports per machine which declared approval its Claude Code settings carry and which they lack. autonomy apply writes the missing ones into the user settings with $defaults kept first, and refuses to run inside an agent session (CLAUDECODE set, or no terminal) and without an interactive confirmation, so no session writes its own permissions through the binary. The two rules that disagree about who writes an approval are reconciled into one. Built on I2790's autonomy reading, which is on branch feature/the-autonomy-a-session-has-is-measured (#1311) and must land first.

Proč

On 2026-10-22 every landing attempt from a session was refused as Merge Without Review and every attempt to add the owner's approval was refused as Self-Modification; the approvals the owner had granted lived in one machine's settings only, and Claude Code ignores autoMode in a committed project settings file.

Aktuální stav

Rule a-standing-approval-is-written-where-permissions-are-read v1 says the worker writes ~/.claude/settings.json; rule the-cooperation-model-is-the-owners-word v2:107-110 says a session hands the owner the text; I2790 is not on master and its non_scope forbids writing settings.

Cílový stav

One rule says the owner writes an approval; the repository lists every standing approval; status names the missing ones per machine; apply, run interactively by the owner, adds them and changes nothing else, and refuses inside a session.

Rozsah

• .ai/repo/rules/project/a-standing-approval-is-written-where-permissions-are-read.v1.md
• .ai/repo/project/issues/I3914.yaml

Závislosti

• I3910○READY The integration executor fast-forwards master to every green head, a combined top included, and nothing else lands

Kritéria přijetí

• Each declared approval names its date, the owner's words and its bounds
• status lists, per settings layer, the declared approvals present and missing (case a_missing_approval_is_reported_per_machine)
• apply writes only missing approvals, keeps $defaults first, is idempotent, and refuses inside an agent session or without confirmation
• Exactly one rule states who writes an approval, and it is the owner

Validace

• bin/majordomus plan validate
• env -u MAJORDOMUS_SHARE cargo test --manifest-path apps/majordomus-cli/Cargo.toml --lib -- autonomy::

Požadované důkazy

• approvals_are_declared

Důkazy

Nic nezaznamenáno. Za každým tokenem výše musí stát příkaz nebo artefakt, než lze tento úkol dokončit; vyprávění se odmítá.

Časová osa

zahájeno

—

ověřeno

—

dokončeno

—

Tato tři pole, důkazy výše a stav závislostí jsou vše, z čeho se stav skládá. Neexistuje žádné pole stavu, které by s nimi mohlo být v rozporu.

Canonical record: .ai/repo/project/issues/I3914.yaml. Read it back with majordomus plan show I3914.