Signals → Governance → Authorization Decision → Execution Runtime → Runtime Provenance → Attestation
1. Execution environment capture

Each execution records runtime metadata such as:

runtime version
system configuration
execution environment (container, node, service)
execution timestamp (metadata only, not used in decisioning)

This information is NOT part of decision logic.

2. Governance isolation guarantee

Runtime Provenance is strictly separated from Governance evaluation.

Governance only consumes:

verified signals
signed policies

It does NOT consume runtime state.

3. Execution context binding

Each execution is bound to:

executionId
Authorization Decision
runtime identity
system configuration snapshot

This ensures full traceability of execution conditions.

4. Observability vs determinism separation

Runtime data is used for:

auditing
debugging
verification

It is NOT used for:

decision making
policy evaluation
authorization logic

This preserves determinism.

5. Attestation integration

Runtime Provenance is included in the final attestation.

The attestation records:

decision hash
signal hash
policy version
runtime identity
execution environment hash

This enables full verification of execution conditions.

Properties of Runtime Provenance
Environment traceability

Every execution can be mapped to its runtime environment.

Deterministic isolation

Runtime state does not affect decisions.

Audit completeness

Full execution context is preserved for verification.

Cryptographic binding

Runtime metadata is anchored in attestations.

Failure behavior

If runtime provenance cannot be captured:

→ execution proceeds but is flagged in audit logs

If attestation integrity is impacted:

→ verification fails (fail-closed)

Summary

Runtime Provenance ensures that:

execution environment is fully traceable
governance remains deterministic and isolated
runtime context is preserved for audits
every decision can be independently verified end-to-end