โ† Back to system overview
Deep-dive

Cloze Account OS

A standalone console for running a brokerage partner account: onboarding, adoption, quarterly reviews, escalations, expansion, all driven off the account itself. It runs today, ready to point at a real set of accounts.

0
Weighted health signals
0
Health grades
0
Sections per cockpit
0
Account files read live
How it's wired
Account files โ†’ engine โ†’ console

Each account is a folder of plain files, not a database row. A reader turns it into structured data, a scoring engine grades it, and a FastAPI console renders it. There is no separate system of record.

๐Ÿ“ The accountplain files, one folder
Mutual success plan Stakeholders + relationship strength Meetings & decisions, dated Open tasks Health file
โ†“
โš™๏ธ Reader + enginestdlib, no dependencies
Account reader (folder โ†’ structured data) Health engine (5 weighted signals) Context-pack assembler
โ†“
๐Ÿ–ฅ ConsoleFastAPI ยท localhost:7788
Portfolio rail, worst-first Per-account cockpit Start โ†’ claude:// deep link
The surface
One cockpit per account

Select an account and its full state stacks into one view, the way real customer-success platforms drill from a portfolio down into a single account.

๐ŸŸก Health

The score, its named grade, the one-line reason, and the top corrective play.

health

๐ŸŽฏ Success Plan

The mutual goals, each with on-track, at-risk, or blocked status.

success plan

โœ… Open Tasks

The account's task list, each row with a one-click Start button.

tasks

๐Ÿ‘ฅ Stakeholders

The map of who matters, with relationship strength per person.

people

๐Ÿ—’ Recent Activity

The latest meetings and decisions, newest first.

activity

๐Ÿ“‡ Portfolio rail

Every account, health dot and score, sorted worst-first for triage.

portfolio
The depth
The mechanisms that earn it

The point isn't the layout. It's the machinery behind the buttons.

Transparent, tunable health

Five weighted signals roll up to a number and a named grade, always carried with the reason and the top fix. The weights live in one place and are meant to be argued with.

Context-aware verdict

The same 60 means different things for a ramping account and an established one near renewal. An overlay reads each score by lifecycle, trajectory, and renewal proximity and grades it On Track, Watch, or Escalate, showing every step of the why. The raw number stays; the judgment sits on top, the way mature customer-success platforms score health.

The Start button

One click assembles the account's context pack (the file paths plus the sponsor, champion, open escalation, and current top play) and opens an AI session already loaded with it via a claude:// deep link.

Drift check

The engine recomputes every score from its parts and flags any stored number that no longer reconciles, so a health file can never quietly go stale.

One assembler, two uses

The same context-pack code powers the Start button and the /account-brief skill. Built once.

Master-detail

A portfolio roll-up plus a per-account cockpit, the shape every mature customer-success platform converges on.

Synthetic by design

The worked account is invented. The system reads any account folder you drop in, sorted worst-health-first.

What's next
Where it goes

Two natural steps, and the file-based design maps onto both in a straight line.