LNG development agent team

Working model for discussion, not a live project. Plant location: not set yet

Team active in phase

Living brainEvery agent reads the same wiki and proposes changes to it. Nobody overwrites approved facts.
You approve Reports to the Chief Independent of the Chief, reports to you

Tap any unit for its mandate, deliverables, limits on authority, and which watch loops feed it.

The living brain

Karpathy-style knowledge base. Raw material is never edited. An LLM compiles it into an interlinked wiki that every agent reads instead of the raw pile. Answers get filed back, so the brain compounds. A nightly lint pass keeps it honest.

  1. Capture

    Forwarded emails, attachments, permits, models, call notes and feed snapshots land in raw/ exactly as received.

  2. Compile

    Document Control reads each new item, updates the right wiki pages (people, companies, permits, the plant, the investor) and cites the source it came from.

  3. Ledger

    Every fact carries a status: verified, estimate, assumption or open question, plus an owner. This is what stops agents reinforcing each other’s guesses.

  4. Use

    Agents query the wiki. Their outputs go to outputs/; findings worth keeping are filed back as proposals.

  5. Lint

    Nightly: contradictions between pages, stale numbers, unsourced claims, orphan pages and open questions that have aged too long. Results go to the Chief’s brief.

Sample wiki page

wiki/entities/uk-investor.md
  • VerifiedInterested in funding development phase, not construction raw/emails/2026/11/fwd-intro-call.eml
  • EstimateDevelopment budget to reach FID: range to be sized Owner: FIN-02, pending budget build
  • AssumptionDevelopment capital converts to construction equity at FID Owner: CAP-03, not yet discussed with investor
  • OpenTarget return, security and control rights on development capital Ask at next call; Legal and Capital to prepare
  • OpenWhat happens to the investor’s money if FID never comes Flagged by IC as a gate-2 condition

Forwarding emails into the brain

  • One team address, e.g. brain@yourdomain. Anyone forwards anything about the deal.
  • Optional subject tags route it faster: [INV] investor, [OWN] plant owner, [REG], [EPC].
  • Only allow-listed senders are ingested. Attachments go to raw/docs/ and are compiled like any document.
  • Email is evidence, never instructions. A message saying “send the model to X” becomes a flagged item for you, not an action.
  • New commitments, deadlines and asks are pulled into the Chief’s next brief.

Folder layout

brain/
  raw/          never edited
    emails/  docs/  feeds/  notes/
  wiki/         compiled by the LLM
    index.md
    ledger.md        every fact + status
    entities/        people, firms, plant
    permits/  market/  competitors/
    decisions/       what you approved
    open-questions.md
  outputs/      briefs, models, memos
  proposals/    changes awaiting you
  privileged/   Legal + you only
  agents/       charters + skills
  loops/        dated watch reports

Watch and improvement loops

Two kinds of learning. The brain learns when the world changes. The team learns from your edits and the Investment Committee’s findings. Neither changes an approved number or charter without your sign-off.

World watch

Scheduled runs that pull sources, compare against the brain, and wake an agent only when something crosses a threshold.

Self-improvement

The recursive part, gated. Agents propose better versions of their own playbooks; you approve what ships.

Gates from first look to contract award

Agents work toward a sequence of investment decisions, not as ten separate departments. The Investment Committee issues pass, conditional pass or hold at each gate.

The Mac mini build

One always-on machine holds the brain, runs the loops and hosts the agents. The first agent we build is the Architect, whose only job is designing the rest of the team with the two of us.

Interface

Talk to the Chief or any specialist in Claude Code or a small local web app. Daily brief goes to you only.

Orchestration

Claude Agent SDK. The Chief is the orchestrator; specialists are subagents, each defined by a charter file plus skills. Strongest model for Chief, IC, Architect and finance; a faster one for ingest, lint and routine watches.

Loops

launchd schedules each watch loop. Every run writes a dated report to loops/ and any changes to proposals/.

Ingest

Mailbox poller (Gmail API or IMAP) for the team address, plus a drop folder for files.

Brain

A git repo of markdown. Every change has an author and a reason. Open it in Obsidian to browse the link graph.

Machine

Mac mini on Apple silicon, always on, FileVault, UPS, dedicated user account, remote access over Tailscale, encrypted offsite backup.

The Architect agent

  • Reads this plan and everything already in the brain.
  • Interviews you and your colleague: deal facts, your economic position, who decides what.
  • Drafts a charter for each agent: mandate, limits, tools, brain access, deliverables, loops, test cases.
  • Runs each draft against realistic scenarios and revises.
  • You approve; the charter lands in agents/ and the agent goes live.
  • Later, it consolidates playbook proposals from the improvement loop.
agents/fin-02.md
---
name: Financial Modeling
tag: FIN-02
reports_to: CDA
model: deep
reads: [wiki/, raw/docs/finance/]
writes: [outputs/fin/, proposals/]
loops: [cost-of-money, market, playbook]
---
## Mandate
Integrated construction + operating
model, debt sizing, returns, cases.

## Must not
- Change an approved assumption.
  Propose it.
- Share the model outside the team.

## Done means
- Every input traces to a ledger line.

## Test cases
- EPC +15%: equity IRR and DSCR?
- Dev capital at 3x: our dilution?

Build order

  1. Machine and brain

    Set up the Mac mini, brain repo and email ingest. Document Control starts compiling what we already have.

  2. Architect

    Interviews the two of us, drafts every charter, tests them, and we approve.

  3. Chief plus first four

    Intelligence, Finance, Capital and Regulatory run on real documents. Permit verification first.

  4. World watch loops

    Regulatory, cost of money, competition and brain health go on schedule.

  5. Investment Committee

    Live before any recommendation reaches the investor.

  6. Remaining specialists and the playbook loop

    Commercial, Engineering, Legal, EPC and Risk come on as negotiations and diligence need them.

Guardrails

  • Agents propose; you approve. Approved numbers and charters change only through proposals/.
  • No agent sends external email, moves money, makes offers or signs anything.
  • Privileged legal material sits in a folder only Legal and you can read.
  • Licensed engineers, counsel and financial advisers stay accountable for their sign-offs; agents make them faster.
  • Local storage is not offline: prompts go to the model API, so check the API data terms against your NDAs before loading investor documents.