Blueprint
It's not just the code and the standard that are open — so is the question of how to run a construction company.
Company = Git organization
Governance documents, roles, decisions, and their reasoning live as versioned files in git — not in a separate wiki that goes stale the moment nobody remembers to maintain it. If you want to know why a decision was made, you read the decision record itself, not a summary of it.
The [AI]/[AI→H]/[H] grid
Every recurring task is assigned to one of three categories:
The grid is an attempt to state honestly where automation makes sense — and where it explicitly doesn’t.
Public-by-exception
Everything is private by default. Publication is a deliberate, approved step, not the default — including for this Blueprint repo itself: what lands here has already been thought through and approved, not a raw draft.
What the first release contains
The git-organization thesis, a role-file template, the [AI]/[AI→H]/[H] grid as a generalized template, and the approval workflow for decisions. Release cadence: quarterly. No live mirror, no sync promise — a release artifact with a version and a date.
If this model resonates — as a founder who wants to copy it, or as someone who’d like to help build it: