Claim-source alignment
Material claims are mapped to their supporting source or marked as partial, contradicted, unresolved, or unsupported. Unsupported claims are removed, narrowed, or sent back for buyer-side judgment.
Independent verification means the first output is not trusted by default.
Drafting and review are separate functions. A producer may assemble the first answer, report, or evidence pack. A separate verification pass tests whether claims match sources, whether contradictions were missed, and whether the work should stop before external use.
The method is intentionally allowed to block delivery. A blocked output is a valid result when the evidence does not support the proposed claim.
Every material claim passes through explicit review gates.
gate_01
Scope boundary
Define the question, audience, allowed sources, exclusion zones, and what should not be automated.
gate_02
Source existence
Verify that cited sources exist, can be retrieved, and match the claim context before they are used as support.
gate_03
Claim-source alignment
Map each material assertion to its support level: supported, partial, contradicted, unresolved, or unsupported.
gate_04
Contradiction handling
Surface conflicting sources and require a response path instead of smoothing disagreement into confident prose.
gate_05
Human signoff
Route final judgment to the responsible expert or buyer-side owner with residual risk visible.
gate_06
Data boundary
Keep engagement data inside the agreed work scope and prevent training, reuse, or unnecessary retention.
How the review handles evidence, contradiction, signoff, and data.
Contradiction handling
Conflicting sources are preserved as review objects. The output must identify the contradiction, state why it matters, and recommend whether to revise, qualify, escalate, or stop.
Human signoff
Axion does not replace accountable judgment. The responsible expert, owner, or principal reviewer receives the evidence trail and residual risk summary before anything is treated as ready for use.
Data boundaries
Engagement data is processed for the agreed scope only. Private materials are not converted into public proof, reused in unrelated work, or treated as training material.
The output is a review package, not a black-box answer.
evidence matrixclaim-support auditindependent contradiction memorevision registersignoff notedata-boundary summary
Artifact mix depends on the engagement. The constant is traceability: reviewers should be able to see what was claimed, what supported it, what conflicted with it, and who accepted the residual risk.