github-such-software/adaptive-multi-protocol-gateway
1
0
Fork 0
mirror of https://github.com/Such-Software/adaptive-multi-protocol-gateway.git synced 2026-10-17 15:41:41 +02:00
Code Issues Packages Projects Releases Wiki Activity

Add signed service manifest contract

Browse Source
This commit is contained in:
jwinterm
2026-07-11 11:05:48 -04:00
parent 1651514c8e
commit bb63585098
14 changed files with 1936 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture.md
+7
View File
@@ -98,6 +98,13 @@ Fixture manifests are the AMPG-to-AMPB boundary. They declare the published URL,
transport, logical context, and transport-context isolation result. They do not prescribe
browser tabs, processes, or local daemon ownership; those decisions remain inside AMPB.
Signed service manifests are the service-to-client identity boundary. An application-owned
route manifest supplies publication policy, while a service manifest represents approved public
policy plus deployed transport addresses. AMPG currently validates manifests and calculates their
digests; applications or hardened external signers own private-key operations. A shared service
identity binds endpoints but never merges browser origins or transport contexts. See
[Signed service manifests](service-manifests.md).
## Platform providers
Platform providers decide what daemon management means on the current host. AMPG detects