TEN-MINUTE QUICK START

Developers

Start with the architecture, inspect schemas, run local validation, then map claims to evidence.

WORKFLOW

Developer workflow

Install

Use Node 24 and the repository package manager. This website has no runtime package dependencies.

Validate

Run npm run validate to check static links, public discovery, chain API sanitization, kernel telemetry, and toolchain registry.

Read schemas

Entity manifest, authority policy, evidence bundle, and verification result specs are public.

Schemas and examples

Inspect evidence

Use the evidence registry and release manifest to connect claims to source, timestamp, maturity, and limitations.

Evidence

Respect compatibility

Unsupported schema versions fail closed with UNSUPPORTED_SCHEMA rather than partial interpretation.

Respect the service boundary

No public token, investment, trading, or financial-return product is claimed.

COMMANDS

Local baseline

git clone https://github.com/Fenrua-Labs-Pty-Ltd/fenrua-web.git
cd fenrua-web
node --version  # v24 required
npm ci
npm run validate
node scripts/test-toolchain-registry.mjs
node scripts/test-verify-examples.mjs

REPRODUCTION PROOF

Expected result

A clean checkout should complete validation with static route, chain API sanitization, kernel telemetry, toolchain registry, and verify-corpus checks passing. The failing fixture is intentionally represented as FAIL_CLOSED.

Verification schemas and examples Passing fixture Failing fixture

COMPATIBILITY AND CONTRIBUTION

Keep the public boundary reproducible

The supported local path uses Node 24 and the committed npm lockfile. Unsupported schema versions fail closed rather than being guessed. Public contributions belong in the repository; private vulnerabilities belong in the security reporting channel.

Repository contribution channel Private vulnerability reporting Capability and claim records Download capability register JSON