§ 01 ── MANIFESTO

We build the substrate
every AI-native company will need.

Ten principles govern what we build, what we refuse to build, and how we treat the customer relationship. They are durable across product evolution and market pressure. They predate Diana Hu's YC framing of AI-native operating companies and survive past it. The principles are the substrate of the substrate.

§ 02 ── PRINCIPLES

What we commit to.

01

METHODOLOGY PRESERVATION

Your organization-methodology is yours (L2). We encode it. We don’t sell it. No engagement makes your overlay part of our product without explicit pattern-migration consent (attribution + compensation gated). The methodology is the institutional invariant. Models execute it. The substrate carries it across model generations.

→ /substrate · L0 / L1 / L2

02

IP CLARITY

L0 universal doctrine (open) · L1 framework (operator IP) · L2 instance (yours). You own the audit chain, customer overlay, eval suite, runbooks, and all data. Spelled out in the MSA. Customer keeps L2 IP unconditionally at any engagement termination.

→ /engagement · MSA terms

03

AUDIT BY DEFAULT

Every action writes to the audit chain via the Audit Curator (sole-emission per tier). There is no code path in our architecture where decisioning bypasses the audit primitive. severity:critical entries are NEVER-deletable. Every claim ships with its lineage attached.

→ /security · audit chain

04

CONSENT IS NON-NEGOTIABLE

Source-level OAuth scopes are the floor. User-level permissions are enforced at query time. Revocation halts within 24 hours; aggregates purge within 72 hours. F9 employee privacy floor is architectural. Per-category opt-in. Default-OFF. No inherited consent across categories.

→ /security · consent + revocation

05

HUMAN AT THE EDGE

Per Jack Dorsey at Block: humans at the edge guiding the company, not in the middleware routing information through it. The L8 canonical floors F1–F6 (Money-Movement · Customer Data · Compliance/Risk · Audit Sole-Emit · Cohort · Code-Shipping) plus 0–3 optional F7–F9 are resource-domain architectural enforcement, not policy. The autonomous code paths do not exist in the codebase. Class A agents (T2 drafters) route. Humans judge where consequences are highest.

→ /security · LF1-F6 canonical floors

06

REVERSIBILITY BIAS

Originals archived before destructive operations. Append before rewrite. ADRs immutable. Audit chain append-only. Amendments logged with rationale. Pre-snapshots on every MINOR and MAJOR cycle.

→ /security · D7 verification

07

ANTI-RITUAL DISCIPLINE

The substrate serves the company, not the reverse. Ceremony is proportional to stakes. Hygiene flags procedures that aren’t earning their keep. We are skeptical of any process the substrate exists to perform but no human could justify in plain language. Token-maxing not headcount-maxing — the substrate exists to make the team leaner, not to grow process around itself.

08

HONEST EXPERTISE

The substrate tells you what it knows, what it verified, and where it’s likely to be wrong. Evidence modes labeled. Confidence bands explicit. No hidden assumptions. Diverge-and-reconcile triggers on substantive decisions. Refusal-to-invent is a posture, not an exception.

→ /substrate · evidence modes

09

SUBSTRATE-MIRRORING (I15)

Every commitment we enforce on customers applies recursively to our own operations. We operate under the same audit chain, the same F1–F6 canonical floors, the same κ ≥ 0.85 verification, the same D7 §12 inspection. The substrate has no outside. Including us.

→ /security · I15 mirror

10

PATTERN MIGRATION

Patterns that prove cross-cutting across multiple customers in the same L1 can migrate L2 → L1 — with explicit customer concurrence, attribution, and compensation. The substrate compounds across the cohort. Customers benefit from every other customer’s L2 → L1 migration. Loop composition is multiplicative across the cohort, not additive.

→ /engagement · migration terms

§ 03 ── THE MODEL CHANGES

The model changes.
The substrate remembers.

── QUERYABLE.COMPANY · 2026

Methodology is the invariant. Models are replaceable execution layers. The substrate carries continuity across model volatility. That’s the architecture. That’s why we build this. Era 3 begins when companies stop adding AI as a tool to Era 2 and start running on AI as the operating system. The substrate is what makes that crossing operational.

§ END ── BUILD WITH US

If this is how you think about company-building — talk to us.