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

Declare the security layer, and repair the placement admission check
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Layer declaration (gate-house). INTENT.md now carries the declaration in its own
voice with layer.yaml as the machine-readable form, adapted from ops-warden's
reference. railiance-platform is Staff: operating OpenBao is not a claim to the
Tooling layer, because §4 is explicit that no operator-of-third-party-Tooling
shape exists and that someone running it stays a declared gap. Six direct
Tooling contacts are mapped by capability rather than by file — one §5.2
conduit, one §5.1 diagnostic, four §5.3 gaps with intended owners and review
dates — and the uncatalogued contacts are listed so the check is total. We are
PEP-shaped and the unreachable-engine stance map is NOT published; that is
recorded as an open obligation to build against v0.8, not left silent.

Placement admission. canned-prompts was added as a PostgresConsumer on
platform-pg-2 in rapp-postgres 1b68b4c without a placement owner here, which is
exactly the cross-repo drift the assurance check exists to catch; the check had
been failing on it. Registered with its real boundary evidence, corrected the
stale test expectation that pinned the overflow cell at one consumer, and
updated the SCOPE occupancy line to 2/4.

Also records owner input received today: key-cape's issuer view on CCR-2026-0020's
presenting actor, and their confirmation that codex-railiance-platform correctly
stays tenant:coulomb, so the flagged T02 discrepancy is closed as not-a-defect.

The whynot-design npm field is NOT changed. Two dated live receipts here name
NPM_AUTH_TOKEN as the field, including an attended founder fetch; that is
recorded against the counterparty claim rather than either side being flipped
before the session settles it.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 1275505@bnt-lap001
Assistant-Session: 97265baa-f08f-4032-b290-a1e2965a69c5
This commit is contained in:
codex 2026-09-09 23:27:14 +02:00
parent f0c2fd58cd
commit f3cf832a35
9 changed files with 342 additions and 16 deletions
Download patch file Download diff file Expand all files Collapse all files

17
workplans/RPF-WP-0035-credential-lane-implementation.md
View file

@ -323,6 +323,23 @@ into this client-identity grant.
## Dependency review — 2026-09-06
### 2026-09-09 tenant question resolved — no change needed
The `tenant:coulomb` / `tenant:platform` discrepancy raised against T02 is not a
discrepancy. KeyCape confirms decision `5ed3fb35-eca9-413a-82b9-95171ba85bf6`
binds the *approval chain* to the landlord zone and was applied to exactly two
registrations, `secrets-engine-approval` and `approval-engine-operator`.
`codex-railiance-platform` is not in that chain and correctly stays
`tenant:coulomb`, as do `secrets-engine-openbao` and the human directory default.
KEY-WP-0013-T04 records this and their
`TestServiceRegistrationTenantsAreExactPerDecision` pins every reviewed client's
tenant against the real fixture, so a reintroduced alias fails their build.
`docs/credential-lane-designs/secrets-engine-service-jwt.md` already says
`tenant:coulomb` and is therefore correct as written. Bind the exact role to
`tenant:coulomb`. Do not "correct" it to `tenant:platform` later; that would
break the issued claim.
SECRETS-WP-0008-T02 now records the local PIP claim/validation join implemented
and tested. Its remaining gate is the unreachable approval-engine claim endpoint
and access-engine Check (SECRETS-WP-0007-T04). Do not carry forward the old local