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.
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.
Static validation is not a substitute for production access control, classification review, or secure storage.
Partition profiles
PUBLIC
Public status record
6 allowed fields · 6 prohibited fields
CONTROLLED
Controlled technical evidence
7 allowed fields · 4 prohibited fields
PROTECTED
Protected facility annex
6 allowed fields · 1 prohibited fields
SOURCE_SELECTION_SENSITIVE
Protected source-selection annex
7 allowed fields · 2 prohibited fields
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.