Architecture Decision Records

Each record captures the context, decision, and consequences of one design choice in the fork management system. They are grouped by the question they answer.

Catalog

Numbers 017, 032, and 034 were retired and are intentionally unused.

Foundation & Core Architecture

"What are the fundamental design choices?"

Foundation decisions that define the system's structure and approach:

Repository Initialization & Setup

"How do I create and configure a new fork?"

Decisions governing repository initialization, configuration, and security setup:

Upstream Synchronization & Integration

"How do I keep my fork in sync with upstream?"

Decisions for synchronizing with upstream repositories and integrating changes:

State Management & Tracking

"How do I track progress and workflow state?"

Decisions for managing workflow state and tracking lifecycle:

Build, Test & Dependencies

"How do I build, test, and maintain dependencies?"

Build architecture, dependency management, and documentation:

CI/CD & Deployment

"How do services get built and published per PR?"

Decisions for the container image build, the image registry, the acceptance-test contract, and the deploy lane designed in Borrow, Prove, Restore:

Release Management

"How do releases get created and published?"

Version management and release automation:

Template Maintenance & Evolution

"How do fork repositories stay updated with template improvements?"

Decisions for propagating template updates to fork repositories:

Workflow Infrastructure & Patterns

"What are the reusable building blocks?"

Technical patterns and infrastructure for workflow implementation:

Lessons drawn from these decisions are collected in Learnings.