# Conformance and fault testing

Availability: **Proposed specification**  
Documentation: **1.1** | Updated: **19 September 2026**

[Documentation home](../README.md)

The cases below are release requirements for a network pilot. They are not recorded passes. Each result must identify the build, configuration, environment, input, expected behavior, observed behavior, raw logs and reviewer.

| ID | Scenario | Pass condition |
| --- | --- | --- |
| NET-01 | Identical request repeated | Same task identifier; no additional reservation |
| NET-02 | Same key with changed content | Conflict; original task remains unchanged |
| NET-03 | Concurrent coordinators allocate | One current attempt and consistent resource reservation |
| NET-04 | Partitioned executor returns late | Old generation cannot commit or trigger payment |
| NET-05 | Delivery acknowledgment is lost | Original delivery returned; no duplicate acceptance |
| NET-06 | Cancellation races with delivery | Atomic ordering; no contradictory closed outcomes |
| NET-07 | Cross-tenant object access | Denied without leaking private object existence |
| NET-08 | Replayed or invalid-key receipt | Rejected with a recorded verification reason |
| NET-09 | Queue messages duplicate or reorder | State constraints hold; sequence gaps reconcile |
| NET-10 | Commit succeeds and notification fails | Recovery republishes the event without losing work |
| NET-11 | Retry and payment notifications repeat | Attempt costs reconcile; ledger effect occurs once |
| NET-12 | Untrusted workload or download target | No unauthorized mount, egress or internal-network access |
| NET-13 | Rules change during execution | Existing tasks retain their frozen profiles |
| NET-14 | Restore or rollback is exercised | State, permission, evidence and accounting links recover |

## Review and release evidence

Functional review belongs to the implementing team. Authorization, isolation and key-handling cases require a security review appropriate to the deployment. Physical actions and real payments require the responsible operator to confirm recovery and reversal behavior.

TEST-01 Preserve failed cases and exclusions in the release record. Passing a subset must not be described as complete network conformance. TEST-02 Independent audits must state auditor, scope, version, date, findings and remediation status. No independent audit is asserted for reference 0.2.

[Previous](./observability.md) | [Next](./release-criteria.md)