Product Tour

Inside the vault.

Five views of the system you get: how decisions are captured, stored, linked, and turned into assets — and the one dialog that guards your data boundary.

Prefer to click instead of read? Open the interactive ledger demo →

High-fidelity mockups — real screenshots in preparation
adamas — vault · ledger
SAL-021 FIN-016 HIR-014 OPS-020 PRD-019 SAL-021 · SALES · 2025-04-14 CONTEXT DECISION TRADE-OFFS LINKED FIN-016 OPS-020 SAL-017
01

The ledger

The core of the vault: every decision is a structured entry — context, the exact call, who made it, the trade-offs accepted, and two-way links to the decisions it shaped.

Filter by domain, follow a link, and the reasoning behind any call from two years ago is three clicks away. Try it in the demo →

adamas — capture inbox
Surfaced this week · 6 candidates FROM #sales · Slack thread · Tue 14:32 Confirm Dismiss FROM weekly review · meeting transcript · Fri 09:12 Confirm Dismiss FROM client email · thread (4 msgs) · Wed 17:05 Confirm Dismiss FROM Jira · ticket comment · Thu 11:48
02

The capture inbox

Hermes reads the week's noise — Slack threads, email, transcripts, tickets — and surfaces the moments that were actually decisions. You confirm or dismiss; nothing enters the ledger unreviewed.

This is the "runs on autopilot" part: capture costs the team minutes per week, not a documentation habit nobody keeps.

adamas — decision graph
SAL-021 FIN-016 SAL-017 OPS-020 PRD-019 FIN-007 FIN-022
03

The decision graph

Decisions connect to each other. Declining one big contract touches pricing, billing, and staffing — and the graph shows those links. When someone asks "why are we set up this way?", the answer is on screen instead of reconstructed from memory.

This is also what compounds: every new entry adds edges, and the graph becomes your company's institutional memory.

adamas — asset generation
Generate asset Onboarding document Hiring framework Investor one-pager SOURCES · 9 DECISIONS HIR-009 · OPS-013 · SAL-011 FIN-022 · SAL-017 · OPS-020 PRD-019 · PRD-008 · OPS-005 Generate → onboarding_automation-engineer.md HOW WE QUOTE WORK HOW WE DELIVER ON SITE WHO DECIDES WHAT traced to 9 ledger entries
04

Asset generation

Pick the asset your stage needs — onboarding doc, hiring framework, investor material — and ADAMAS assembles it from the ledger, with every section traced to its source decisions.

When a decision changes, the asset regenerates. The documentation stays current instead of going out of date. Read a full generated sample →

adamas — hybrid approval
Cloud processing requested Task: summarize 214 supplier emails (heavy) WOULD BE TRANSMITTED Result returns to your vault. Route is logged in the ledger. Approve once Run locally
05

The boundary dialog

The only moment data can leave your machine — and it never happens silently. You see exactly what would be transmitted, approve or decline per task, and the route is logged in the ledger.

Decline, and the task runs locally instead. The default is always: nothing leaves. Full security details →

What ADAMAS Generates

Every department, from one ledger.

Each asset is assembled from decisions you already made — traced to its source entries, and re-generated when those decisions change. Nothing is invented. The departments map to the five domains in the interactive demo.

Hiring & People

Hiring
  • Role onboarding document Live
  • Hiring decision framework Live
  • Promotion & comp-anchor rationale Generatable
  • Org-design memo Generatable
  • Offer & rejection rationale log Generatable

Sales & Revenue

Sales
  • Deal-qualification playbook Generatable
  • Pricing & rate-card rationale Generatable
  • Scope & discovery SOP Generatable
  • Win / loss decision review Generatable
  • Channel & contract policy Generatable

Product & Delivery

Product
  • Product & roadmap rationale Generatable
  • Tech-stack decision (ADR) log Generatable
  • Sunset / end-of-life policy Generatable
  • Build-vs-buy memo Generatable

Finance

Finance
  • Capital-allocation policy Generatable
  • Pricing-floor & contingency model Generatable
  • Billing & cash-cycle SOP Generatable
  • Financial decision memo pack Generatable

Operations

Ops
  • Operating cadence & rituals doc Generatable
  • Handover & continuity protocol Generatable
  • Safety & compliance SOPs Generatable
  • Risk register Generatable

Investor & Board

Cross-domain
  • Investor one-pager Live
  • Board decision digest Generatable
  • KPI & commitments tracker Generatable
  • Data-room index Generatable

The two assets that make a founder-led company legible

These aren't per-department — they assemble the entire ledger. They're what an acquirer, a board, or a bank asks for, and what most $2–5M founder-led firms simply cannot produce on demand.

The Decision Diligence Binder

Every reasoned decision, by department, with owners and trade-offs — exported as one document. The file a buyer's lawyer asks for during due diligence.

The Founder-Continuity Dossier

"If the founder steps away tomorrow, here is every decision and why." Directly answers the key-person risk that discounts founder-led valuations.

Live = demonstrated in the generation panel above. Generatable = supported by the ledger structure; surfaced as your entries accumulate. See a full generated sample →

The architecture behind these views, in one diagram: how it works →

Book a Clarity Audit →