1.2.0-rc.1 / Evidence and duties
Interpreting evidence
What signatures, observations and reports establish—and where they stop.
This RC1 documentation describes evidence carried by the current 1.2.0-draft.3 profiles; the native policy remains 1.2.0-draft.1.
Odexa distinguishes the terms that were accepted, what an instrumented boundary observed, and what a participant reported. Preserve those distinctions when displaying or counting records.
| Evidence | Supported interpretation |
|---|---|
| Agreement receipt | The appointed service recorded the authenticated client’s explicit acceptance of exact retained terms. A receipt is not an access token. |
| Gateway admission | This particular request passed the current authorization boundary. Admission alone is not completed delivery. |
| Gateway transport report | The named boundary reports completed or interrupted local response writes, with method, status and observed bytes. |
| Client report | The authenticated reporter made this claim about an operation or continuing storage. |
| Collector intake | The collector retained this exact authenticated report. It does not establish that the reported action happened. |
| Payment assertion | The appointed verifier asserted a state for the bound quote, mandate and agreement. It is not independently observed bank settlement. |
Assets and delivery
An asset reference binds an origin-controlled asset ID, immutable version ID, exact manifest payload digest and representation ID. A matching manifest links the declared metadata, length and digest to a published representation. Moving a URL does not transfer its access grant.
A full representation comparison requires the observed media metadata, decoded length and digest. Encoded bodies and decoded representations have separate byte domains. A range, HEAD or 304 response cannot establish full representation delivery. An interrupted write preserves its known local prefix; an admission without a terminal report remains unresolved.
Even a full local byte match does not prove remote application receipt, legal ownership, training or model influence. See asset evidence and gateway reporting for the exact qualifications.
Counts and unknown outcomes
Exact retries retain the original event and intake identity. Multiple reports about one operation do not create extra completed uses. Conflicting scope, purpose, agreement, terminal state or timing must remain visible rather than selecting a convenient winner. Continuing-storage checkpoints are separate from completed writes and inherit the accepted retention and use deadlines.
The optional observation_coverage_v1 registry declares observers, scopes and intervals. Its reporting ratios use a separately trusted journal of known expectations, such as admitted requests or reports awaiting an acknowledgement. Timely, late, missing, pending and conflicting outcomes remain distinct. Without a known denominator, the percentage is null. One report for one known admission does not mean every agent request was captured.
See measurement rules, observation coverage and storage contracts. Static policy publication alone observes no traffic.
Verifying an archive
Select the ordinary, storage, asset and free or paid archive profile explicitly. Verification checks its signed inventory, original bytes, required dependencies and message correlations using independently obtained origin and participant trust. Keys carried by the archive do not establish their own trust.
Closure applies to the declared source snapshot. It cannot prove that every event was recorded or disclosed elsewhere. Historical timestamps remain qualified source testimony. Import is inert: it supplies no credentials, transfers no live agreement and restores no access.
Start with free archives or paid archives. These are protocol evidence formats; the reference download’s file inventory is a separate, unsigned packaging record.