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

Document credential lane designs and adopt fast projection sync

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883
This commit is contained in:
codex 2026-09-05 10:41:56 +02:00
parent 4c70fa83c5
commit 193b1276f3
9 changed files with 486 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

40
AGENTS.md
View file

@ -98,21 +98,25 @@ curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
**Close:**
1. Update workplan file task statuses to reflect progress
2. Log: `POST /progress/` with a summary of what changed
3. After workplan file changes, run:
3. After workplan file changes, commit the source changes and run:
```bash
statehub fix-consistency
uv run --project ~/repo-manager rmgr sync --path . --push
```
Coding agents should run this directly; ask the operator only if the CLI or
State Hub API is unavailable. This syncs task status from files into the hub DB.
If C-06/C-11 reports that this host is not the identifier registrar, do not
retry, set `STATEHUB_REGISTRAR`, or create hub rows manually. Commit and push
the file-backed work, then invoke repo-manager once:
```bash
uv run --project ~/repo-manager rmgr registrar-reconcile \
--path . --confirm-primary --push
```
If unavailable, send one deduplicated registrar request to `repo-manager`;
missing UUIDs do not block continued work from the repository files.
This assigns missing deterministic identifiers, pushes ahead commits, verifies
the exact Forge commit and `primary/railiance01`, then reconciles the repository
projection. Read the receipt: success requires an applied/noop outcome for the
expected commit. A queued receipt is pending, not synchronized.
On duplicate-identity, wrong-primary, commit-mismatch, or retirement refusals,
inspect the named records and fix the source/authority mismatch first. Do not
set `STATEHUB_REGISTRAR`, invent Hub rows, or blanket-acknowledge retirements.
Existing UUIDs remain managed; identity repair needs a scoped reviewed plan.
Run `statehub fix-consistency` separately for a deep consistency audit and
generated brief/index refresh; it is no longer the routine projection path.
Its HTTP reads may exceed the installed client's timeout. Do not repeatedly
restart a slow deep audit to accomplish a routine sync. If the CLI/API is
unavailable, retain local evidence and report sync as pending.
---
@ -203,7 +207,7 @@ owner: codex
topic_slug: ...
created: "YYYY-MM-DD"
updated: "YYYY-MM-DD"
state_hub_workstream_id: "<uuid>" # written by fix-consistency — do not edit
state_hub_workstream_id: "<uuid>" # managed by Repo Manager — do not edit
---
```
@ -220,7 +224,7 @@ derived health labels, not frontmatter statuses.
id: RPF-WP-NNNN-T01
status: wait | todo | progress | done | cancel
priority: high | medium | low
state_hub_task_id: "<uuid>" # written by fix-consistency — do not edit
state_hub_task_id: "<uuid>" # managed by Repo Manager — do not edit
` ` `
Task description text.
@ -230,6 +234,6 @@ Status progression: `todo` → `progress` → `done`; use `wait` for waiting/blo
To create a new workplan:
1. Write the file following the format above
2. Run `statehub fix-consistency` locally.
3. On a non-registrar C-06/C-11 skip, use the scoped repo-manager command above
once. Never export registrar authority directly or send duplicate requests.
2. Commit the source, then run `uv run --project ~/repo-manager rmgr sync --path . --push`.
3. Verify the exact-commit primary receipt. Use `statehub fix-consistency` only
for a separate deep audit; handle refusals as described in Session Protocol.