# ADR 0007 — GitHub Actions + ARC Day-One CI

**Status:** Accepted

## Context

AWP must own CI progression/observability without rebuilding a CI executor. The project already targets K3s for execution.

## Decision

Use GitHub Actions as the initial CI provider and Actions Runner Controller on K3s for ephemeral runners. AWP owns `CIExecution`, results/evidence correlation, required-check policy and progression; GitHub owns workflow/job mechanics; ARC owns runner registration/scaling/pod lifecycle.

## Consequences

Project workflows stay project-owned. Runners are trust-tiered, ephemeral and unprivileged by default. Full CI planning/VerificationAuthority activates in I5; I1 only consumes focused evidence and actual required checks for MergeGate.

## Rejected Alternatives

- ARC treated as CI engine;
- custom CI executor;
- privileged static runners;
- workspace checks treated as complete CI authority.

## Increment Realization

I0 runner/provider substrate, I1 merge evidence, I5 full CI control plane.