AI-powered virtual executive team — a single coherent executive persona backed by 8 specialist agents (FastAPI + Next.js).
Open Executive — Company Fixtures
Pre-built company data suites for demos, evals, and development. Each fixture contains a full company context — profile, documents, and episodic memory seed data.
Available Fixtures
| Fixture | Company | Industry | Stage | Revenue |
|---|---|---|---|---|
tandem_robotics |
Tandem Robotics | Humanoid Robotics / Warehouse Automation | Series C | $90M |
halcyon_motors |
Halcyon Motors | Electric Vehicles / Automotive | Series C | $140M |
meridian_petroleum |
Meridian Petroleum | Oil & Gas — Refining / Crude Trading | Private / PE-backed | $3.2B |
solo_studio |
Tallgrass Studio | Independent Brand & Product Design Studio | Bootstrapped, owner-run | $310K |
tandem_robotics, halcyon_motors, and meridian_petroleum are clean-baseline
research demo fixtures (see the callouts below). All three are fictional companies that
share one synthetic roster — placeholder emails (example.com) and non-routable
Discord IDs — so nothing in these fixtures maps to a real person.
halcyon_motorsis the reference fixture for demoing the research feature from a clean baseline. It's a fictional affordable-EV startup whose competitive landscape names real, frequently-changing players (Tesla, Rivian, Lucid, BYD, Ford, GM, Hyundai/Kia) plus real policy and supply-chain entities (IRA §30D tax credit, EV tariffs, CATL / Panasonic / LG Energy Solution, NHTSA). On load it seeds the company's memory (decisions, initiatives, prior advice) but no pre-baked alerts or in-flight actions — the Today page reads "all clear." A+30swatchlist_research_scanthen auto-fires the executive research workflow: the 7 specialists web-search current news, the Executive proposes what we should be watching and adds the highest-signal sources to the watchlist, and only routes something to a department head if it's genuinely urgent. From there the page builds up organically rather than starting pre-populated. The roster is synthetic (placeholder emails + non-routable Discord IDs); to actually deliver routed DMs in a live demo, replace them with real contact IDs and supply live Slack/Discord tokens. You can also trigger the scan manually by asking the Executive "what should we be looking into this week?"
meridian_petroleumis a second clean-baseline research demo fixture — a Gulf Coast independent oil refiner, crude trader, and fuels marketer whose P&L is driven by geopolitics. Its docs and watchlist scan name real, fast-moving entities (the Israel–Iran conflict, Strait of Hormuz shipping, OPEC+ / Saudi Aramco, Brent/WTI, OFAC Iranian-crude sanctions, VLCC war-risk insurance, EIA/IEA reports, and refiner peers Valero / Marathon / Phillips 66 / PBF). Likehalcyon_motorsit loads with memory but a clean Today page, then the same+30swatchlist_research_scanresearches the geopolitical and political landscape and proposes what to watch — building the watchlist organically instead of pre-seeding every lane. The roster is synthetic (placeholder emails + non-routable Discord IDs), shared with the other demo fixtures.
solo_studiois a reference fixture for solo mode — one person using Open Executive just for themselves. Solo principals can be at any level (a business owner, an executive inside a larger organisation, an independent); this fixture is one example: Tallgrass Studio, a fictional one-person design studio.people.yamlholds only the principal (its owner, wildcard authority),departments.yamlholds four areas (strategy, finance, marketing, product) headed by the principal with one or two goals each, andworkspace.yamlsetsmode: soloand the principal's role (role_kind: owner, plusrole_title,remitandmeasured_on— every role key is optional in any fixture'sworkspace.yaml, as isreports_to). Loaded, the Executive works for that one person: no department check-ins or channels, goals grouped by area, and nobody else contacted unless the principal asks. Its eval scenarios are the built-insolo_001–solo_003(packages/core/openexecutive/evals/_scenarios/), which run as solo mode through theirworkspace_mode: solokey; load this fixture first for the matching goals and memory.solo_004andsolo_005cover in-house executives and need no fixture (solo_005plays its principal's role through the scenario's ownprincipal_roleblock). It stages no scheduled actions, so nothing fires on load.
Loading a Fixture
Via the UI
Open /demo in the Open Executive UI. Click "Load" on any company card.
Via the API
# List available fixtures
curl http://localhost:8000/fixtures
# Load a specific fixture (replaces active company data)
curl -X POST http://localhost:8000/fixtures/halcyon_motors/load
What Gets Replaced
Loading a fixture replaces:
packages/core/company/profile.yaml— company profilepackages/core/company/docs/— company documents (re-indexed into ChromaDB)- Episodic memory rows — decisions, initiatives, advice_given (cleared and seeded)
- People — leadership and key employees with channels, authority scopes, availability windows
- Departments — company-specific org shape, charters, OKRs, authority levels (including informational departments with no specialist agent — useful for nonprofits with "Volunteer Coordination" or "Family Services")
- Workspace settings — reset to the defaults (team mode, no time zone of its own), then taken from the fixture's optional
workspace.yaml
Running Fixture-Specific Evals
Each team fixture ships with 2 eval scenarios in fixtures/companies/<name>/scenarios/
(solo_studio uses the built-in solo_* scenarios instead — see above).
A scenario can set workspace_mode: solo (or team) to run as that mode without
changing the install's own setting.
cd evals
python run_evals.py \
--scenarios ../fixtures/companies/halcyon_motors/scenarios/ \
--output results/halcyon_motors/
Fixture Structure
fixtures/companies/<name>/
profile.yaml # CompanyProfile schema (see openexecutive/memory/company_profile.py)
docs/ # Company documents indexed into ChromaDB
*.md
memory.json # Episodic seed data (decisions, initiatives, advice_given)
people.yaml # Leadership + key employees as Person records
departments.yaml # Company-specific departments + OKRs + authority levels
workspace.yaml # Optional: solo/team mode + the user's time zone
scenarios/
<name>_001.yaml # Eval scenario 1
<name>_002.yaml # Eval scenario 2
Authoring departments.yaml
A department can be specialist-aligned (mapped to one of the 9 specialist agents) or informational-only:
departments:
- slug: marketing
title: Growth & Brand Marketing
specialist_key: cmo # → routes to the CMO specialist
head_person_name: Maya Torres
authority_level: propose_only # auto_execute | propose_only | escalate
charter:
mission: ...
scope: [...]
out_of_scope: [...]
headcount: 12
budget_usd: 4200000
okrs:
- quarter: Q2 2026
key_result: Reduce CAC from $28 to $22
target: <$22 CAC
current: $28
status: at_risk # on_track | at_risk | off_track
- slug: volunteer_coordination
title: Volunteer Coordination
specialist_key: null # informational only — no specialist agent
...
Authoring workspace.yaml (optional)
Both keys are optional; a fixture without the file loads in team mode with no
time zone of its own (the server's USER_TIMEZONE, else UTC, applies).
mode: solo # solo | team — solo: one person using Open Executive
# just for themselves, so department check-ins don't run
timezone: America/Chicago # IANA zone for the brief times, "tomorrow at 9", quiet hours
A value that doesn't validate (including a region like America rather than a
zone like America/Chicago) is logged and ignored; it never stops the load.
Loading a fixture while your own company is live writes your current settings
to workspace.yaml in the backup — even when an earlier backup is reused — so
unloading the fixture restores them. Unloading from an older backup that has no
workspace.yaml leaves the current settings as they are.
Adding a New Fixture
- Create
fixtures/companies/<your_company>/ - Add
profile.yamlfollowing theCompanyProfileschema - Add
docs/*.mdfiles with company context - Add
memory.jsonwith seed data (can be empty:{"decisions":[],"initiatives":[],"advice_given":[],"scheduled_actions":[]}) - Optionally add
scenarios/*.yamlfor evals
The fixture will appear automatically in GET /fixtures and the UI Demo page.