Verified Truth — Reference Bibliography

Document: VERIFIED_TRUTH_REFERENCES.md Version: 1.0 Date: 2026-06-26 Owner: Maxim Geller Status: Deliverable E of six requested in Mikhail Goman's scientific review

Preface

This bibliography lists the public-domain references that the Verified Truth Ecosystem builds on, operates alongside, or distinguishes itself from. The purpose is to give a serious reviewer the entry points to verify our positioning claims independently.

Each entry follows a standardised structure:

• Title
• Author / Organization · Year
• Link
• Why it matters — one sentence on its place in its field
• Relation to Verified Truth — one sentence on how it intersects with this work
• Limitation — one sentence on what it does not address
• Engagement — one of:
  • DEEPLY ENGAGED — we have read and synthesised this material; our claims about it are grounded in primary source
  • READ — we have read the source; secondary synthesis is from our notes
  • LISTED — the source is included for completeness; substantive engagement is pending

This honesty discipline matters because a reference list that pretends to have engaged sources it has not engaged is worse than a reference list that admits the gap. The LISTED items in this document are sources we believe we should engage with as the doctrine matures; they are flagged so a reviewer knows the calibration.

This is v1.0. A more complete narrative survey per category is provided in the companion Research Landscape Map (truth.equiwork.io/research/landscape), which extends each entry below into a full historical and current-state treatment. This document is the bibliographic backbone underneath that landscape.

1. Provenance Standards

1.1 W3C PROV-DM: The PROV Data Model

W3C Provenance Working Group · 2013 https://www.w3.org/TR/prov-dm/

• Why it matters. PROV is the W3C Recommendation that standardised how to model the provenance of digital artifacts using three core classes (Entity, Activity, Agent) and their relations.
• Relation to Verified Truth. Our Verified Event vocabulary is conceptually compatible with PROV's entity/activity/agent decomposition. We extend it with explicit approval semantics and authority levels.
• Limitation. PROV is descriptive; it does not include business workflow execution, approval predicates, or canonical state machines.
• DEEPLY ENGAGED

1.2 W3C PROV-O: The PROV Ontology

W3C Provenance Working Group · 2013 https://www.w3.org/TR/prov-o/

• Why it matters. The OWL2 expression of the PROV-DM model, enabling interoperable provenance representation across systems.
• Relation to Verified Truth. Provides a reference vocabulary that downstream consumers of Verified Events could map onto if interop is desired.
• Limitation. RDF/OWL-based; not directly used in our internal implementation but available as an export target.
• READ

1.3 PROV-Overview

W3C Provenance Working Group · 2013 https://www.w3.org/TR/prov-overview/

• Why it matters. The non-technical entry point to the PROV family, useful for reviewers without W3C-document fluency.
• Relation to Verified Truth. The most accessible reference for understanding the provenance literature this work positions itself relative to.
• Limitation. High-level only; technical specifics require the individual documents.
• DEEPLY ENGAGED

2. Formal Verification and Temporal Logic

2.1 The Temporal Logic of Programs

Amir Pnueli · 1977 Proceedings of the 18th Annual Symposium on Foundations of Computer Science (FOCS 1977), pages 46–57. DOI: 10.1109/SFCS.1977.32

• Why it matters. The founding paper of temporal logic in computer science. Introduced linear temporal logic as a framework for reasoning about reactive and concurrent programs over time. ~5,800+ citations.
• Relation to Verified Truth. Our Verified Event substrate operates on temporal sequences with implicit before/after relations; the literature underpinning rigorous reasoning about such sequences begins here.
• Limitation. Pure temporal logic does not address evidence, approval, or human authority — concerns that sit outside its mathematical scope.
• READ

2.2 Temporal Verification of Reactive Systems: Safety

Zohar Manna, Amir Pnueli · 1995, Springer ISBN: 978-0387944593

• Why it matters. The canonical textbook on safety and liveness properties of reactive systems via temporal logic.
• Relation to Verified Truth. Provides the formal vocabulary for distinguishing "something bad never happens" (safety) from "something good eventually happens" (liveness) — both relevant to the EquiWork lifecycle invariants.
• Limitation. Mathematical model; does not address how human-bearing actors fit into the formalism.
• LISTED

2.3 The Temporal Logic of Actions (TLA)

Leslie Lamport · 1994 ACM Transactions on Programming Languages and Systems, Vol. 16(3), pages 872–923 https://lamport.azurewebsites.net/pubs/lamport-actions.pdf

• Why it matters. Combines first-order logic, set theory, and temporal logic into a specification language usable in industry. TLA+ (the language) and TLC (the model checker) are used at AWS, Microsoft, and Intel to verify distributed protocols.
• Relation to Verified Truth. TLA+ could be used to formally verify the EquiWork canonical state machine. We do not yet do this; it remains a strong candidate for hardening the protocol.
• Limitation. Proves the design, not what actually happened in production. Verified Truth handles what TLA+ does not: the record of execution.
• DEEPLY ENGAGED

2.4 seL4: Formal Verification of an Operating-System Kernel

Gerwin Klein, June Andronick, Kevin Elphinstone, et al. · 2010 Communications of the ACM, Vol. 53(6), pages 107–115. DOI: 10.1145/1743546.1743574 https://cacm.acm.org/research/sel4-formal-verification-of-an-operating-system-kernel/

• Why it matters. First complete machine-checked functional correctness proof of a general-purpose OS kernel (8,700 lines of C + 600 lines of assembly), verified in Isabelle/HOL.
• Relation to Verified Truth. Demonstrates that formal verification at production scale is achievable for critical infrastructure code. A precedent for the level of rigor we aspire to in EquiWork's protocol implementation.
• Limitation. Resource cost is substantial; verifying every line of an application stack is currently impractical.
• READ

2.5 A Formally Verified Compiler Back-End

Xavier Leroy · 2009 Journal of Automated Reasoning, Vol. 43(4), pages 363–446 CompCert: https://compcert.org

• Why it matters. CompCert is a formally verified optimising C compiler with a machine-checked Coq proof that compiled assembly preserves the semantics of source C.
• Relation to Verified Truth. Another precedent demonstrating that proof-assistant-grade verification is achievable for production tools.
• Limitation. Coq proofs are time-intensive; the technique applies to small surface-area components, not whole web applications.
• READ

2.6 The Coq Proof Assistant (now Rocq)

INRIA / Coq development team · 1989+ https://rocq-prover.org

• Why it matters. The most widely used proof assistant for verifying mathematical theorems and program correctness. Used in CompCert, the Four Color Theorem proof, the Feit-Thompson theorem proof.
• Relation to Verified Truth. A tool that could be used to prove invariants of the Verified Truth protocol (e.g., that no code path lets AI emit an approval predicate).
• Limitation. Interactive proof construction; requires substantial expertise.
• LISTED

2.7 Isabelle/HOL

Lawrence Paulson, Tobias Nipkow, Makarius Wenzel et al. · 1986+ https://isabelle.in.tum.de

• Why it matters. The proof assistant used to verify seL4. Higher-order logic based, with the Isar structured proof language.
• Relation to Verified Truth. Alternative to Coq for any future formal verification work on the protocol.
• Limitation. Same as Coq — high expertise required, resource-intensive.
• LISTED

3. Security Certification

3.1 ISO/IEC 15408 — Common Criteria for Information Technology Security Evaluation

ISO/IEC JTC 1/SC 27 · Current revision 2022 https://www.iso.org/standard/72891.html Portal: https://www.commoncriteriaportal.org

• Why it matters. The international standard for IT product security certification. Multi-part standard (Parts 1–5) covering requirements, security functional requirements, security assurance requirements, evaluation methodology, and Protection Profile templates.
• Relation to Verified Truth. Common Criteria's separation of Protection Profile (user's needs), Security Target (vendor's claim), Target of Evaluation (the artifact), and independent evaluator was a direct architectural inspiration for separating concerns in the Verified Truth framework.
• Limitation. Static, point-in-time, heavyweight, restricted to IT products. Verified Truth applies the same architectural separation continuously and across multi-domain scope.
• DEEPLY ENGAGED

3.2 Common Criteria Recognition Arrangement (CCRA)

Multiple national certification bodies · current https://www.commoncriteriaportal.org/ccra/

• Why it matters. The international agreement that allows Common Criteria certificates issued in one member country to be recognized in others.
• Relation to Verified Truth. Conceptual precedent for cross-jurisdiction trust transfer.
• Limitation. Limited to specific assurance levels and product categories.
• READ

4. Distributed Ledgers and Oracles

4.1 ChainLink: A Decentralized Oracle Network

Steve Ellis, Ari Juels, Sergey Nazarov · 2017 (whitepaper); 2019 mainnet https://link.smartcontract.com/whitepaper

• Why it matters. The first major decentralized oracle network. Addresses "the oracle problem" — how deterministic on-chain code can react to off-chain data without reintroducing a single point of failure.
• Relation to Verified Truth. EquiWork could use Chainlink CCIP for cross-chain settlement, VRF for randomized reviewer selection. Infrastructure component, not substrate.
• Limitation. Aggregates what data sources report; garbage in, garbage out. No human approval semantics.
• DEEPLY ENGAGED

4.2 DECO: Liberating Web Data Using Decentralized Oracles for TLS

Fan Zhang, Sai Krishna Deepak Maram, Harjasleen Malvai, Steven Goldfeder, Ari Juels · 2020 USENIX Security 2020 / Cornell University https://www.deco.works

• Why it matters. Zero-knowledge proof that web data (over TLS) was retrieved authentically from a source, without requiring the source to participate.
• Relation to Verified Truth. Potential primitive for evidence collection from web sources in a future Verified Truth evidence adapter layer.
• Limitation. Not yet widely deployed; specific to TLS-secured web sources.
• LISTED

4.3 EIP-712: Ethereum typed structured data hashing and signing

Remco Bloemen, Leonid Logvinov, Jacob Evans · 2017 (proposal); 2018 production https://eips.ethereum.org/EIPS/eip-712

• Why it matters. The standard that lets users sign structured data (not raw bytes) in their wallets with human-readable previews. Widely adopted across DeFi, NFTs, and Web3 governance.
• Relation to Verified Truth. EquiWork uses EIP-712 for binding signatures on agreement payloads. The cryptographic primitive is solved by this standard.
• Limitation. Ethereum-ecosystem-specific; alternatives exist (CMS, JWS) for other contexts.
• DEEPLY ENGAGED

5. Supply Chain Provenance

5.1 IBM Food Trust

IBM · 2018 general availability (Walmart pilot 2016) https://www.ibm.com/products/supply-chain-intelligence-suite/food-trust

• Why it matters. The most-deployed industrial provenance system, built on Hyperledger Fabric. Famous for reducing mango-to-farm trace from 6+ days to 2.2 seconds at Walmart. Members include Walmart, Carrefour, Nestlé, Unilever, Dole, Tyson Foods.
• Relation to Verified Truth. Proof point that immutable industrial logistics traceability works at scale. CAP applies the same idea across multiple verticals from a unified substrate.
• Limitation. Food-only; permissioned consortium; covers logistics events but not the agreements that produced the goods.
• DEEPLY ENGAGED

5.2 GS1 Digital Link

GS1 · v1.1.1 current; 2027 global sunrise for 2D barcodes at retail https://www.gs1.org/standards/gs1-digital-link

• Why it matters. Encodes traditional product identifiers (GTIN, GLN, SSCC, batch, expiry) into web-addressable URIs while maintaining POS scanner compatibility. Used by 2+ million companies globally.
• Relation to Verified Truth. CAP can use GS1 Digital Link as one of several identity inputs for physical objects.
• Limitation. Identification standard, not verification system. Content at the resolved URL is whatever the brand puts there.
• DEEPLY ENGAGED

5.3 Oracle Blockchain Platform / GoDirect Trade

Oracle / Honeywell Aerospace · 2018+

• Why it matters. Production example of industrial-grade blockchain provenance for aerospace parts marketplaces.
• Relation to Verified Truth. Demonstrates demand for high-value object provenance in industrial verticals.
• Limitation. Industry-specific; same overall limitations as IBM Food Trust.
• READ

5.4 DSCSA — Drug Supply Chain Security Act

United States Congress · 2013; phased enforcement through 2023 https://www.fda.gov/drugs/drug-supply-chain-integrity/drug-supply-chain-security-act-dscsa

• Why it matters. US federal law requiring electronic, interoperable serialization and tracing of prescription drugs through the supply chain.
• Relation to Verified Truth. Domain-specific regulation that prefigured the requirements Verified Truth implements as architectural defaults.
• Limitation. US-only; pharmaceutical-only.
• LISTED

5.5 HL7 FHIR Provenance Resource

HL7 International · FHIR R5 current https://www.hl7.org/fhir/provenance.html

• Why it matters. The healthcare industry standard for representing provenance metadata in interoperable patient and clinical records.
• Relation to Verified Truth. A domain-specific instance of provenance modeling; demonstrates that healthcare requires structured evidence capture.
• Limitation. FHIR-specific; not directly applicable outside healthcare without translation.
• LISTED

6. Digital Identity and Trust Services

6.1 W3C Verifiable Credentials Data Model v2.0

W3C Verifiable Credentials Working Group · 2025 (Recommendation) https://www.w3.org/TR/vc-data-model-2.0/

• Why it matters. The W3C standard for cryptographically verifiable claims about a subject, supporting privacy-preserving selective disclosure.
• Relation to Verified Truth. Identity primitives that EquiWork could integrate as the identity layer of its actor model.
• Limitation. Identity attestation only; does not address lifecycle composition or business workflow.
• DEEPLY ENGAGED

6.2 W3C Decentralized Identifiers (DIDs) v1.0

W3C Decentralized Identifier Working Group · 2022 (Recommendation), v1.1 Candidate Recommendation 2026 https://www.w3.org/TR/did-1.1/

• Why it matters. The W3C standard for self-sovereign identifiers (did:method:identifier syntax) that resolve to verifiable identity metadata without centralized authority.
• Relation to Verified Truth. Candidate identity scheme for Verified Truth actors; complementary to W3C VCs.
• Limitation. Multiple methods (did:key, did:ion, did:web, etc.) with varying maturity.
• READ

6.3 eIDAS — Regulation (EU) 910/2014 on electronic identification and trust services

European Parliament and Council · 2014 https://eur-lex.europa.eu/eli/reg/2014/910/oj

• Why it matters. The EU regulation establishing Simple, Advanced, and Qualified Electronic Signatures (QES) with legal equivalence to handwritten signatures across the EU.
• Relation to Verified Truth. Future integration target for legal-weight signatures in EU jurisdictions.
• Limitation. EU-only legal framework; QES providers are accredited and limited.
• DEEPLY ENGAGED

6.4 eIDAS 2.0 — Regulation (EU) 2024/1183

European Parliament and Council · 2024 https://eur-lex.europa.eu/eli/reg/2024/1183/oj

• Why it matters. The 2024 revision adding the EU Digital Identity Wallet (EUDI Wallet), qualified electronic attestations of attributes, and convergence with W3C VC/DID standards.
• Relation to Verified Truth. Future-state identity infrastructure for EU users; the EUDI Wallet may become a primary identity input.
• Limitation. Implementation rollout phased through 2026-2030; jurisdictional coverage still EU-only.
• READ

6.5 RFC 3161 — Time-Stamp Protocol (TSP)

IETF · 2001 https://datatracker.ietf.org/doc/html/rfc3161

• Why it matters. The internet standard for cryptographic timestamping by trusted third parties.
• Relation to Verified Truth. A primitive for proving "this event happened no later than time T" when stronger guarantees than block height are needed.
• Limitation. Requires trust in the TSA (Time Stamping Authority).
• LISTED

7. Academic Knowledge Provenance

7.1 ORCID — Open Researcher and Contributor ID

ORCID Inc. · 2012 https://orcid.org

• Why it matters. Persistent identifier for individual researchers (16-digit format, e.g., 0000-0002-1825-0097). 24+ million records as of 2025.
• Relation to Verified Truth. The identity foundation for the Scientific Knowledge Passport concept. We build on, not replace.
• Limitation. Identifies the researcher but says nothing about the structure of their work history beyond linked publications.
• DEEPLY ENGAGED

7.2 ISO 26324 — Digital Object Identifier system

ISO · 2022 (current revision) https://www.iso.org/standard/81599.html

• Why it matters. The international standard for persistent identifiers of digital objects (papers, datasets, books, preprints, grants).
• Relation to Verified Truth. DOIs identify scholarly outputs; the Scientific Knowledge Passport uses them as references rather than reinventing.
• Limitation. Identification standard; the resolved metadata depends on the registrar.
• DEEPLY ENGAGED

7.3 Crossref

Crossref · 2000+ https://www.crossref.org

• Why it matters. The largest DOI registrar (~180 million scholarly publications), maintaining 2+ billion citation links connecting the corpus.
• Relation to Verified Truth. Existing infrastructure for "who cited whom" that the Scientific Knowledge Passport would compose with, not replace.
• Limitation. Citation network only; does not capture experimental evidence, laboratory equipment provenance, or mentorship lineage.
• DEEPLY ENGAGED

7.4 DataCite

DataCite · 2009 https://datacite.org

• Why it matters. DOI registrar for research data and other non-traditional scholarly outputs. 92+ million records.
• Relation to Verified Truth. Identifier service for the dataset references that would be linked from Scientific Knowledge Passport experimental records.
• Limitation. Same as Crossref — identifies, does not preserve experimental context.
• READ

7.5 ROR — Research Organization Registry

ROR Community · 2019+ https://ror.org

• Why it matters. Open persistent identifiers for research organizations, replacing fragmented institutional identifiers (Funder ID, Ringgold, GRID).
• Relation to Verified Truth. Identifier scheme for institutional affiliations in the Scientific Knowledge Passport.
• Limitation. Organization-level; does not address sub-institutional structure (departments, laboratories).
• READ

7.6 OpenAlex

OurResearch · 2022+ https://openalex.org

• Why it matters. Open, free aggregate of ~240 million scholarly works from Crossref, ORCID, DataCite, and additional sources. Successor to Microsoft Academic Graph.
• Relation to Verified Truth. Reference graph the Scientific Knowledge Passport can query to enrich researcher profiles with publication-level context.
• Limitation. Aggregator; quality depends on upstream sources.
• READ

8. Theoretical Foundations

8.1 How to Do Things with Words

J.L. Austin · William James Lectures 1955; published posthumously 1962, Oxford University Press ISBN: 978-0198245537

• Why it matters. The founding work of speech act theory. Distinguishes "constative" utterances (describing facts) from "performative" utterances (doing things — promising, naming, sentencing).
• Relation to Verified Truth. Contracts are performative utterances par excellence: "I agree" creates the agreement rather than describing it. The framework's treatment of agreements as event records that do something legal owes structurally to this distinction.
• Limitation. Philosophical analysis; not engineered as a system specification.
• READ

8.2 Speech Acts: An Essay in the Philosophy of Language

John R. Searle · 1969, Cambridge University Press ISBN: 978-0521096263

• Why it matters. The systematic development of speech act theory after Austin. Categorises illocutionary acts (assertives, directives, commissives, expressives, declaratives) and analyses their felicity conditions.
• Relation to Verified Truth. The framework's separation of declaration, evidence, analysis, verification, approval, and canonical state can be read as making explicit the felicity conditions that contracts implicitly rely on.
• Limitation. Philosophical theory; subsequent legal and computational applications are by others.
• READ

8.3 Event sourcing as a software architecture pattern

Greg Young, Martin Fowler, and others · mid-2000s onwards Foundational essays: https://www.martinfowler.com/eaaDev/EventSourcing.html

• Why it matters. The software architecture pattern of treating application state as a sequence of events from which any current view is derived. Widely adopted in domain-driven design and CQRS architectures.
• Relation to Verified Truth. The Verified Event substrate is conceptually adjacent to event sourcing but designed for human reasoning about what happened, not for software state management.
• Limitation. Event sourcing addresses application state; does not include authority, evidence, or approval semantics by itself.
• READ

8.4 EU AI Act — Regulation (EU) 2024/1689

European Parliament and Council · 2024 https://eur-lex.europa.eu/eli/reg/2024/1689/oj

• Why it matters. The first comprehensive AI regulatory framework, requiring effective human oversight for high-risk AI systems.
• Relation to Verified Truth. Our architectural commitment to AI being structurally non-authoritative aligns with and exceeds the AI Act's oversight requirements.
• Limitation. EU regulation; enforcement provisions phased through 2026.
• READ

8.5 Sarbanes-Oxley Act, Sections 302 and 404

United States Congress · 2002

• Why it matters. Required named executives to personally attest to financial controls; a US regulatory move to put a specific human's name on an attestation rather than just an organisation's seal.
• Relation to Verified Truth. Precedent for requiring identified, accountable individual humans at consequential approval points.
• Limitation. US public-company financial reporting only.
• LISTED

9. Cryptographic Primitives Used

9.1 FIPS PUB 180-4 — Secure Hash Standard (SHA-256, SHA-3 family)

NIST · 2015 (current revision) https://csrc.nist.gov/pubs/fips/180-4/upd1/final

• Why it matters. The US Federal standard defining the SHA-2 family of cryptographic hash functions. SHA-256 is the most widely used.
• Relation to Verified Truth. SHA-256 is used to anchor agreement content hashes at the moment of freezing. Standard primitive, no proprietary modification.
• Limitation. Not quantum-resistant; future migrations may be needed.
• DEEPLY ENGAGED

9.2 RFC 6234 — US Secure Hash Algorithms

IETF · 2011 https://datatracker.ietf.org/doc/html/rfc6234

• Why it matters. The IETF informational reference for SHA-2 family implementations.
• Relation to Verified Truth. Reference for SHA-256 conformance.
• Limitation. Informational only; the normative standard is FIPS 180-4.
• LISTED

10. What is NOT in this bibliography (honest gap declaration)

A bibliography is a statement of what we have engaged with. The following are categories or sources that should be in a complete bibliography but are not yet, with honest reasons:

10.1 Speech act applications in digital contract law

There is substantial literature applying Austin and Searle to digital contracts, smart contracts, and electronic agreements (Reidenberg, Hildebrandt, and others). We have read Austin and Searle directly but have not synthesised the secondary legal-philosophical literature. The companion Research Landscape Map sketches this gap; deeper engagement remains future work.

10.2 GDPR provenance extensions

The European data-protection community has developed several provenance extensions specifically for GDPR compliance (GDPRtEXT, SPIRIT, etc.). These are listed for completeness but not yet engaged with at depth. Future engagement is on the path forward.

10.3 Industrial accountability frameworks

Frameworks like NIST SP 800-53 (security controls), COBIT, and ITIL address accountability and audit at the organisational level. They are adjacent to Verified Truth's discipline but operate at a different scope. Listed here for awareness; not yet engaged.

10.4 Detailed pharmaceutical and automotive serialisation standards

DSCSA (above) is listed; deeper engagement with EU FMD, GS1 EPCIS for serialisation, and PEPPOL for cross-border procurement is owed.

10.5 Scientific reproducibility and research provenance literature

Vincent Cerf's work on long-term digital preservation, the FAIR data principles (Findable, Accessible, Interoperable, Reusable), and the broader open science movement intersect directly with the Scientific Knowledge Passport concept. Listed here as gap; deep engagement belongs to a Scientific Knowledge Passport white paper rather than this general bibliography.

10.6 Formal contracts and smart contract languages

Solidity, Vyper, Move, Marlowe, DAML, and other domain-specific languages for executable contracts have substantial design literature behind them. We have read several whitepapers; full engagement is pending.

10.7 Russian-language scientific provenance literature

Given the founder's bilingual context and the Russian aerospace research tradition (ЦАГИ, etc.), Russian-language work on scientific provenance, archive theory, and academic genealogy belongs in this bibliography. None is currently engaged.

How to use this bibliography

As a reviewer: Use it to verify our positioning claims independently. If a claim in the public portal references W3C PROV (for example), trace the claim to entry 1.1 here, then to the W3C source itself.

As an author writing new material: If a new strong claim invokes prior art, add the relevant reference here with appropriate engagement tag. Do not invoke sources you have not engaged with.

As a researcher considering deeper review: The LISTED entries are honest gaps. If your expertise covers any of them, your contribution would be valuable.

Companion documents

• truth.equiwork.io/research/landscape — Deliverable A (narrative survey of eight intellectual fields)
• VERIFIED_TRUTH_COMPARISON_MATRIX.docx — Deliverable B (17 systems × 11 columns)
• truth.equiwork.io/research/whats-new — Deliverable C (seven structural moves against prior art)
• truth.equiwork.io/research/claims-discipline — Deliverable D (every claim status-badged)
• RESPONSE_TO_SCIENTIFIC_REVIEWER.md — Deliverable F (Memo to Mikhail Goman, private)
• verified-truth-v3.html and verified-truth-v3-ru.html — public portal v3
• related-work-data.json — structured reference data for the nine Related Work cards in the portal

Status of the six deliverables

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

• ✅ A — Research Landscape Map · truth.equiwork.io/research/landscape
• ✅ B — Comparison Matrix · VERIFIED_TRUTH_COMPARISON_MATRIX.docx
• ✅ C — What Is New Here? · truth.equiwork.io/research/whats-new
• ✅ D — Claims Discipline · truth.equiwork.io/research/claims-discipline
• ✅ E — Reference Bibliography (this document) · truth.equiwork.io/research/references
• ✅ F — Reviewer Response Memo (private correspondence to the reviewer)

Status and revision

• Version 1.0 (2026-06-26). First comprehensive bibliography of the Verified Truth Ecosystem.
• Future versions will deepen the LISTED entries to READ or DEEPLY ENGAGED as engagement extends, and may add fields (DOI, ISSN, secondary citations).

Acknowledgement

This bibliography exists because Mikhail Goman's review made explicit what every serious work of synthesis needs: visible engagement with the prior art that defines its field. The references included are the ones we have engaged with substantively. The references listed as gaps are the work that follows.