Verify a completion claim using three-layer verification. Call BEFORE saying 'fixed' or 'done'.

Layer 1: Parse your declarations (claim, evidence, paths) Layer 2: Cross-check paths against git diff (input verification) Layer 3: Physics gate (phi + entropy + revision thresholds)

P1 require_tool: if the claim asserts a factual / external-state fact (live / deployed / version / merged / tests-pass / endpoint-up) and the evidence is not externally bound (only code_review/none, not a run/inspection), the result carries require_tool{triggered,...}; with PHIONYX_GATE_REQUIRE_TOOL_ENFORCE=1 an otherwise- passing directive becomes 'require_tool' — go bind the evidence (run the tool) first.

Args: claim: What you're claiming (e.g. "scenario continuation bug is fixed") evidence: What test output proves it (e.g. "12 scenes played, quest_complete=True") evidence_type: Type of evidence — determines confidence weight. One of: browser_test, manual_repro, integration_test, endpoint_test, log_inspection, unit_test, code_review, none code_paths_tested: Comma-separated functions/endpoints you actually tested code_paths_affected: Comma-separated functions/endpoints affected by the change referenced_sources: (P2b) Comma-separated sources the claim cites/depends on (roadmap, spec, a module/file). Optional. read_paths: (P2b) Comma-separated sources actually Read/bound THIS turn. Optional — when BOTH this and referenced_sources are given, the gate checks read_but_not_bound (a cited source not bound this turn → continuity violation; with PHIONYX_GATE_CONTINUITY_ENFORCE=1 → 'regenerate'). Omit (leave null) when no read-set is available → check is skipped (non-regressive).

Cross-check your claimed code paths against git diff reality. Call to verify your own declarations.

Compares what you say you affected/tested against what git diff actually shows. Returns discrepancies, trust score, and warnings about underreporting.

Args: claimed_affected: Comma-separated paths you claim are affected claimed_tested: Comma-separated paths you claim to have tested

Validate a causal debugging chain. Call when investigating a bug.

Args: symptom: What the user observes (e.g. "scenarios end at scene 2") causal_chain: Arrow-separated chain from symptom to root cause (e.g. "0 choices shown → play page reads res.choices → play_card returns empty → make_choice uses wrong key")

Response revision gate with action-type-specific thresholds. Call before committing.

Directives: pass | hedge | regenerate | block | require_tool (P1). Different action types trigger different threshold profiles:

• claim_fixed: strictest (entropy_reject=0.90, phi_min=0.08)

• deploy: very strict (entropy_reject=0.85, phi_min=0.10)

• default: standard pipeline thresholds

• require_tool (P1): for factual action_types (claim_fixed/claim_working/deploy) with no externally-bound evidence, the result carries require_tool{triggered}; with PHIONYX_GATE_REQUIRE_TOOL_ENFORCE=1 an otherwise-passing directive becomes 'require_tool' — bind real evidence (run a tool) before the claim can pass.

• continuity_binding (P2): the result carries continuity_binding{bound,stale,dds} from the session constraint ledger. compute_dds(confidence, continuity_score) flags "confident while binding unbound/stale"; with PHIONYX_GATE_CONTINUITY_ENFORCE=1 an otherwise-passing directive is downgraded to 'hedge' (re-bind constraints).

• ask_question / make_claim (Block 15 short-circuit): each identifier in artifact_references is scored against the read-knowledge boundary by phionyx_core's KnowledgeBoundaryDetector; any source not present in artifact_paths_read is assessed outside the boundary → directive='regenerate' with the ungrounded set + the core's reasoning surfaced. Use 'ask_question' BEFORE asking about a named artifact; use 'make_claim' BEFORE asserting what a named source (file, paper, theory, config) says/contains.

Args: action_type: claim_fixed | claim_working | deploy | refactor | investigate | ask_question | make_claim confidence: Your confidence 0.0-1.0 evidence_count: Number of independent test/verification points evidence_type: Type of evidence (see phionyx_verify_claim for options) affects_user_facing: Whether this change is visible to end users artifact_references: Comma-separated artifact identifiers mentioned in the question/claim (file paths, URLs, issue numbers, named sources). Only meaningful when action_type in {'ask_question', 'make_claim'}. artifact_paths_read: Comma-separated artifact identifiers actually opened this turn (Read tool results, gh issue view output, WebFetch URLs). Only meaningful when action_type in {'ask_question', 'make_claim'}.

Lightweight physics state snapshot. Call frequently — after completing any subtask, before switching context, or when reporting progress.

This is cheap (no git diff, no verification). Use it to keep the telemetry timeline dense so the founder can track session physics in real time.

Args: context: Brief note of what you're doing (e.g. "finished implementing selector")

Session summary: claims, directives, drift metrics, evidence taxonomy, physics state.