Name the problem
Describe the repeated work, friction, or loss without smuggling in a product answer.
Editorial deskPublic briefsState stays visible
The Briefing Desk
Make the problem legible
before you build.
Short papers for people deciding whether a hard problem deserves a new tool, a new rule, a new partnership, or a better question.
Editorial ruleEvidence before urgency. Boundaries before features.Briefings are useful when they improve the next decision, not when they make the biggest promise.
Briefing 001 · Current inquiry
The Coordination Tax
Working hypothesisWhen systems forget, people become the database.
This is a model to challenge, not a completed finding.
Across fragmented services and organizations, people repeatedly reconstruct context that the system cannot carry. The repeated explanation, reconciliation, and follow-up are a coordination tax.
Software is relevant where it can preserve context, clarify responsibility, or reduce repeated work. It is insufficient where the real boundary is authority, trust, incentive, or care.
Open the living dossierLocate leverage
Find the narrow boundary where better software could change the system's behavior.
Set the evidence gate
State what must be learned, measured, or challenged before a build is warranted.
Publish the limit
Say where software ends and authority, trust, policy, or care must begin.
The desk
Small papers. Sharp edges.
The desk connects investigations to built cases. Each piece names its state so a reader can tell what is observed, what is proposed, and what still needs proof.
0105
Current inquiry
The Coordination Tax
Map the work people perform when context stops at an institutional boundary.
Working hypothesisOpen the living dossier
02Case note
Citadel
The operating layer around coding agents is where routing, verification, and handoff become a product problem.
Released systemInspect the case
03Case note
ProofJudge
A signed acceptance receipt can preserve provenance without pretending that a judgment is objective truth.
Built systemRead the trust boundary
04Case note
Context Aggregator
A workspace becomes portable only after someone decides what should travel, what should be scrubbed, and what should stay behind.
Archived experimentTrace the pipeline
In formation
What makes a problem software-shaped?
The editorial thesis behind the desk: locate the repeated work, the lost context, and the smallest testable change.
Method notePressure-test the thesis
How to use the desk
A briefing should improve the next decision.
Read one before commissioning a build, use one to align a team, or underwrite the investigation that makes a consequential bottleneck measurable.
Diagnose
Give a messy system a shared language before a feature list takes over.
Choose leverage
Separate a software-shaped intervention from a problem that needs policy, authority, or care.
Commission
Fund a bounded briefing or prototype with a named evidence gate and an independence rule.
Selection rule
Submissions are signals, not a backlog.
We select questions for consequence, leverage, access to evidence, and a testable intervention. A submission can start a conversation; it does not purchase a conclusion or guarantee a build.
Bring the desk to a real system
Commission a decision briefing.
For a funder, operator, or domain expert, the first useful deliverable may be a clearer question and a credible evidence gate before it is software.
See partnership paths