K09 · bounded executable evidence infrastructure

Public and Protected Evidence Partitions

Direct answer

K09 publishes 4 partition profiles so public status and corrections remain visible without exposing protected facility or acquisition details.

Authority and disclosure boundary. K09 publishes static tools, synthetic fixtures, source-derived event records, signed offline imports, non-certifying traces, redacted procurement structures, and public/protected partition schemas. It does not perform live monitoring, reveal protected topology or credentials, decide awards, certify facilities, authorize operations, or prove factual truth from a signature.

Claim-level evidence boundary

VERIFIED PROJECT IMPLEMENTATION

Protected details are excluded

K09 workbook and evidence-partition tooling rejects credential and protected-topology fields from public fixtures.

Scope: K09 offline reference tools and synthetic fixtures.

Static validation is not a substitute for production access control, classification review, or secure storage.

SRC-W3C-PROV-O: PROV-O at a glance

Partition profiles

Public visibility rule

Public records may expose stable identity, bounded state, last review, corrections, limitations, machine records, challenge routes, and opaque protected-reference IDs. They must not expose credentials, private keys, exact protected coordinates, network topology, protection settings, privileged evidence, evaluator notes, detailed price records, or protected source-selection material.

Integrity and truth

A public record can be hashed and signed while still being incomplete or wrong. Partitioning controls disclosure; it does not independently establish truth, classification correctness, or authorization.