Skip to main content

ADR-0000: Establish a2c-workflow as the canonical A2C repository

  • Status: Accepted
  • Date: 2026-06-11
  • Deciders: Michel Gillet

Context​

A2C (Architecture-to-Commit) requires a single authoritative repository where the workflow method is defined, versioned, and maintained. Without an explicit foundational decision, a2c-workflow could be treated like a downstream project that "adopts" A2C — which inverts the relationship between workflow definition and workflow consumption.

Decision​

Establish a2c-workflow as the canonical A2C workflow repository.

This repository:

  • defines the A2C method (docs, rules, templates, prompts, plans, profiles)
  • is versioned as the workflow product (see VERSION)
  • is validated through reference projects that adopt A2C as their governing workflow
  • is not a downstream consumer that adopts A2C from elsewhere

Downstream A2C-based projects record their own ADR-0000 to adopt a specific A2C version. That adoption pattern applies to consumer repositories only — not to a2c-workflow itself.

Consequences​

Positive​

  • Clear separation between workflow definition and workflow adoption
  • Foundational scope of this repository is explicit in architectural history
  • Downstream ADR-0000 convention remains unambiguous for consumer projects

Negative​

  • Contributors must remember two distinct ADR-0000 meanings (definition repo vs consumer repo)

References​