Skip to content

Decision Memory System (DMS)⚓︎

A place where thinking lives long enough to teach us something.

DMS is a specialized environment designed for capturing and learning from our thinking. It bridges the gap between making a choice and gaining wisdom.

Philosophy: Clarity Before Code

This repository is the Source of Truth for the DMS project. It defines the "Soul" of the system—its language, behavior, and purpose—before a single line of application code is written.

Quick Start⚓︎

If you are new here, follow this path to understand the system:
1. Understand 2. Explore 3. Design
Overview Domain Model Architecture
Why we built this and what it solves. The language of Topics and Choices. How the system is built.

Explore the Documentation⚓︎

The core pillars of the DMS philosophy and design.

  • Overview — The simplest way to understand DMS.
  • Vision — Our long-term intent and real-world scenarios.
  • Behavior — How a Topic moves from a question to a lesson.
  • Collaboration — How humans work together and handle disagreement.

Everything related to roles, security, and privacy.

  • Roles — Who is who? (Owners, Advisors, Reviewers).
  • Permissions — What can each role actually do?
  • Visibility — How we protect sensitive thinking and privacy.

For developers and stakeholders looking at the engine and the roadmap.

Why Use DMS?⚓︎

We don't lack intelligence; we lack a memory of our own thinking.

Stop repeating mistakes by looking back at why you made them.
Onboard new members by letting them see years of trade-offs in minutes.
Build Confidence by tracking your "Expected vs. Actual" outcomes.

The Bottom Line

DMS is the bridge between making a choice and gaining wisdom.