DRKM Blueprint System

Active

Decision Log

Architectural and governance decisions for the DRKM Blueprint System

Active·Owner: markus·2026-04-04

Recent Decisions

This page references the decision log stored in data/decisions.json. For details on each decision, see the data file.

Key Decisions by Category

Architecture Decisions

  • DR-001: Use Next.js App Router with static export
  • DR-003: Use MDX for content with YAML frontmatter
  • DR-004: Deploy to Cloudflare Pages via GitHub Actions
  • DR-005: Enforce Zod validation for all structured data

Design Decisions

  • DR-002: Adopt stone palette as primary color system
  • DR-006: Seven page templates, no custom templates

Process Decisions

  • DR-007: Corrected role assignments - Greg owns design/UX/brand

Decision Format

Each decision in the log includes:

  • ID: Unique identifier (DR-### for architectural/governance)
  • Title: Clear, one-sentence summary
  • Date: When decision was made
  • Status: active, superseded, or archived
  • Owner: Team member with authority in this domain
  • Context: Why this decision was needed (2+ sentences)
  • Decision: What was decided (2+ sentences)
  • Consequences: Expected outcomes and tradeoffs (2+ sentences)
  • Tags: Categories for grouping (architecture, design, process, etc.)
  • Linked Pages: Related documentation pages

Decision Making Framework

All decisions follow the same framework:

  • 1. Identify the problem - What needs deciding?
  • 2. Gather context - What factors matter?
  • 3. Generate options - What are the alternatives?
  • 4. Evaluate tradeoffs - What's the cost/benefit of each?
  • 5. Make decision - Owner decides based on their domain
  • 6. Communicate - Share decision and rationale with team
  • 7. Document - Record in decision log with full context
  • 8. Monitor - Track outcomes against expectations

How Decisions Evolve

Decisions are not permanent:

  • Active: Current decision, in effect
  • Superseded: Replaced by newer decision
  • Archived: No longer relevant

When a decision proves wrong or circumstances change, we create a new decision that supersedes the old one, preserving both in the log.

Accessing Full Decision Details

For the complete decision log with all fields, see data/decisions.json in the project repository.