Six Means of Knowing: Why One Channel Is Never Enough

How do you know what an AI agent’s output is actually true?

A team ships a verifier. It checks the output against a single benchmark — a test set, a regex, a downstream API call. Green light. Ship.

A month later the agent produces an output that passes the verifier and breaks production. The verifier was honest about what it checked. The output was true to the verifier. The verifier was checking one channel.

One channel is never enough.

This is not a flaw in the specific verifier. It is a structural property of verification. Any single instrument has a blind spot. The blind spot is not a bug to fix; it is the shape of what that instrument cannot see.

Older traditions of inquiry worked this out millennia ago. They named six independent means of valid knowing — six channels, each catching what others miss. The lesson the framework received from them is direct: if you want to verify what an agent produced, you need more than one channel.

Why Single Channels Fail

A single verification channel succeeds inside its frame. It fails at the frame’s edge. The failure modes are predictable:

Direct check passes; structure is wrong. The output matches the test fixture. It also embeds a subtle reordering that breaks downstream callers. The direct check sees match. It does not see the structure.

Structure check passes; comparison fails. The output is well-formed JSON. It also gives “$50” where the comparable case would give “$5,000.” The structure check sees JSON. It does not see the gap to the reference case.

Comparison passes; testimony contradicts. The output matches the reference case for cost. The customer’s mandate says cost should be discounted under the active promotion. The comparison sees the reference. It does not see the mandate.

Testimony aligns; postulation breaks. The output respects the mandate. It also takes an action that, to make sense, would require an authority not in evidence anywhere. The testimony check sees the words. It does not see what would have to be true for the words to be coherent.

Postulation works; absence is missed. The output respects every active rule. It also fails to surface the row that should have been flagged for review. Every active check fires; the silent absence does not.

Each channel sees one face of the truth. Each has a frame within which it succeeds and a frame at which it ends. If you only run one, the agent’s output is verified inside one frame and unverified at every other frame’s edge.

Six Channels, Six Faces

The framework’s six-channel verification — what older traditions called six valid means of knowing — covers the failure modes by composition:

1. Direct evidence. What did the agent actually emit? This is the first-line check: the literal output. It catches direct failures. It does not catch structural or contextual failures by itself.

2. Inference from premises. Given the inputs, the model state, and the rules, what should follow? This catches outputs that are well-formed but not what the premises entail. The output is rejected because the inference does not lead there.

3. Comparison to reference. What does this output look like next to a known-good case for the same situation? This catches outputs that pass direct and inference checks but diverge from the reference in ways that matter. The reference is the calibration witness.

4. Authority and testimony. What does the mandate say? What does the policy say? What does the human-in-the-loop say? Authority is its own channel. Testimony is its own channel. Outputs that pass the mechanical checks but contradict the authority record fail this channel.

5. Postulation — what must be true for this to make sense? This is the channel that catches outputs whose surface is fine but whose implicit prerequisites are not in evidence. If the output assumes an authority that does not exist anywhere in the input chain, postulation flags it.

6. Absence — what is missing. The check that something did not happen. The row that should have been processed and was not. The flag that should have fired and did not. The exception that should have been raised and was silenced. Most verification frameworks have no instrument for this channel — and most production failures land here.

These six are not the same channel rephrased. They are six structurally distinct ways of arriving at “this output is valid” — each catching a class of failure the others cannot catch.

The Composition Property

The point is not that you need all six on every output check. The point is that the six are independent. A failure mode that slips past one passes directly to the next. A failure mode that survives all six is genuinely a multi-channel failure — and those are the cases where you actually want to ship.

This is the same logic as cryptographic verification: a single signature is breakable; multiple independent signatures over the same artefact compound the security. Independence is the property that gives the composition its strength. Two channels that are actually one channel in disguise compose to one channel’s coverage. Two genuinely independent channels compose to a strictly larger coverage.

The six channels were named because they are demonstrably independent — each can succeed where another fails, and the cases where they all align are categorically different from the cases where any single one fires alone.

What Engineering This Looks Like

In an agent’s verification pipeline, the six channels show up as concrete instruments:

• Direct evidence: hash, signature, exact-match assertion against expected output
• Inference: premise-tracing — given inputs and model state, what does the rule pipeline derive?
• Comparison: reference-case retrieval — what did similar inputs produce in known-good cases?
• Authority: mandate validation, policy attestation, HITL gate
• Postulation: implicit-prerequisite check — what would have to be true for this output’s claims to hold?
• Absence: silence detection — what should have happened here that did not?

Most production systems have one or two of these — typically direct evidence and (sometimes) authority. The other four are common gaps. Inference is hard to instrument. Comparison requires reference data. Postulation is often only available in adversarial review. Absence is the hardest of all because instruments are mostly built to fire on events, not on their absence.

A team that ships verification on one or two channels has not shipped verification. They have shipped a partial-coverage instrument that will be confidently wrong in the cases that matter most.

The Disposition

Older traditions held that truth is multi-witnessed. A single witness can be honest and still wrong; a single instrument can be precise and still blind. The way to arrive at confidence is independence — multiple instruments, each with its own frame, each catching what the others miss, agreeing.

The framework received this. The six-channel verification architecture is the engineering instance of it. Output integrity, in this discipline, is not the strength of the strongest channel; it is the agreement of independent channels. Where they disagree, you do not ship. Where they agree, you have engineered something close to the bounded answer the verification frame promises.

A team that takes “what an agent says it produced” as truth has skipped the discipline. A team that takes “what one verifier confirms” as truth has skipped the property of independence. The discipline holds when the channels are six and the channels are independent and the agreement is structural, not stipulated.