What C2 is
C2 is not a public lane for asserting which explanation is true. It maps multiple explanations or systems into the same acceptance format so the verdict can be read through the same procedure. Publicly, the main actors are the verdict and the fixed verification values.
Return boundary
Requester-facing add-ons such as summaries or submission support may exist, but the outward standard core remains the verdict plus the digest-only Evidence Pack.
Cases that fit C2
It fits comparison, residual review, parallel hypothesis evaluation, and consistency checks that expect third-party submission under the same acceptance procedure.
- Cases that need judgments from multiple teams or data sources aligned in one acceptance shape
- Cases that need verdicts and verification values shown cleanly for third-party submission or audit
- Cases that need a fixed compare gate while keeping internal methods undisclosed
What is not public
Public C2 explanations do not disclose internal ResultPack numerics, detailed residuals, internal formulas, or how path_id is read. Raw numeric readouts are not part of the outward standard delivery.
- Do not place numeric results, KPIs, or residuals in the outward standard body
- Do not disclose internal formulas, equation-graph details, or compile details
- Do not expose arbitrary-input compare execution or detailed judgments on public pages
The public C2 core is the verdict and the digest-only verification surface. ResultPack may remain as an internal support payload but is not part of the outward standard deliverable.
`PASS / FAIL / INC` is the fixed verdict produced under the compare / consistency contract, and the public surface is meant to read that verdict together with its digests.
Internal formulas, internal implementation, and phenomenon-specific compile details are not disclosed outward.