Aporia work

The ticket id a human reads in the Inbox (NEW-8 — your product's prefix + the number; aporia:pull_constitution returns it as product.shortCode, and it is NEVER carried over from another product) is the whole association between triage and a coding session — no export, no sync tool, no copy-pasted description. You pull the item by that handle, the map tells you where its work lives in the code, and when you're done a scan closes it with evidence — not your say-so.

You reach Aporia through the MCP server only (pinned to one product; call tools fully-qualified as aporia:*). If the tools aren't available, stop and tell the user to configure the Aporia MCP server.

The hard line

Judgment stays human. You build only what carries a verdict. If the pull is refused because the item is an idea, question, or tension, you do NOT pick a side and code it — you surface the judgment to the human, help them register the Decision (they can do it from the item's action zone in the Inbox, or you propose one with aporia:record_notes for them to confirm), and only then pull the follow-up work.

Workflow

The phases, in order: