ADR-0001 — Establish the Bluefly Engineering Governance repository

• Status: Superseded
• Date: 2026-06-29

Superseded by the accepted GitLab-backed BluCity-Docs authority and the repository/workspace location contract in ADR-0006. This record is historical and non-executable.

Context

Governance artifacts (Authority Corpus, Relationship Graph, Operating Model, Decisions, Standards, Evidence) were being produced in a Claude job's tmp/ directory and in Claude's private memory. That makes them invisible to other runtimes (Codex, Gemini, OpenClaw), to other engineers, to CI, and to a fresh workstation. Output trapped in one agent's ephemeral state is not governance.

Decision

Create a dedicated, version-controlled bluefly-governance repository as the single canonical home for engineering governance, with one responsibility per directory: - authorities/ — immutable upstream evidence (verbatim quote + URL) - relationships/ — evolution / supersession / conflict graph between authority entries - operating-models/ — Bluefly interpretations + decisions, each citing authority_ids[] - decisions/ — ADRs (reviewed, accepted, versioned) - standards/ — agent-behavior standards - evidence/ — investigations, runtime receipts - schemas/, agents/

The traceability chain is: Upstream Docs → Authority Corpus → Relationship Graph → Operating Model → Decision Record → Runtime Verification.

Rule

An agent's output is not governance until merged into the canonical GitLab repository via review. Temporary work belongs only under Scratch/; model memory is never an artifact authority.

Consequences

• Every human and agent reads the same corpus from Git.
• Changes are reviewable (PR), traceable (history), and reproducible (clone).
• Current authority: GitLab project blueflyio/blu/blucity-docs; registered Mac worktrees are backed by /Volumes/AgentPlatform/Applications/.