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

Accept ADR-0002: hosted Trust Service stack (WP-0006-T02)

Browse source 
Maintainer (Bernd) accepted 2026-07-29 with no changes requested.
T03-T08 may now build against PostgreSQL + per-Licensor API tokens +
railiance-cluster hosting + Python/src/target_revenue reuse.
This commit is contained in:
tegwick 2026-07-29 20:57:38 +02:00
parent 809f7aa0f9
commit d35820365b
2 changed files with 21 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

18
docs/adr/ADR-0002-hosted-trust-service-stack.md
View file

@ -1,10 +1,10 @@
---
id: ADR-0002
title: "Hosted Trust Service stack: storage, auth, and deployment target"
status: proposed
status: accepted
date: 2026-07-29
decided_by: null
accepted_at: null
decided_by: Bernd
accepted_at: "2026-07-29"
workstream: TREV-WP-0006 (trust-service-implementation)
alternatives_considered: [Go service, file/git-based ledger store, per-repo-hosted SQLite]
---
@ -13,12 +13,12 @@ alternatives_considered: [Go service, file/git-based ledger store, per-repo-host
## Status
**Proposed, not yet accepted.** Per `docs/adr/ADR-0001-stage0-library-stack.md`'s
own Revisit trigger, this is that separate, later decision — hosting,
multi-tenant storage, and authentication were explicitly out of ADR-0001's
scope and are not inherited from it. This ADR requires explicit maintainer
sign-off (`workplans/TREV-WP-0006-trust-service-implementation.md` T02,
`human_accept_required: true`) before any of T03–T08 build against it.
**Accepted 2026-07-29** by the maintainer (Bernd). Per
`docs/adr/ADR-0001-stage0-library-stack.md`'s own Revisit trigger, this was
that separate, later decision — hosting, multi-tenant storage, and
authentication were explicitly out of ADR-0001's scope and are not
inherited from it. T03–T08 (`workplans/TREV-WP-0006-trust-service-implementation.md`)
may now build against this decision.
## Scope

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

@ -74,9 +74,11 @@ multi-tenant, authenticated context without redefining any schema field.
```task
id: TREV-WP-0006-T02
status: todo
status: done
priority: high
human_accept_required: true
human_accepted_by: Bernd
human_accepted_at: "2026-07-29"
state_hub_task_id: "06eabd46-5de5-4d80-9bb7-c70ef6d80df9"
```
@ -92,15 +94,15 @@ 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.
**Result:** Accepted 2026-07-29 by the maintainer (Bernd), no changes
requested. `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. T03–T08 may now build against this decision.
## Phase Registry and Extension Registry hosting