A colossal marble head under construction by robed figures placing blocks
How it remembersCase Study #0FAQFounder’s note
INSTITUTIONAL INTELLIGENCE

Every decision your company ever made: remembered, current, and cited.

Apostra reads the places your company already works and turns them into a living record of its decisions: what was decided, who made the call, and what got rejected. If it can’t cite a source, it doesn’t say it. The record your team reads today is the brain your agents run on tomorrow.

Join the waitlist

Live fire? Claim the 48-hour mirror demo →

FIG. 01AN INSTITUTIONAL MEMORY, UNDER CONSTRUCTION · ONE CITED DECISION AT A TIMEAPOSTRA · MMXXVI
Figures gathered at an inscribed stele at golden hour
FIG. 02THE RECORD OUTLASTS THE DAYAPOSTRA · MMXXVI

Your company writes everything down. And remembers nothing.

The archive is complete. The index is a person.

Stop being your company’s search engine.

Every “why is it built this way?” interrupts your most expensive people. Every departure walks out with the only copy of the reasoning.

why did we pick this schema?wasn’t that vendor rejected?who decided the rollback?didn’t we settle this in March?what did we promise them?why is pricing set up like this?who owns this now?why not the other approach?× every week, aimed at you

It reads the trail you already leave.

Read-only access to the channels and repos you choose, with 6 to 12 months of history backfilled at install. No wiki to write, no fields to fill.

EVERY TEAM · EVERY CHANNEL

All of it becomes one record.

ONE LINE OF THE RECORD

Here’s what that looks like.

One decision from the record: what was decided, the messages it was read from, and the two versions it replaced. All in the open, nothing typed by hand.

Planner-agent output schema settled — feeds the code-gen agent

active · sig 0.85 · conf 0.55 · @ @ · Nov 20 2025 · #ai-stack · Forge · engineering

JSON schema with subject, topic, exam_type, and a per-question object: question_type, core_concept, difficulty, diagram fields.

REJECTED ALONG THE WAY

question_description holding only a brief description — renamed to question_text since it holds the actual generated question.

RECEIPTS
“Thinking of going with this as the output of the planner agent / what goes into the code gen agent:” #ai-stack · open in Slack ↗
“A correction here — question_description → question_text, would be the actual textual question generated by the planner” #ai-stack · open in Slack ↗
LINEAGE — THE SCHEMA TOOK THREE TRIES
supersedes · “JSON question schema: id, subject, topic, stem, options…” · Oct 3
which superseded · “seed-bank schema: question, options, answer…” · Sep 25
READS
Nobody wrote this card. It was read out of #ai-stack, stamped with who, when, and how sure.
PROVES
Every line quotes the message it came from, linked back to Slack. No source, no claim.
STAYS CURRENT
This schema took three tries. The two it replaced are still here, dated.
WE RAN IT ON OURSELVES FIRST
13%

of what the founder confidently remembered about his own company was materially wrong.

Measured on 11 months of one real company’s Slack and GitHub history. Reading the same archive, the machine rebuilt the company’s decisions at 92% precision and 95.7% recall — and his memory turned out to be the least reliable system in the company.

Read Case Study #0 →

What he remembered vs. what happened.

The machine checked every confident memory against the messages. Some of them looked like this.

“we moved it because email wasn’t getting read”
NOT FOUND IN THE RECORD

The record had the real reason, with the thread to prove it: the template broke on mobile. Open rate was never measured.

// SWAP-BEFORE-SHIP · illustrative pair · replace with an adjudicated example
THE TAX

What you stop paying for.

ONBOARDING

A new hire is useful in two weeks, not two months.

The brief lands on day one. After that, context finds them as they work.

SETTLED

A settled question stays settled.

Someone reopens a closed call. The record appears in the thread. The meeting never gets scheduled.

DEPARTURES

People leave. The reasons don’t.

The moment a departure is announced, their decision surface gets snapshotted, before the why walks out.

Built for your people.
Built for your agents.

The same record serves both. Your people get the answer with its receipt attached. Your agents get validity: what still holds, what was superseded, and what the team actually confirmed.

FOR YOUR PEOPLE

The digest moved to Slack in November. The email template broke on mobile, and the fix was raised but not taken. Superseded in February by the weekly ledger.

FOR YOUR AGENTS
claim_id: dec_0417
status: superseded → dec_0562
valid: 2025-11-04 → 2026-02-11
confidence: 0.94 · confirmed ×3
receipts: [#product/09:42, PR#218, #eng/14:07]

Institutional intelligence is whether
your company can remember the why.

I grant early access in order and read this list personally. If you have a live fire (a departure, hires starting, a post-mortem due), skip the line.

Live fire? Claim the 48-hour mirror demo →