coulomb/target-revenue
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Draft ADR-0002: hosted Trust Service stack (WP-0006-T02, awaiting sign-off)

Browse source 
Proposes PostgreSQL with database-enforced append-only guarantees,
per-Licensor API tokens decoupled from the existing Ed25519 entry
signatures, and railiance-cluster's existing k3s/GitOps baseline for
hosting rather than new infrastructure, reusing src/target_revenue/
directly behind a thin HTTP layer. Task left todo per the human-accept
gate policy already applied to ADR-0001.
This commit is contained in:
tegwick 2026-07-29 20:55:05 +02:00
parent 5f75afc6cc
commit 809f7aa0f9
2 changed files with 221 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

10
workplans/TREV-WP-0006-trust-service-implementation.md
View file

@ -92,6 +92,16 @@ assumed by default.
**Human accept gate:** per the same policy as ADR-0001 — agents may draft,
must not treat as accepted without explicit maintainer sign-off.
**Status: ready for review, not done.** Drafted at
`docs/adr/ADR-0002-hosted-trust-service-stack.md`: PostgreSQL (append-only
enforced at the database-grant/trigger level, not just convention) for
storage; per-Licensor API token for write/read-grant access control,
decoupled from the existing Ed25519 per-entry signature; `railiance-cluster`'s
existing k3s/Helm/GitOps baseline (on the `railiance-infra`-provisioned
HostEurope server) for hosting, rather than new infrastructure; Python
reusing `src/target_revenue/` directly behind a thin HTTP layer. Awaiting
maintainer sign-off before T03–T08 build against it.
## Phase Registry and Extension Registry hosting
```task