Skip to content

Navigation Menu

Appearance settings

View all features
View all solutions
- EXPLORE BY TOPIC
  AI
  Software Development
  DevOps
  Security
  View all topics
- EXPLORE BY TYPE
  Customer stories
  Events & webinars
  Ebooks & reports
  Business insights
  GitHub Skills
- SUPPORT & SERVICES
  Documentation
  Customer support
  Community forum
  Trust center
  Partners
View all resources
- COMMUNITY
  GitHub SponsorsFund open source developers
- PROGRAMS
  Security Lab
  Maintainer Community
  GitHub Stars
  Archive Program
- REPOSITORIES
  Topics
  Trending
  Collections
- ENTERPRISE SOLUTIONS
  Enterprise platformAI-powered developer platform
- AVAILABLE ADD-ONS
  GitHub Advanced SecurityEnterprise-grade security features
  Copilot for BusinessEnterprise-grade AI features
  Premium SupportEnterprise-grade 24/7 support
Pricing

Appearance settings

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

Uh oh!

There was an error while loading. Please reload this page.

banza-protocol / banza Public

Notifications You must be signed in to change notification settings
Fork 0
Star 0

Code
Issues
Pull requests 1
Actions
Security and quality
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Security and quality
Insights

docs(website): record the completed Website Phase 2 merge and production deployment - #33

#33

Open

fm65 wants to merge 3 commits into

mainbanza-protocol/banza:mainfrom

docs/phase2-merge-and-deployment-recordbanza-protocol/banza:docs/phase2-merge-and-deployment-recordCopy head branch name to clipboard

Conversation Commits3 (3)Checks Files changed

Open

docs(website): record the completed Website Phase 2 merge and production deployment#33
fm65 wants to merge 3 commits into
mainfrom
docs/phase2-merge-and-deployment-record

docs(website): the ledger said frozen, and the system had moved on fo…

4f26c47

Select commit

Loading

Failed to load commit list.

Uh oh!

There was an error while loading. Please reload this page.

Sign in for the full log view

Repository Purity on: pull_request 1

No non-protocol artifacts in BANZA

Identity Guard on: pull_request 122

No operator-specific brand in BANZA

No central human authority over operators

Public surfaces present only the active model

Operator verification is Workbench-only

Governance docs present only the active model

Homepage final public-release contract

Homepage final audit & premium polish

Footer BanzAI/Guide + Operador Zero navigation

Global navigation is three distinct destinations

Homepage keeps the minimal public-release shape

Homepage layout — left-aligned headings, short footer boundary, clean copy

BanzAI resolves explicit ADR/RFC documents before generation

BanzAI documentary answers are scoped to what was asked

Reference chapter order — Operador Zero at 09

Operador Zero stays a simulator

Operador Zero vocabulary contract

Operador Zero public surface hardened

zero.banza.network single-page lab design

zero.banza.network host-aware routing

Operador Zero read-only reference surface

Operador Zero cross-browser routing

BanzAI single canonical interface

Operador Zero standalone surface

Operador Zero full E2E protocol validation

Operador Zero realistic demo journey

Operator Zero Only demo/example policy

Rust and UI cannot disagree about a slug

BanzAI release QA gate intact

Operator journey closed end to end, one evaluator

BanzAI session context reflects real validation state

Public copy matches the deployed protocol-agent architecture

Official SVGs pass the visual-quality policy

Official SVGs follow the canonical visual system

BanzAI is the native protocol agent, not an authority

PostgreSQL holds protocol state, not financial value

Operator onboarding contract

Operador Zero origin-proof closure

BanzAI operator-experience canonicalization

BANZA Whitepaper v1.0 contract (WP1-FINAL)

Public technical claims — executable evidence gate

Whitepaper canonical-source boundary (Overleaf PT dossier is the source)

Whitepaper canonical build is reproducible (hermetic verify)

Trust-invariant realignment

Reference information architecture is canonical

Layer/profile naming split is canonical (Camada 1/2/3 vs L0–L4)

Estado Protocolar keeps PostgreSQL as implementation, not protocol (Ch05)

Confiança keeps the trust boundary — root signs only the Key Manifest, trust ≠ certification...

Conformidade e Certificação keeps distinctions — L0–L4 profiles ≠ layers/certificates, va...

Operadores keeps operator (entity) ≠ implementation (evaluated subject) — one operator → ma...

Operador Zero stays a reference implementation — non-normative, non-production, no real funds, ...

Federation stays a bounded local per-interaction technical relation — never a network/membershi...

Governance stays a public process of the maintainers over the rules — never a regulator of oper...

Developer resources keep norm vs tool distinct — no tool/stack becomes a protocol requirement (...

Reference roadmap stays durable — §14 "Evolução do Protocolo" carries no milestone/date/comm...

Reference FAQ stays a faithful compression — §15 preserves the §1–§14 distinctions (Ch15)

Canonical discovery surface — one .well-known machine-readable surface, no retired root routes

Single canonical protocol-evolution surface — /roteiro retired, §14 is the only narrative

Canonical trust signing chain — root signs only the Key Manifest, BRL by the revocation-domain key

License, Notice, Trademark and Open Governance

BanzAI Local Qwen Inference

BanzAI is a single public interface on /banzai

BanzAI Qwen-first grounded routing

BanzAI action boundary & knowledge safety

BanzAI knowledge & conversational context

BanzAI is an operational protocol agent

BanzAI guided operator journey

BanzAI journey product copy + safe JSON upload

BanzAI docs reflect the deployed state

BanzAI public surface final consistency

BANZA three-layer architecture

Banzami scheme-role boundary

Regulatory-state claim boundary

Real-money activation fail-closed

Protocol/scheme separation

Conflict of interest + domain separation

Certification ≠ admission ≠ authorisation

L2 certification model

certification page (/certificacao)

technical registry page (/registo-tecnico)

glossary page (/glossario)

public-surface canonicalization

canonical five-band Home

/o-que-e route removal

Home + route canonicalization readiness

mandatory post-synthesis authority validator

runtime SSOT /banzai/runtime

SimB retired from active surfaces

canonical BanzAI architecture framing

canonical BanzAI reference (7 sections · 2 diagrams · frozen architecture)

BanzAI architecture manifest (parity with §12 + terminology invariants)

Git authorship identity guard (no Claude attribution)

Technical Registry naming parity (Registo Técnico)

BanzAI mark consistency (one official mark)

degraded-mode render honesty

"Validar operador" sidebar mode

operator → implementation target model

endpoint-originated official journey

no manual input in the official flow

developer draft tool isolation

closed target registry (operator-zero only)

no arbitrary URL (registry-resolved only)

SSRF-hardened Rust artifact fetcher

fetch → receipt origin binding

nine endpoint-fetched steps

single Resultados area

no duplicate navigation tabs

no orphan tabs

state-contextual step actions

static header vs contextual right panel

Certification Readiness vs Status language

Operador Zero parity

Operador Zero no-bypass

Operador Zero public E2E evidence

no fixture as production evidence

OperationReceipt §30 origin fields

JourneyReceipt §31 origin fields

Rust decides, Qwen only explains

Rust fetch authority

semantic non-regression

validation UI accessibility

validation UI responsive

endpoint-originated validation readiness

Rust Rule Guard on: pull_request 1

No new non-Rust engine

Conformance on: pull_request 7

Validate conformance vectors

Validate invariant registry

OpenAPI compatibility check

Schema compatibility check

QR payload compatibility

Trace contract check

Manifest schema validation

Rust Engines on: pull_request 21

banzai-evidence (R2 engine)

banzai-query-core

banzai-onboarding

banza-artifact-fetcher

banza-target-registry

banzai-api-kb (R6 retrieval)

banzai-repo-indexer

banza-simb (R8 simulator)

banza-evidence-bundle

banza-operator-manifest

banza-l1-readiness

banza-l2-readiness

banza-l3-readiness

banza-l4-readiness

banza-security-assurance

banza-production-gate (M2 protocol gate)

banza-root-ceremony

banza-reference-trust-model

banza-open-governance

banza-root-ceremony-cli

banza-repo-guards (R10 gates)

operator-zero-core on: pull_request 2

operator-zero-core (simulator engine)

operator-zero-e2e-root

banza-conformance-rs on: pull_request 1

banza-conformance-rs (R4 runner)

banza-certification on: pull_request 1

banza-certification (L2 authority)

banza-trust on: pull_request 1

banza-trust (R5 verifier)

banza-trust on: push 1

banza-trust (R5 verifier)

Identity Guard on: push 122

No operator-specific brand in BANZA

No central human authority over operators

Public surfaces present only the active model

Operator verification is Workbench-only

Governance docs present only the active model

Homepage final public-release contract

Homepage final audit & premium polish

Footer BanzAI/Guide + Operador Zero navigation

Global navigation is three distinct destinations

Homepage keeps the minimal public-release shape

Homepage layout — left-aligned headings, short footer boundary, clean copy

BanzAI resolves explicit ADR/RFC documents before generation

BanzAI documentary answers are scoped to what was asked

Reference chapter order — Operador Zero at 09

Operador Zero stays a simulator

Operador Zero vocabulary contract

Operador Zero public surface hardened

zero.banza.network single-page lab design

zero.banza.network host-aware routing

Operador Zero read-only reference surface

Operador Zero cross-browser routing

BanzAI single canonical interface

Operador Zero standalone surface

Operador Zero full E2E protocol validation

Operador Zero realistic demo journey

Operator Zero Only demo/example policy

Rust and UI cannot disagree about a slug

BanzAI release QA gate intact

Operator journey closed end to end, one evaluator

BanzAI session context reflects real validation state

Public copy matches the deployed protocol-agent architecture

Official SVGs pass the visual-quality policy

Official SVGs follow the canonical visual system

BanzAI is the native protocol agent, not an authority

PostgreSQL holds protocol state, not financial value

Operator onboarding contract

Operador Zero origin-proof closure

BanzAI operator-experience canonicalization

BANZA Whitepaper v1.0 contract (WP1-FINAL)

Public technical claims — executable evidence gate

Whitepaper canonical-source boundary (Overleaf PT dossier is the source)

Whitepaper canonical build is reproducible (hermetic verify)

Trust-invariant realignment

Reference information architecture is canonical

Layer/profile naming split is canonical (Camada 1/2/3 vs L0–L4)

Estado Protocolar keeps PostgreSQL as implementation, not protocol (Ch05)

Confiança keeps the trust boundary — root signs only the Key Manifest, trust ≠ certification...

Conformidade e Certificação keeps distinctions — L0–L4 profiles ≠ layers/certificates, va...

Operadores keeps operator (entity) ≠ implementation (evaluated subject) — one operator → ma...

Operador Zero stays a reference implementation — non-normative, non-production, no real funds, ...

Federation stays a bounded local per-interaction technical relation — never a network/membershi...

Governance stays a public process of the maintainers over the rules — never a regulator of oper...

Developer resources keep norm vs tool distinct — no tool/stack becomes a protocol requirement (...

Reference roadmap stays durable — §14 "Evolução do Protocolo" carries no milestone/date/comm...

Reference FAQ stays a faithful compression — §15 preserves the §1–§14 distinctions (Ch15)

Canonical discovery surface — one .well-known machine-readable surface, no retired root routes

Single canonical protocol-evolution surface — /roteiro retired, §14 is the only narrative

Canonical trust signing chain — root signs only the Key Manifest, BRL by the revocation-domain key

License, Notice, Trademark and Open Governance

BanzAI Local Qwen Inference

BanzAI is a single public interface on /banzai

BanzAI Qwen-first grounded routing

BanzAI action boundary & knowledge safety

BanzAI knowledge & conversational context

BanzAI is an operational protocol agent

BanzAI guided operator journey

BanzAI journey product copy + safe JSON upload

BanzAI docs reflect the deployed state

BanzAI public surface final consistency

BANZA three-layer architecture

Banzami scheme-role boundary

Regulatory-state claim boundary

Real-money activation fail-closed

Protocol/scheme separation

Conflict of interest + domain separation

Certification ≠ admission ≠ authorisation

L2 certification model

certification page (/certificacao)

technical registry page (/registo-tecnico)

glossary page (/glossario)

public-surface canonicalization

canonical five-band Home

/o-que-e route removal

Home + route canonicalization readiness

mandatory post-synthesis authority validator

runtime SSOT /banzai/runtime

SimB retired from active surfaces

canonical BanzAI architecture framing

canonical BanzAI reference (7 sections · 2 diagrams · frozen architecture)

BanzAI architecture manifest (parity with §12 + terminology invariants)

Git authorship identity guard (no Claude attribution)

Technical Registry naming parity (Registo Técnico)

BanzAI mark consistency (one official mark)

degraded-mode render honesty

"Validar operador" sidebar mode

operator → implementation target model

endpoint-originated official journey

no manual input in the official flow

developer draft tool isolation

closed target registry (operator-zero only)

no arbitrary URL (registry-resolved only)

SSRF-hardened Rust artifact fetcher

fetch → receipt origin binding

nine endpoint-fetched steps

single Resultados area

no duplicate navigation tabs

no orphan tabs

state-contextual step actions

static header vs contextual right panel

Certification Readiness vs Status language

Operador Zero parity

Operador Zero no-bypass

Operador Zero public E2E evidence

no fixture as production evidence

OperationReceipt §30 origin fields

JourneyReceipt §31 origin fields

Rust decides, Qwen only explains

Rust fetch authority

semantic non-regression

validation UI accessibility

validation UI responsive

endpoint-originated validation readiness

banza-certification on: push 1

banza-certification (L2 authority)

banza-conformance-rs on: push 1

banza-conformance-rs (R4 runner)

Rust Engines on: push 21

banzai-evidence (R2 engine)

banzai-query-core

banzai-onboarding

banza-artifact-fetcher

banza-target-registry

banzai-api-kb (R6 retrieval)

banzai-repo-indexer

banza-simb (R8 simulator)

banza-evidence-bundle

banza-operator-manifest

banza-l1-readiness

banza-l2-readiness

banza-l3-readiness

banza-l4-readiness

banza-security-assurance

banza-production-gate (M2 protocol gate)

banza-root-ceremony

banza-reference-trust-model

banza-open-governance

banza-root-ceremony-cli

banza-repo-guards (R10 gates)

Rust Rule Guard on: push 1

No new non-Rust engine

Repository Purity on: push 1

No non-protocol artifacts in BANZA

operator-zero-core on: push 2

operator-zero-core (simulator engine)

operator-zero-e2e-root

Annotations

1 warning

Complete job

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

No non-protocol artifacts in BANZA

succeeded Aug 21, 2026 in 24s

Loading

Re-running jobs...

Footer

© 2026 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Community
Docs
Contact

You can’t perform that action at this time.