DRKM Blueprint System

Active

Requirements Overview

Overview of functional and non-functional requirements for the blueprint system

Active·Owner: greg·2026-04-04

System Requirements

The DRKM Blueprint System must meet three classes of requirements: functional (what it does), non-functional (how well it does it), and architectural (how it's built).

Functional Requirements

The system must:

  • Generate deterministic scaffolds from specifications without variation
  • Support seven page templates — overview, narrative, reference, data-index, status, decision-log, changelog
  • Manage MDX content with YAML frontmatter for all pages
  • Validate all content against Zod schemas before publishing
  • Generate navigation automatically from content frontmatter
  • Enforce status vocabulary (active, forming, draft) consistently
  • Maintain changelog automatically with contributor and change type tracking

Non-Functional Requirements

  • Performance: Static export produces pages loading under 2 seconds
  • Accessibility: WCAG Level AA compliance minimum
  • Browser support: All modern browsers (Chrome, Firefox, Safari, Edge)
  • Mobile: Fully functional on all device sizes
  • Build time: Complete build cycle under 60 seconds

Architecture Requirements

  • Built on Next.js 14+ with App Router
  • Static export for deployment to Cloudflare Pages
  • TypeScript for type safety across the codebase
  • Zod for schema validation and runtime type checking
  • MDX for content with gray-matter for frontmatter parsing
  • Tailwind CSS for styling with utility-first approach
  • shadcn/ui for component primitives and patterns

Deployment Requirements

  • Automated deployment to Cloudflare Pages via GitHub Actions
  • Zero-downtime deployments
  • Rollback capability via git revert
  • CI validation before deployment
  • Production and development environments

Data Requirements

  • Content stored as MDX files with YAML frontmatter
  • Structured data stored as JSON files
  • All data conforms to defined schemas
  • No database required for standard deployments