coulomb/railiance-apps
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
e0f9a08b1c01f4213c190f5902d53a2ca54f539c
railiance-apps/.custodian-brief.md
tegwick 179b87e244 chore(consistency): sync task status from DB [auto] 
Updated by fix-consistency on 2026-06-04:
  - update .custodian-brief.md for railiance-apps
2026-06-04 12:24:54 +02:00

2.2 KiB
Raw Blame History

Custodian Brief — railiance-apps

Domain: railiance
Last synced: 2026-06-04 10:24 UTC
State Hub: http://127.0.0.1:8000 (adjust if running on a remote machine)

Active Workstreams

Extract railiance-forge and formalize forge-layer contracts

Progress: 0/10 done | workstream_id: 1960b22b-82ae-4b67-9fff-397bd38bdd65

Open tasks:

  • · T01 - Define the railiance-forge repository contract 129c2920
  • · T02 - Create and register the railiance-forge repository 0e71e5a6
  • · T03 - Move current forge deployment surface out of railiance-apps 57162f50
  • · T04 - Re-scope railiance-apps and railiance-enablement 64ac73e7
  • · T05 - Define artifact lifecycle, retention, and provenance policy a99520c3
  • · T06 - Define CI runner, Actions, and GitOps ownership 37945939
  • · T07 - Define backup, restore, and secret handoff contracts da8bfbab
  • … and 3 more open tasks

S5 app release readiness and scope alignment

Progress: 1/6 done | workstream_id: 685f1c18-33c0-400d-a2b1-e1dae0f27c3e

Open tasks:

  • · T02 - Normalize app image promotion and package registry docs f8f63edb
  • · T03 - Create a reusable S5 app onboarding checklist 4eab93a9
  • · T04 - Define app data backup and restore handoffs 299d9623
  • · T05 - Make manifest dry-run workflow prerequisites explicit 6cf0e662
  • · T06 - Define Gitea package registry storage and retention posture 382ba252

App deployment improvements (lessons from RAILIANCE-WP-0002)

Progress: 6/7 done | workstream_id: b61a9aca-4e43-4b3d-a48b-999e0fa842cf

Open tasks:

  • ! I03 — Publish issue-core to a Gitea Python package registry f412b874 (wait: issue-core package build and vergabe-teilnahme registry dependency are prepared; final unblock requires a Gitea package username/token to publish issue-core==0.2.0 and regenerate vergabe-teilnahme/uv.lock from the Gitea PyPI registry.)

MCP Orientation (when available)

If the state-hub MCP server is reachable, call: get_domain_summary("railiance") This provides richer cross-domain context. If the MCP call fails, use this file as your orientation source.

Reference in New Issue View Git Blame Copy Permalink