EXTENDED DOCUMENTATION
Validation
Canonical Validation Sequence
Run these checks after any meaningful change to runtime logic, deployment config, or public docs/frontend behavior.
Workspace Validation Layers
The workspace now exposes validation at two levels:
Repo-local layers
Workspace-level layers
From
:
These orchestrators call the repo-local layers across:
Recommended usage:
- use for code and config changes
- use for testnet smoke and cross-repo integration
- use only when you intentionally want the full local + live stack
Targeted Neo N3 Regression Paths
These cover:
- callback injection rejection
- NeoDID registry and ticket boundary behavior
- encrypted ref requester/callback binding
- fulfillment replay rejection
- AA session-key downstream Oracle boundaries
- integrated attack regression
Environment Validation
SaaS Validation
What “Healthy” Means
- the web app builds successfully
- control plane tests pass
- worker and relayer tests pass
- Oracle key publication matches the runtime
- pinned signer identities match expected addresses
- testnet smoke and verify flows pass end to end
- no documentation pages or explorer pages reference removed topology or stale routes
- workspace validation can be run in layered mode without reintroducing manual cross-repo sequencing
CURRENT DESIGNUPDATED FOR DUAL-CVM ARCHITECTURE