Smart Contract Layer Readiness

This check answers one practical question: is the smart-contract layer ready to use in the current development or pre-production environment?

It is not a launch approval, audit approval, or mainnet checklist. It only reads the evidence produced by the runtime, contract, rehearsal, and soak checks.

Run The Evidence

npm run contracts:rc-gate -- --profile local --continue-on-failure --json --out test-results/contracts/rc-gate-report.json
npm run contracts:incident-drills -- --continue-on-failure --json --out test-results/contracts/incident-drills-report.json

The RC gate covers fuzzing, runtime security, runtime compatibility vectors, operator launch rehearsal, contract soak smoke, docs build, and sidecar provenance.

The incident drill suite covers sidecar availability, runtime mismatch, readiness stuck states, failure spikes, deactivation dependency checks, migration rollback, and backup/restore pressure.

Generate Readiness

npm run noos -- contracts layer-readiness --json --out smart-contract-layer-readiness.json

For Markdown:

npm run noos -- contracts layer-readiness --out smart-contract-layer-readiness.md

Decision Rules

• ready: all required evidence artifacts exist and report their expected pass status.
• not-ready: a required artifact is missing or reports a failing status.

Required Evidence

• test-results/contracts/rc-gate-report.json with overallStatus: "pass"
• test-results/contracts/incident-drills-report.json with overallStatus: "pass"
• test-results/contracts/operator-launch-rehearsal-report.json with ok: true
• test-results/contracts/contract-soak-report.json with ok: true

When It Fails

Run the recommended command shown in the readiness report for each missing or failing artifact. Treat runtime compatibility failures as pinned protocol-vector changes: inspect the diff before accepting a new vector.