PROTOCOL ORIENTATION

Protocol infrastructure

Fenrua BlackBox Protocol is protocol infrastructure for verifiable AI automation and governable autonomous AI execution. The platform view separates what is inspectable today from specifications, research, and planned work.

CURRENT CAPABILITY STATES

Maturity stays attached to the record

These summaries are generated from the canonical capability register. A public page, specification, or record is not promoted into a service merely by being visible here.

reference-implementation · generally-available

Website and public evidence interface

Public website for company information, technical documentation, evidence records, status information, and bounded read-only observations.

Lifecycle
active
Public interface
Fenrua public website
Owner
public-platform

Limitation: The static public interface does not attest to protected systems, private infrastructure, or live block-card data.

Non-claim: It is not a self-service account, checkout, client-upload, or interactive AI interface.

Promotion gate: Release only through the declared static release validation and public artifact binding process.

specification · source-only

Security kernel specification

Public specification for security-kernel responsibilities, primitive maturity, and fail-closed conditions.

Lifecycle
active
Public interface
Security kernel route; Security kernel specification
Owner
security-architecture

Limitation: The specification is not itself a production engine or production-safety certificate.

Non-claim: It does not replace applications, models, tools, cloud infrastructure, or chains.

Promotion gate: Require an implemented scope-specific control, tests, evidence, and release decision before promoting a specification claim.

Inspect boundary
specification · source-only

Utility catalogue

Public catalogue of utility concepts with purpose, boundary, and maturity labels.

Lifecycle
active
Public interface
Utilities route
Owner
public-platform

Limitation: Catalogue entries have different maturity levels and may not expose a usable service interface.

Non-claim: A listed utility is not automatically installed, live, hosted, or production approved.

Promotion gate: Require a purpose, usable interface, boundary, evidence, and limitation before promoting an individual utility beyond source-only status.

Inspect boundary
prototype · local

Local verifier foundation

Repository-local verification result fixtures and deterministic result-code boundary.

Lifecycle
active
Public interface
Verifier fixture check; Verifier route
Owner
developer-platform

Limitation: No live server-side verifier or public upload flow is claimed.

Non-claim: A fixture result cannot establish production runtime conformity or validate artifacts that were not supplied.

Promotion gate: Require an implemented verifier, usable public interface, documented inputs, evidence bundle, and limitations before broader availability.

Inspect boundary
research · not-available

Local Trust Gate

Planned local integration concept with no implemented public interface or release evidence in the current repository.

Lifecycle
planned
Public interface
No public interface recorded.
Owner
developer-platform

Limitation: No public implementation, CLI, SDK, API, hosted interface, or release artifact is recorded.

Non-claim: This register does not claim Local Trust Gate is available, tested, beta, or production ready.

Promotion gate: Require a public implementation, usable interface, evidence record, limitations, and owner-approved release decision before any availability promotion.

Inspect boundary

MEASUREMENT BOUNDARY

Efficiency claims require a reproducible method

The public platform does not publish a measured AI-efficiency benchmark. The standard defines the workload, baseline, environment, quality, uncertainty, and artifact inputs required before a future performance claim can be made.

NEXT BY ROLE

Inspect before integrating

Technical reviewers can trace claims and evidence. Developers can reproduce local checks. Service discussions remain agreement-specific and do not become public self-service workflows.