Briefs

Input and handoff documents that fed a specific session of agent-executed work against this repo. They are preserved for historical reference, not as living documents.

What goes here

• Session handoffs (SESSION_BRIEF_*.md). Written at the end of a session to brief the next session — either a sibling parallel session running against the same repo, or the same agent picking up after a context gap. Short, scoped, often name state that was left behind (account IDs, resource ARNs, outstanding items).
• Build briefs (BRIEF_*.md). Written by a human before a session to tell the agent what to build, why, and under what constraints. The output of those sessions landed in tracked code + docs; the brief is kept alongside as the input-of-record.
• System briefings (*_BRIEFING.md). Point-in-time snapshots of the system as it existed at that date. Useful for diffing "how did the system look then vs. now" when an auditor or future contributor asks.

What does NOT go here

• Long-form session records. Those go in docs/session-log/. The distinction is audience and shape:
  • A brief is short, pragmatic, and consumed once.
  • A session log is long, narrative, and read later for audit evidence.
• Change records of infrastructure. Those go in docs/infrastructure/change-log.md.
• Secrets or credentials. Never in any file under this directory. A brief can name a secret (e.g. "MONGODB_URI_WAITLIST_WRITE") but never its value.

Naming

• SESSION_BRIEF_<YYYY-MM-DD>[_topic].md
• BRIEF_<SHORT_TOPIC>.md
• <TOPIC>_BRIEFING.md

Existing files predate strict naming and are kept as-is for link stability.

Index

• SESSION_BRIEF_2026-04-16_17.md — handoff across the 2026-04-16 / 17 session boundary.
• SESSION_BRIEF_2026-04-17_atlas.md — Atlas-session handoff to AWS migration session (precedent for the 2026-04-17-atlas-staging session log).
• ASKFLORENCE_SYSTEM_BRIEFING.md — 2026-04-17 point-in-time system briefing, v0.3.2.
• BRIEF_CA_PROPOSAL.md — input brief for building /creative-adbundance/proposal, consumed in v0.16.0.
• creative-adbundance-analytics-brief.md — partner-facing handoff explaining the user flow, the auth-wall cut between marketing and portal, and the per-tool compliance review loop. Authored 2026-05-11 for ENG-280. Companion to the internal Marketing vs. Portal Analytics control doc.
• BRIEF_FLORENCE_AI_ARCHITECTURE.md — 2026-04-22 input brief framing the Florence AI architecture + infrastructure research track. Not finalized architecture; authoritative decisions live on the Florence AI architecture parent GitHub issue.
• doctor-rx-session-prompt.md — input prompt for the parallel doctor-rx worktree (research-first; consumed by the worktree's session brief).
• plans-redesign-brief.md — input brief for the /plans page redesign worktree (Wave 1 shipped in v0.36.0).
• SESSION_PROMPT_2026-05-01_tier-0-5-federal.md — input prompt for the Tier 0.5 federal+NY ZIP USPS-completeness audit + apply session (#80). Outcome header at top; full reports in docs/validation/tier-0-5-federal-uspscompleteness.md + audit-operations-runbook.md.