Skip to content

hpark0011/decision-engineering

v0.1.0MIT

Keep system intent explicit, authoritative, enforceable, traceable, and correctable with a Markdown decision ledger.

decision-engineering

Run Decision Engineering by locating, creating, changing, validating, and tracing a Markdown decision ledger whose decisions remain explicit, authoritative, enforceable, traceable, and correctable. Use when a requirement, feature, architecture change, bug, policy, or implementation choice needs to be routed to an existing decision or expressed as a new one; when logic ownership or domain boundaries are unclear; when reviewing for duplicated policy, ambiguous fact authority, missing enforcement, hidden decisions, or consumer re-derivation; and when reconciling intended decisions with code behavior.

Read SKILL.md at the source

Pinned to revision 6d6497589f09, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.