ARCHIVED CHAPTER 07

Evidence, Verification, and Auditability

Make relevant events and decisions inspectable while keeping confidential inputs within their boundaries.

A system becomes easier to operate when it can explain the relationship between a request, a decision, and a result. Evidence is the material that supports that explanation. Hybrid-Chain includes evidence-oriented capabilities across its products, together with public verification surfaces for records that are appropriate to expose.

Different records answer different questions

Record or evidenceQuestion it can help answerWhat should not be inferred automatically
Integrity commitmentDoes the checked material match this reference?The material is true, legally sufficient, or currently retrievable.
Decision recordWhat outcome was recorded for the reviewed subject?The proposed action has executed.
Operation receiptWhat stage did the responsible service acknowledge?Every downstream stage has completed.
Publication or inclusion evidenceIs the referenced record present in the relevant published history?The underlying private content is public or available to the reader.
Execution lineageWhich recorded package and context relate to this result?Every possible workload is enabled or the result is correct for every business purpose.

Continuity across systems

Evidence Streams addresses the need to follow admitted events and their context over time. In an investigation, the goal is not merely to collect more logs. It is to locate the relevant records, understand their provenance, and identify gaps or changes in continuity. Other modules contribute evidence specific to their own responsibility, such as a governance decision, a funding observation, or an execution record.

Applications can connect these records to their business workflow without treating them as interchangeable. A notification may report that a stage occurred, while the authoritative service supplies the current state. A lost response may require reconciliation. A retry should not be assumed safe merely because an earlier attempt was not visible to the caller.

Private context and public verification

Public verification is most valuable when it exposes what is needed to check the public claim and excludes unrelated private material. Explorer records can support transparency around selected events without becoming a directory of confidential documents, personal information, wallet secrets, or internal operating arrangements.

For organizations, this creates a practical path between complete opacity and indiscriminate disclosure. An authorized reviewer can inspect detailed context where permitted, while another party can inspect a narrower public record. The evidence's subject, scope, freshness, and authority determine which conclusions are justified.

Auditability as a product property

The platform's advantage is the opportunity to make evidence part of normal operation rather than reconstructing it only after an exception. Reviewable outcomes help engineering, operations, and governance teams discuss the same event with clearer terms. They do not replace independent assurance, responsible interpretation, or the legal requirements of a particular organization.

Hybrid Explorer: a public route from claim to evidence

Hybrid Explorer is the dedicated public, read-only interface for finding published Hybrid-Chain records and examining their available evidence. Its directories span ledger and wallet activity, identity and authority records, markets, assets, execution, contracts, and other proof domains. Public browsing gives engineers and reviewers a common reference without granting access to account operations or confidential source material.

The distinction between a searchable record and a verified conclusion is essential. A directory can contain historical, test, incomplete, or differently scoped evidence. An interface label describes the check or state presented by that interface; a reviewer must still identify the exact subject and supporting material before relying on it. An unavailable response or empty result should remain an unavailable or empty observation, not be promoted into a successful check or a claim that an event never occurred.

A repeatable Explorer walkthrough

StepWhat to doWhat to retain
1. Find the exact subjectSearch a public identifier or select the appropriate evidence directory. Use the returned record type and references, not a similar name.Record URL, identifier, evidence class, and the question being investigated.
2. Establish network and timeCheck Mainnet, Testnet, or Devnet context and distinguish event time from the time you observed the record.Network, relevant version or event, observation time, and any freshness limitation.
3. Follow supplied referencesOpen the supporting records or base-layer references actually associated with the subject.The relationship between records and any missing or inaccessible evidence.
4. Inspect the stated verificationIdentify what was checked, which evidence supports it, and whether a further check is available to the reviewer.Passed, failed, and unperformed checks, with their method and scope.
5. State a bounded conclusionDescribe only what those checks establish for that subject. Reconcile business completion with the responsible service where required.The supported conclusion, unresolved questions, and separate conditions for completion.

For example, a Data Vault public event can support review of a protected-state transition through published commitments and associated evidence. It does not provide the underlying file or grant permission to retrieve it. Checking that an event is included in a published batch is a different question from establishing current authorized retrieval, and neither establishes that the document's business assertions are true.

Publication, verification, and finality are distinct

Explorer settlement views explicitly separate development, testing, and production contexts, and distinguish operational evidence from financial settlement. Technical readiness describes an observed condition; governance approval concerns a permitted change; settlement finality concerns the exact completed operation under its applicable rules. A wallet activation, test credit, or infrastructure proof must be interpreted in its own class.

This makes Explorer useful as a shared inspection surface rather than a substitute for the responsible system. Its public evidence can help a team explain what happened and locate what remains unproven. It does not move assets, expose private identity or signing material, or convert a displayed record into authority to act.

From private decisions to scoped institutional evidence

Banking adds a useful distinction between a private audit record, a signed application receipt, a published commitment, and an externally checked proof. Each concerns a different subject and trust boundary. Selected Testnet compliance events can have validator-verified evidence while another instruction retains only application-local history. A report must identify the class actually present instead of describing every event as on-chain or finalized.

The Auditable Asset Manager illustrates disclosure by audience. A client can receive an understandable decision explanation, a manager can retain restricted research, and an authorized institutional reviewer can inspect the evidence required for oversight. Public commitments should exclude confidential client or strategy material. The proof must support the specific public claim without implying access to the private source.

A narrow allocation proof and its interpretation

The public Asset Manager describes an experimental Testnet range proof for a committed allocation within a mandate limit. The claim concerns that allocation relation under the proof's assumptions. It does not establish that input records are true, prices are current, holdings are complete, an investment is suitable, or a participant has regulatory authorization. Production cryptographic review and the wider operational acceptance remain separate gates.

An illustrative reviewer records the mandate version and limit, the subject commitment, the supported verification result, and which additional business checks were performed privately. A suitable conclusion describes the checked allocation relation and its Testnet scope. It leaves input validation, execution, valuation, and settlement as separate questions for their responsible services.

Evidence should survive a cross-application handoff

A Cortex inquiry, a proposal, an institutional approval, and a financial outcome should be related only through supported references that identify the same subject and terms. Similar labels or timestamps are not a reliable join. Keep the proposal version and represented parties clear, retain the applicable decision references, and report where the relationship remains unverified. This connects the public architecture to practical audit work without publishing private conversations or internal proof mechanisms.