Member Cycle — One Issue Inside a Batch, Verified Only Where It Is Cheap
Objective: Implement ONE issue in its own worktree off a shared integration branch, test it by relevance, review it at the level the scheduler assigned (review=full: full-cycle-grade, security included; review=light: at least the correctness reviewer — never zero agents), and hand over to a parent orchestrator that owns all expensive verification
Use it
Inspect metadata
ai-dossier info imboard-ai/git/member-cycle Download to the current directory
ai-dossier pull imboard-ai/git/member-cycle Verify, then run
ai-dossier run imboard-ai/git/member-cycleNeeds the CLI.
Trust and risk
| Declared risk level | medium (modifies_files, network_access) |
|---|---|
| Requires approval | no |
| Checksum | sha256:d7eec3bcf9d6349552ee86ee395c6012332233fdedfc2339319951f9e88340cd |
| Signature | ed25519, key imboard-ai by Yuval Dimnik <yuval.dimnik@gmail.com> |
| Signed at | 2026-09-24T09:21:21.057Z (covers frontmatter+body) |
| Public key | m97FPrnq/zKlQArLvJl3bTZCUMWWpp/d0UJ/OfUKZeE= |
These values are copied from the published dossier header. This site does not verify
them: run ai-dossier verify before trusting a dossier.
Details
| Categories | development |
|---|---|
| Tags | issue, workflow, batch-cycles, member, integration-branch, handover, runstate, review |
| Authors | Yuval Dimnik |
| Source | raw .ds.md |