Enforce fixture interaction policy

This commit is contained in:
jwinterm
2026-07-06 03:28:14 -04:00
parent f930f606fd
commit d3c287074b
6 changed files with 245 additions and 4 deletions
+6 -4
View File
@@ -3,7 +3,8 @@
> Status: draft | Updated 2026-07-06 | Applies to: AMPB and AMPG compatibility checks
AMPB can check AMPG fixture manifests without contacting any network. The check confirms
that each generated fixture URL routes to the expected AMPB transport and profile.
that each generated fixture URL routes to the expected AMPB transport and profile, and
that its declared interaction policy fits that transport.
## Command
@@ -11,12 +12,13 @@ that each generated fixture URL routes to the expected AMPB transport and profil
python3 -m ampbrowser fixture check ../adaptive-multi-protocol-gateway/dist/wownero/ampg-fixture-manifest.json
```
The command exits non-zero when any fixture route does not match the manifest.
The command exits non-zero when any fixture route or interaction policy does not match the
manifest.
## Scope
Fixture checks validate route selection only. They do not verify daemon health, hidden
service reachability, IPFS pinning, TLS, or content freshness.
Fixture checks validate route selection and declared interaction policy only. They do not
verify daemon health, hidden service reachability, IPFS pinning, TLS, or content freshness.
The manifest must not contain private deployment notes, service keys, credentials, or
host inventory.