Public Evidence Surface
Public website, evidence records, trust records, release scope, and local validation paths make the reviewable surface inspectable.
STAGED PROTOCOL DIRECTION
BlackBox Roadmap
Fenrua BlackBox Protocol is built for autonomous systems that must be questioned before they are trusted. This public roadmap describes staged protocol direction for governable AI execution, bounded evidence, and review discipline.
PUBLIC / PRIVATE BOUNDARY
Direction, not a disclosure or availability claim
This roadmap describes staged protocol direction and public review boundaries. It does not disclose private infrastructure, formulas, credentials, topology, provider routes, operational wiring, or protected implementation details.
Future-stage items are not availability claims unless explicitly marked as live on fenrua.ai. Public records support technical review, verification, evidence inspection, and professional due diligence; they do not prove protected runtime safety or public-mainnet deployment.
CONTROLLED MATURITY PATH
Twelve public stages
Each stage describes a bounded public meaning and preserves the distinction between direction, evidence, and live capability.
Official Source and Impersonation Boundary
fenrua.ai is the sole source of truth. Fenrua has no public token, claim page, or public-mainnet contract.
Governable AI Execution
Capability is not authority. AI-linked tool calls and model actions require bounded evidence and review before they can be trusted.
Trust Gate Direction
Manifest, policy, request, revocation, evidence construction, and verification describe the direction. ALLOW is not EXECUTE, and future tooling is not claimed as live.
Open reviewer pathTenant Identity and Scoped Access
Future tenant-scoped evidence projection is intended to preserve separate review boundaries without cross-tenant disclosure.
Agent Capture and Evidence Events
Model, tool, and infrastructure actions can become bounded evidence records while protected implementation details remain outside the public surface.
Proof Ingress Direction
The P/N-521 proof-kernel direction may inform future bounded proof ingress. This page does not describe equations, formulas, witnesses, or implementation details.
Tenant Logical Blocks
Future tenant-local history and evidence sequencing are described only at a high level; internal private-chain heights and topology are not published.
Encrypted Archive and Recovery
Continuity, recovery, evidence custody, and fail-closed operation guide the direction without disclosing protected recovery mechanisms.
Selective Disclosure
Reviewers should receive only authorised evidence while private infrastructure and confidential execution remain protected.
Challenge and Replay Review
A future review path may let authorised reviewers question, replay, and challenge bounded evidence without receiving the whole machine.
Production Rollout Gates
Staged acceptance, validation, rollback, recovery, and review controls guide promotion. Future stages are not availability or production claims.
REVIEW PATH
Evidence before authority
Inspect the current public trust records, release scope, and legal boundary before treating any external claim as authoritative.
Trust Gate reviewer path · Trust records · Release verification · Legal and company boundary