Question 1

What does monthly executive summary drafting actually deliver, and how does the 4-skill bundle decompose?

Accepted Answer

An orchestration layer that sits above the operator BI + warehouse + financial-planning + reverse-ETL + LLM-drafting + document-generation + board-management + investor-reporting + policy-as-code + WORM-storage stack and produces the monthly executive summary that goes to the CEO + CFO + COO + CMO + Board + PE-LP investors + franchisor leadership + franchisee council. The skill is a four-skill bundle on the rollup-reporting agent. Skill 1 — Roll-Up: pull canonical metrics from the operator data warehouse (Snowflake, Databricks, BigQuery, Redshift, ClickHouse — operator chooses), the operator BI semantic layer (Looker, Tableau, Power BI, Sigma, Hex, Mode, Preset, ThoughtSpot, Domo, Sisense, Qlik — operator chooses), and the operator FP&A platform (Anaplan, Adaptive Insights, Pigment, Mosaic, Cube, Vena, Planful, Workday Adaptive, Causal, Pry, Drivetrain, Finmark, Jirav — operator chooses). The Roll-Up produces a canonical metric set defined by operator finance + operator counsel — typical metric families include revenue (gross, net, recognized under ASC 606), same-store-sales, new-customer acquisition, customer retention and churn, LTV and CAC by cohort, marketing-attributed revenue, channel mix, per-location performance, per-vertical performance, working capital, AI-swarm operating cost. Roll-Up never invents metrics; it reads what the operator data team has defined and what the operator finance team has reconciled. Non-GAAP measures (adjusted EBITDA, adjusted revenue, contribution margin) carry their SEC Regulation G reconciliation to the closest GAAP measure when the operator is a public registrant or controlled subsidiary. Skill 2 — Draft: generate the narrative using the operator-chosen LLM (Anthropic Claude, OpenAI GPT, Microsoft Copilot, Google Gemini, Mistral — operator chooses, with operator-approved deployment posture). The Draft skill produces a structured narrative aligned to the operator-counsel-approved executive-summary template — headline summary, variance commentary against the operator-approved plan, root-cause hypotheses (clearly framed as hypotheses, not conclusions), forward outlook with stated assumptions, actions in progress, open questions. Draft never asserts material-incident-class claims (cybersecurity incident, material adverse change, MNPI-class events) — those route through operator counsel + CFO + disclosure committee before any drafting language commits. Draft preserves attorney-client privilege markers and MNPI markers from the operator counsel repo by refusing to incorporate flagged content into the distributed draft. Skill 3 — Distribute: route the final approved draft to the operator-defined distribution list with per-recipient scope filtering. The CEO and CFO see the full draft. The Board sees a board-formatted version generated through the operator board-management vendor (Diligent, OnBoard, Boardable, BoardEffect, BoardPaq, Govenda — operator chooses). PE-LP investors see an LP-formatted version generated through the operator investor-reporting vendor (Carta, Pulley, Allvue, eFront, iLevel, Dynamo, Juniper Square, Ontra, Aduro Advisors — operator chooses) following the operator LPA reporting obligations + ILPA Quarterly Reporting Standards templates + AICPA valuation guidance + the per-investor confidentiality covenants in the LPA. Franchisor leadership sees the franchisor view; franchisee council sees a franchisee-scoped view that respects FDD Item 19 Financial Performance Representations restrictions — any metric distributed to franchisees that could be construed as an FPR must comply with FTC Franchise Rule 16 CFR Part 436 substantiation and FDD update timing or be removed from the franchisee view. Skill 4 — Attest: emit the per-distribution attestation record (recipient list, version hash of the distributed document, attestor identity, distribution timestamp, per-recipient scope filter applied, counsel-policy-version that governed scope filtering, MNPI-handling attestation, SEC Reg FD selective-disclosure attestation when applicable). The attestation lives in the operator WORM audit trail and forms the chain-of-custody evidence the operator needs in a future SEC inquiry, state-AG investigation, FTC matter, franchisee dispute, or LP audit. The BI, warehouse, financial-planning, reverse-ETL, LLM, document-generation, board-management, investor-reporting vendors below ship strong primitives. The orchestration above them — operator-counsel-approved scope filtering per audience, SEC Reg FD selective-disclosure enforcement, FDD Item 19 substantiation enforcement for franchisee views, ILPA + LPA reporting compliance for LP views, MNPI quarantine, attorney-client privilege preservation, audit trail — is operator-side architecture.

Question 2

Where does single-vendor BI dashboarding stop compounding for monthly executive summary drafting?

Accepted Answer

Single-vendor BI dashboarding is solved. Looker ships a strong semantic layer + dashboards. Tableau and Power BI ship strong BI. Anaplan and Adaptive Insights ship strong financial planning. Carta and Juniper Square ship strong investor reporting. Diligent ships strong board management. The compound case the rollup-reporting agent has to handle is the one where the same monthly close produces (a) an internal management view, (b) a CEO + CFO + COO + CMO + General Counsel staff-meeting view, (c) a Board view that becomes a board-meeting package, (d) a PE-LP investor view that flows through ILPA Quarterly Reporting Standards templates + the operator-specific LPA reporting covenants + the AICPA valuation guidance (ASC 820 fair value) + the per-investor confidentiality side letters, (e) a franchisor-leadership view, (f) a franchisee-council view that must respect FDD Item 19 Financial Performance Representations restrictions under FTC Franchise Rule 16 CFR Part 436, (g) — for public registrants — a Reg FD-compliant view that avoids selective disclosure of MNPI to one investor class before others, (h) — for public registrants — a Reg G compliant non-GAAP reconciliation when the summary includes non-GAAP measures, (i) — when an SEC Reg S-K Item 1.05 material cybersecurity incident has been determined within the month — a coordinated disclosure that respects the four-business-day disclosure window. Per-distribution scope filtering needs operator-counsel-approved policy because the same number (an attribution-credit revenue figure, a churn cohort, an AI-swarm cost) may be reportable to the Board but not to franchisees, or reportable to LP investors but not to retail franchisees, or reportable through ILPA templates but not through public marketing. FTC Pfizer 1972 reasonable-basis substantiation applies when marketing-attributed revenue figures get carried forward into marketing claims (a CMO who quotes attribution figures from the monthly summary in an outbound pitch deck is making a marketing representation that the FTC will hold to substantiation). Attorney-client privilege preservation across drafts and distributions requires the orchestration to refuse to incorporate operator-counsel-flagged content into LLM drafting prompts. MNPI handling for public registrants and registrants with controlled subsidiaries requires the orchestration to quarantine MNPI from drafting paths until disclosure-committee approval clears it for the appropriate distribution class. Without an orchestration layer above the BI + warehouse + financial-planning + LLM + board + investor-reporting vendors, per-audience scope filtering breaks down (the franchisee view leaks metrics that fall under FDD Item 19), SEC Reg FD selective-disclosure controls fail (a quote in a board package leaks to investors before the Reg FD-compliant disclosure), ILPA + LPA reporting obligations miss covenants, MNPI quarantine fails, attorney-client privilege breaks when LLM prompts contain privileged content, and the audit trail of "which version, to which recipient, with what scope filter, under which counsel policy version, with what MNPI attestation" fragments across consoles. The orchestration above the vendors is what holds the cross-vendor + cross-audience + cross-regulatory invariants.

Question 3

How does Skill 2 Draft preserve attorney-client privilege and quarantine MNPI when an LLM is in the loop?

Accepted Answer

Privilege and MNPI quarantine sit at the prompt-construction boundary, before any LLM call. Step 1 — operator counsel maintains a privilege-flagged content register and an MNPI register in the operator counsel repo. Privilege-flagged content includes any communication or document that operator counsel has identified as covered by attorney-client privilege or attorney work-product doctrine. MNPI-flagged content includes material non-public information per the operator counsel definition (material in the sense that a reasonable investor would consider it important; non-public in the sense that it has not been disclosed through Reg FD-compliant channels). Step 2 — the orchestration prompt-construction layer reads every candidate input (metric values from the warehouse, FP&A commentary, prior-month narrative, plan variance commentary, root-cause notes from the operator data team) and checks against the privilege and MNPI registers before constructing the LLM prompt. Flagged content does not enter the prompt. The orchestration records the suppressed-content identifiers in the audit trail without recording the content itself, preserving privilege over the suppression event. Step 3 — the LLM call runs on operator-approved infrastructure (operator-deployed LLM, operator BAA-equivalent with the LLM vendor, operator zero-retention configuration when the vendor offers it). For Anthropic Claude, OpenAI GPT, Microsoft Copilot, Google Gemini, or Mistral, the operator chooses the deployment posture (cloud vendor + region + retention + audit + per-account isolation) under operator counsel policy. Step 4 — the LLM output passes through a post-generation review checklist before any human reviewer sees it. The checklist verifies that no MNPI-equivalent content surfaces via inference (a hallucinated number resembling an MNPI metric), that no privileged-content reference surfaces, that any non-GAAP measure used in the draft has its Reg G reconciliation attached, that any forward-looking statement carries the operator-counsel-approved safe-harbor language for public registrants. Step 5 — human review by operator finance + operator counsel + CFO is required before the draft is approved for any distribution. The orchestration does not autonomously approve drafts. The Distribute skill refuses to route a draft to any audience until the operator-counsel-approved approval gate has cleared. Step 6 — the audit trail records the prompt-construction policy version + suppression events + LLM vendor and deployment posture + post-generation checklist version + reviewer chain with timestamps to the WORM audit trail with per-statute retention.

Question 4

How does Skill 3 Distribute enforce SEC Reg FD + FDD Item 19 + ILPA + LPA covenants + FTC reasonable-basis substantiation per audience?

Accepted Answer

The Distribute skill runs a per-audience scope filter against the operator-counsel-approved distribution matrix. For public registrants and their controlled subsidiaries, SEC Regulation FD (17 CFR 243) prohibits selective disclosure of MNPI to securities-market professionals or shareholders before broad public disclosure. The orchestration enforces this by refusing to route MNPI-flagged content to any selective audience (Board package, LP package, franchisor-only view) without disclosure committee approval that the content has either been broadly disclosed or qualifies under a Reg FD exception (Rule 100(b)(2) exceptions for persons owing duties of trust or confidence, ordinary-course communications, transient communications). When the disclosure path requires a Form 8-K, the orchestration surfaces the requirement to operator counsel + CFO + disclosure committee. For non-GAAP financial measures, SEC Regulation G + Item 10(e) of Regulation S-K require reconciliation to the most directly comparable GAAP measure, prohibit titles confusingly similar to GAAP titles, and require the GAAP measure to receive equal or greater prominence; the Distribute skill verifies non-GAAP usage in the draft carries the reconciliation. For SEC Reg S-K Item 1.05 (effective December 18, 2023) material cybersecurity incidents, the orchestration verifies that any cybersecurity-related content in the monthly draft has been routed through the disclosure committee’s materiality assessment within the four-business-day disclosure window. For franchisor operators distributing any view to franchisees, the FTC Franchise Rule 16 CFR Part 436 + FDD Item 19 governs Financial Performance Representations. The Distribute skill refuses to route any metric to franchisees that meets the FPR definition unless the metric has been included in the current FDD with proper substantiation; metrics that have not been so included get removed from the franchisee view. State franchise-registration states (14 states with active franchise-registration requirements: California, Hawaii, Illinois, Indiana, Maryland, Michigan, Minnesota, New York, North Dakota, Rhode Island, South Dakota, Virginia, Washington, Wisconsin) and the 23 franchise-relationship states add per-state filing + per-state disclosure overlays. For PE-sponsored portfolio operators, the LPA-specific reporting covenants govern LP distribution. ILPA Quarterly Reporting Standards (Capital Account Statement template + Cash Flow Templates + Fee and Expense templates) provide standardized templates that many LPAs adopt. AICPA valuation guidance (ASC 820 fair value measurement, ASC 825 financial instruments) governs fair-value disclosures. FINRA Rule 2210 communications standards apply when distributions reach retail-customer LPs. The orchestration emits the LP package through the operator investor-reporting vendor (Carta, Allvue, eFront, iLevel, Juniper Square, Dynamo, Ontra — operator chooses) using the LPA-compliant template. For metrics that may carry forward into operator marketing (a CMO who would quote attribution-attributed revenue in an outbound pitch), the orchestration tags the metric with the FTC Pfizer 1972 reasonable-basis substantiation chain so downstream marketing claims can demonstrate the substantiation. The Distribute skill writes per-distribution attestation (recipient, version hash, scope filter applied, counsel-policy-version) to the WORM audit trail.

Question 5

What compliance does the orchestration enforce, and how does it map to SEC Reg FD/Reg G/SOX/MNPI + FDD Item 19 + ILPA/LPA + FTC substantiation + privilege/Rule 10b5-1?

Accepted Answer

Five anchors. Anchor 1 — SEC Regulation Fair Disclosure (17 CFR 243) + SEC Regulation G + Item 10(e) of Regulation S-K non-GAAP financial measures + SEC Reg S-K Item 1.05 Material Cybersecurity Incidents (effective December 18, 2023, four-business-day disclosure window) + SOX Section 302 CEO/CFO certification + Section 404 internal control over financial reporting + Material Non-Public Information handling for public registrants and controlled subsidiaries. The Distribute skill enforces Reg FD selective-disclosure prohibitions; the Draft skill quarantines MNPI from LLM prompts; the orchestration verifies Reg G non-GAAP reconciliations attach to any non-GAAP measure used; the orchestration verifies the SOX-implicating metrics in the draft have been reconciled to the financial close. Anchor 2 — Franchise Disclosure Document Item 19 Financial Performance Representations under FTC Franchise Rule 16 CFR Part 436 (FPR substantiation requirements, FDD update timing, prohibition of FPR outside the FDD or sales calls about prospective franchisees) + per-state franchise registration in 14 registration states (California, Hawaii, Illinois, Indiana, Maryland, Michigan, Minnesota, New York, North Dakota, Rhode Island, South Dakota, Virginia, Washington, Wisconsin) + 23 state franchise-relationship laws governing termination, non-renewal, transfer, encroachment. The Distribute skill removes FPR-class metrics from franchisee views unless properly substantiated in the current FDD. Anchor 3 — PE/LP investor reporting standards. ILPA Quarterly Reporting Standards (Capital Account Statement template + Cash Flow Templates + Fee and Expense templates — widely adopted across the PE LP community since 2011 and updated through subsequent versions) + per-fund LPA reporting covenants and confidentiality side letters + AICPA valuation guidance (ASC 820 fair value measurement, ASC 825 financial instruments) + FINRA Rule 2210 communications standards when distributions reach retail-customer LPs + ILPA Principles 3.0 on alignment of interests, governance, transparency. The Distribute skill emits LP packages through the operator investor-reporting vendor with LPA-compliant templates. Anchor 4 — FTC Section 5 unfairness and deception + FTC Pfizer 1972 reasonable-basis substantiation doctrine + Lanham Act 15 USC 1125(a) false advertising + state UDAP + FTC Endorsement Guides 2024 + FTC Fake Review Rule 16 CFR Part 465 (effective October 2024) when monthly-summary metrics carry forward into marketing claims. The orchestration tags substantiation chains on metrics so downstream marketing can demonstrate reasonable basis. Anchor 5 — Attorney-client privilege + attorney work-product doctrine preservation + Material Non-Public Information handling + insider-trading prophylactics including SEC Rule 10b5-1 trading plan coordination for public registrants (when an executive on a Rule 10b5-1 plan is set to transact in a window adjacent to monthly close, the disclosure committee evaluates whether the monthly summary contains MNPI that would require the 10b5-1 plan to be paused or the disclosure timing adjusted) + state-AG litigation-hold preservation + Federal Rule of Civil Procedure 26 work-product protections. The orchestration’s prompt-construction privilege quarantine + post-generation MNPI scan + disclosure-committee approval gate enforce these requirements. Broader gate also enforced: GDPR for EU consumer PII in the underlying metrics + CCPA cross-context-behavioral-advertising opt-out when joining attribution data + PCI DSS when the metric chain touches payment data + HIPAA when healthcare-vertical PHI + per-vertical regulator rules via policy-as-code (OPA Rego + AWS Cedar + Casbin + Cerbos + Oso). WORM audit trail (AWS S3 Object Lock + GCS retention + Azure Blob immutable + Snowflake Time Travel) with per-statute retention (SEC Reg FD records 5yr + SOX 7yr + IRS 7yr + FINRA 6yr + FTC 7yr + state-AG variable + LPA-specified + GDPR 6yr + HIPAA 6yr) per operator counsel policy.

Question 6

What does the engagement look like across Tier 1 → Tier 2 → Tier 3, and what does the Tier 3 reporting cycle commit to?

Accepted Answer

Tier 1 AI Readiness Assessment (2-3 weeks, diagnostic): audits the operator current monthly close + reporting posture against the 4-skill bundle + 5-anchor governance compliance overlay + per-vendor BI + warehouse + financial-planning + LLM + board + investor-reporting state; deliverable is a gap-pack report identifying which audiences receive reports without per-audience scope filtering, which non-GAAP measures lack Reg G reconciliation, which FDD Item 19 FPR-class metrics are leaking into franchisee views, which LP distributions miss ILPA template alignment or LPA covenant compliance, which LLM-drafting paths lack MNPI quarantine or privilege preservation, whether the disclosure-committee gate is wired for Reg FD or Reg S-K Item 1.05 events, whether Rule 10b5-1 trading-plan coordination is wired with the disclosure committee, and a recommended remediation sequence for Tier 2. Tier 2 AI Swarm Setup Sprint (4-8 weeks): builds the 4-skill bundle on the rollup-reporting agent, wires the BI + warehouse + financial-planning + reverse-ETL + LLM + document-generation + board-management + investor-reporting + policy-as-code + WORM-storage vendors (operator-chosen subset), configures the operator-counsel-approved per-audience scope filter matrix + privilege register + MNPI register + non-GAAP reconciliation library + FDD Item 19 FPR-substantiation library + ILPA template integration + LPA covenant overlay + Rule 10b5-1 coordination workflow, wires the disclosure-committee gate, runs 30-day shadow + canary period before flipping to enforce-mode. Tier 3 Fractional CMO with AI Swarm (6-month minimum, 1-2 days/wk embedded): continues operating with monthly Roll-Up + Draft + Distribute + Attest cycle + quarterly per-audience scope filter review + quarterly ILPA template + LPA covenant review + quarterly FDD Item 19 substantiation review + quarterly disclosure-committee policy review + quarterly compliance evidence packages. Tier 3 reporting is a 6-workstream pre-engagement-baseline reporting cycle (per-audience scope filter compliance + per-distribution attestation completeness + LLM-drafting privilege/MNPI quarantine effectiveness + non-GAAP reconciliation coverage + FDD Item 19 substantiation coverage + WORM audit-trail completeness) measured against the operator’s pre-engagement baseline. Each workstream surfaces trend direction and the gap to operator-defined targets. Reporting carries explicit caveats: BI + warehouse + financial-planning + reverse-ETL + LLM + board + investor-reporting vendor SLA + SEC interpretive guidance + SEC Reg S-K Item 1.05 implementing guidance + SOX amendments + FTC Franchise Rule interpretive guidance + state franchise registration amendments + ILPA Reporting Standards updates + AICPA valuation guidance updates + FINRA rulemaking + state-AG enforcement signals + state insurance + -regulator amendments sit outside Completions control. Attorney-client privilege preservation across operator-counsel-approved per-audience scope filter matrix + privilege register + MNPI register + non-GAAP reconciliation library + FDD Item 19 substantiation library + LPA covenant overlay + Rule 10b5-1 coordination records + disclosure-committee approval records is maintained per operator counsel policy.

Question 7

Who owns the metric definitions, the scope-filter matrix, the privilege and MNPI registers, the disclosure-committee workflow, and the audit trail?

Accepted Answer

Operator owns every artifact. The BI subscriptions (Looker, Tableau, Power BI, Sigma, Hex, Mode, Preset, ThoughtSpot, Domo, Sisense, Qlik — operator chooses) run under operator billing on operator-controlled accounts. The data warehouse (Snowflake, Databricks, BigQuery, Redshift, ClickHouse — operator chooses) runs under operator cloud account. The financial-planning subscription (Anaplan, Adaptive Insights, Pigment, Mosaic, Cube, Vena, Planful, Workday Adaptive, Causal, Pry, Drivetrain, Finmark, Jirav — operator chooses) runs under operator billing. The reverse-ETL subscription (Hightouch, Census, Rudderstack, Polytomic — operator chooses) runs under operator billing. The LLM-drafting vendor (Anthropic Claude, OpenAI GPT, Microsoft Copilot, Google Gemini, Mistral — operator chooses, with operator-approved deployment posture and operator-controlled zero-retention configuration where supported) runs under operator account. The document-generation tooling (DocSend, Coda, Notion, Confluence, Google Workspace, Microsoft 365, Adobe Acrobat — operator chooses) runs under operator billing. The board-management vendor (Diligent, OnBoard, Boardable, BoardEffect, BoardPaq, Govenda — operator chooses) runs under operator billing. The investor-reporting vendor (Carta, Pulley, Allvue, eFront, iLevel, Dynamo, Juniper Square, Ontra, Aduro Advisors — operator chooses) runs under operator billing. The canonical metric definitions live in the operator data team + operator finance + operator counsel-aligned semantic layer. The operator-counsel-approved per-audience scope filter matrix + privilege register + MNPI register + non-GAAP reconciliation library + FDD Item 19 FPR-substantiation library + LPA covenant overlay + ILPA template configuration + Rule 10b5-1 coordination workflow + disclosure-committee policy live in operator counsel repo. The Roll-Up + Draft + Distribute + Attest skill code lives in operator code repo. The LLM prompt-construction layer with privilege and MNPI quarantine lives in operator code repo. The WORM audit trail lives on operator-controlled cloud storage (AWS S3 Object Lock + GCS retention + Azure Blob immutable + Snowflake Time Travel) with per-statute retention enforcement. The policy-as-code policies (OPA Rego + AWS Cedar + Casbin + Cerbos + Oso) live in operator code repo, counsel-aligned. The SEC Reg FD + Reg G + Reg S-K + SOX + MNPI + FDD Item 19 + ILPA + LPA + FINRA + FTC Pfizer substantiation + Rule 10b5-1 compliance evidence records are operator-counsel-and-CFO-maintained. Completions owns the orchestration knowledge — how to design the per-audience scope filter matrix against the operator’s actual stakeholder mix, how to wire the LLM privilege and MNPI quarantine, how to wire the disclosure-committee gate for Reg FD + Reg S-K Item 1.05 events, how to compose the ILPA + LPA + AICPA-aligned LP package, how to design the FDD Item 19 substantiation propagation, how to coordinate the Rule 10b5-1 trading-plan workflow with the disclosure committee — and that knowledge transfers under the Tier 3 transition path (30-60 days at engagement end with full hand-off of the per-audience scope filter matrix maintenance playbook, the privilege and MNPI register maintenance runbook, the LLM prompt-construction privilege quarantine runbook, the disclosure-committee coordination playbook, the ILPA + LPA reporting playbook, the FDD Item 19 substantiation playbook, the Rule 10b5-1 coordination playbook, and the compliance evidence-package generation playbook). Completions credentials revoke on engagement-end.

The real ecosystem this sits above

BI + warehouse

Financial planning + FP&A

LLM drafting + document generation

Board management + investor reporting

Policy-as-code + WORM + legal research

Frequently asked