BUILD STATUS
NBX applies the same evidentiary discipline to its website that it is being built to apply to automated decisions. Implemented, active, planned, reserved, and unauthorized capabilities are not interchangeable.
NBX preserves the distinction between supporting evidence and externally established authority. This does not grant authority, issue permits, hold credentials, or enable production execution.
NBX is actively hardening the stage that characterizes what a proposed action may change and the scope through which consequences could propagate.
Later stages are intended to evaluate whether a governed action may approach a defined external adapter and to preserve evidence of what crossed that boundary and what occurred.
The pilot remains observational and read-only. It does not merge, deploy, promote, hold credentials, issue authority, or perform a production mutation.
The current site does not prove production deployment, production mutation, live authority issuance, credential custody, adapter enforcement, autonomous execution, autonomous remediation, final seal, customer validation, or compliance certification.
PUBLIC CLAIM BOUNDARY
Public communication is deliberately bounded. It must be accurate enough to evaluate NBX without publishing private implementation or implying capability that has not been proven.
Build completion does not independently authorize deployment, promotion, production egress, customer access, or autonomous execution. Repository truth controls publication status, and any material status change must be verified before publication.
BOUNDED PILOT CONVERSATION
Describe one action family, the initiating workflow, its evidence sources, the external authority boundary, the bounded change surface, and the receipt or replay outcome your organization must retain.