Migration note: Migrated from ADR-0022 on 2026-05-02 per ADR-0047. Original file retained at docs/adr/0022-ado-project-consolidation-and-board-structure.md with deprecation banner.

GOV-0002: ADO Project Consolidation and Board Structure¶

Sources¶

ADR-0022: ADO Project Consolidation and Board Structure (2026-04-04)

Field	Value
ID	GOV-0002
Date	2026-04-04
Status	Accepted
Deciders	Ben Peries
Class	security/GOV

Context¶

The Archon Platform was initially scaffolded across 4 separate ADO projects (archon-platform, archon-apps, archon-cloud, archon-pipelines). No ADR documented this decision — it was a default scaffold choice with no deliberate rationale. All work items created to date (WI #1-42) already land in the archon-platform project regardless of domain. The separation added cross-project friction with zero benefit at current scale.

Decision¶

Consolidate all repos under the single ADO project archon-platform. Separate concerns using 4 Area Paths instead of 4 projects:

Area Path	Repo	Scope
Platform	archon-platform	Ansible, Terraform, k3s, infra
Apps	archon-apps	IT and OT application workloads
Cloud	archon-cloud	Azure, GCP, AWS, Cloudflare IaC
Pipelines	archon-pipelines	Shared pipeline templates

IT/OT separation within the Apps area is enforced via tags (IT, OT) on work items, mirroring the folder-level separation already enforced in archon-apps (it/ vs ot/).

Sprints are bi-weekly starting 2026-03-31, matching project inception date.

Consequences¶

One board per domain area, one backlog, one wiki, one ADR sequence
Cross-repo work items link cleanly within a single project
Repo migration from separate ADO projects to archon-platform project is a one-time manual operation (ADO UI only — no CLI support)
archon-docs remains the sole source of truth for all documentation
Cloudflare IaC will live in archon-cloud/cloudflare/ when implemented

Note on Agile Framework and Board Discipline¶

This ADR established the ADO board as the work tracking system using Scrum conventions (sprints, Product Backlog Items, area paths). It is acknowledged that Scrum was designed for human teams with sprint ceremonies and velocity tracking. Its overhead model may not be optimal for a single-operator platform evolving toward agentic AI operations.

The board-as-single-source-of-truth decision holds regardless of which Agile framework is in use. If the Scrum implementation evolves in a future ADR, the board discipline remains the correct pattern. GOV-0003 formalizes enforcement of this principle.

GOV-0003: ADO board single source of truth and WI-first branching policy (extends this ADR)