Status and attestation provenance

Candidate behavior — not yet released

This page describes next-release behavior in unpublished candidates: operator after v0.13.212, wrapper after v0.2.210 and agent after v0.13.168. Published releases do not provide this v2 provenance contract. Use the component versions for the published set.

Every status and attestation payload carries a provenance map. Its keys are JSON pointers to individual fields, array elements and empty collections. Missing or malformed tags fail the Wire coverage guard. The evidence type is imported from Wire by producers and consumers.

Tag	Meaning
measured	A dated observation; requires measured_at and a named method.
inferred	A deduction; requires its rule. It grants no Active protection or measured credit.
planned	A future control; it carries no measurement date or method.

Wrapper memory_tier reflects recorded allocation syscall outcomes. Repeated reads retain their observation time. anchor_mode uses validated, unexpired process-registration receipts. Readiness alone establishes neither property. Unavailable observations are inferred with a rule explaining their absence.

The agent labels per-vector attachment inventory measured only when its dynamic snapshot also passes the runtime attachment identity proof. Retained startup state and configured enforcement modes remain inferred. An attached hook does not by itself prove complete enforcement of all paths. With that same live proof, enforcement_healthy and lsm_active carry the live attachment inventory evaluation as their measurement method. Configuration and historical failures stay inferred.

The operator retains producer evidence on each check. active and measured_active require a valid measured observation. Inferred results remain in inferred_active, with zero protection credit. The v2 report signs the complete evidence separately while retaining the frozen v1 signature contract; older signatures do not authenticate the new fields.

Wrapper transport has a separate limit: the operator currently reads unauthenticated wrapper status over skip-verify HTTPS, without a response HMAC. Wrapper memory observations can earn measured points with HMACVerified=false. Here measured describes the reported syscall observation; it does not establish producer authenticity. The report signature authenticates what the operator collected, not the wrapper response. The agent path requires a verified response HMAC. Do not interpret wrapper measured credit as equivalent transport authentication.

CLI target audit labels annotation counts and DaemonSet readiness inferred. Its JSON uses annotatedWorkloads, annotatedCount, annotationCoveragePercent and ebpfAgentReady; these fields describe metadata and readiness rather than measured enforcement. target validate labels annotation counts inferred. CLI assess labels derived tiers inferred in text and JSON. Dated producer observations remain attached to their input fields; they never become a measured tier or a workload-delivery guarantee. Planned inputs remain planned.

A measurement establishes the named path at its observation time. Continuing protection, other nodes, a newer release and confidential-hardware key release require their own observations.