Policy — Operating Cadence & Integrations
NOT YET ACTIVE — The automated briefing/report cadence described below (daily-reports workflow, SessionStart/SessionEnd Notion posts) is a no-op. The required secrets (ANTHROPIC_API_KEY, NOTION_TOKEN, NOTION_REPORTS_PAGE — AR-003) have not been wired in GitHub Actions. Until AR-003 is resolved, no automated briefings or reports are generated or posted. The times and sequences below describe the intended cadence, not current behaviour.
HR documentation · binding. How sessions open and close, the daily cadence, the timezone, and the integration channels. Consolidates decisions made across the org’s build.
Timezone
America/New_York (Atlanta). Daily times: 06:00 briefing, 17:00 day’s report.
Session open (SessionStart hook)
- Verify archive integrity (Archivist).
- MCP-reconcile with the Notion “Agents” registry (read-only;
/agents:sync). - Boot into org / Personal-Assistant posture.
- The PA writes the daily briefing and posts it to the Notion “Daily Reports” page (06:00 ET).
Session close (SessionEnd hook + agent routine)
- Verify integrity; warn on uncommitted / unpushed work.
- MCP-reconcile (
/agents:sync) — the agent’s close routine. - The PA writes the day’s report and posts it to the Notion “Daily Reports” page (17:00 ET).
- Capture decisions — reconcile the session’s decisions and directives into
rules (
CLAUDE.md) and policies (hr/policies/) (GR-6). - The SessionEnd hook posts the Notion API session log.
Channels
- MCP in-session (the agent), Notion API unattended (hooks / the
daily-reportsworkflow). Daily reports and reviews go to Notion. - Email is not used for the daily cadence.
Status
NOT YET ACTIVE (see notice at top of file).
The daily-reports workflow and the Notion API posts are gated and no-op
until the AR-003 secrets (ANTHROPIC_API_KEY, NOTION_TOKEN,
NOTION_REPORTS_PAGE) are set in GitHub Actions (per SOP-004).
Until AR-003 is resolved:
- No automated briefings or reports are generated or posted to Notion.
- The SessionStart/SessionEnd MCP reconciles and Notion posts described above do not run automatically.
- Briefings and reports may be produced manually, in-session, by the PA if needed.
The 06:00/17:00 times and the session lifecycle sequences describe the intended automated cadence, not behaviour that currently fires.