Decisions,with receipts.

A local-first decision log for 5–15 person product teams. Ask why a choice was made, see the graph behind the answer, and know which answers went stale.

Embedded Relate graph, one file, no model

hive / ask
Hive answering “Why did we move off Auth0?” with an answer, numbered citations, a context receipt, and a graph of the nodes it used.

The decision is in the notes. The reason is in someone's head.

Find the note. Miss the decision.

Search returns the meeting note, the doc, and three threads. None of them say what was actually chosen.

See the text. Miss the path.

The reason lives on the decision, the person who made it, and the project it affects. A chunk of text does not connect them.

Read the answer. Miss that it is stale.

When a decision changes, the old answer keeps circulating. Nothing tells you which answers relied on it.

Ask. Read the receipt. Review what changed.

01

Ask

A question in plain language. Hive seeds from Relate's full-text index, then expands two hops.

02

Read the receipt

The active decision, the person, the project, the note, and the decision it replaced. Every answer carries the exact nodes it used.

03

Review what changed

Correct a decision. The old one stays, marked superseded. Every answer that asserted it moves to review.

A real context bundle

  • Northwind call — SSO is a dealbreakerNote
  • Move from Auth0 to Okta for enterprise SSODecision, active
  • Use Auth0 for authenticationDecision, superseded
  • Sam OkaforPerson
  • RillProject

The demo lets you click through the full bundle.

The answer is not a chunk. It is a path.

A vector store can find the notes that mention Auth0. It cannot tell you that Okta replaced Auth0, who made the call, or which answers relied on the old decision. Those are edges.

  • Current, not just relevant. Follow SUPERSEDES to the newest decision.

  • Provenance, not just citations. Every answer stores the nodes it used.

  • Impact, not just search. Find the answers that asserted a decision you just changed.

the schema

(:Note)-[:STATES]->(:Decision)
(:Decision)-[:DECIDED_BY]->(:Person)
(:Decision)-[:ABOUT]->(:Project)
(:Decision)-[:SUPERSEDES]->(:Decision)
(:Answer)-[:USED]->(:Note | :Decision | :Person | :Project)
(:Answer)-[:ANSWERED_WITH]->(:Decision)

Built on Relate — the embedded graph database from Neo4j.

A small team that writes decisions down.

Hive is for the 5–15 person product team that keeps notes and keeps answering the same “why?” questions. It is not a wiki, a chatbot, or a compliance system.

Product and engineering leads

Stop re-litigating decisions. Find the reason, the person, and the note.

New teammates

Ask why the API looks like this and get the meeting note, not a guess.

Teams preparing for a review

Show the decision trail, including what was replaced and why.

Today: add-only, one store, one writer, no bulk import.

Ask the ledger.

The demo is seeded with a fictional 18-note company. No signup. It runs locally on one file.

Open the demo
01Why did we move off Auth0?
02What did we decide about pricing?
03Why did we leave Vercel?

These are the suggested questions inside the demo.