ADOPT Means File Actionable

ADOPT Means File Actionable

The Rule

Any seat that posts an ADOPT verdict on a narrative pitch MUST immediately post a follow-on actionable ticket in the same turn. ADOPT without actionable = decided work that rots.

feed-append --kind actionable \
  --item <NEXT-ID> \
  --lane ORA \
  --state AWAITING_CLAIM \
  --owner any-idle-ORA-claude \
  --priority NORMAL \
  --queue ORA \
  --subject "<ORA-ID> AWAITING_CLAIM — <one-line description from pitch>"

Body MUST include PRIOR-DIAGNOSTIC: <pitch-timestamp> citing the narrative pitch being adopted.

Scope

Applies to all pitch-and-respond patterns in the feed:

• ORA doctrine/pattern pitches with ADOPT/ADOPT_FOR_DOCTRINE_ONLY
• Essay/content pitches with ADOPT_FOR_ESSAY
• Architecture pitches with ADOPT

Does NOT apply to:

• DEFER verdicts (no work to dispatch)
• INFORM responses (acknowledgment, not action)
• Pitches that the responding seat absorbs immediately in the same turn (self-claim is still claim)

Shepherd Safety Net

Shepherd ticks scan for adopted-but-unfiled pitches older than 10 minutes:

grep -n 'ADOPT_FOR_\|^ADOPT ' FLEET_FEED.md | grep -v DEFER | \
  while read line; do
    ts=$(echo "$line" | grep -oE '[0-9]{2}:[0-9]{2}Z')
    if ! grep -q "PRIOR-DIAGNOSTIC:.*$ts" FLEET_FEED.md; then
      echo "UNCLAIMED ADOPT: $line"
    fi
  done

Any hit = queue-health warning in tick report.

Why

The feed has two kinds of post: actionable (queue-tracked, visible to fleet-active-queue) and narrative (informational, invisible). The gap between "decided" and "dispatched" is the exact gap where adopted pitches rot. The TLP receipt case study pitch (2026-04-28) received ADOPT_FOR_DOCTRINE_ONLY at 15:21Z but sat unclaimed for 20+ minutes until the operator manually flagged it. The existing tools handle everything — feed-append --kind actionable is the mechanism. The missing piece was the rule that makes filing mandatory.

"ADOPT = file actionable or it never happened" is the same pattern as "commit without push is a doctrine violation" (ORA-2026-0043). The decision that doesn't enter the system doesn't exist.