The method · Genesis

Turning an intention into something you can check.

Most ideas die in the gap between intention and structure. Genesis is the working method used behind ORÆ to close that gap — turning a rough intention into objectives, constraints, risks and milestones that can be reviewed later. It is one method among many.

Our reading

Described because it is what is actually used here — not because it is the right way to work. Take what is useful, ignore the rest.

The transformation

An intentionis read without flattening its meaning — captured as purpose, not as a task.
An ideabecomes objectives, constraints and the questions that must be answered.
A projectgains a clear architecture: scope, license, risks and dependencies made explicit.
A memoryholds the decisions and the reasons behind them — accountability over time.
A roadmapsequences the work so each phase gates the next. The road refuses leaps.
Milestonesturn ambition into checkable, public deliverables.
Governanceattaches the refusals and the human checkpoints from the start.
Executionstays traceable — what was done, why, and what could be reversed.

Genesis is deliberately modest. It is small enough to be tested honestly on a single project: if a rough intention cannot be turned into a structure someone else could review, the idea probably is not ready yet — and that is useful to find out early rather than late. It is a habit of writing things down before starting, nothing more. No tooling is required, nothing is certified by following it, and plenty of good work is done entirely without it.

Intention becomes architecture.
Where this gets applied
← Back to ORÆ