Fenrua BlackBox Protocol
by Fenrua Labs Pty Ltd
ROLE-BASED ORIENTATION
Choose a Fenrua BlackBox Protocol review path by the question you need to answer. Every path states the current public surface, available evidence, known limits, and a shortest reproducible next step.
STARTING PATHS
These paths use current public records only. They do not imply an investment, account, token, or hosted-product journey.
npm run validatenpm run validatenode scripts/test-verify-examples.mjsnpm run validatenode scripts/test-verify-examples.mjsnpm run validatenpm run validateBROWSER / PUBLIC-RECORD INSPECTION
Inspection only: read these public records before deciding whether local reproduction is required. The no-clone path is inspection, not reproduction. It does not replace local reproduction, runtime testing, protected-system attestation, security certification, formal verification, independent audit, or production approval.
Inspect what the public release record binds and what remains outside its static artifact scope.
Read release-integrity boundaryRead current public assertions with their capability context, evidence class, and limitation.
Inspect claimsRead the purpose, integrity method, freshness model, disclosure boundary, and non-proof statement for each class.
Inspect evidence classesRead lifecycle, maturity, availability, limitations, non-claims, and promotion gates beside the relevant capability.
Inspect capability maturityRead the distinction between public records and agreement-specific service or evidence scope.
Inspect service boundaryRead why bounded signed observations remain separate from static release records and do not state a static chain condition.
Inspect observation boundaryClone the repository and run the Node 24 validation path only when local reproduction is required.
Open local reproduction pathREVIEWER COMPLETION
Choose the lane that matches the record or question in front of you. These routes remain scoped to public records, private vulnerability reporting, or agreement-specific contact.
Use the current manifest when recording the inspected source commit, artifact hashes, validation scope, and stated limitations.
Open current release recordTrace a public assertion to its capability context and then read the evidence-class boundaries that apply.
Inspect claimsStart with browser/public-record inspection before deciding that local reproduction is necessary.
Open no-clone pathUse the Node 24 local route only when a reviewer needs to reproduce the public source surface.
Open local reproduction pathUse the public repository path for documentation or source issues. Do not place vulnerability details there.
Open public repositoryUse the private security path for vulnerability details and keep it separate from public documentation or source issues.
Open security reportingUse the published contact channel for agreement-specific service or evidence scope.
Contact partnershipsCompare a later release record, document status, evidence record, and bounded observation state when returning.
Open reviewer delta