Skip to main content

Module provenance

Module provenance 

Source
Expand description

Declared reliance & judgement provenance as a DAG — the evidentiary substrate that keeps a natural person’s authorship and responsibility intact while making their toolchain auditable.

(Timothy, 2026-07-03; see docs/plans/adr-authority-attestation-guardianship-model.md §8/§9/§10.) When a natural agent forms a judgement for another person, they must declare which other agents informed it. A Reliance records who/what contributed and how; because a consulted agent carries their own JudgementProvenance (nested via Reliance::sub_provenance), informed_by is not a flat list — it is a directed acyclic graph of contributions.

Load-bearing distinctions:

  • Selfhood ≠ personhood, authorship stays with the natural person. A AgentType::SoftwareAgent is tooling & provenance — it never bears liability, but its use MUST be disclosed and scoped. The natural person responsible_agent bears authorship + responsibility.
  • Dual-timed veracity. Each contribution carries its veracity as reasonably assessed at the time (Reliance::veracity_at_time, against the JudgementProvenance::epistemic_horizon) and as later determined by forensic review (Reliance::veracity_determined). The gap between the two is exactly where the malice / negligence / honest-error distinction lives (§10).
  • Epistemic horizon is a content-addressed reference (Merkle root / checkpoint hash) to the information-state available to the agent at decision time — the hindsight-resistance mechanism.
  • Standing declaration. A RelianceDeclaration lets an agent declare, up front, which tools they MAY use, so a principal can consent to the toolchain before relying on the agent. An undeclared software agent discovered later is a serious integrity breach — see has_undeclared_ai.
  • Disclosure is two independent axes (subject vs other agents) over a proof modality; the process subject’s right-to-know is the first-class default (§9).

Structs§

AgentRef
A reference to a contributing agent. capacity is a role/credential term id (e.g. a professional registration URI); version pins a software agent or instrument to a specific version/configuration so result variation is attributable (§10).
DisclosurePolicy
Per-node disclosure policy over two independent axes (§9): what the process subject (the natural person the decision is about) may see, versus what other agents / institutions may see. The subject’s right-to-know is the first-class default; others get proportionate disclosure.
JudgementProvenance
The provenance of a single judgement: the natural (or other) agent responsible for it, the ordered set of contributions that informed it, an optional epistemic horizon, and free-form procedure notes. Because each Reliance may carry a nested sub_provenance, this type is recursively a DAG node.
Reliance
One contribution to a judgement — an edge in the provenance DAG. Records the contributing agent, the nature of reliance ("diagnostic-support", "drafting", "data-source", "consult", …), whether the agent/tool was used within its validated/insured scope, dual-timed veracity, and — when the contributor is itself an agent that formed a judgement — that contributor’s own nested provenance (sub_provenance), which is what makes informed_by a DAG rather than a flat list.
RelianceDeclaration
A standing declaration (capacity-level) of the agents/tools an agent MAY use, so a principal can evaluate and consent to the toolchain before relying on the agent (§8.2). This is not the per-judgement record; it is the up-front permission surface against which has_undeclared_ai checks actual reliance.

Enums§

AgentType
The kind of agent that contributed to a judgement. Weight and liability differ per kind (§8.1): a natural person bears authorship + responsibility; a software agent is tooling whose use must be disclosed and scoped but which never bears liability; an instrument has calibration/validation state; a dataset/source is provenance for input data. Modelled as an enum here (a closed, well-known set); finer agent-kind facets live in the extensible taxonomy.
DisclosureModality
The proof modality by which a provenance node (or the DAG) is disclosed (§9).
InputVeracity
Veracity of a contributed input, over the extended epistemic vocabulary (§10). Used dual-timed: once for the assessment at the time (against the epistemic horizon) and again for the later, forensic determination. The default is InputVeracity::Uncertain — nothing is assumed accurate.

Functions§

has_undeclared_ai
The integrity-breach detector (§8.3): returns true if any AgentType::SoftwareAgent appearing in jp.informed_by (recursively, through nested sub_provenance) is not covered by declaration’s permitted set (matched by AgentRef.id). An undeclared AI reliance discovered after the fact is a serious integrity breach — the omission is itself evidence.