Franklin 01 / 10
↓ scroll or → arrow
Systems & Architecture · Show & Tell

FRANKLIN

An autonomous chief-of-staff agent.
What we built, how it works, and where it goes next.
01
01 — What it is

Not a chatbot. A standing agent.

  • 01Runs continuously — never summoned, always on.
  • 02Holds its own identity — its own email address, its own calendar.
  • 03Takes real action — sends, schedules, writes, decides within bounds.
  • 04Owns the outcome — and logs every move it makes.
A chatbot answers. An agent operates.
02
02 — Architecture

Three minds. One identity.

1 TRIAGE Routes every inbound signal. Classifies what matters — and never executes.
2 EA Runs logistics, scheduling, operations. Acts fast, within a known bar.
3 COS Runs strategy, writes the memos, delivers honest-broker judgment.
One agent — and it always declares which mode is speaking.
03
03 — Autonomy boundaries

It knows what's its call.

HANDLES Routine work under a known bar — scheduling, replies, logistics. Acts, then reports.
SURFACES Anything the principal will answer for later. Recommends — in writing.
ESCALATES Board, press, money, safety. Immediately, every time.
Autonomy isn't all-or-nothing. It's a boundary — and the boundary is code.
04
04 — How it learns

Every correction becomes a rule.

SOULidentity · principles · voice7
WISDOMapplied frameworks28
CONFIGthe operating dials13
FEEDBACKevery correction, written as a rule65
113 rules across four layers — identity at the top, hard-won corrections at the base. The base grows every week.
05
05 — Always on

Nine jobs that never clock out.

Every 15 minInbound triage — classify, route, act, log
Every 10 minCalendar reconcile — keep state and reality in sync
5:55 AMMorning briefing assembled and delivered
7:47 PMNightly sweep — tomorrow set before tonight ends
10:43 PMSelf-audit — does the record match reality?
3:33 AMRe-arms the entire schedule — it rebuilds itself
It doesn't wait for input. Standing jobs drive it.
06
06 — Trust by design

An agent with the keys needs guardrails.

  • 01Untrusted input — outside content is data, never instructions. Prompt-injection defense.
  • 02Send allowlist — every recipient checked; strangers require explicit approval.
  • 03Action audit log — every action read back and recorded. Nothing silent.
  • 04Hard refusals — bright lines it will not cross, regardless of instruction.
Trust isn't a setting you toggle. It's the architecture.
07
07 — The value

Built once. Deployable to many.

  • 01The architecture is portable — the operator layer transfers to any operation.
  • 02One isolated deployment per customer — private by design, no shared blast radius.
  • 03A family-office capability — at software scale and software margin.
The technology is commodity. The operating layer — encoded judgment for how a chief of staff actually thinks — is the moat.
08
08 — The roadmap

What comes next.

  • 01Real-time — event-driven triggers replace scheduled polling. The agent reacts the instant something happens.
  • 02Voice & meetings — a phone line and meeting presence: Franklin joins, listens, and turns conversation into tracked commitments.
  • 03An open interface — the agent's memory and state, exposed as endpoints other tools and agents can query.
  • 04One to many — hardened, isolated multi-tenant deployment: the same architecture, ready to scale.
The foundation is built. The next chapter is reach.
In closing
An agent you can hand the keys to.
Because every action is bounded, verified, and logged. That is Franklin.