Evidence is not authority.
Tests, reviews, policies, observations, and model output may support a decision. They do not independently establish permission.
PUBLIC ARCHITECTURE
A governed action remains the same attributable object across every boundary.
The public architecture explains the structural contract around evidence, authority, impact, adapter position, replay, and lifecycle state. Private implementation details remain outside the public boundary.
ARCHITECTURAL INVARIANTS
Three distinctions cannot be collapsed.
These are structural rules, not interface labels. Each prevents a different form of silent authority transfer.
Authentication is not permission.
Knowing who or what produced a proposal does not establish that the proposal is authorized to cross an operational boundary.
Permission is not execution.
A bounded decision or decision receipt does not itself perform an external action, hold credentials, or create production effect.
ARCHITECTURAL PLANES
Three planes organize the public model.
Each plane has a distinct responsibility. No plane is permitted to silently absorb the responsibility of another.
Establish what is being requested.
Attributable object identity, custody, declared intent, evidence collection, correlation, and evidence integrity.
Establish whether the boundary is satisfied.
Evidence remains separate from external authority, bounded permission, impact classification, and adapter eligibility.
Preserve what the decision means.
Decision receipts, replay evidence, attributable outcomes, and explicit object lifecycle state.
The external boundary is observed and governed; it is not a shortcut to execution.
NBX is intended to preserve whether a proposed action approached or crossed a defined adapter boundary and what occurred afterward. Adapter evaluation does not grant authority, hold credentials, or perform the external action.
PUBLICLY EXPLAINED
- Structural planes and governing invariants
- Pilot operating boundary
- Initial wedge and controlled expansion posture
- High-level adapter, decision, replay, and lifecycle concepts
REMAINS PRIVATE
- Private schemas and internal data structures
- Validation logic, policy evaluation methods, and implementation records
- Security-sensitive adapter and enforcement mechanisms
- Private repository structure, receipt fields, and replay-binding mechanics
BOUNDED PILOT CONVERSATION
Bring NBX one consequential action boundary.
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.