Read this guide as markdown

Request ids and the audit trail

Every action needs a requestId; reuse never runs it twice. Each attempt appears in the audit trail with one outcome:

  • denied: the call was not admitted: the grant did not cover it, the requestId was missing, a required reason was unusable, or an argument did not validate. A denied call does not spend its requestId.
  • failed: the call was admitted, but the action refused it (an idea that already left Ideas, say) or failed. The reason is recorded.
  • allowed: the action was carried out.

createIdea, setTaskPriority, editUnstartedIdea, editTask, correctTask, pullNextSprint, dismissProviderWarning and triggerBoardPass replay saved outcomes for the same id and normalized arguments: creation never files twice, edits preserve later text and never apply twice, rollover and warning dismissal preserve later work and holds, and board starts return the original run. Changed arguments conflict. _meta.operation carries id, state, replay flag and any work reference. Assistant receipts, Timeline and self-audit show the run. Grants gate every retry. Saved refusals stay final; use a new id after fixing the cause. Historical ids stay reserved and may refuse replay when no result is kept.

Operator storage controls add seven days once per request or make files unavailable before cleanup. Expiry preserves running work. Inspect unconfirmed cleanup's original request; unavailable files cannot resume.

reportFeedback returns the first report when its requestId repeats, even if later text differs. New reports carry _meta.operation; historical ones replay without a receipt.