TROUPE STANDUP PROTOCOL DRAFT v0.1

Drafted by: quill Date: 2026-10-29 Status: DRAFT — needs troupe review before adoption

PURPOSE

Standardize how each wizard submits a standup entry so the standup-bot can aggregate them into a clean daily report without post-processing.

SCOPE

Applies to every wizard with a wizard-work/<name>/ directory under /root/troupe-standup/.

ENTRY FORMAT

File name: standup-.md Location: /root/troupe-standup/wizard-work//

Required front-matter block (YAML-ish, plain text):

Wizard:   <name>
Date:     <YYYY-MM-DD>
Lane:     <lane-name>
Status:   green | yellow | red

Status definitions: green — on track, no blockers yellow — at risk, needs decision or help red — blocked, cannot proceed

Required body sections (in order):

DONE (bullet list)
- Each bullet: one shipped artifact with absolute path
- No vague claims like "worked on X"
BLOCKERS (bullet list or "None")
- State exactly what is missing and from whom
NEXT (bullet list)
- Next concrete artifact to ship, with target path
EVIDENCE CHECK (one line)
- A single shell command whose exit code reflects status: exit 0 = done, no blockers exit 2 = at risk (yellow) exit 3 = blocked (red)

VERIFICATION

The standup-bot will:

Verify the file exists at the expected path.
Parse Wizard, Date, Lane, Status from the front-matter.
Run the EVIDENCE CHECK command; non-zero exit is a failure.
Collect all DONE, BLOCKERS, NEXT into the daily report.
Flag entries with missing sections or unparseable front-matter.

ESCALATION

If a wizard's EVIDENCE CHECK exits non-zero for two consecutive days, the standup-bot opens a ticket in the inbox/ directory addressed to Alexander.

CHANGELOG

v0.1 — 2026-10-29 — Initial draft (quill)

VERDICT: Draft artifact written and verified on disk. CHECK: test -f /root/troupe-standup/wizard-work/quill/standup-2026-10-29.md && test -s /root/troupe-standup/wizard-work/quill/standup-2026-10-29.md

2.1 KiB Raw Permalink Blame History