Functional Requirements

| ID | Requirement | Acceptance Criteria | Priority | Owner | |---|---|---|---|---| | REQ-001 | Deterministic scaffold generation | Given same input, Markus produces identical output every time | Critical | rafa | | REQ-002 | Seven page templates | System supports overview, narrative, reference, data-index, status, decision-log, changelog templates | Critical | greg | | REQ-003 | MDX content management | All page content stored as MDX with YAML frontmatter, gray-matter parsing works correctly | Critical | rafa | | REQ-004 | Zod schema validation | All structured data validates against schemas, build fails if validation fails | Critical | rafa | | REQ-005 | Navigation generation | Navigation tree generated automatically from content frontmatter, no manual nav config required | High | rafa | | REQ-006 | Status vocabulary enforcement | Only active, forming, draft statuses allowed; invalid statuses cause build failure | High | rafa | | REQ-007 | Changelog automation | Entries added automatically with timestamp, contributor, change type, and description | High | markus | | REQ-008 | Template binding | Pages automatically bind to correct template based on frontmatter, no manual binding | High | rafa | | REQ-009 | Search functionality | Full-text search across all content pages with filters by section and status | Medium | rafa | | REQ-010 | Mobile responsiveness | All pages render correctly on mobile, tablet, and desktop viewports | High | greg | | REQ-011 | Metadata generation | SEO metadata (title, description, og tags) generated from frontmatter automatically | Medium | rafa | | REQ-012 | Link validation | All internal links validated at build time, broken links cause failure | Medium | rafa |

Content Requirements

• Every page must have required frontmatter fields: title, slug, section, template, status, owner, lastUpdated, description, order
• Section names must be consistent across all projects (overview, vision, requirements, architecture, design, operations, governance, roadmap, changelog)
• Order field determines page sequence within sections
• Slug must be unique within the project
• Owner must be a valid team member

Data Requirements

• JSON data files validate against Zod schemas
• All array data includes required fields per entity type
• Dates in ISO 8601 format (YYYY-MM-DD)
• Tag arrays support flexible tagging systems
• Linked references between entities are consistent