FROWhitepapers / ExecutiveDecision
ExecutiveDecision — Whitepaper (Architecture Stub)
Powered by FNAI · Fractal Research Organization
Status: Soon to come on fro-site · Architecture LOCKED Oct 25 2026 (America/Denver) · App build NOT done · Soft-announce HOLD / not claimed · Pricing TBD
Owned by: FNAICourtStack (with JusticeUnhinged, FNAICourt, LegislativeCreation) — CourtStack owns build after whitepapers
Slogan: Always be about the research.
Contact: contact@fractalresearchorganization.org
Abstract
ExecutiveDecision is Fractal Research Organization’s executive-branch product in the FNAI government family: an FNAI executive-branch app designed so presidents, senior advisors, OMB/OSTP/NSC surfaces, and agency heads can get ledger-anchored decision support without collapsing separation of powers into a single opaque chatbot.
The public story is simple. Executive work is drowning in statutes, executive orders, OMB circulars, agency metrics, AI inventories, and national indicators — while constitutional hard limits, civil liberties, and due process must stay enforceable, not decorative. ExecutiveDecision is designed as the executive node of one constitutional mesh with FNAICourt (judicial), LegislativeCreation / FNAI Legislature (legislative), and JusticeUnhinged (law enforcement): four separate installs, shared FRO SSO when wired, talking only through typed backend APIs.
On fro-site today the product is labeled Soon to come. That is deliberate honesty. Architecture is LOCKED (Oct 25 2026 America/Denver). Phase I agents are named: PCA, RMA, PSA, WAA. Inter-branch contracts exist as typed stubs only. The app build is NOT done. FNAICourtStack owns the build after whitepapers. Soft-announce is HOLD / not claimed. This paper is the public map — substrate, Phase I agents, out-of-scope honesty, ECC vision, constitutional constraints, and mesh posture — so reviewers can judge the research without inventing Soft-announce, without conflating FractalMed Soft-announce / payment / PHI, and without treating this stub as a shipped Executive Command Console.
1. Problem
Modern executive offices do not lack documents. They lack a research-honest executive substrate that turns policy, risk, compliance, and workforce briefing into decision support — without usurping Congress, the courts, or agency accountability, and without pretending a dashboard is the Constitution.
Chronic bottlenecks the Court family already knows from the judicial, legislative, and LE nodes:
- Corpus overload. Statutes, regulations, executive orders, OMB circulars, OSTP guidance, GAO reports — the challenge is mapping obligations to agencies, not finding a homepage.
- Risk blindness. AI inventories, bias/drift/misuse, shadow-AI, program risk — leadership needs continuous scores that are reproducible and ledger-traceable, not slide-deck theater.
- Policy option poverty. Drafting EOs and strategies without explicit trade-offs, constitutional tags, and statutory implications invites either paralysis or reckless certainty.
- Workforce translation gap. Technical AI and program issues must become memos and briefings with citations — not vibes.
- Cross-branch blindness. Executive proposals that ignore judicial constitutionality risk, legislative statutory authority, or LE civil-liberties constraints are incomplete on purpose if the mesh is missing.
- Audit amnesia. Recommendations that are not ledger-anchored cannot be defended later as research-honest decision support.
- Console theater. A pretty “national dashboard” without hard constitutional rules is marketing, not governance research.
- Monolith temptation. Merging Court, Leg, LE, and Executive into one binary erases separation of powers as a product rule.
FRO’s answer is not “replace the President with a model.” It is amplify executive research work — compliance checklists, risk scores, policy options, workforce drafts — while encoding separation of powers, civil liberties, and due process as substrate constraints. Soft-announce elsewhere does not unlock ExecutiveDecision.
The problem ExecutiveDecision attacks is: how do you give the executive branch an FNAI app that is honest about Phase I vs later phases, stubs vs live mesh, architecture-locked vs app-not-built — without shipping a national chatbot that pretends to be government?
2. What ExecutiveDecision is (and is not)
Is
- FRO’s executive FNAI product — catalog slug
executive-decision, product name ExecutiveDecision. - An executive-branch app in the same constitutional mesh as Court, Legislature, and JusticeUnhinged.
- A stack with four intended layers: Executive Substrate (DDFNL-ledger + FractalOS instance scoped to Executive), Agent Mesh (specialized FNAI agents), Interface (consoles for senior leadership and agency surfaces), Inter-Branch Integration (typed channels to Judicial / Legislative / LE FNAI).
- Phase I foundation (when build opens): Executive DDFNL + core schemas / ACL / constitutional constraint layer + agents PCA, RMA, PSA, WAA.
- Owned and built under FNAICourtStack, alongside JusticeUnhinged, FNAICourt, and LegislativeCreation. BossGrok / FRO surface coordinates fro-site honesty and Soft-announce HOLD.
- Architecture LOCKED Oct 25 2026 America/Denver. Mesh YES (James). Inter-branch typed API stubs exist for design. Build HOLD for live network / app code / production deploy of the ED app itself.
Is not
- Not a replacement for elected executives, agency heads, counsel, or oversight bodies. Human judgment stays in the loop.
- Not “AI runs the executive branch.” Assist ≠ autonomous executive power.
- Not the Executive Command Console (ECC) as a finished product. ECC full UI is out of scope for Phase I.
- Not Soft-announce live. fro-site marks the product Soon to come. Soft-announce is HOLD / not claimed.
- Not an app build that is done. Architecture locked ≠ app shipped. CourtStack owns build after WPs.
- Not live inter-branch APIs in Phase I. Stubs and schemas only; no live calls in Phase I scope.
- Not FNAICourt, JusticeUnhinged, or FNAI Legislature. Those are peer branches with their own whitepapers.
- Not ParadigmZero Free Web, FractalMed, or FNAI Sentinel Soft-announce. Do not treat Soft-announce elsewhere as Soft-announce for ExecutiveDecision. Especially: no FractalMed Soft-announce / payment / PHI conflation.
- Not a dump of proprietary implementer internals into this public paper. Public map only.
3. Architecture locked (Oct 25 2026)
Architecture status: LOCKED by James, Oct 25 2026 America/Denver. What follows is the public-safe summary of the locked design — not a claim that the app is built.
3.1 High-level stack
| Layer | Role |
|---|---|
| Executive Substrate | DDFNL-ledger + FractalOS instance dedicated to Executive operations, with strict constitutional scoping |
| Agent Mesh (FNAI) | Specialized multi-agent system for governance, policy, risk, operations, workforce |
| Interface | Consoles for President & senior advisors; OMB/OSTP/NSC; Agency heads & CIOs |
| Inter-Branch Integration | Secure, protocolized channels to Judicial FNAI, Legislative FNAI, Law Enforcement FNAI |
3.2 Substrate data domains
| Domain | Examples |
|---|---|
| Policy & Legal Corpus | statutes, regulations, executive orders, OMB circulars, OSTP guidance, GAO reports |
| Operational Data | agency performance metrics, budgets, program outcomes, procurement data |
| Risk & Compliance | AI inventories, risk assessments, audits, incident reports |
| National Indicators | economic, environmental, health, security, infrastructure, social metrics |
3.3 Ledger roles
- Immutable audit: every FNAI recommendation, simulation, and decision-support output is ledger-anchored.
- Interagency schemas + ACL: shared cross-agency schemas with per-agency access control.
- Constitutional boundary encoding: separation of powers, civil liberties, due process as enforceable substrate rules (hard rules block; soft rules require logged override justification).
This is research product architecture. It is not a live national data feed claim and not Soft-announce.
4. Phase I agents (PCA / RMA / PSA / WAA)
Phase I — Foundation — is the implementer scope when CourtStack opens the build. Initial agents and honest success criteria:
| Agent | Class | Role | Phase I success (design bar) |
|---|---|---|---|
| PCA — Policy-Compliance | Governance | Map governance requirements to agency obligations; checklists, gap flags, remediation | Per-agency compliance checklist from the legal corpus; every gap flag ledger-anchored |
| RMA — Risk-Monitoring | Risk | Continuous risk scoring; bias/drift/misuse + shadow-AI detection; leadership dashboards | Reproducible risk score per registered AI system, traceable to inputs |
| PSA — Policy-Synthesis | Policy | Draft policies/strategies/EOs; options with trade-offs; constitutional & statutory tags | ≥2 policy options with trade-offs; each tagged; hard-rule violations blocked |
| WAA — Workforce-Augmentation | Workforce | Draft memos/briefings; just-in-time training; translate AI issues to policy language | Memos/briefings from substrate data with citations to versioned ledger entries |
Phase I also includes: Executive DDFNL instance, core schemas for the four data domains, per-agency ACL, and the constitutional constraint layer.
Deliverable posture for Phase I (when unlocked): design doc + API sketch for Phase I agents — not a production deploy without James YES.
5. Out of scope for Phase I (honest HOLD)
The following are real roadmap items and are explicitly out of Phase I:
| Out of scope (Phase I) | Notes |
|---|---|
| ECC full UI | Executive Command Console views/modes are designed; full UI is Phase II+ |
| SSA — Strategy-Scenario | Fractal Monte Carlo / counterfactuals — Phase II |
| PPA — Program-Performance | KPI monitoring / reallocation suggestions — Phase II |
| PBA — Procurement & Budget | Spend alignment — Phase II |
| OCA — Oversight Coordination | OMB/OSTP/GAO/GSA/CIO sync — Phase II |
| IRA — Incident Response | Triage + DDFNL logging of incidents — Phase II |
| Live inter-branch APIs | Typed stubs only in Phase I; no live HTTP clients, no network mocks that hit peers |
Later agent classes (KGA Knowledge-Graph and others) remain design vocabulary in the locked architecture; they are not Phase I ship claims.
6. Executive Command Console (ECC) — vision, not Phase I ship
ECC is the intended leadership interface. Vision (architecture):
Views
- National State Dashboard — cross-domain indicators, anomaly & trend detection.
- Policy Decision Workspace — proposals with simulations (when SSA exists), Judicial FNAI legal analysis, budget implications (when PBA exists); side-by-side comparison.
- Risk & Compliance Panel — live risk scores; incident/remediation drill-down (when IRA exists).
Modes
- Query — natural-language questions.
- Scenario — multi-variant simulations under constraints.
- Alert — push alerts for constitutional risk, oversight deadlines, emerging crises.
Honesty: describing ECC is not claiming ECC is built. Phase I does not include ECC full UI. Soft-announce does not cover a public ECC demo.
7. Constitutional constraints
Constraint classes encoded in the substrate design:
| Class | Meaning |
|---|---|
| Separation of powers | No usurping legislative or judicial functions |
| Civil liberties | Hard limits on surveillance, enforcement, discrimination |
| Due process & rule of law | No bypassing required procedures |
Hard rules: non-overridable; block outputs.
Soft rules: require explicit override justification + ledger logging.
These rules are product research ethics with teeth — not a marketing FAQ. They are why PSA must tag constitutional/statutory implications and why inter-branch hardBlock (when live) must keep non-actionable options off the actionable surface.
8. Inter-branch mesh — stubs only
Four separate apps, one constitutional mesh (FRO SSO when wired; talk only via typed APIs):
| App | Branch role |
|---|---|
| JusticeUnhinged | Law Enforcement FNAI — civil liberties, ops constraints, oversight |
| FNAICourt | Judicial FNAI — constitutionality, precedent, legal-challenge risk |
| LegislativeCreation (FNAI Legislature) | Legislative FNAI — statutory authority, pending alignment, appropriations |
| ExecutiveDecision | Executive FNAI — policy synthesis + ECC; designed to call all three before surfacing proposals |
Phase posture: typed stub contracts and schemas exist for design. NO LIVE NETWORK for ED↔peer mesh in Phase I. Phase I may import types only — no HTTP clients. Live wiring is a later phase (full mesh). Branches may eventually read executive policy-status only; ExecutiveDecision is designed so PSA gates through peers before ECC surfaces actionable options — when that wiring is unlocked.
Do not confuse stub contracts with Soft-announce or with a live mesh.
9. Data lifecycle (design)
- Ingest — agency feeds, trusted statistical indicators, legal/policy updates; normalization, quality checks, provenance tagging, ledger anchoring of critical inputs.
- Process — Phase I: PCA / RMA / PSA / WAA work against substrate; later phases add SSA simulations, PPA performance, etc.
- Output — dashboards, briefings/memos, draft policies, alerts/incident reports; all versioned, ledger-anchored, traceable to inputs and constraints.
No claim is made that national live feeds are connected today. This is the research lifecycle the architecture locks.
10. Roadmap (locked phasing)
| Phase | Name | Scope (summary) |
|---|---|---|
| I | Foundation | Executive DDFNL + schemas / ACL / constitutional layer; agents PCA, RMA, PSA, WAA; inter-branch stubs only |
| II | Command | ECC for senior leadership + OMB/OSTP; agents SSA, PPA, PBA, OCA, IRA |
| III | Full mesh | Judicial + Legislative + LE FNAI live integration; constraint engine auto-tags recommendations with legal basis, constitutional risk, oversight implications |
App build: NOT done. Ownership of implementation: FNAICourtStack (with JU / Court / Leg). Soft-announce remains HOLD until Security PASS (and James unlock) — not claimed on this paper.
11. Research ethics spine
Always be about the research is not a sticker. For ExecutiveDecision it means measurable product rules:
| Rule | Public meaning |
|---|---|
| Amplify, don’t replace | Executives, counsel, and oversight remain decision-makers |
| No autonomous executive power | Assist ≠ exercising Article II by model |
| Hard rules block | Constitutional / civil-liberties hard hits are non-overridable |
| Soft rules log | Overrides require justification + ledger |
| Separate installs | ED, Court, Leg, JU remain distinct apps; mesh is typed APIs |
| Stubs ≠ live | Inter-branch stubs are not live APIs |
| Architecture ≠ ship | Locked design is not Soft-announce and not “app done” |
| Status honesty | Soon means Soon; Soft-announce is product-scoped and HOLD / not claimed |
| No Soft-announce bleed | PZ Free Web, FractalMed, and Sentinel Soft-announce statuses do not apply to ExecutiveDecision |
| No FractalMed PHI conflation | ED is not medical Soft-announce, payment, or PHI |
12. Status honesty on fro-site
| Claim | Reality today |
|---|---|
| Product tag on fro-site | Soon to come |
| Soft-announce | HOLD / not claimed |
| Architecture | LOCKED Oct 25 2026 America/Denver |
| App build | NOT done — CourtStack owns build after WPs |
| Phase I agents named | PCA, RMA, PSA, WAA |
| ECC full UI | Out of scope Phase I |
| SSA / PPA / PBA / OCA / IRA | Out of scope Phase I |
| Live inter-branch APIs | No — stubs only |
| Public download | Off |
| Pricing | TBD |
| Conflation with PZ Free Web Soft-announce | Forbidden |
| Conflation with FractalMed Soft-announce / payment / PHI | Forbidden |
| Conflation with Sentinel Soft-announce | Forbidden |
When Soft-announce for ExecutiveDecision becomes true, FRO will say so on the product page and in this paper’s status line — not by borrowing another product’s banner.
13. Ownership — FNAICourtStack
ExecutiveDecision is owned for build by FNAICourtStack, the same ownership lane as:
- JusticeUnhinged
- FNAICourt
- LegislativeCreation (FNAI Legislature / Legislature Creator)
BossGrok / FRO surface coordinates Soft-announce and fro-site catalog honesty. Soft-announce remains HOLD / not claimed for this product until Security and James unlock say otherwise. CourtStack owns the app build after whitepapers — this stub paper does not start that build.
14. How to read the catalog today
- Product page:
/products/executive-decision— Soon to come - This whitepaper:
/whitepapers/executive-decision - Sibling papers (separate): JusticeUnhinged, FNAICourt, FNAI Legislature
- Do not look for an ExecutiveDecision Free Web twin of ParadigmZero — different product shape
- Do not look for FractalMed payment / PHI stories here
- Contact for research / partnership questions: contact@fractalresearchorganization.org
15. Close
ExecutiveDecision is the executive branch of FRO’s research government family: substrate + agent mesh + eventual ECC + typed inter-branch links, with an ethics spine that keeps humans in the loop and Soft-announce product-scoped.
Architecture is LOCKED (Oct 25 2026 America/Denver). Phase I agents are PCA, RMA, PSA, WAA. ECC full UI, SSA/PPA/PBA/OCA/IRA, and live inter-branch APIs are out of Phase I. Inter-branch work is stubs only. The app build is NOT done; FNAICourtStack owns build after whitepapers. On the public catalog it is Soon to come. Soft-announce is HOLD / not claimed. Pricing is TBD. It is not ParadigmZero Free Web, not FractalMed Soft-announce/payment/PHI, not FNAI Sentinel — and their Soft-announce states do not transfer. It is not Court, not Legislature Creator, not JusticeUnhinged — those are peers.
Always be about the research.