Why you chose X, in one place.

The pain

• —You picked Postgres over DynamoDB six months ago. Today you wonder whether to switch. You can't reconstruct the trade-offs you weighed back then.
• —Slack threads decay. "The decision" lives in a 40-message thread that's already been archived twice.
• —When you ask Claude to weigh a new option, it has no idea what you already rejected and why.
• —Onboarding a teammate means re-explaining every past decision from memory.

What you do in Memory.Wiki

1. 1
   Write the decision as a short doc

   Context (what we knew), Options (what we considered), Decision (what we picked), Consequences (what we expect). 200-400 words. Memory.Wiki auto-tags the intent as "decision" after the next concept refresh.
2. 2
   Cite the inputs

   Link the customer interview, the spike branch, the cost-model spreadsheet, the AI conversation that helped you think. Each link survives because Memory.Wiki URLs are permanent.
3. 3
   Bundle by area

   Group all infra decisions, all pricing decisions, all hiring decisions into bundles. The hub log shows when each was made and who edited it.
4. 4
   Recall when you revisit

   "Why did we pick Postgres?" → the Hub Assistant cites your own doc + its inputs. The AI now argues using your actual reasoning, not generic advice.

What you get back

• ✓Every decision has a permanent URL. Paste it into any AI when you need to revisit.
• ✓Concept index links decisions to the same source material — patterns in your own thinking become visible.
• ✓Teammates onboard themselves by reading the decisions log instead of asking you.
• ✓When you reverse a decision, the old doc stays — version history shows what changed and why.

Worked example

Try it with what's on your desk right now.

No signup. Drop in your first doc and the URL is yours.

Other shapes the URL takes