Oath.
Living organisational memory

Every IC navigates their company blind.
Oath fixes that.

A 30-minute daily voice session with each employee, anchored to their calendar, that builds a queryable, current, full-fidelity record of what your company is actually doing. Powering both a private personal intelligence graph for the individual and a sanitised organisational graph anyone in the company can ask.

A knight kneels and lays a hand on the hilt of a sword while a robed figure offers a chalice — the act of taking an oath.
The oath, kept daily.
The problem

Inside a company, the people doing the work know the least about it.

An IC joining a project mid-stream has no reliable way to understand its history. A developer about to build a feature can't see if another team is already building it. An employee trying to understand a strategic shift has no way to surface the decision trail.

None of this is solved by OKR tools, Notion wikis, or Confluence pages — they're always out of date and incomplete. This isn't a management problem. It's an information architecture problem, felt most acutely by the people inside the company trying to do good work.

The daily session

A 30-minute structured interview, anchored to your calendar.

Oath enters every session already knowing your schedule. It walks slot by slot and probes for what the calendar can't know: what was decided, what shipped, what blocked you, what felt repetitive.

Two mages bind hands within a glowing sigil — a pact between two parties.
A binding, daily, between you and the record.
Oath
Good afternoon — let's walk through your day. You had a 9am with Jane. What did you two cover?
You
We finalised the campaign timeline and aligned on who owns the design hand-off.
Oath
Got it. Did you make enough progress on the campaign timeline, or are there things that still need resolving before it can move forward?
You
We're blocked on final assets from design — should be cleared by Wednesday.
Oath
Noted as a blocker. From 10 to 11 you had a free block — what were you working on?
You
The marketing brief — that's on the Q3 brand OKR.
Oath
Nice — that maps directly to the brand OKR. Did it get to a state where it felt done, or is there more to go?
Calendar-as-scaffold

Every meeting becomes a probe. Every free block becomes a question.

Aggressive about depth

Vague answers get sharpened by a deeper reasoning model in real time.

Natural filter

Real work fills 30 minutes. Empty days surface themselves, no interrogation required.

What you get

The personal intelligence graph nobody has time to maintain — maintained for you.

Every session feeds a private, full-fidelity knowledge graph of your work. Yours alone. No manager, peer, or executive can query it.

Two figures sit alone on a rooftop above a neon city, sharing a quiet drink — a private confidence.
Yours alone. Always.

Personal recall

“What did I decide about the contractor budget in April?” “What was the outcome of the Spartacus kick-off?” “What have I shipped in the last 30 days?” Always answerable.

Upward management update

At the end of each session, a strategically framed summary for your manager. You review it, edit it, click send. You retain full control of the narrative.

Tomorrow's plan

The following morning, a priority list built from where you left off — unresolved threads, upcoming calendar, OKR alignment.

Personal brand engine

On demand, your wins become LinkedIn posts, wiki entries, or blog drafts. The record is being built; publishing from it is almost free.

What anyone can ask

A company Wikipedia that is always current — because it's built from what people actually did today.

The organisational graph is queryable by anyone, with project-level resolution. The IC layer ICs always wanted, and never had.

A figure raises a fist over an oath book before a crowd — the collective record, held in common.
The shared layer, held in common.
Who is working on something related to video production?
Sarah has been leading video production for the brand OKR since March. She's in post-production on the Q3 campaign and currently blocked on a design hand-off. Mike on the content team has been doing adjacent scripting work.
Is anyone already working on a component-library refresh?
There's exploratory work in the design team — not currently mapped to an active OKR, so it may be early-stage or informal. Worth a conversation before starting something parallel.
Why did we move away from the original auth approach?
In early April the engineering team flagged a performance issue during a session. The decision to switch was made in a cross-functional review on April 9th, primarily on latency grounds.
The privacy model

Two layers. One private, one shared. By design, not by policy.

Every session is processed into two distinct graphs. The separation is the reason Oath can make a company legible without making any individual surveillable.

Layer 1 · Private

Personal Intelligence Graph

The full session transcript, structured and linked to meetings, projects, OKRs, dates, collaborators. Accessible only by you. Never visible to managers, peers, or executives.

Layer 2 · Shared

Organisational Context Graph

A processed summary. Specific conversations and verbatim quotes are discarded; substance is retained: which projects are active, what role each person plays, how things are progressing, and which OKRs they connect to.

Resolution, not role. Access is governed by the depth of information being requested, not by who is asking. Project-level is open to everyone. Day-level is private. Managers get directional signal on their reports — enough to manage proactively, never enough to surveil.
For managers

A Monday-morning recap good enough to replace the standup.

Aggregated, directional, never surveillance. Written at the level a good chief of staff would brief you.

Team recap — week of 16 June

Overall the team is well-aligned. Spartacus is progressing and looks on track for Q3, though the data-pipeline dependency is worth watching. The infrastructure migration is moving more slowly than last week — three team members flagged it as lower priority than expected, which may be worth a check-in on resourcing.

One alignment note: some backend work has come up across a few sessions this week that isn't mapped to an active OKR — worth understanding whether it should be formalised or deprioritised.

One team member's output has been lighter relative to peers over the past two weeks. No specific blockers flagged, but the pattern is worth a conversation.

What the recap does NOT contain: session transcripts, verbatim quotes, or anything that would read as eavesdropping on a person's day. The signal threshold for flagging any individual is a sustained pattern — typically two or more weeks. One quiet day is noise.

The compounding curve

Value isn't linear. It compounds with time.

An organisation with 12 months of Oath data has an intelligence asset that cannot be replicated by switching tools.

Day 1

Sessions are structured but general. Your personal graph begins. The org graph starts with whatever was bootstrapped at setup.

Week 4

The AI knows your projects, vocabulary, collaborators, and OKRs. Sessions get faster and more specific.

Month 3

A rich, queryable contribution record. Meaningful alignment signal. Agents can start operating on the context layer.

Month 12

Living institutional memory. New hires onboard with context. Executives can identify systemic misalignment between effort and strategy.

What Oath is not

Clarity on the boundaries.

Not a surveillance tool

Anyone can see what projects a colleague is working on and whether it's aligned. No one can see another person's schedule, transcripts, or individual output scores.

Not a management product employees tolerate

The primary user is the IC. Management intelligence is downstream of employees engaging honestly because the product works for them first.

Not an interrogation

Bad days, slow days, days dominated by invisible work all exist. The AI helps frame them constructively, not extract confessions.

Not a performance review

Oath data is a longitudinal contribution record, not a verdict. Treating output signals as immediate grounds for action misunderstands the product.

Start with one 30-minute conversation.
Compound it for a year.

The investment is real. So is the asset it builds: a contribution record, an organisational memory, and the substrate every AI agent in your company will need to be useful.