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

Triage the older secrets-engine inbox: record platform waits and railiance-clock
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details

Browse source 
railiance-platform e82bb289 recorded against SECRETS-WP-0006-T05 (explicit wait
on T04 serving; CCR-2026-0003 is provenance only). 29cccf8a recorded against
SECRETS-WP-0008-T06, including the open tenant:coulomb vs tenant:platform
question for the service JWT, left for an owner session. railiance-clock's
review request opened as SECRETS-IN-0003. The intelligence-radar messages are
superseded by SECRETS-WP-0010-T03 (done 2026-09-16) and answered by pointer.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
This commit is contained in:
tegwick 2026-09-21 07:37:53 +02:00
parent 8a48cb05df
commit 377ec06d69
3 changed files with 54 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

28
intakes/intakes.md
View file

@ -76,3 +76,31 @@ description: >-
complete, and changing a documented local checkout path ahead of the move
would document a path that does not exist yet. Close by updating that one
line when flex-auth confirms the rename has landed.
## SECRETS-IN-0003 — railiance-clock: consumer review of the time-sample profile and adoption condition
```yaml
id: SECRETS-IN-0003
kind: intake
title: 'railiance-clock: review signing custody, rotation and lifecycle-consumer adoption condition'
status: open
origin: cross-repo
origin_ref: hub messages f90b9f17 and 302291b5 (railiance-clock, 2026-09-14)
priority: low
owner: secrets-engine
requested_by: railiance-clock
resolution: ''
description: >-
railiance-clock published its foundation (commit 0a144b6, RCLK-WP plans) and a
candidate time-sample profile (commit 7af595b, specs/sample-profile-v0.1.md:
JWS Compact ES256, decimal-string ns, pinned authority/environment/policy,
bounded elapsed intervals). Asked of secrets-engine: review signing custody
and library compatibility for ES256 JWS, rotation/revocation and independent
bootstrap, and return a linked lifecycle/consumer adoption condition
(RCLK-WP-0002-T04, RCLK-WP-0004 propose a future server-side clock contract).
Nothing is adopted or unblocked by it: the existing refusal of shifted
validation clocks stands, and no key, policy or OS clock changed. Recorded at
triage 2026-09-21 and not reviewed there: a custody and adoption review is
owner design work, not a cheap reply. No secret values requested or sent.
```