The substrate

The objects
beneath the work.

Tehom Primitives are the typed objects every governed system is built from. A record carries its own origin, its boundary, and the proof that backs it — so meaning travels with the data, not in the application around it.

01 — Why typed

Most systems keep meaning in the application. Tehom keeps it in the record.

When meaning lives in code, every new surface has to re-derive what a thing is, where it came from, and whether it can be trusted. The knowledge erodes at each boundary.

A typed primitive carries that knowledge with it. Its origin, its claim state, its boundary and proof are part of the object — readable by any system that holds it.

That is what makes the substrate transferable. Amar and Or are not separate databases — they are two readings of the same governed records.

02 — The families

Twelve typed primitive families.

Every governed record belongs to one. Together they describe what a thing is, where it came from, what it permits, and what backs it.

01

Source

Where a record comes from — its authority and system of origin.

02

View

How a record should be read, and the state of its claim: source-backed, projected, or degraded.

03

Boundary

What a record permits and forbids — the edge an agent works inside.

04

Proof

The evidence that backs a claim, and the gates that pass or fail on it.

05

Review

The judgment a record carries — who reviewed it, and the disposition reached.

06

Memory

What persists across cycles — the durable trace a record leaves behind.

07

Seat

The role an actor holds — what a human or agent may review, route, and gate.

08

Workflow

The route work travels — the lanes, states, and transitions a record moves through.

09

Artifact

What an agent produces — the output and its lineage back to a Source.

10

Authority

Who or what may grant, govern, or override — the final say on a record.

11

Relation

The typed edge between records — how Or remembers what connects to what.

12

Block

What stops the work — a blocker that must clear before motion resumes.

Gold marks a family that carries judgment — Proof, Review, Authority — where a human decision is recorded.
03 — Inside a record

Every record carries its own envelope.

No matter the family, a typed record reads the same way: where it came from, how it should be read, and the state of its claim. Surfaces render it; none of them own it.

record · MARK-1184 · family Boundaryread-only projection
Source
where it came from
tehom-dev-standards · markdown_projection
View
how it should be read
claim · judgment · source-backed
Boundary
what it permits
read-only · protected actions disabled
Proof
what backs the claim
3 of 4 gates · 1 pending
Review
who judged it
human · Reviewer seat · awaiting
Authority
who may override
Founder Operator · owner route
Amar reads them as work

The operating layer moves these records through lanes and the human gate.

enter the bridge →
Or reads them as memory

The relationship layer reads the typed edges between the same records.

open the graph →