github-such-software/adaptive-multi-protocol-browser
1
0
Fork 0
mirror of https://github.com/Such-Software/adaptive-multi-protocol-browser.git synced 2026-10-22 08:48:33 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add isolated transport broker

Browse Source
This commit is contained in:
jwinterm
2026-07-11 09:34:51 -04:00
parent 4379b99245
commit 2c68c072ba
20 changed files with 731 additions and 206 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/fixture-manifests.md
+7 -5
View File
@@ -1,10 +1,11 @@
# Fixture Manifests
> Status: draft | Updated 2026-07-06 | Applies to: AMPB and AMPG compatibility checks
> Status: draft | Updated 2026-07-11 | 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, and
that its declared interaction policy fits that transport.
that each generated fixture URL routes to the expected AMPB transport and profile, uses
the declared transport-profile isolation contract, and fits that transport's interaction
policy.
Route-expanded fixtures may include `route.match` and `route.fixture_path`, which identify
the route group that produced the fixture.
@@ -20,8 +21,9 @@ manifest.
## Scope
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.
Fixture checks validate route selection, profile isolation expectations, and declared
interaction policy only. They do not verify process separation, 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.