Extend release readiness tracking to cover BReg and Casework operations
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation, release
Research direction
Start with release/READINESS.md and compare its existing Registry Relay and Evidence operations checklist with the OPS-21, ops-15, and sibling-ticket references in the issue. Add BReg and Casework rows for backup/restore, upgrades, observability, and HA/replica guidance, with completion tracked as the corresponding tickets close.
Written by the indexing model from the issue text.
Description
release/READINESS.md states it "tracks the evidence that Registry Relay
and Evidence are ready for a stable release." Its operations section is
entirely unchecked, and it does not cover BReg or Casework operations at
all. The related internal readiness scorecard and 1.0 readiness material
predate BReg and Casework and were written for the Relay/Notary era.
An operator (or a release manager) has no single tracked checklist
confirming that BReg's and Casework's backup, upgrade, observability, and
HA stories have been exercised and verified before a release ships, even
though several of those stories are exactly what this audit and its sibling
tickets (day-two runbooks, config convergence) are filling in.
Recommend adding BReg and Casework rows to release/READINESS.md covering
at minimum: backup/restore, upgrade, observability (metrics/logs/audit
export), and HA/replica guidance, checked off as the corresponding tickets
close.
Found in the 2026-09-24 lifecycle audit (OPS-21 and README section 6
capability gap item ops-15); the detailed finding is in the internal audit
report.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- Avg merge
- 5h 6m
- Merged PRs (30d)
- 170
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from registrystack/registry-stack
-
agent-ready area:platform bug criticality:p3 rust triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
registrystack/registry-stack#1583 · 1 comment ·
Maintainers usually reply within 1 day
-
docs(breg): configure/breg.mdx lists stages for a request_lifecycle when, which bregctl refusesOpenagent-ready area:breg area:docs criticality:p3 documentation triage:needs-implementation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
registrystack/registry-stack#1574 ·
Maintainers usually reply within 1 day
-
agent-ready area:evidence bug criticality:p3 triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
registrystack/registry-stack#1449 ·
Maintainers usually reply within 1 day
-
agent-ready area:breg bug criticality:p3 triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
registrystack/registry-stack#1405 ·
Maintainers usually reply within 1 day
-
agent-ready bug criticality:p2 github_actions triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1393 ·
Maintainers usually reply within 1 day
All issues in registrystack/registry-stack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
solana-foundation/pay-kit#341 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
anthropics/buffa#487 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
arkworks-rs/algebra#1161 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
lbjlaq/Antigravity-Manager#3525 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rustdesk/rustdesk-server#708 ·