main.ts:247

// don't change this — ask Jake

#engineering

@channel does anyone remember why we chose Postgres?

March offsite

"We talked about this at the March offsite..."

Jake left six months ago.

Three people have searched and found nothing.

Nobody took notes.

Your product is a thousand decisions.
Most of them walked out the door.

Reckon is the decision record your team never kept. What was chosen, why, and what it replaced — accessible to your whole team and your AI agents.

Get started with GitHub
decisions / acme-platform
5 active 2 deprecated
technical Use Postgres over MongoDB
accepted 4 months ago
product Target self-serve SMBs first
accepted 6 months ago
technical Roll our own auth
deprecated 8 months ago
product Annual billing not worth complexity yet
accepted 3 months ago
technical Event sourcing over CRUD
accepted 5 months ago
product Kill the recommendations feature
accepted 2 months ago
technical Redis for caching layer
deprecated 7 months ago
product Free tier for conversion
proposed 1 week ago
technical Use Postgres over MongoDB
accepted 4 months ago
product Target self-serve SMBs first
accepted 6 months ago
technical Roll our own auth
deprecated 8 months ago
product Annual billing not worth complexity yet
accepted 3 months ago
technical Event sourcing over CRUD
accepted 5 months ago
product Kill the recommendations feature
accepted 2 months ago
technical Redis for caching layer
deprecated 7 months ago
product Free tier for conversion
proposed 1 week ago

Your agents are fast, capable, and architecturally blind.

An agent doesn't know you deprecated Redis. It doesn't know you're targeting self-serve SMBs. It doesn't know the team chose event sourcing over CRUD.

So it builds what looks correct and is strategically wrong. You review it, reject it, explain the context from memory, and wait for a regeneration.

You're paying for AI to go faster. Then paying your most expensive people to slow it down.

claude-code
> Add a caching layer to the API

The decision record your team never kept.
That your agents desperately need.

Product decisions
Technical decisions

"We chose Stripe" connects to "We're targeting self-serve SMBs." Your database choice underpins your multi-tenancy strategy. When the foundation shifts, see everything built on top of it.

Product decisions and technical decisions aren't separate things. They're the same graph.

Target self-serve SMBsUse StripeFree tier pricingWebhook architectureUsage-based limitsOnboarding flow
01

Capture what's in your head

What was chosen, why, what it replaced. Thirty seconds for a decision your team already made but never recorded.

02

Decisions evolve. Track that.

Draft. Proposed. Accepted. Deprecated. The full history stays — not just what you decided, but how your reasoning changed.

03

Map what depends on what

Link decisions that build on each other. When a product decision changes, see every technical choice that was built on it.

04

Agents connect in two minutes

Add Reckon's MCP server to Claude Code, Cursor, or Windsurf. Every decision is instantly searchable by every agent on your team.

A place for thoughts that need time to settle.

Get started with GitHub

Free while in early access. No credit card required.

reckon