Tehom Investor Deck Proof Appendix
- Date prepared: 2026-06-25
- Purpose: show where Cycle 115/117/119 Tehom customer-zero evidence strengthens the Tehom investor deck
- Boundary: this is deck support, not the case study itself, and it does not replace the white paper
Format And Voice Standard
The investor deck's philosophical and epic frame is intentional and should remain intact. This appendix uses a quieter diligence register: specific claims, evidence links, caveats, and proposed proof-bridge slides. The repair is not to flatten the deck into an engineering report. The repair is to give the deck a stronger proof bridge:
The internal operating proof exists. The seed round funds productization and external customer proof.
The deck should preserve the fear/control problem, Leviathan, the guide posture, Amar as the governed loop, Or as durable work memory, and the epic first-principles appendix. The new material belongs in the proof bridge and diligence appendix.
Tehom Language Bridge
Use Tehom language where it clarifies the investment story:
- Horizon: the long direction the round funds.
- Mark: the arrival condition that proves progress.
- Path: the route from internal operating Proof to business-workflow Proof.
- Move: a committed bet; keep
BET-####when citing source records. - Proof and Trace: source-backed evidence and provenance.
- Judgment: an accountable decision, including ADRs.
- Source, View, and Boundary: the source of truth, the rendered surface, and the authority limit.
Deck Update Thesis
The cycle evidence advances the deck by moving one claim from aspiration to internal operating proof: Tehom has already run its governed work loop against itself. In this packet, customer zero is Tehom itself. H&J and PetroSuites are the first business-workflow proof lanes the round should instrument next.
Claims The Cycle Advances
| Deck claim | What the current cycle proves | How to say it in the deck |
|---|---|---|
| Leaders fear losing control as machine work accelerates. | Cycle 117 surfaced concrete control failures: stale source, lifecycle ambiguity, non-current review, runtime provenance, cleanup disagreement, and dependency misclassification. | Leviathan is not theoretical. Tehom observed it in its own operating system and made it diagnosable. |
| Amar is a governed control loop. | Ask, Prove, Review, Resolve, Remember, Repair, and Improve all happened across source-backed cycles and Moves. | The loop has already run inside Tehom. |
| Or preserves the story of work. | PRs, run checks, reviews, security reviews, session logs, closeouts, Judgments, and runtime records created retrievable memory. | Or is the memory layer that lets delegated work remain explainable. |
| Customer-zero is the proving ground. | 147 bet files, 145 completed, all with verification and retrospective structure, plus 715+ hours of governed agent work across 10 calendar days. | Tehom is customer zero for the operating loop; H&J and PetroSuites are the first business proof lanes. |
| The model is not the moat; memory is. | The cycles generated proprietary operating memory: accepted evidence, repair patterns, authority rules, and recurrence decisions. | Tehom's moat compounds through governed work history. |
| Seed capital funds proof. | The foundation plus internal operating proof now exist. | The seed round funds productization, instrumentation, external pilots, and measurable outcomes. |
Proof Copy Repairs
| Deck location | Current posture | Replacement posture |
|---|---|---|
Slide 15, Operating proof | The foundation exists. The seed round funds the proof. | The internal operating proof exists. The seed round funds external proof. |
Slide 16, Customer-zero | The outcomes are not claimed yet. | Customer zero is Tehom itself. The loop has already governed its own agent-work operating system. This round instruments H&J and PetroSuites as first business proof lanes. |
Appendix I-12, Early evidence | 55+ hours of continuous autonomous execution | 715+ hours of governed agent work across 10 calendar days, managed by one human owner with evidence, review, and repair preserved. |
| Ask slide | Fund the governed work layer. | Capital now converts internal operating proof into productized customer proof. |
Recommended Proof-Bridge Slides
Add these after Slide 16 Customer-zero or place the first two in the main deck and the rest in Appendix I.
Customer-Zero Stress Test
Headline:
The operating loop has already run against Tehom itself.
Metrics:
- 3 completed cycles.
- 147 canonical bet files.
- 145 completed, 1 superseded, 1 intentionally deferred.
- 715+ hours of governed agent work across 24 overlapping sessions and 10 calendar days.
- 184.09-hour main execution session.
- 13 filtered actual user prompts in the main execution session.
- 6 ADRs added and 3 governing ADRs touched.
Speaker note: present this as internal operating proof, not customer ROI.
The Control Loop Became Real Work
Headline:
Ask. Prove. Review. Resolve. Remember. Repair. Improve.
Map:
- Ask: Marks became cycles and Moves.
- Prove: run checks, Source checks, runtime evidence, and session logs.
- Review: PR contract, human review, security review, and Forgejo status.
- Resolve: guarded merge, post-merge verification, terminal closeout, supersession, and deferral.
- Remember: Or-directed source records, Timescale, PRs, Judgments, Move retrospectives, and agent-session logs.
- Improve: repair bets, recurrence rules, execution-lane policy, and follow-on cycles.
Leviathan Became Diagnosable
Headline:
The failure state was observed, classified, and repaired.
Map:
- Stale source -> source map and freshness gates.
- Lifecycle ambiguity -> work timeline and terminal state.
- Missing evidence -> evidence panel and run-check handles.
- Unclear authority -> review, security, and PR contract gates.
- Repeated failures -> repair history and recurrence rules.
- Unsafe acceleration -> action boundaries and opt-in execution lanes.
From Internal Proof To External Proof
Headline:
The seed round turns internal operating proof into customer proof.
Use-of-funds proof path:
- productize Amar surfaces around real evidence types;
- instrument H&J and PetroSuites workflows;
- measure onboarding, approval, resolution, lost-lead, repeat-failure, and time-to-repair outcomes;
- convert one measurable business-workflow improvement into outside pilots;
- harden security, governance, and auditability.
Product Surface Mapping
| Amar View | Cycle evidence that makes it tangible |
|---|---|
| Work timeline | Cycle open/close dates, bet status transitions, PR and merge history, and agent-session logs. |
| Proof panel | Run-check IDs, CI statuses, review IDs, security review IDs, runtime deploy records, and post-merge Source verification. |
| Judgment trail | PR contract validation, guarded merge, review/security gates, human prompt interventions, supersession, and deferral. |
| Source map | Source-anchor repair, origin/dev freshness checks, runtime Trace, worktree/path diagnostics. |
| Unresolved work queue | Superseded BET-987, deferred BET-520, and unchecked residual items tied to known terminal decisions. |
| Repair history | Cycle 117 repair chain, recurring failure classes, closeout records, recurrence rules, and ADR-091 through ADR-096. |
| Action Boundaries | Default execution-lane mode blocked, broader/final checks retained, and Brain-labeled retrieval kept advisory rather than authoritative. |
| Lesson suggestions | Judgment production, follow-on cycles, execution-lane policy, and graph-substrate correction. |
Diligence Caveats For Speaker Notes
715+ hours of governed agent workmeasures logged wall-clock agent-session footprint across the Cycle 115/117/119 window, not labor-hours saved.- Session-hours can overlap.
- Commit author
Matt Hooddoes not prove manual authorship because many commits occurred inside agent-driven sessions. - The current proof is internal operating proof. External customer traction, commercial ROI, and cross-customer repeatability still need funding and measurement.