Skip to content
PETROVA

The two-class human allowlist gains alex@devarno.cloud, the author of jzero T1 countersigns

rank: decision outranks: []

Section titled “rank: decision outranks: []”

The two-class human allowlist gains alex@devarno.cloud, the author of jzero T1 countersigns

Section titled “The two-class human allowlist gains alex@devarno.cloud, the author of jzero T1 countersigns”

Date: 2026-11-07 Status: closed Supersedes: none Superseded-by: none — current Amends: docs/decisions/2026-10-10-two-class-landing-authority.md (§4 only: the human allowlist. Everything else in that decision stands.) MR-compliance: MR-4, MR-7

Context

Section titled “Context”

docs/decisions/2026-10-10-two-class-landing-authority.md §4 says a box counts as human-ticked only if git blame on main attributes it to a commit authored by flight@arno.host or alex@devarno.com. That decision is closed and append-only (MR-7), so its text is not edited here.

The list leaves out alex@devarno.cloud. jzero T1 countersigns are authored under that address: the 2026-10-10 decision’s own sign-off line records the tick in 3363c8a1 as “authored by the human (jzero.run T1, session alex@devarno.cloud)”. Under §4 as written, the M1 scribe-close check would treat that tick as not human and classify the close as S. FLIGHT ruled on 2026-11-06 (RL-17b, option a) to add it.

Searched 2026-11-07 at def092fd: no workflow, script or test in this repo holds the allowlist. landing-class (§5) is not built yet, and git grep for flight@arno.host and alex@devarno.com outside decision, finding, audit and evidence docs finds only the registry notes and example values in verb schemas and tests, none of which enforce §4. So this amendment changes no code.

Decision

Section titled “Decision”

The §4 allowlist becomes exactly three addresses: flight@arno.host, alex@devarno.com and alex@devarno.cloud. Everything else in §4 is unchanged. Agent identities (fleet@devarno.cloud, ops@devarno.cloud, any *[bot], noreply@anthropic.com as author) still never count. Note that alex@devarno.cloud is a different address from those agent identities, and the match is on the full address, never on the domain.

When landing-class is built, it reads this list as amended here. Changing the list again is S.

Alternatives considered

Section titled “Alternatives considered”
  • Leave §4 as written — rejected. The T1 countersign tick in 3363c8a1 would fail M1(c), so every scribe close for a doc countersigned through jzero would queue for FLIGHT.
  • Allow the whole devarno.cloud domain — rejected. fleet@ and ops@ are agent identities on that domain, and §4 says they never count.
  • Edit the closed decision — rejected. MR-7: decision docs are append-only.

Consequences

Section titled “Consequences”

For code:

  • None now. The future landing-class workflow takes the three-address list.

For docs:

  • docs/decisions/2026-10-10-two-class-landing-authority.md is untouched. Readers of its §4 follow the Amends pointer here once this decision is countersigned.

For in-flight phases: none.

For invariants: none added, modified or repealed.

References

Section titled “References”
  • docs/decisions/2026-10-10-two-class-landing-authority.md §4 (the list amended)
  • docs/decisions/2026-08-10-countersign-gates-closed-status.md (only a human ticks)
  • FLIGHT ruling RL-17b, 2026-11-06, option a: add it

Sign-off

Section titled “Sign-off”
  • Subagent: Claude Opus 5.5, 2026-11-07 (drafted; read at petrova def092fd)
  • Human countersign — the §4 allowlist of the two-class landing authority gains alex@devarno.cloud — flight@arno.host, 2026-11-07 (jzero.run T1)

Countersigned by human:flight@arno.host on 2026-11-07 at jzero.run T1 — box ticked in commit db22d786d, authored as alex@devarno.cloud: the §4 allowlist of the two-class landing authority gains alex@devarno.cloud. Status flipped open→closed on 2026-11-07 by an agent as scribe (MR-7).