Evidence is not authority.
Model output, scanner results, tests, approvals, and observations remain evidence unless a separate authority boundary is satisfied.
ABOUT NBX
Automation should not inherit authority from momentum.
NBX is being built for environments where consequential actions must remain attributable, bounded, and replayable even when AI tools and automated systems operate faster than traditional review.
THE PROJECT THESIS
A proposal is not permission.
Modern systems can produce recommendations, code, configurations, transactions, and operational actions at machine speed. The difficult problem is not generation. It is preserving the difference between what a system observed, what it proposed, what an authority permitted, what crossed an external boundary, and what actually occurred.
NBX began as an architecture program in 2025, focused on preserving attributable evidence across consequential automated actions.
NBX is one private backbone with a defined initial commercial wedge and controlled future expansion. The project is being built in lawful stage order rather than assembled as a collection of loosely related automation products.
OPERATING PRINCIPLES
The boundaries are the product.
NBX is defined less by the number of systems it can connect to than by the assumptions it refuses to make.
Access is not permission.
Credentials and tool access do not prove that a particular action is permitted for a particular object, purpose, or time.
Mutation is not promotion.
A changed object does not become production-ready merely because it exists, passes a tool, or can be deployed.
Automation cannot self-approve.
The system proposing or executing an action cannot create its own authority by asserting intent, success, or urgency.
Private implementation. Public category. No inflated claims.
The website describes what NBX is, what it is being built to do, which pilot comes first, and which applications remain future governed domains. It does not expose private internals or present planned architecture as completed runtime capability.
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.