Skip to content
APP / PROTOCOL SPECIFICATION

Agentic Provenance Protocol Specification

The technical model for representing, correlating and independently verifying autonomous activity.

01

Scope

#scope

APP defines how provenance information about autonomous activity can be represented and exchanged across independently controlled systems.

02

Core Objects

#core-objects

Actor · Principal · Authority · Activity · Intent · Action · Observation · Evidence · Policy · Correlation · Execution · Outcome · Verification

03

Evidence Semantics

#evidence-semantics

Evidence states express whether a claim is verified, asserted, inferred, unresolved, conflicted, stale, revoked or unavailable. See the Evidence Model.

Open related model →
04

Correlation Semantics

#correlation-semantics

Correlation strength is represented independently from claim state so that related observations are not automatically treated as proven links.

Open related model →
05

State Evolution

#state-evolution

Historical observations remain immutable. Current state evolves as evidence is added, expires, conflicts or is revoked, without erasing earlier protocol history.

06

Identifiers

#identifiers

Implementations require stable identifiers for activities, observations and evidence so state can be referenced and correlated. These object definitions do not prescribe a canonical wire encoding; implementations must document their identifier and serialisation conventions.

07

Provenance

#provenance

Evidence retains its source, observation point, time context and derivation path so a verifier can understand why a claim is supported.

08

Verification

#verification

APP separates an original observation from subsequent independent verification of that observation or the claims derived from it.

09

Transport Independence

#transport-independence

APP does not require one transport. Representations may move through interfaces appropriate to the controlled boundary while preserving protocol semantics.

10

Versioning

#versioning

Evidence exchange requires explicit version context. These conceptual definitions do not establish a published version negotiation or compatibility contract.

11

Conformance

#conformance

These technical definitions are not a certification programme. No external ratification, published conformance test suite or universal adoption is claimed.