An opinionated methodology kernel.

The contract is two markdown files

PRODUCT.md says what the product is and who it is for. ARCHITECTURE.md says how it is built. Together they are the contract — the source of truth the AI builds against. Code changes that violate the contract get rejected before they merge.

Brainstorm before build

Every non-trivial change starts with a Brainstorm artefact: approaches considered, risks surfaced, architecture proposed. The brainstorm is the evidence of considered design. Vibe-coding is not banned — it is just not the default path for things that matter.

Glass Box, not Black Box

You see exactly what the Brain is doing, what tools it is using, and what it is about to change. Nothing happens you can’t see. Every action is reversible, attributable, and queryable months later.

PROV on every step

Provenance is not an afterthought — it is a primitive. Every brainstorm, plan, code edit, test run, deploy step, audit finding, and human approval lands as a typed PROV node. Replay any decision; defend it under audit.

Human pilot, AI amplifier

The Centaur model. The human pilots the mission and owns the call. The AI amplifies — proposes, executes, audits, reports — but never lands a regulated merge without human approval. The cockpit metaphor is literal.

BYOK + BYOI architectural commitment

You bring your keys; you bring your infrastructure. Jorv never proxies your provider calls and never stores your code. The architectural simplicity is what makes the predictability real — not a marketing claim.

D

Discover

Map the unknowns. Surface contradictions. Build the conviction graph before you build the code. Jorv Discovery is the dedicated cockpit; the principle applies to every product.

C

Create

Build the thing. The Builder cockpit is the workhorse. Brainstorm, plan, execute under the glass box. Ship with the PROV chain intact.

R

Reach

Get the thing in front of users. Marketing, sales, education, support — the Business cockpit (coming) covers the lifecycle. Until then, the family-level discipline holds.

L

Learn

Feedback, telemetry, audits, retrospectives. Every learning loop folds back into the contract docs. The contract is the system’s memory.