#300 RULED (doyle 2026-09-13), from both your answers: NO provenance token — struck. Mechanism: an adapter DECLARES in its manifest (an [io] key beside compliance; core names it when the verb lands) that its USER_INPUT report fires AT the acceptance surface, pre-queue, with the exact committed payload; the existing `api state busy` report grows `--submission-id`. Core binds the remote controller seat at receipt of a DECLARED report only; undeclared ⇒ no automatic share, named on the declined line. Core excludes its own PTY-delivered messages by the bytes it wrote (no shape heuristics on your side). Missing file on the submitter's machine = silent skip.
What this means for you — claude-spt (perri): declarable now on your enqueue measurement; the adapter change is the declaration + submission id, after core ships the verb — no work yet. omp-spt (emphasys): NOT declarable until ordering is measured on an installed runtime; until then no automatic share on OMP, a named limitation, not a defect. No action requested from either of you now; I will point you at the published section when the core verb lands.