@adaptic/maestro 1.0.0

package/docs/workflows/executive-cadence.md

@@ -0,0 +1,218 @@
+# Executive Cadence -- CEO Brain
+
+This document defines the full operating rhythm for the CEO Brain system. All times are GST (UTC+4, Asia/Dubai). Each cadence item maps to a workflow YAML definition and produces a defined output.
+
+---
+
+## Daily Cadence
+
+### 06:00 -- Morning Brief
+
+| Field            | Value                                                           |
+| ---------------- | --------------------------------------------------------------- |
+| **Workflow**     | `workflows/daily/morning-brief.yaml`                            |
+| **Owner**        | sophie-chief-of-staff                                           |
+| **Duration**     | ~30 minutes                                                     |
+| **Output**       | `outputs/briefs/daily/{date}/ceo-morning-brief.md`              |
+| **Template**     | `docs/prompts/morning-brief-template.md`                        |
+| **Dependencies** | Market data feeds, Gmail access, Slack access, executive memory |
+
+Steps: Market sweep, news intelligence scan, email triage, Slack triage, open loops review, workstream pulse, calendar review, synthesis. Parallel execution where possible. Final brief delivered by 06:30.
+
+### 08:00 -- Communications Triage (Morning)
+
+| Field            | Value                                                  |
+| ---------------- | ------------------------------------------------------ |
+| **Workflow**     | `workflows/daily/comms-triage.yaml`                    |
+| **Owner**        | sophie-chief-of-staff                                  |
+| **Duration**     | ~15 minutes                                            |
+| **Output**       | `outputs/followups/daily/{date}/routing-log-{time}.md` |
+| **Dependencies** | Slack, Gmail, WhatsApp access                          |
+
+Scans all inbound channels since the last triage. Extracts action items and routes them to appropriate queues. Updates executive memory with new open loops.
+
+### 12:00 -- Midday Communications Triage + Slack Follow-Up Sweep
+
+| Field            | Value                                                                             |
+| ---------------- | --------------------------------------------------------------------------------- |
+| **Workflow**     | `workflows/daily/comms-triage.yaml` + `workflows/daily/slack-followup-sweep.yaml` |
+| **Owner**        | sophie-chief-of-staff                                                             |
+| **Duration**     | ~20 minutes                                                                       |
+| **Output**       | Routing log + follow-up drafts                                                    |
+| **Dependencies** | Executive memory (open loops), communications policy                              |
+
+Comms triage runs first, then the follow-up sweep checks for overdue replies and commitments. Drafts follow-up messages using templates from `docs/prompts/followup-message-template.md`. Pre-approved messages are sent automatically; others are queued for CEO review.
+
+### 17:00 -- Afternoon Communications Triage + Slack Follow-Up Sweep
+
+Same as 12:00. Second sweep of the day to catch afternoon-accumulated items before the evening wrap.
+
+### 18:00 -- Evening Wrap
+
+| Field            | Value                                                              |
+| ---------------- | ------------------------------------------------------------------ |
+| **Workflow**     | `workflows/daily/evening-wrap.yaml`                                |
+| **Owner**        | sophie-chief-of-staff                                              |
+| **Duration**     | ~20 minutes                                                        |
+| **Output**       | `outputs/briefs/daily/{date}/ceo-evening-wrap.md`                  |
+| **Dependencies** | Morning brief, completed items, communications summary, open items |
+
+Summarises the day: what was completed, what remains open, communications sent and received, and priorities for tomorrow. References the morning brief to assess day-over-day progress.
+
+### 22:00 -- Overnight Monitoring Begins
+
+| Field        | Value                                  |
+| ------------ | -------------------------------------- |
+| **Workflow** | Passive monitoring (no dedicated YAML) |
+| **Owner**    | system                                 |
+| **Output**   | Accumulated for morning brief          |
+
+Low-frequency monitoring of critical channels. No active triage -- items accumulate for the 06:00 morning brief. System health checks continue.
+
+---
+
+## Weekly Cadence
+
+### Wednesday 10:00 -- Rollup Pipeline Review
+
+| Field            | Value                                                    |
+| ---------------- | -------------------------------------------------------- |
+| **Workflow**     | `workflows/weekly/rollup-pipeline-review.yaml`           |
+| **Owner**        | corporate-development                                    |
+| **Duration**     | ~30 minutes                                              |
+| **Output**       | `outputs/briefs/weekly/{date}/rollup-pipeline-review.md` |
+| **Dependencies** | Entity map, executive memory, regulatory filing status   |
+
+Reviews all acquisition pipeline targets: current stage, movement since last week, due diligence progress, new target scan, and regulatory filing status. Feeds into the Friday strategic memo.
+
+### Friday 14:00 -- Weekly Strategic Memo
+
+| Field            | Value                                                                                                           |
+| ---------------- | --------------------------------------------------------------------------------------------------------------- |
+| **Workflow**     | `workflows/weekly/strategic-memo.yaml`                                                                          |
+| **Owner**        | strategic-planning                                                                                              |
+| **Duration**     | ~45 minutes                                                                                                     |
+| **Output**       | `outputs/memos/weekly/{date}/strategic-memo.md`                                                                 |
+| **Template**     | `docs/prompts/weekly-strategic-memo-template.md`                                                                |
+| **Dependencies** | All daily briefs from the week, workstream status, competitive intelligence, pipeline update, regulatory update |
+
+The anchor document of the weekly cadence. Aggregates the full week into a strategic synthesis: key developments, workstream status for all five priorities, strategic implications, decisions needed, and risk watch.
+
+### Monday (manual) -- Priority Review
+
+| Field        | Value                                     |
+| ------------ | ----------------------------------------- |
+| **Workflow** | Manual review of `config/priorities.yaml` |
+| **Owner**    | sophie-chief-of-staff + CEO               |
+| **Output**   | Updated `config/priorities.yaml`          |
+
+CEO and Sophie review the priority stack. Reprioritise if needed. Update milestone statuses. This is a manual checkpoint that shapes the week ahead.
+
+---
+
+## Monthly Cadence
+
+### First Monday 09:00 -- Board Readiness Review
+
+| Field            | Value                                                                                     |
+| ---------------- | ----------------------------------------------------------------------------------------- |
+| **Workflow**     | `workflows/monthly/board-readiness.yaml`                                                  |
+| **Owner**        | board-prep                                                                                |
+| **Duration**     | ~45 minutes                                                                               |
+| **Output**       | `outputs/board/monthly/{date}/board-readiness-review.md`                                  |
+| **Dependencies** | Financial summary, strategic progress, risk register, regulatory status, pipeline summary |
+
+Assesses board readiness: what materials exist, what gaps remain, what updates are needed for the next board meeting. Covers financials, strategy progress, risk register, regulatory posture, and M&A pipeline.
+
+### End of Month -- Monthly Retrospective
+
+| Field        | Value                           |
+| ------------ | ------------------------------- |
+| **Workflow** | Manual (planned for automation) |
+| **Owner**    | sophie-chief-of-staff           |
+| **Output**   | Monthly retrospective document  |
+
+Review of the month: what worked, what didn't, adjustments to cadence, system performance metrics, and process improvements. Informs quarterly planning.
+
+---
+
+## Quarterly Cadence
+
+### First Monday of Quarter 09:00 -- Strategic Scenario Analysis
+
+| Field            | Value                                                                                                |
+| ---------------- | ---------------------------------------------------------------------------------------------------- |
+| **Workflow**     | `workflows/quarterly/strategic-scenario-analysis.yaml`                                               |
+| **Owner**        | strategic-planning                                                                                   |
+| **Duration**     | ~60 minutes                                                                                          |
+| **Output**       | `outputs/memos/quarterly/{date}/strategic-scenario-analysis.md`                                      |
+| **Dependencies** | Market assessment, competitive deep dive, regulatory outlook, pipeline assessment, platform maturity |
+
+Comprehensive scenario analysis across four scenarios (base case 35%, upside 10%, downside 35%, severe downside 20%). Covers macro environment, competitive landscape, regulatory developments, pipeline health, and platform readiness. Produces strategic recommendations for the quarter.
+
+### Quarterly -- OKR Refresh
+
+| Field        | Value                           |
+| ------------ | ------------------------------- |
+| **Workflow** | Manual (planned for automation) |
+| **Owner**    | sophie-chief-of-staff + CEO     |
+| **Output**   | Updated quarterly objectives    |
+
+Review quarterly objectives against actual progress. Set objectives for the next quarter. Align with the scenario analysis output.
+
+---
+
+## Cadence Dependencies Map
+
+```
+Daily Morning Brief (06:00)
+    |
+    v
+Comms Triage (08:00, 12:00, 17:00)
+    |
+    v
+Follow-Up Sweep (12:00, 17:00)
+    |
+    v
+Evening Wrap (18:00) <--- references Morning Brief
+    |
+    v
+(accumulates for 7 days)
+    |
+    v
+Weekly Pipeline Review (Wed 10:00) --+
+                                     |
+                                     v
+Weekly Strategic Memo (Fri 14:00) <--+-- aggregates all daily briefs
+    |
+    v
+(accumulates for ~4 weeks)
+    |
+    v
+Monthly Board Readiness (1st Mon) <--- references weekly memos
+    |
+    v
+(accumulates for ~3 months)
+    |
+    v
+Quarterly Scenario Analysis (1st Mon of quarter)
+```
+
+---
+
+## Workflow Inventory
+
+| Workflow                    | File                                                   | Schedule                    | Status  |
+| --------------------------- | ------------------------------------------------------ | --------------------------- | ------- |
+| Morning Brief               | `workflows/daily/morning-brief.yaml`                   | Daily 06:00                 | Defined |
+| Comms Triage                | `workflows/daily/comms-triage.yaml`                    | Daily 08:00, 12:00, 17:00   | Defined |
+| Slack Follow-Up Sweep       | `workflows/daily/slack-followup-sweep.yaml`            | Daily 12:00, 17:00          | Defined |
+| Evening Wrap                | `workflows/daily/evening-wrap.yaml`                    | Daily 18:00                 | Defined |
+| Rollup Pipeline Review      | `workflows/weekly/rollup-pipeline-review.yaml`         | Wednesday 10:00             | Defined |
+| Weekly Strategic Memo       | `workflows/weekly/strategic-memo.yaml`                 | Friday 14:00                | Defined |
+| Board Readiness Review      | `workflows/monthly/board-readiness.yaml`               | 1st Monday 09:00            | Defined |
+| Strategic Scenario Analysis | `workflows/quarterly/strategic-scenario-analysis.yaml` | 1st Monday of quarter 09:00 | Defined |
+
+---
+
+All times GST (UTC+4). Scheduling is configured in `config/environment.yaml`.

package/ingest/README.md

@@ -0,0 +1,87 @@
+# Ingestion Pipeline
+
+This directory contains configuration and processing artefacts for the Maestro agent's information ingestion pipeline. The pipeline is responsible for incorporating new documents, repository changes, and external information into the knowledge base.
+
+## Pipeline Flow
+
+```
+Source Identification
+        |
+        v
+Content Extraction
+        |
+        v
+Relevance Assessment
+        |
+        v
+Entity Extraction
+        |
+        v
+Memory Update
+        |
+        v
+Synthesis Generation
+```
+
+### 1. Source Identification
+
+New information sources are identified through:
+
+- Changes detected in registered source repositories (see `knowledge/sources/source-registry.yaml`)
+- Manual addition of new documents, emails, or meeting notes
+- Alerts from monitored external sources (regulatory updates, market data, news)
+
+Each source is validated against the source registry. New sources are evaluated for authority and relevance before being added to the registry.
+
+### 2. Content Extraction
+
+Raw content is extracted from the source in a structured format:
+
+- **Code repositories:** Diffs, new files, commit messages, PR descriptions
+- **Documents:** Full text extraction with metadata (author, date, version)
+- **Emails/communications:** Sender, recipients, subject, body, attachments
+- **Regulatory filings:** Structured fields, requirements, deadlines, conditions
+
+### 3. Relevance Assessment
+
+Extracted content is evaluated for relevance to active strategic domains:
+
+- Scored against active initiatives and open loops in executive memory
+- Classified by domain (regulatory, M&A, technology, fundraising, etc.)
+- Prioritised by urgency and strategic importance
+- Low-relevance items are logged but not promoted to active memory
+
+### 4. Entity Extraction
+
+Named entities are identified and reconciled against the entity map (`knowledge/entities/entity-map.yaml`):
+
+- People, companies, regulators, products, and targets
+- New entities are flagged for addition to the entity map
+- Relationships between entities are captured and updated
+
+### 5. Memory Update
+
+Relevant information is used to update executive memory (`knowledge/memory/executive-memory.yaml`):
+
+- Initiative status changes
+- New open loops or loop closures
+- Relationship updates (new contacts, last-contact dates)
+- Regulatory dependency changes
+- Pipeline progression (fundraising, hiring, rollup targets)
+
+### 6. Synthesis Generation
+
+Updated information is incorporated into the next scheduled synthesis cycle:
+
+- Critical updates trigger immediate digest generation
+- Routine updates are batched into the next daily digest
+- Domain-significant changes are flagged for the next weekly synthesis
+
+## Adding New Sources
+
+To add a new information source to the pipeline:
+
+1. Add an entry to `knowledge/sources/source-registry.yaml` with path, type, domains, and freshness check method.
+2. Run an initial ingestion pass on the source.
+3. Update the entity map with any new entities discovered.
+4. Verify that executive memory reflects any relevant state captured from the new source.

package/mcp/README.md

@@ -0,0 +1,51 @@
+# MCP Server Configuration
+
+This directory contains Model Context Protocol (MCP) server configurations for the Maestro agent system. MCP servers provide structured tool access for agents.
+
+## Active MCP Servers
+
+### Filesystem Access
+
+- **Purpose**: Read/write access to sophie-ai repo and source repositories
+- **Scope**: ~/sophie-ai, ~/adapticai, ~/ai-born, ~/ftlab-framework, ~/adaptic-legal, ~/dfsa-submission, ~/rollup-strategy
+
+### Web Fetch
+
+- **Purpose**: HTTP requests for market data, news, API access
+- **Scope**: Approved domains only
+
+### GitHub
+
+- **Purpose**: Repository management, PR monitoring, issue tracking
+- **Scope**: Adaptic.ai organisation repositories
+
+### Sequential Thinking
+
+- **Purpose**: Extended reasoning for complex strategic analysis
+- **Scope**: Available to strategic-planning and corporate-development agents
+
+### Memory
+
+- **Purpose**: Persistent memory across sessions
+- **Scope**: CEO Brain knowledge base
+
+## Planned MCP Servers
+
+### Google Calendar (via API)
+
+- **Purpose**: Calendar read/write for scheduling workflows
+- **Status**: Planned — requires OAuth setup
+
+### Slack API (supplementary)
+
+- **Purpose**: Programmatic Slack access in addition to desktop control
+- **Status**: Planned — requires workspace app installation
+
+### Linear / Project Management
+
+- **Purpose**: Task and project tracking integration
+- **Status**: Planned
+
+## Configuration
+
+MCP server configurations are defined in the Claude Code settings and `.mcp.json` files. See `config/mcp-servers.json` for the active configuration.

package/package.json

@@ -0,0 +1,48 @@
+{
+  "name": "@adaptic/maestro",
+  "version": "1.0.0",
+  "description": "Maestro — Autonomous AI agent operating system. Deploy AI employees on dedicated Mac minis.",
+  "type": "module",
+  "bin": {
+    "maestro": "./bin/maestro.mjs"
+  },
+  "files": [
+    "bin/",
+    "scaffold/",
+    "scripts/",
+    "agents/",
+    "workflows/",
+    "policies/",
+    "teams/",
+    "docs/",
+    "public/assets/",
+    "plugins/maestro-skills/",
+    "schedules/",
+    "desktop-control/",
+    "ingest/",
+    "mcp/",
+    ".claude/commands/",
+    ".claude/settings.json",
+    ".env.example",
+    "README.md"
+  ],
+  "publishConfig": {
+    "access": "restricted",
+    "registry": "https://registry.npmjs.org/"
+  },
+  "scripts": {
+    "prepublishOnly": "echo 'Publishing @adaptic/maestro...'"
+  },
+  "engines": {
+    "node": ">=20.0.0"
+  },
+  "os": [
+    "darwin"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/adapticai/maestro.git"
+  },
+  "author": "Adaptic.ai <dev@adaptic.ai>",
+  "license": "UNLICENSED"
+}

package/plugins/maestro-skills/plugin.json

@@ -0,0 +1,55 @@
+{
+  "name": "maestro-skills",
+  "version": "1.0.0",
+  "description": "Maestro operational skills — executive briefings, communications, hiring, strategy, and domain-specific workflows for autonomous AI agents",
+  "skills": [
+    {
+      "name": "morning-brief",
+      "description": "Produce the Morning Brief — priorities, overnight developments, open loops, workstream pulse. Universal across all agent archetypes."
+    },
+    {
+      "name": "evening-wrap",
+      "description": "Produce the Evening Wrap — what closed today, what didn't, tomorrow's priorities. Universal across all agent archetypes."
+    },
+    {
+      "name": "inbox-triage",
+      "description": "Triage all inbound communications across Slack, Gmail, and WhatsApp. Classify by urgency, draft responses, flag items for principal attention."
+    },
+    {
+      "name": "hiring-triage",
+      "description": "Review new job applications, AI screen candidates, draft advancement/rejection messages, produce hiring pipeline status."
+    },
+    {
+      "name": "slack-followup",
+      "description": "Check all pending Slack follow-ups — messages awaiting reply, commitments overdue, threads needing continuation."
+    },
+    {
+      "name": "weekly-memo",
+      "description": "Produce the Weekly Strategic Memo — synthesis of the week, workstream status, strategic implications, recommendations."
+    },
+    {
+      "name": "draft-comms",
+      "description": "Draft a communication in the appropriate voice (agent, principal draft, institutional). Applies communication governance rules."
+    },
+    {
+      "name": "decision-brief",
+      "description": "Present a decision to the principal with options, pros/cons, and a recommendation using structured decision framework."
+    },
+    {
+      "name": "pipeline-review",
+      "description": "Review the active pipeline — target status, progress, new items, regulatory/filing status."
+    },
+    {
+      "name": "board-deck",
+      "description": "Prepare board deck materials using Gamma for presentations and Mermaid for diagrams. Assembles content from all domain agents."
+    },
+    {
+      "name": "regulatory-status",
+      "description": "Check regulatory status across all relevant jurisdictions — gap progress, incorporation status, licensing timelines."
+    },
+    {
+      "name": "schedule-meeting",
+      "description": "Schedule a meeting using Google Calendar MCP or Calendly. Handle timezone conversion, find availability, send invites."
+    }
+  ]
+}

package/plugins/maestro-skills/skills/board-deck.md

@@ -0,0 +1,68 @@
+---
+name: board-deck
+description: Prepare board deck materials using Gamma for presentations and Mermaid for diagrams. Assembles content from all domain agents for board meetings.
+---
+
+# Board Deck Preparation
+
+You are Sophie Nguyen, Chief of Staff AI. Assemble and prepare board deck materials.
+
+## Data Sources
+
+1. **Financial data** — Read `memory/workstreams/finance.md` and `inputs/finance/` for latest financial metrics, P&L, cash position.
+2. **Acquisition pipeline** — Read `memory/workstreams/acquisitions.md` for deal pipeline status and completed transactions.
+3. **Regulatory progress** — Read `memory/workstreams/regulatory.md` for licensing status across all jurisdictions.
+4. **Hiring/team** — Read `memory/workstreams/hiring.md` for headcount, open roles, recent hires.
+5. **Product/tech** — Read `memory/workstreams/product.md` for platform development, integration milestones.
+6. **Strategic priorities** — Read `memory/executive/priorities.md` and `config/strategy.md` for the strategic narrative.
+7. **Weekly memos** — Read recent files from `outputs/briefs/weekly/` for trend data and synthesis.
+8. **Prior board deck** — Check `outputs/board/` for the last deck to maintain continuity.
+
+## Deck Structure
+
+Prepare content for the following slides (standard board deck order):
+
+```
+1. TITLE & AGENDA
+2. EXECUTIVE SUMMARY — 3-5 bullets, quarter highlights, key ask (if any)
+3. FINANCIAL OVERVIEW — Revenue, burn, runway, key metrics vs plan
+4. ACQUISITION PIPELINE — Funnel visual, active targets, closed deals
+5. REGULATORY STATUS — Jurisdiction matrix, timeline to licensing
+6. TEAM & HIRING — Org chart changes, key hires, open roles
+7. PRODUCT & TECHNOLOGY — Platform milestones, integration status
+8. STRATEGIC OUTLOOK — Market positioning, next quarter priorities
+9. RISKS & MITIGATIONS — Top 3 risks with mitigation plans
+10. ASK / DISCUSSION ITEMS — Decisions needed from the board
+```
+
+## Diagram Generation
+
+Use Mermaid syntax for the following standard diagrams:
+
+- **Acquisition funnel** — Stages with target counts
+- **Regulatory timeline** — Gantt chart across jurisdictions
+- **Org chart** — Current team structure
+- **Financial trend** — Key metric trajectories
+
+Save Mermaid diagrams to `outputs/board/diagrams/`.
+
+## Presentation Assembly
+
+1. Write each slide's content as a structured markdown section in `outputs/board/board-deck-YYYY-MM-DD.md`.
+2. Include speaker notes for Mehran under each slide.
+3. If Gamma MCP or API is available, generate the presentation directly. Otherwise, prepare content ready for manual Gamma import.
+4. Flag any data gaps — sections where the data is stale or missing.
+
+## Output
+
+1. Full deck content to `outputs/board/board-deck-YYYY-MM-DD.md`.
+2. Mermaid diagrams to `outputs/board/diagrams/`.
+3. Speaker notes included inline.
+4. Present a summary of the deck with any data gaps or decisions needed before the board meeting.
+
+## Quality Checks
+
+- Every metric must have a source reference and a date stamp.
+- Compare current period to prior period and plan/budget.
+- No surprises — anything in the deck should have been in a weekly memo already.
+- Board tone: confident but transparent. Acknowledge challenges directly.

package/plugins/maestro-skills/skills/decision-brief.md

@@ -0,0 +1,89 @@
+---
+name: decision-brief
+description: Present a decision to the CEO with options, pros/cons, and a recommendation. Uses the decision recommendation template for structured decision-making.
+---
+
+# Decision Brief
+
+You are Sophie Nguyen, Chief of Staff AI. Present a structured decision for Mehran to make.
+
+## Required Inputs
+
+When invoked, gather from the user (or infer from context):
+
+- **Decision**: What needs to be decided?
+- **Context**: Why is this decision needed now? What triggered it?
+- **Constraints**: Timeline, budget, dependencies, regulatory requirements
+- **Stakeholders**: Who is affected by this decision?
+
+## Data Gathering
+
+1. **Read relevant workstream files** from `memory/workstreams/` for domain context.
+2. **Check prior decisions** in `memory/executive/decisions.md` for precedent or related choices.
+3. **Read strategic priorities** from `memory/executive/priorities.md` to assess alignment.
+4. **Check templates** in `templates/decision-brief.md` for the standard format.
+5. **Gather any external data** relevant to the decision using available tools.
+
+## Decision Brief Structure
+
+```
+# Decision Brief: [Short Title]
+**Date**: [DATE]
+**Decision Owner**: Mehran
+**Prepared by**: Sophie Nguyen
+**Urgency**: [Decide today / This week / Can wait]
+
+## Context
+[2-3 sentences: why this decision is needed now, what happens if we don't decide]
+
+## Options
+
+### Option A: [Name]
+- **Description**: [What this option entails]
+- **Pros**:
+  - [Pro 1]
+  - [Pro 2]
+- **Cons**:
+  - [Con 1]
+  - [Con 2]
+- **Cost/Effort**: [Estimate]
+- **Risk Level**: [Low/Medium/High]
+
+### Option B: [Name]
+[Same structure]
+
+### Option C: [Name] (if applicable)
+[Same structure]
+
+## Comparison Matrix
+| Criteria | Option A | Option B | Option C |
+|---|---|---|---|
+| Strategic alignment | [H/M/L] | [H/M/L] | [H/M/L] |
+| Speed to execution | [H/M/L] | [H/M/L] | [H/M/L] |
+| Cost | [$] | [$] | [$] |
+| Risk | [H/M/L] | [H/M/L] | [H/M/L] |
+| Reversibility | [H/M/L] | [H/M/L] | [H/M/L] |
+
+## Sophie's Recommendation
+**I recommend Option [X]** because [2-3 sentence rationale connecting to strategic priorities and current constraints].
+
+**Key risk to mitigate**: [The biggest risk of this option and how to address it]
+
+## Next Steps (if approved)
+1. [Immediate action]
+2. [Follow-up action]
+3. [Communication needed]
+```
+
+## Output
+
+1. Save to `outputs/decisions/decision-brief-[topic]-YYYY-MM-DD.md`.
+2. Log the decision (once made) to `memory/executive/decisions.md` with date, choice, and rationale.
+3. Present the brief in conversation and await Mehran's decision.
+
+## Principles
+
+- Always present at least 2 options (including "do nothing" if applicable).
+- Be honest about tradeoffs — don't stack the deck for your recommendation.
+- Make the recommendation clear and confident, but respect that the decision is Mehran's.
+- Flag if this decision is reversible vs. one-way door.