assay project-enforcement-health¶

Project one existing assay.enforcement_health.v0 or assay.enforcement_health.v1 document, or one verified evidence bundle carrying assay.sandbox.degraded, into a lossy observation.

assay project-enforcement-health --format json --input PATH

--input is required. No input means no projection document and no claim.

Output¶

On success, stdout is exactly one assay.enforcement_health_projection.v0 document:

{"schema":"assay.enforcement_health_projection.v0","lossy":true,"source_schema":"...","observation":"applied|degraded|not_requested"}

source_schema is the input identity. Mapping:

active maps to applied only when the supporting producer invariants hold (v0 confirmed attach and strong; v1 both Landlock confirmations, strong, and no failure). Constructor-illegal active, v0 not_applicable, unknown schema or status, forged v1 absent, and malformed, missing, or oversized input exit nonzero with empty stdout.

Bundle input is integrity-verified before projection. The command selects by the event type, validates the existing typed degradation payload, and refuses missing, duplicate, unknown, tampered, oversized, or contradictory active-health input with empty stdout. Its bundle limits are 64 KiB compressed input, 1 MiB decoded input, 512 KiB event data, 1,000 events, and 64 KiB per event line.

Normative¶

Absence of a projection is no claim. It is never a pass. This command does not prove enforcement efficacy, egress absence, or a sealed sandbox.

For standalone health JSON, the projection checks coherence of an already-typed document, not authenticity or provenance. A coherent handwritten carrier can therefore project. For bundle input, verification establishes bundle integrity; it does not establish producer authenticity or enforcement efficacy.