Report Stack Mapper
Map the source layer before you automate the brief.
List the reports behind the morning view, then turn the messy stack into a clean operating summary you can bring to a workflow review.
Cedar workbench
Turn the stack into a usable review note.
How to read the map
The useful parts are the places where trust can break.
Once the reports are visible, the first pilot can define required versus optional sources, arrival windows, business-date rules, and what the brief should say when the morning is incomplete.
Required sourceIf it is missing, dependent KPIs should block or be clearly blanked.Trust
Optional sourceIf it is late, the output can ship with a visible caveat and rerun path.Caveat
Manual sourceIf a person edits it, the pilot needs approval rules and handoff notes.Owner
Wrong date riskBusiness-date checks should happen before any AI summary or recommendation.Blocker
Next step
The map is the start of the pilot scope.
Once source reports are visible, the build can define required inputs, late-file behavior, business-date checks, and the prepared output.