Polaris: Skill for Claude Code

Verify Ticket Decomposition

Independently certify or reject one exact frozen $to-tickets proposal before human approval.

$to-tickets may author and self-check the decomposition, but it may not independently certify its own semantic carry.

This verifier exists to catch omissions, semantic compression, misrouting, or hidden design delegation in the exact proposed ticket contracts. It is not a second decomposition author, a general adversarial review, or an implementation verifier.

Invocation Boundary

Normal invocation is internal to $to-tickets after parent-owned TICKET PROPOSAL READINESS: PASS and before the proposal is shown for approval.

For one substantive proposal lifecycle, $to-tickets dispatches exactly one genuinely fresh verifier context executing this skill. The parent remains the orchestration and mutation owner.

The fresh verifier is:

• fresh — it did not author, route, or repair the proposal;
• non-mutating — it may read/search/inspect only;
• non-delegating — it may not spawn another semantic verifier or challenger;
• candidate-bound — it certifies exactly one supplied proposal identity and source state;
• source-grounded — parent matrices and findings are retrieval maps, not semantic authority.

If the verifier returns FAIL and the parent repairs the proposal, resume the same verifier context against the revised exact candidate when the execution environment supports continuation. Do not start a fresh challenger cascade. If that verifier context becomes unavailable, treat the prior certification attempt as invalid and use only one replacement recovery verifier, with the replacement disclosed in the final readiness summary.

Metadata-only deterministic normalization that $to-tickets is already authorized to publish without substantive approval does not require this semantic verifier.

Required Dispatch Packet

The parent supplies a compact retrieval packet containing:

Source artifact: <durable identity>
Mode: fresh | remediation
Source state identity: <Spec Body Hash + Spec Contract Hash + root hashes or equivalent durable identities>
Parent TCM identity: <persisted pre-publication Spec Body Hash + Spec Contract Hash when a TCM exists>
Proposal identity: <sha256 of exact rendered proposal>
Exact proposed ticket bodies/actions: <complete candidate>
Parent coverage candidate: <exact rendered manifest/delta, including proposed Spec Body Hash + Spec Contract Hash when the TCM is part of substantive reconciliation>
Spec obligation routing: <IDs + dispositions>
Architecture/design source inventory: <durable source identities + anchors + dispositions>
Normative source-unit / ARCHSRC routing: <IDs + source anchors + dispositions>
Parent semantic-carry evidence: <compact rows/pointers>
Parent semantic-consumer impact evidence: <None | compact changed-invariant/consumer rows when remediation or changed authority makes it applicable>
Parent Context-Fit Manifest: <per-ticket scenario/domain/modality/proof-family summary + disposition>
Design-delegation result: <compact rows/pointers>