No target
Weekly active teams · teams
Dana WhitmoreChief Executive
One folder, rendered.
The map has eight folders of templates, which raises a fair question: and then what? This is the answer for one of them. accountability/ holds four files — who exists, what the numbers mean, what was agreed, and how a number becomes a colour. Here is what those four files look like when something reads them.
The company below is called Kestrel and does not exist. Fourteen invented people, invented targets, invented measurements, all of it published in the repository so you can read the files this page was built from.
- 3 green
- 1 yellow
- 3 red
- 1 no target
- 6 needs setup
- 1 stale
No metric agreed
Not in goals.md
Omar HaddadChief Technology Officer
Reports to Dana Whitmore
$498K / $674K
Net new ARR · AUD
Priya RamanHead of Revenue
Well behind plan
121 / 209
Qualified accounts · count
Luca FontanaHead of Marketing
Well behind plan
21 mo / 18 mo
Runway · months
Grete SorensenHead of Finance
On plan
100% / 100%
Report on time · %
Noor AbadiChief of Staff
On plan
Reports to Omar Haddad
61% / 70%
Activated in 14 days · %
Sam OkaforHead of Product
Slightly behindProposed
11.5 d / 9.0 d
P75 bug lead time · days
Marta KovacsEngineering Lead
Well behind planStale
2.1 h / 2.0 h
First response time · hours
Rui AlvesSupport Lead
On plan
Reports to Sam Okafor
No metric agreed
Not in goals.md
Ines DelacroixProduct Designer
Reports to Marta Kovacs
No metric agreed
Not in goals.md
Tobias LundSoftware Engineer
No metric agreed
Not in goals.md
Amara DialloSoftware Engineer
No metric agreed
Not in goals.md
Kwame OseiSoftware Engineer
No metric agreed
Not in goals.md
Yuki TanakaData Engineer
A chart where everyone is green because the gaps are hidden tells you nothing.
Nothing above was typed.
Every colour on this page was computed when the page was built, from four files and one rule. Change a target in the repository and the colour changes here.
os/accountability/org-chart.md who exists, and who reports to whom
os/accountability/metrics.md what each number means, and which way is good
os/accountability/goals.md the target, its shape, and who agreed it
data/observations/2026-09-12.json what was measured, and on what date
│
▼
os/accountability/status-rules.md ──► one colour per person, never averaged, never inheritedOne card, worked through
Three things the rule refuses to do
Where a dashboard fits.
A dashboard is not a ninth folder. It is a reader. os/ holds what a person decided, data/ holds what was measured, and anything that renders them — this page, a weekly report, an agent running a skill — is a view over the same files. Which is why a gap on the chart is never a bug in the chart. It is a gap in a file, and the fix is in the file.
It also means there is nothing to migrate off. No database holds the company, so the reader can be replaced, rewritten or thrown away without losing anything that matters.
The version of this I run for a real company is a fuller thing — pan-and-zoom org chart, person detail, trends, OKRs, generated weekly and board reports — and it is not public, because it has a real company in it. What is public is the model, the example, and the rule, which is the part worth copying.
