FORGE CONTROL ROOM
Canterbury Locksmiths Ltd / Wayne Fisher
-
Total Projects
-
Live
-
Worklist
-
Critical Issues
Sync Health
Loading sync health...
Active Projects
Loading projects...
Motus Tab Status
Loading...
Critical & High Issues
| Severity | Issue | Blocks | Status |
|---|---|---|---|
| Loading... | |||
Ranked Worklist
The board, ranked. Ready work by severity band then load-bearing power (cr_next); blocked and parked behind toggles. Read-only; refreshes on load.
Ready — do these next
All Projects
Loading...
Loading...
Known Issues
Bugs, blockers, and outstanding tasks
Severity
State
Project
| Sev | Issue | Project | Description | State | |
|---|---|---|---|---|---|
| Loading... | |||||
Session Starter
Generate a context block to paste at the top of a new Claude chat
1. What do you want to achieve this session?
2. Select projects in scope
3. Your context block (copy this into Claude)
Session Protocol
START: Paste the context block above into a new Claude chat as your first message.
DURING: Card bodies are not in the block — they are often months stale. Ask for one with /pickup <CODE>, and check whether work is live with verify_deployed.py. Never infer either.
END: Type close out. That runs the whole docs/CLOSEOUT.md cycle — board recon, verify-deployed, review block, one approval, one commit.
CLOSE: Nothing to copy back. The close-out writes the board, the session doc and the handover itself.
DURING: Card bodies are not in the block — they are often months stale. Ask for one with /pickup <CODE>, and check whether work is live with verify_deployed.py. Never infer either.
END: Type close out. That runs the whole docs/CLOSEOUT.md cycle — board recon, verify-deployed, review block, one approval, one commit.
CLOSE: Nothing to copy back. The close-out writes the board, the session doc and the handover itself.
Tools & Subscriptions
Everything you're paying for and why
Loading...