DFEP / public working draft
The Dynamic Feed Evidence Protocol is a target architecture for exchanging, preserving and examining machine evidence across systems. The target is an open protocol; this page is a public, non-normative overview, not an accepted standard or a production conformance programme.
Protocol family
DFEP is being explored as an umbrella for interoperable evidence objects. The names below describe the intended protocol family, not production-ready protocol versions.
A source-attributed record of what was reported or measured, with time, freshness and limitations kept explicit.
Durable identifiers and lifecycle metadata for the entities that originate, relay or attest to evidence.
A record of a machine, model, tool or human interaction without overstating what the witness independently established.
A signed evidence artifact designed to preserve provenance and integrity while keeping the underlying claim separate.
A reproducible reconstruction of available historical evidence, policy inputs and declared dependencies.
Relationships among sources, observations, claims, witnesses, receipts, corrections and subsequent decisions.
Honest boundary
Dynamic Feed already operates evidence and receipt capabilities. DFEP is the additive direction intended to make those ideas independently implementable over time.
The platform exposes live data tools, specialist receipt families, signing and verification paths. Those capabilities predate DFEP and retain their existing contracts.
The draft direction is to define vendor-independent objects, algorithms and tests that another team could implement without relying on Dynamic Feed code.
Existing receipt bytes, signing semantics and legacy canonicalization are frozen. DFEP work must be additive. It cannot silently reinterpret, rewrite or invalidate historical receipts.
RFC 3161 and OpenTimestamps material may be present in current artifacts, but full independent cryptographic verification is not implemented for every path today. This page does not describe those timestamps as fully verified.
A valid signature can establish integrity and attribution under a key and scheme. It does not, by itself, prove that an underlying real-world claim is true.
DFEP and DFR have no accepted protocol version or standards-body approval.
Dynamic Feed does not currently claim that its platform, receipts or SDKs conform to DFEP.
The protocol direction preserves provenance, disagreement and limitations rather than certifying objective truth.
Open direction, earned authority
For the current legacy receipt format and additive draft context, read the receipt specification. That material is not a DFEP or DFR conformance claim. Explore the live product through Project Atlas.
