DFT Evidence Ledger

The evidence ledger tracks what each public domain, application, implementation, and source record currently supports.

It separates:

  • source-bounded theory;
  • architecture models;
  • critical applications;
  • implementations;
  • publication records;
  • live-domain evidence;
  • missing evidence;
  • review gaps.

The ledger does not certify DFT.
It makes DFT easier to inspect.

Formalization Records: Tensor binding and fiber dynamics are currently classified as review-needed formalization records. They require independent review before operational or technical validation claims can be supported.

Cross-domain evidence ledger

What each domain supports — and what remains open

This ledger separates theory sources, architecture models, critical applications, implementations, publication records, domain evidence, and review gaps. Evidence supports scoped claims only; it does not validate the entire theory by itself.

RecordClassStatusSupportsMissingBoundary
Digital Fabrica Theorytheory-sourcesource-bounded
  • • root theory
  • • fabric model
  • • formalization program
  • • external peer review
  • • formal proof archive
  • • independent validation report
DFT is presented as a source-bounded research and architecture framework, not an externally validated universal theory.
DFT Architecture Stackarchitecture-modelsource-bounded
  • • DFDF
  • • FNS
  • • IDFF
  • • SIDS
  • • formal specification
  • • implementation conformance tests
  • • independent security review
The stack is an architecture model and formalization target, not a certified standard.
YellowChainyellowchain.orgcritical-applicationevidence-needed
  • • governance fabric
  • • identity fabric
  • • resource-ledger fabric
  • • current live-domain evidence
  • • DID implementation evidence
  • • resource-ledger operational evidence
  • • governance protocol specification
YellowChain is a strategic critical application. Operational DID, ledger, and governance claims require separate evidence.
New Millennium Frontiernewmillenniumfrontier.orgcritical-applicationlive-site-supported
  • • verifiable science coordination
  • • challenge registry
  • • publication provenance
  • • review workflows
  • • validator workflow evidence
  • • challenge registry evidence
  • • publication process evidence
  • • external review record
NMF is a coordination layer. It does not replace universities, journals, or external peer review.
CitizenSolarcitizen.solarcritical-applicationlive-site-supported
  • • storage-first energy fabric
  • • telemetry evidence
  • • Community Energy Bank
  • • BESS orchestration
  • • operational telemetry dataset
  • • grid/market participation evidence
  • • performance evidence
  • • regulatory boundary evidence
CitizenSolar is an energy infrastructure application domain. Operational and performance claims require published evidence.
CySyscy-systems.comcritical-applicationevidence-needed
  • • enterprise cybernetics
  • • knowledge fabric
  • • governance fabric
  • • execution fabric
  • • current live-domain evidence
  • • service model evidence
  • • case evidence
  • • deployment evidence
CySys is the enterprise infrastructure and advisory arm. Deployment, adoption, and audited infrastructure claims require source evidence.
Stitchiastitchia.xyzimplementationimplementation-candidate
  • • compliance-first DPI
  • • cfDAO workflows
  • • organization governance
  • • technical architecture packet
  • • compliance review
  • • security review
  • • operational status
Stitchia is an implementation candidate, not certified compliance infrastructure unless separately documented.
Global Freight Exchangefreight-exchange.orgimplementationimplementation-candidate
  • • logistics fabric
  • • freight capacity coordination
  • • supply-chain evidence
  • • marketplace operating evidence
  • • transaction evidence
  • • legal/settlement boundary
  • • carrier/user evidence
GFE is a logistics implementation candidate. It must not imply regulated exchange status, market scale, or live settlement without evidence.

Evidence Maturity

Each record is assigned a maturity level from M0 to M5.

The maturity level describes what the record may safely claim today and what evidence is needed to advance.

Maturity is not prestige.
It is claim discipline.

Maturity ladder

Claim strength follows evidence strength

A record can move upward only when evidence improves. This protects the public DFT corpus from implying more than the record supports.

Score 0

M0 — Mentioned

The entity, concept, or route is named, but has not yet been supported by current source evidence.

Score 1

M1 — Source-bounded

The claim is supported by an internal or public source record and has clear validation boundaries.

Score 2

M2 — Live-site supported

The claim is supported by reachable public route evidence, title, metadata, or page text.

Score 3

M3 — Implementation candidate

The claim is connected to a concrete implementation candidate with an evidence table and missing-evidence boundary.

Score 4

M4 — Operational evidence

The claim is supported by published operational evidence with scope, date, responsible entity, and limitations.

Score 5

M5 — External review

The claim is supported by independent review, certification, peer review, audit, or formal external evaluation within a clearly stated scope.

Evidence maturity

From mention to external review

Evidence maturity scores what each DFT record may safely claim today and what evidence is needed before stronger claims can be made.

M0 — Mentioned

Score 0

The entity, concept, or route is named, but has not yet been supported by current source evidence.

M1 — Source-bounded

Score 1

The claim is supported by an internal or public source record and has clear validation boundaries.

M2 — Live-site supported

Score 2

The claim is supported by reachable public route evidence, title, metadata, or page text.

M3 — Implementation candidate

Score 3

The claim is connected to a concrete implementation candidate with an evidence table and missing-evidence boundary.

M4 — Operational evidence

Score 4

The claim is supported by published operational evidence with scope, date, responsible entity, and limitations.

M5 — External review

Score 5

The claim is supported by independent review, certification, peer review, audit, or formal external evaluation within a clearly stated scope.

RecordCurrent levelReasonNext evidence needed
Digital Fabrica TheoryM1-source-boundedDFT has public theory, ontology, architecture, and source-boundary routes, but not external validation.
  • • canonical public source page
  • • DOI/archive records
  • • formalization route links
DFT Architecture StackM1-source-boundedDFDF/FNS/IDFF/SIDS are now publicly modeled and diagrammed, but not formal specifications or certified standards.
  • • technical architecture packets
  • • implementation conformance checklist
  • • layer-by-layer specification
YellowChainM1-source-boundedYellowChain is classified as a strategic governance/identity fabric, but current public route evidence remains incomplete.
  • • live domain capture
  • • governance fabric page
  • • DID fabric evidence boundary
New Millennium FrontierM2-live-site-supportedNMF has live-site support and is framed as a verifiable-science coordination layer, while validation boundaries remain explicit.
  • • challenge registry evidence
  • • validator workflow evidence
  • • publication review workflow evidence
CitizenSolarM2-live-site-supportedCitizenSolar has live public positioning as an energy infrastructure domain, but operational telemetry and deployment evidence remain pending.
  • • BESS architecture packet
  • • telemetry evidence boundary
  • • Community Energy Bank implementation status
CySysM1-source-boundedCySys is classified as enterprise cybernetic infrastructure/advisory arm, but live service/case evidence needs capture.
  • • live route inspection
  • • service model route
  • • case/evidence route
StitchiaM3-implementation-candidateStitchia is classified as a concrete implementation candidate, with evidence boundaries and missing technical/compliance review items.
  • • technical architecture packet
  • • operational status
  • • security/compliance boundary
  • • case evidence
Global Freight ExchangeM3-implementation-candidateGFE is classified as a concrete logistics implementation candidate, with explicit marketplace/settlement overclaim boundaries.
  • • marketplace status evidence
  • • transaction evidence boundary
  • • legal/settlement model
  • • technical architecture packet