SPIP
Tests configured freshness, precision, ordering and integrity conditions for execution-relevant live evidence.
A reference testbed for verifiable consequential execution.
Five complementary control surfaces. One observable effect model. Normal execution, deliberate failure injection, and reviewable evidence.
A digitally capable system may be able to produce an effect. NET0 tests whether the configured execution-relevant conditions remain sufficient for the exact candidate effect at the release boundary.
Each challenge changes one configured condition while keeping the rest of the demonstration explicit. The v0.1.1 package is simulation-only.
—Every simulated challenge run produces a structured evidence package and SHA-256 manifest. The external-node validation track also records hash-bound task, result, marker and manifest evidence. These records are experimental demonstrator artefacts, not certificates or legal proof.
RUN_ID/ ├── RUN_MANIFEST.json ├── ENVIRONMENT.json ├── EFFECT_REQUEST.json ├── evidence/ ├── spip/ ├── acavp/ ├── pact/ ├── tpol/ ├── authorization/ ├── execution/ ├── recovery/ ├── MANIFEST.sha256 └── SUMMARY.md
| Run | Challenge | Decision | Effect | Created |
|---|---|---|---|---|
| Loading simulation-run registry… External-node validation is a separate evidence track and is not represented as a simulation run in this table. | ||||
Design intent: the public KVM8 service can request, observe and record demonstrations, but it should not become the sole physical root of trust for later hardware phases.
Tests configured freshness, precision, ordering and integrity conditions for execution-relevant live evidence.
Tests configured authenticity and current-validity conditions for the relied-upon endpoint, component or identity.
Tests whether the candidate physical action remains within the configured model, tolerances and feasibility envelope.
Evaluates verified execution-relevant inputs under an explicit deterministic policy profile.
Tests configured final release verification for the exact candidate effect before consequential execution.
These are non-confidential demonstrator summaries. They do not define patent scope.
Public interface, API, run registry and evidence mirror.
CURRENT FOUNDATIONReal external compute / decision node used in the validated task-scoped safe-software-effect round trip. This is not physical-actuation evidence.
SIGNED SOFTWARE RUN VALIDATEDIndependent verification node.
INTEGRATION PLANNEDCross-platform reproduction/challenge node.
INTEGRATION PLANNEDConstrained/intermittent-connectivity endpoint.
INTEGRATION PLANNEDPrimary physical endpoint and secondary challenge endpoint.
INTEGRATION PLANNEDEnd-to-end research into consequential claims and evidence-to-effect continuity.
Independent research architecture concerned with current effect authority, constraints, continuity and reviewability.
Non-confidential technology/IP portfolio and commercialisation context.
Applied experimental demonstrator and reference testbed.