informed-decision/docs
tegwick 4d33a59f5b docs(T07): settle the approver origin as decisions.coulomb.social
The operator assigned decisions.coulomb.social, not the decide.coulomb.social
this workplan proposed. Redirect URIs match byte-exactly at /authorize, so the
proposal is corrected in place rather than reconciled after submission — a
one-character miss presents as a rejected approval, not as a registration
defect.

DNS resolves. The Ingress and certificate are written in railiance-apps
(manifests/informed-decision-ingress.yaml, dry-run clean) but not applied, so
T07 stays progress: DNS alone is not an origin, and a host that does not answer
over TLS fails the same way a wrong hostname does, only later.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EJbh7o7UWF4tQ5jxygnNGu

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2072522@bnt-lap001
Assistant-Session: 46173adf-7302-4ede-99d6-963b61359928
2026-09-10 16:17:52 +02:00
..
specs Raise INFD-IN-0004: approval-engine's R3 answer conflicts with the ruling 2026-09-10 13:59:52 +02:00
evidence-path-design.md Apply GH-DEC-2026-013 and GH-DEC-2026-014; close INFD-IN-0002 2026-09-10 07:57:57 +02:00
finding-r3-linkage-conflict.md Raise INFD-IN-0004: approval-engine's R3 answer conflicts with the ruling 2026-09-10 13:59:52 +02:00
gate-house-decision-request-layer-placement.md Raise INFD-IN-0001: layer placement and approver-UI ownership 2026-09-09 14:07:13 +02:00
keycape-client-registration.md docs(T07): settle the approver origin as decisions.coulomb.social 2026-09-10 16:17:52 +02:00