The maths,
not the pitch
Short guides on the mechanisms OrgGen computes for you. Every claim is checked against the product — and where a limit exists, it is written down.
Converting a SAFE: the three candidate prices
A SAFE does not convert "at the cap" or "at the discount": it converts at the lowest of three candidate prices. This guide gives the exact calculation, shows why an 8M post-money cap is not an 8M pre-money cap, and names the two situations where the cap changes nothing.
Updated August 18, 2026Read the guide →Liquidation waterfall: who gets what, in which order
An exit is not split pro-rata to the cap table. Preferences come first, some come twice, and a rational investor sometimes waives their own. This guide describes the four mechanisms and the invariant that holds them together: the sum paid always equals the exit price.
Updated August 18, 2026Read the guide →Exporting a C4 diagram from your agent: Mermaid or PlantUML
An architecture export is never complete: the target grammar has a finite number of slots, and the model has more. This guide says which of the two C4 formats keeps what, what both leave behind, and why OrgGen tells you rather than letting you find out in an architecture review.
Updated August 18, 2026Read the guide →Driving tasks and arbitration from your agent
An agent can create tasks and raise a question to decide — never answer it itself. This guide shows the exact cycle (propose → arbitrate → in-progress → closed), the six verbs the agent can call, and why this is not a code of conduct but a lock checked at compile time.
Updated October 3, 2026Read the guide →What your agent prepares, what you sign
"Your agent gets a version signed" would be a lie: no tool allows it. What the agent actually does is name a milestone (`save_version`) — proposing, collecting signatures, and sealing stay human actions, in the app. This guide explains why that boundary is deliberate, not a regrettable limitation.
Updated September 5, 2026Read the guide →Multi-project cascade: managing N subjects as one graph
Twenty subsidiaries, twenty separate OrgGen projects, one navigable graph: a block linked to another project shows a badge and dives in inline, without copying. This guide distinguishes linking / creating empty / forking — three gestures easily confused — and shows what the sharing cascade actually opens up, and to whom.
Updated September 5, 2026Read the guide →