Skip to main content

How to read weekly bulletins

When you'd read this: when you want a running record of what changed in your application this week, without tracking every backlog edit and release event by hand.

A weekly bulletin is a per-application report of change over the past week — backlog items created, elaboration stage moves, dependency changes, and release scope/plan activity. It is generated automatically; there is nothing to click to make one exist.

Where bulletins come from​

A scheduled job runs every Monday and generates one bulletin per application, covering the week since the previous one. There is no on-demand "generate now" button, and no way to trigger one from the UI — this is deliberate. The absence of a trigger is also why a bulletin never appears the moment you want it: if this week's hasn't landed yet, wait for the next scheduled run.

If a run is delayed or fails, the next successful bulletin simply covers the longer, extended period — nothing is skipped or lost, it just arrives as one wider report instead of several narrow ones.

Why bulletins contain no AI-generated content​

Every figure in a bulletin is a straightforward difference between two recorded states in the database — "3 backlog items were created," "this item moved from E1 to E2." No model call is involved anywhere in producing one. That is what makes a weekly bulletin cheap to generate and safe to trust without review: there is no judgement in it to be wrong about, only recorded fact.

Where to find bulletins​

Open your application's dashboard (My Application) and look in the Tools & Reports panel. It shows how many bulletins exist and the date of the most recent one; click through to the full list.

Reading a bulletin​

Each bulletin lists six change categories for its period:

  • Backlog items created
  • Elaboration stage transitions — forward and backward reported separately, never netted against each other, so a regression is never hidden behind an unrelated advance elsewhere
  • Dependencies added and dependencies removed — also always separate
  • Release scopes created and release scopes closed
  • Release plan state transitions

Each category is collapsed by default; click its heading to drill into the individual entries (which items, which stages, which scopes and plans).

Exporting a bulletin​

Open a bulletin and use Export as JSON to download its full content as a file — useful for archiving a period's figures outside the application, or feeding them into your own reporting. Export is always a manual, human-initiated action; nothing is emailed or otherwise sent out automatically.

If you see "Bulletin generation failed"​

Occasionally a bulletin's generation run fails (after one automatic retry) and, instead of a real bulletin, you'll see a placeholder reading "Bulletin generation failed — this requires investigation." This is not a bulletin — no real figures were computed for that period. It exists only so the gap is visible rather than silently missing. The next successful run will automatically extend back and cover everything since the last real bulletin, so nothing from the failed period is permanently lost — but a repeated failure needs a person to look into why, since generation won't fix itself by retrying alone.

Result​

A quiet, cumulative record of your application's backlog and release activity, arriving once a week with no spending cost and nothing for you to review unless something looks wrong.