Verified Truth
v3.2 · 2026
Research Document C

What Is New Here?

Document: WHAT_IS_NEW_HERE.md Version: 1.0 Date: 2026-06-26 Owner: Maxim Geller Status: Deliverable C of six requested in Mikhail Goman's scientific review Audience: scientific reviewers, investors, partners, anyone asking "what is actually novel about this work"

The honest opening

The Verified Truth Ecosystem does not claim to invent any of the following:

Each of these is a mature field with decades of research, standards bodies, working implementations, and existing commercial systems. We build on or operate alongside this work. A separate document, the Comparison Matrix (VERIFIED_TRUTH_COMPARISON_MATRIX.docx), names seventeen specific systems and standards and states what each one solves and what it does not solve. A separate section of the public portal at truth.equiwork.io, Existing Foundations and Related Work, presents the nine most important of these as cards with research notes.

If you came to this document looking for an invention of a fundamental primitive, you will not find one.

What you will find is an architectural claim. It is the claim that follows.

The central claim

The invention is not one component. The invention is the architecture that connects components into a living verification process.

Specifically: a small number of architectural moves, made together in a single system, produce a property that no existing system we have surveyed produces. That property is the continuous preservation of evidence-backed, context-bound, human-approved operational truth — preserved at the moment it happens, not reconstructed years later.

This document enumerates the architectural moves. For each, it (a) names the move, (b) names the prior art it builds on, (c) states what is novel about this specific composition, and (d) tags each claim with an explicit status from the Claims Discipline taxonomy.

Calibration: this document does not claim novelty of the individual moves. It claims novelty of the combination. If any reviewer identifies an existing system that combines all seven moves in the same way, we will revise.

The seven structural moves

Move 1 — Treat important reality as a sequence of Verified Events

The move. The smallest preserved unit is not a document, contract, ticket, or record. It is a Verified Event — a structured artifact with an actor, a timestamp, an evidence reference, a predicate, a context, and a verifiable status. The system stores chains of Verified Events. Documents and records are derived from these chains, not the other way around.

Prior art.

What is novel in the composition. Verified Events are structured for human reasoning about what happened, not for software state management. Each event carries authority and evidence references that allow a third party (auditor, court, scientific reviewer) to walk the chain and assess validity. The chain is the substrate; documents are derived views. EXISTS in EquiWork's implementation; CONCEPT for the universalisation across all domains.

Move 2 — Separate declaration, evidence, analysis, verification, approval, and canonical state

The move. Most existing systems blur these. A "signed" document might be checked, accepted, recorded, and treated as canonical all in one undifferentiated motion. In this framework, these are explicit, sequential, and separately authoritative stages. A declaration is not evidence. Evidence is not analysis. Analysis is not verification. Verification is not approval. Approval is not canonical state. Each stage has its own actor type, authority requirement, and predicate.

Prior art.

What is novel in the composition. Common Criteria certifies a product version once, statically, at high cost. Peer review handles individual papers. Quality systems are heavyweight regulatory frameworks. The Verified Truth framework applies the same architectural separation continuously, lightweight, per-event, across multiple domains, with all stages preserved in one substrate. EXISTS for EquiWork lifecycle; CONFIDENTIAL DETAIL for exact composition mechanics; CONCEPT for application to scientific knowledge.

Move 3 — Make AI non-authoritative by design

The move. AI participates in the system as an analyst, not as an authority. AI-generated attestations are bounded by the framework architecture so that they cannot become canonical state without an explicit human approval event. The bound is structural — written into the protocol — not a runtime policy that could be relaxed under pressure.

Prior art.

What is novel in the composition. Most AI integrations claim human-in-the-loop as a policy or a UX choice. The Verified Truth framework makes AI's non-authoritative role structural — embedded in the protocol composition itself. There is no code path through which AI output becomes canonical without an explicit human approval event. The implementation specifics that enforce this are kept under invite or NDA per public-vs-protected content discipline. EXISTS in EquiWork's implementation; CONFIDENTIAL DETAIL for the enforcement composition.

Move 4 — Keep humans responsible for final approval, identified and accountable

The move. Every consequential acceptance — milestone approval, ownership transfer, sealing of a canonical record — requires a qualified human authority: a specific, identified, legally accountable person. Automation does not bypass this. The system is built so that the human cannot be removed from the loop.

Prior art.

What is novel in the composition. Existing systems require human approval at the signing moment. The Verified Truth framework requires identified human approval at every state transition that affects ownership or canonical state, not just at initial signing — and it preserves the chain of these approvals so that later review can see who approved what and on what evidence. EXISTS in EquiWork's implementation; PARTIAL in the sense that the legal weight this human approval chain carries in any specific jurisdiction is RESEARCH HYPOTHESIS until tested in dispute.

Move 5 — Connect agreements, contributions, products, and ownership under one event model

The move. The same predicates, the same authority model, the same audit discipline apply to a software contract (EquiWork), a bottle of wine (CAP via Tasting & Toasting), a contributor's equity (EquiWork's accepted-work profile), a painting's provenance (CAP for art conservation, planned), and a scientific career (Scientific Knowledge Passport, concept). Building a new vertical is integration work, not reinvention.

Prior art.

What is novel in the composition. No existing system we have surveyed applies the same predicate vocabulary, authority model, and audit discipline across agreements, physical objects, and scientific knowledge. The architecture is designed for this. The proposition that this single substrate works at production scale across all three domains is a RESEARCH HYPOTHESIS — only EquiWork is implemented end-to-end. CAP is in pilot discovery. Scientific Knowledge Passport is concept. The architectural moves required for the substrate to be domain-agnostic are made; the demonstration that they hold under load in all three verticals is forthcoming.

Move 6 — Preserve proof context at the moment reality happens

The move. Evidence is captured at the moment a Verified Event occurs, with all relevant context — timestamp, actor, surrounding state, supporting artifacts — preserved as part of the event record. The framework does not assume the system will be available to reconstruct context later; it captures everything that would be needed for future review at the moment of recording.

Prior art.

What is novel in the composition. Existing systems preserve fragments — flight data for crashes, forensic snapshots for investigations, timestamps for signed documents. The Verified Truth framework treats continuous proof-context preservation as the default operating mode, not as a special-purpose capability invoked on demand. The cost of doing this continuously is borne up front so that reconstruction later is not necessary. EXISTS for EquiWork's audit chain; CONFIDENTIAL DETAIL for exact mechanism; RESEARCH HYPOTHESIS for the claim that this lowers downstream dispute cost (testable in actual dispute scenarios, not yet tested).

Move 7 — Make accepted work, product provenance, and scientific knowledge part of the same trust architecture

The move. A person's verified contributions (work they have done that has been formally accepted), the verified provenance of physical objects they own or produce, and the verified history of their scientific or professional knowledge live in the same architecture with the same audit guarantees. A user's accepted-work profile (from EquiWork), object passports (from CAP), and scientific knowledge passport (from the SKP concept) are coherent views of one underlying event substrate.

Prior art.

What is novel in the composition. No existing system we have surveyed unifies accepted work + object provenance + scientific knowledge under a single trust architecture with a single audit discipline. The proposition that this unification is valuable — that a researcher's published work, the laboratory equipment provenance, and their contractual relationships with industrial partners belong in one preservation system — is the claim. CONCEPT + RESEARCH HYPOTHESIS. Demonstration requires real pilots in at least one vertical beyond agreements (CAP for wine is the nearest candidate). Universal demonstration requires all three working together.

What this architecture is for

It is for cases where any of the following are true:

It is not for cases where:

What this is not

To complement the preceding "what this is for", a calibrated list of what this is not. These are the boundaries.

How to read the rest of the doctrine in light of this document

This document sits between two other documents that ground specific claims:

When reading the public portal at truth.equiwork.io, every strong claim should fit into the matrix or the claims discipline document. If you find a claim that does not, that is a gap in the doctrine; please flag it.

The closing reformulation

We do not claim to invent provenance, signatures, formal verification, AI integration, blockchain, identity, or any of the primitives this work builds on.

We claim a specific composition of these primitives into an architecture that preserves evidence-backed, context-bound, human-approved operational truth at the moment it happens.

The invention is the architecture that connects components into a living verification process.

Status and revision

Status of the six deliverables

This document is Deliverable C of six requested in Mikhail Goman's scientific review. All six are now complete:

Companion documents