SATCOMDevelopment operations

Development / Delivery / Evidence

From finding to finished.

One view of the work across Register Call, The Villager, SATCOM, Ace and Cursor. Finish a bounded item, verify the result, then take the next.

Manage cards in Admin ↗Use a development prompt

Loading the reviewed development board…

Cards are stored in the existing Admin Kanban. This SATCOM view reads reviewed items; card moves made in Admin appear after refresh. Detailed acceptance/source notes are maintained with the reviewed release record.

Blocked items remain visible until their dependency is resolved. Done requires evidence. Planning windows are targets, not promises. No private customer data belongs in this public development view.

How to record and complete work
  1. Open the existing Admin board to add or move a card. Keep the stable DEV or PROV task ID.
  2. Include the project, owner, priority, next action, acceptance check and dated evidence. Keep sensitive details in the private operations repository.
  3. For a new public development card, add its reviewed definition and backend ID to data/codex/development-board.json through the application repository, then deploy. Unreviewed backend cards are excluded from this public view.
  4. Move work to Review only with a concrete result. Move it to Done after the acceptance check and release evidence pass.
  5. Use MCP satcom_board with a project and small limit to retrieve only the task context needed.