Public Contract is the accessible front door to a family of independent browser workstations. Examine how a system is evaluated, compare a baseline with a candidate, or investigate technical compliance conditions—without confusing a software result with legal approval.
OPEN / REVIEW_REQUIRED / HALT are technical states, not government authorization.
Each route has a distinct purpose. Start with the goal; move between workstations using the shared navigation.
Read the Public Contract series and examine the browser laboratory for execution boundaries, Transformer reference paths, receipts, and evidence construction.
Open this when: understanding how an action moves from proposal to a bounded, inspectable result is the goal.
Compare declared baseline and candidate JSON, CSV, or text through exact, structural, typed, or schema checks. Produce local SHA-256 evidence receipts and maintain a browser-local ledger.
Open this when: a change must be tested against explicit criteria, with differences localized and results preserved.
Explore the regulatory workspace within the Forge. Inspect applicability assumptions, conditional classifications, review requirements, technical signals, and evidence boundaries.
Open this when: tracing why a proposed use case needs particular controls, review, or evidence is the priority.
Public workstations are available for inspection and bounded demonstrations. Commercial implementation, authorization services, integrations and formal deliverables require separately agreed scope and licensing.
Review the architecture, demonstration boundary and published reference materials.
Choose Verify, Compliance or Forge; each runs within its own documented scope.
Draft local requirements, then initiate contact through the listed business channel.
Reference records, workstation outputs, and production authorizations are separate evidence classes. Inspect the published material and the explicit outstanding gates.
Explore the evidence registry →