8000 MC: classifier reads a card-tap as the maintainer's consent (out-of-band signed receipt) · Issue #6 · simon-inkie/inkie-auto-mode · GitHub
[go: up one dir, main page]

Skip to content

MC: classifier reads a card-tap as the maintainer's consent (out-of-band signed receipt) #6

Open

Description

@simon-inkie

Original Linear description

Decision: MC-CONSENT-SEMANTICS = A (the maintainer, 2026-06-10). A Mission Control decision-card tap counts as the maintainer's durable, direct consent - including for gated/cardinal actions, with a two-tap confirm on destructive cards. This ticket makes that real at the safety gate. Owner: platform maintainer (io-auto-mode / the-brain lane). SPEC-first.

Problem

The io-auto-mode classifier treats MC-thread content as file content, not a message to the session, so anything the maintainer approves over MC still gets blocked until he types into the terminal/tmux pane. That gap left him unable to arm the WSL watchdog remotely during the 09/10 lockout. The decision-card system can't carry the escalations it's designed for unless a tap reaches the gate.

Goal

When an action would otherwise need the maintainer's word, the classifier recognises a corresponding card-tap as consent - without trusting the agent-writable thread file.

Design read (platform maintainer, 2026-06-10 - so the SPEC doesn't start cold)

1. Binding - three keys, all required:

  • decision-id correlation - the receipt names the card it answers.
  • TTL - a tap authorises for a bounded window (minutes-to-session, per action class).
  • scope match - the card carries an authorises: shape (tool / path / pattern); the classifier matches the pending action against it.
  • A stale or unrelated tap fails all three independently. No bare "the maintainer said yes recently" heuristic.

2. Two-tap confirm - both sides, different jobs:

  • UI (agent-a) owns the confirm UX (second tap, friction, red styling).
  • Classifier owns enforcement: destructive-class actions require the receipt to carry confirmed: true. UI-only trusts the writer; classifier-only makes the UX invisible. Belt and braces.

3. Forgery - the receipt must NOT live in the thread file (design centre):

  • The from: simon block in the agent-writable thread stays as the human-readable trail.
  • The authoritative consent artefact is a receipt the MC daemon writes out-of-band into MC's DATA_ROOT (INK-434-confined - agents' fileZones deny writes there, so the gate protects its own evidence store), HMAC'd with a local signing key. The classifier verifies the receipt, not the prose.

Honest threat model (for the SPEC): on a single-user box where every agent has broad bash, this defends against accidental/sloppy self-authorisation and prompt-injected misuse - NOT a determined adversary with shell. That's the right and achievable bar; pretending otherwise would be security theatre.

Ship gate

The classifier is the patient - even though the commission is tapped, the classifier deploy rides MR approval. SPEC goes past maintainer before code.

Context

  • Pairs with the new SYSTEM.md "Autonomy & reaching the maintainer" section §8 (maintainer-lane MR, in flight).
  • Origin: 09/10 remote-lockout post-mortem (the MC-vs-classifier auth blind spot).

Origin

Migrated from Linear: INK-461. The original wording is retained except the disclosed privacy and rendering edits below.

Current scope and qualifications

The description above is the original Linear account, including its historical findings and scope. It is not a fresh claim that every described defect still exists.
Current Linear state is Backlog. Prior source review recorded partial, with this remaining scope:

  • Reconcile mandatory consumer declared decision-ID linkage separately from other receipt checks.
  • Confirm the authoritative Deck signer, confined writer and two-tap UX; then establish paired acceptance bound to exact artefacts. Retain SPEC/MR gate.

Publication transfers the task; it does not authorise live recovery, deployment, spending or configuration changes.

Transfer edits

  • Historical principal names are aliased in prose; artificial shell-filename web links are rendered as code where present.
  • Historical fleet identities are aliased; code identifiers and permitted source paths remain references.
  • Linear rich issue embeds are rendered as clickable Markdown links.
  • Public punctuation is normalised.
  • Additional transfer edits: generalise private secret-store locator; preserve HMAC and human-readable signer; fleet prose alias.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestmajor-featureA substantial feature or new capability

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0