pla-status-thread-eta
PLA Status Thread: Always Carry the Estimated Completion Time
Section titled “PLA Status Thread: Always Carry the Estimated Completion Time”Extends project-status-thread.md (core, t1k-plane) for playable-ad (PLA) projects: any project whose
repo ends in PLA or that builds a playable through t1k-playablelabs-*.
Every post in the project’s status thread (start, milestone, blocked, done) carries these lines, under the
### Time estimate heading:
- ETA to the next human step (usually stage 19 playtest) as a clock time in UTC and in the owner’s local time, never only a duration.
- Basis: measured (from run-log stage timings) or rough (not measured yet). A rough ETA says so.
- Change since the last post: earlier, later, or unchanged, with the reason when later.
- Builds: Jenkins builds so far, and the expected count to green QA.
When a milestone moves the ETA, the post says so in the same message. At DONE the post gives actual wall-clock against the first ETA.
Estimates come from measured stage durations in run-<game>.md first; with none, from the lane’s
t1k-estimator / /t1k:estimate output, else a stated rough range. Never invent a precise time.
Same limits as the parent rule: milestones only, at most one update per 5 minutes, no secrets, sub-agents never post.