railiance-platform

Author	SHA1	Message	Date
codex	f04c8016d9	Refresh credential procedure work records All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa	2026-08-22 13:01:16 +02:00
codex	864cc20b96	Add attended Whitehat E2 credential projection All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa	2026-08-22 12:59:38 +02:00
codex	ab7dee5382	Refresh platform work record index All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa	2026-08-22 12:43:46 +02:00
custodian-sync	a48e893672	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-22: - update .custodian-brief.md for railiance-platform Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa	2026-08-22 12:42:12 +02:00
custodian-sync	a4642274a2	chore(consistency): renormalize lifecycle state [auto] Updated by fix-consistency on 2026-08-22: - workplan status: ready → active Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa	2026-08-22 12:42:06 +02:00
repo-manager	5141bf1d0b	chore(registrar): assign State Hub identifiers All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa	2026-08-22 12:39:42 +02:00
custodian-sync	0bb9aa84c3	chore(consistency): sync task status from DB [auto] Some checks failed CI Smoke / container-smoke (push) Waiting to run Details CI Smoke / host-smoke (push) Has been cancelled Details Updated by fix-consistency on 2026-08-22: - update .custodian-brief.md for railiance-platform Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa	2026-08-22 12:39:40 +02:00
codex	8e26afc6a6	Add audit custody and recovery coordination workplan All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa	2026-08-22 12:34:25 +02:00
codex	429cc912ed	Finish coding-agent high-risk boundary coverage All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa	2026-08-22 10:03:54 +02:00
custodian-sync	7a1dcb8a52	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-22: - update .custodian-brief.md for railiance-platform Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa	2026-08-22 10:03:35 +02:00
codex	d40eb3c2a9	Finish hub-core credential lane workplan All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa	2026-08-22 00:28:18 +02:00
custodian-sync	6f4a53543e	chore(consistency): sync task status from DB [auto] Some checks are pending CI Smoke / container-smoke (push) Waiting to run Details CI Smoke / host-smoke (push) Waiting to run Details Updated by fix-consistency on 2026-08-22: - update .custodian-brief.md for railiance-platform Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa	2026-08-22 00:27:58 +02:00
repo-manager	c54de0f3d0	chore(registrar): assign State Hub identifiers All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details	2026-08-21 21:39:10 +02:00
custodian-sync	f106ee941c	chore(consistency): sync task status from DB [auto] Some checks are pending CI Smoke / container-smoke (push) Waiting to run Details CI Smoke / host-smoke (push) Successful in 0s Details Updated by fix-consistency on 2026-08-21: - update .custodian-brief.md for railiance-platform	2026-08-21 21:39:09 +02:00
codex	105a34784b	docs: add scoped registrar recovery guidance All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details	2026-08-21 21:38:35 +02:00
codex	456a80c2f6	Finish OpenRouter provider lane workplan	2026-08-21 21:22:52 +02:00
custodian-sync	d2da02b2ec	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-21: - update .custodian-brief.md for railiance-platform	2026-08-21 21:20:53 +02:00
codex	4689645621	docs: record hub-core credential handoff All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details	2026-08-21 21:07:10 +02:00
custodian-sync	fe40bdb395	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-21: - update .custodian-brief.md for railiance-platform	2026-08-21 21:06:00 +02:00
codex	bb7cfcb184	feat: add hub-core database lease projections All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details	2026-08-21 17:30:44 +02:00
custodian-sync	77f2535369	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-21: - update .custodian-brief.md for railiance-platform	2026-08-21 17:30:37 +02:00
custodian-sync	d59444b676	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-21: - update .custodian-brief.md for railiance-platform	2026-08-21 17:29:32 +02:00
codex	382f04412a	Close CCR drift and high-risk policy gaps All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details	2026-08-21 01:29:28 +02:00
custodian-sync	852a8ab661	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-21: - update .custodian-brief.md for railiance-platform	2026-08-21 01:28:52 +02:00
custodian-sync	71ee9ddd4c	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-21: - update .custodian-brief.md for railiance-platform	2026-08-21 01:27:44 +02:00
codex	1206ed55da	Finish Core Hub private shadow onboarding All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details	2026-08-21 00:51:06 +02:00
custodian-sync	a18d3dea33	chore(consistency): sync task status from DB [auto] Some checks are pending CI Smoke / host-smoke (push) Waiting to run Details CI Smoke / container-smoke (push) Waiting to run Details Updated by fix-consistency on 2026-08-21: - update .custodian-brief.md for railiance-platform	2026-08-21 00:50:27 +02:00
codex	90a0192e4f	Record Core Hub lease and network readiness All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details	2026-08-20 23:44:35 +02:00
custodian-sync	29cfd26c01	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-20: - update .custodian-brief.md for railiance-platform	2026-08-20 23:44:27 +02:00
codex	06c69f140e	Track Core Hub credential approval gate All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 2s Details	2026-08-20 23:33:18 +02:00
codex	07ed6217b7	Advance RPF-WP-0021 platform onboarding All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details	2026-08-20 23:31:47 +02:00
custodian-sync	8caba51801	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-20: - update .custodian-brief.md for railiance-platform	2026-08-20 23:29:14 +02:00
codex	cb321deeab	Finish RPF-WP-0019 apps-pg controls and recovery All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details	2026-08-20 22:58:45 +02:00
custodian-sync	272c1691c3	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-20: - update .custodian-brief.md for railiance-platform	2026-08-20 22:56:39 +02:00
codex	402731fc53	docs: index attended OpenRouter rotation All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details	2026-08-20 22:52:17 +02:00
custodian-sync	a5902593b3	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-20: - update .custodian-brief.md for railiance-platform	2026-08-20 22:50:34 +02:00
codex	ceed3c051d	docs: record provider incident and core hub rotation All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details	2026-08-20 22:47:38 +02:00
codex	131502e6e7	docs: refresh core hub publication evidence All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 2s Details	2026-08-20 12:00:02 +02:00
codex	ac69f90300	feat: prepare core hub platform onboarding All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details	2026-08-20 11:18:30 +02:00
custodian-sync	f19f89ae58	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-20: - update .custodian-brief.md for railiance-platform	2026-08-20 09:48:54 +02:00
custodian-sync	50edbf5554	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-19: - update .custodian-brief.md for railiance-platform	2026-08-19 01:11:47 +02:00
codex	56d516e10c	Add unique publication ids to platform ADRs All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details RPLAT-ADR-0001–0003 so policy-nexus can register the S3, placement, and file-backed decision records.	2026-08-19 01:09:18 +02:00
codex	7fb7c503df	chore(consistency): sync RPF-WP-0020 registration All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details	2026-08-18 15:19:19 +02:00
codex	b1f973c2d5	Pin apps-pg targets to railiance01 by cluster identity; seed RPF-WP-0020 All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Two reachable clusters each carry a CNPG Cluster named apps-pg in a namespace named databases. KUBECONFIG is an environment variable, so the Makefile ?= default never applied, and RAILIANCE01_KUBECONFIG pointed at config-hosteurope - a different cluster. Had the environment pointed at the other reachable cluster instead of an unauthorized one, make apps-pg-deploy would have applied RPF-WP-0019 connection limits, role timeouts and backup config to the wrong cluster and reported success. The Unauthorized error was the only thing that prevented it. Filename selection cannot protect against this: both kubeconfigs resolve to a 127.0.0.1 tunnel port and the environment wins either way. railiance01-guard pins identity instead, comparing the live kube-system namespace UID against RAILIANCE01_CLUSTER_UID, and fails closed on mismatch or unreachability. It gates apps-pg deploy, backup-deploy, overflow-dry-run, status and shell. Verified refusing on the wrong cluster, refusing when unreachable, and passing on railiance01. Not global: db-status legitimately targets the other cluster for gitea-db. RPF-WP-0019 blocker note corrected - the cluster was never unreachable, our wiring was wrong. RPF-WP-0020 seeded for the pre-existing CCR test failure, which is two unrelated problems: CCR-2026-0010 is an active lane missing its whole openbao.auth block, and CCR-2026-0011 is an honest in-flight draft the suite has no way to express. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-18 15:18:37 +02:00
codex	1cbde550b5	chore(consistency): regenerate WORK-RECORDS.md after RPF-WP-0018 close All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details	2026-08-18 13:36:31 +02:00
custodian-sync	fe6af08e91	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-18: - update .custodian-brief.md for railiance-platform	2026-08-18 13:36:15 +02:00
codex	dc4245361d	Finish RPF-WP-0018; RPF-WP-0019 repository-complete All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details RPF-WP-0018 closed: all seven tasks done. The provider-declaration finding was adopted upstream and its canonical form is the provider: block in tenancy.yaml; adaptive-pricing declined the standing co-signature and supplied typed tier minima instead, recorded in ADR-0002. Three corrections against our own output are recorded in the documents rather than edited away. RPF-WP-0019 T03 done (ceiling of three, memory binding, apps-pg-2 named as overflow, enforced by make apps-pg-verify-capacity). T01/T02 are repository-complete: backup target, retention, per-consumer connection limits, role timeouts and Burstable resources are declared in source and published in s3-consumer-interfaces 1.1.0 before rollout. They stay in progress because no live application, backup success or restore proof exists, and declared configuration is not a section 13 artifact. T04 waits on that window. apps-pg R reason corrected to say the target is declared-not-applied rather than absent. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-18 13:35:04 +02:00
custodian-sync	e52ae26001	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 2s Details Updated by fix-consistency on 2026-08-18: - update .custodian-brief.md for railiance-platform	2026-08-18 07:30:13 +02:00
custodian-sync	bb524e1a79	chore(consistency): sync task status from DB [auto] All checks were successful CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Successful in 1s Details Updated by fix-consistency on 2026-08-17: - update .custodian-brief.md for railiance-platform	2026-08-17 23:03:21 +02:00
codex	b15215d191	RPF-WP-0018: mark unevidenced P1 claims; seed RPF-WP-0019 for apps-pg Some checks failed CI Smoke / host-smoke (push) Successful in 0s Details CI Smoke / container-smoke (push) Has been cancelled Details Placement policy 3.1 records that the P1 levels for vergabe and coulomb_social are provisioning declarations without the SS13 isolation probes - apps-pg has none. 3.2 records that apps-pg cannot produce the noisy-neighbour artifact at all until per-consumer controls exist, per SS13.4: with nothing to bind, a probe could only demonstrate degradation. RPF-WP-0019 seeded for the three live defects the disclosure work found: no backup, no per-consumer controls, no isolation probes. Kept separate from RPF-WP-0018 so declaring is not confused with fixing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-17 23:01:57 +02:00

1 2 3 4 5 ...

327 commits