Use exact final-action entrypoints

Order entrypoints are root-native protocols, not ordinary prompts. They protect the final service action without weakening the research, approval, policy, broker, and audit boundaries.

Choose your order path #

00From provider to orderSet up Paper or a broker provider, then follow connection, ticket, approval, and final-action checkpoints.→01tcx-order-allowCurrent-turn grant for one possible later effect.→02tcx-order-submitExact final submit grammar and result handling.→03tcx-order-cancelExact final cancel grammar and result handling.→

Before any order path #

There is no tcx-order umbrella skill. The three entrypoints below are unavailable in Plan mode and subagents. The browser viewer, public REST, generic CLI, and direct MCP calls expose no usable final mutation.

Use tcx-workflow when the task is still evidence gathering. Use these exact protocols only after you intentionally choose a final-action path.

Current turn only

`tcx-order-allow`

Admit at most one later submission or cancellation attempt in this root task.

Use it when: You intentionally allow one possible final effect after the research, ticket, review, and approval gates are satisfied.
Exact first meaningful line: Use one allowed mode with no comments, aliases, or extra flags. Only the skill token may be replaced by its matching workspace link.
What it does not do: It does not submit an order, grant approval, or persist to another turn.
Lifecycle: The single-use grant is bound to the workspace, session, turn, original complete prompt, permission mode, and mode; it expires after one hour and is revoked on use, Stop, or the next turn.

Allowed modes

$tcx-order-allow --mode paper
$tcx-order-allow --mode validation
$tcx-order-allow --mode live

Final action

`tcx-order-submit`

Submit one already-approved order using exact canonical identifiers.

Use it when: You already know the ticket id and matching approval receipt id.
Exact prompt: The meaningful prompt is the action grammar. Only the skill token may be its matching workspace link; do not add prose, another skill, or --name=value syntax.
Result: The canonical service returns a redacted accepted, rejected, duplicate, or needs-review result.
Do not: Do not automatically retry an uncertain or needs-review result.

Submit grammar

$tcx-order-submit --ticket-id <ticket-id> --approval-receipt-id <approval-receipt-id>

Final action

`tcx-order-cancel`

Cancel one known submitted broker order using exact canonical identifiers.

Use it when: You know the ticket, broker-order, and matching approval receipt identifiers.
Exact prompt: The meaningful prompt is the action grammar. Only the skill token may be its matching workspace link; do not add prose, another skill, or aliases.
What it does not do: It does not discard a local draft or retry an uncertain outcome.
Final gates: Policy, approval, payload validation, broker health, confirmation, idempotency, reconciliation, and audit remain service-owned.

Cancel grammar

$tcx-order-cancel --ticket-id <ticket-id> --broker-order-id <broker-order-id> --approval-receipt-id <approval-receipt-id>