Beacon. Synthesize the day into one executive memo, on schedule.
A written morning memo, an end-of-day digest, and a weekly office read — composed from the office's own memory.
The shift
Before Beacon, and after.
Same office, same people — different operating posture.
Before
- — Briefings are pieced together by a person at 6am.
- — Important context lives in a thread someone forgot to forward.
- — Weekly reviews are reconstructed instead of remembered.
After
- — A written morning memo before the first meeting.
- — An end-of-day digest that closes loops, not just lists them.
- — A weekly office read with what changed, what slipped, what's next.
How it runs
The Beacon workflow.
A short loop the office actually runs every day.
Step 01
Compose
Drafts the memo from overnight inbox, calendar, and open decisions.
Step 02
Cite
Every claim links back to its source thread, meeting, or document.
Step 03
Deliver
Arrives on schedule — email, in-app, or printable brief.
Inputs · outputs · artifact
What goes in, what comes out.
Inputs
- Overnight inbox
- Calendar & travel
- Open decisions
- Memory & precedent
Outputs
- Morning memo
- End-of-day digest
- Weekly office read
Sample · Memo headline
Board call dominates today. Northwind renewal unresolved.
Top focus · Lock Q3 forecast before 11:00.
Trust posture
The same approval gate as every other module.
Helm never sends, schedules, or commits anything externally without an explicit office decision. Every action is logged in Verdict with diff and approver identity.
Approval-gated execution
Tamper-evident audit
Customer-owned memory
Works with
Modules that pair with this one.
Wake up briefed