# Sovereign Evolution 3 — CI status

**Hosted CI: NOT ACTIVE, NEVER RUN.** `git remote -v` is empty, so no CI provider has seen this repository. Every
result below is labelled LOCAL.

## Configuration (repository side, done)

- Platform targeted: **GitHub Actions** (`.github/workflows/ci.yml`; `actions/checkout@v4`, `actions/setup-python@v5`).
- Job `authorization-regression-gate`:
  - installs `scripts/ci/requirements-authorization.txt` (a pip-resolved lock; `pip check` clean);
  - builds `cain-native-enforcer` with `cargo build --release --locked`;
  - runs `run_authorization_suite.py --self-test` and then the suite;
  - uploads `authorization-suite.json`.
- The runner fails on:
  - any failed test;
  - any skipped required test;
  - any of the 26 required files missing or collecting nothing;
  - a write to the production-ledger canaries.

  `live_host` tests are deselected and counted.
- Branch triggers: `push`/`pull_request` on `main`/`master`. The work branch `ironclad-prompt8-qualification` would
  run only via a PR into `main`, or if the trigger list is widened.

## LOCAL evidence

| Run | Revision | Exit | Result |
|---|---|---|---|
| LOCAL runner, shared tree | HEAD after d190f159 | 0 | 275+11 passed, 0 skipped, canaries unchanged |
| LOCAL clean checkout (fresh worktree + fresh venv + lock + `cargo build --locked`) | bfe0637e | 0 | 275 passed, 0 skipped, self-test OK |

## What the owner must do to activate hosted CI (nothing here was invented or attempted)

1. Choose the host and repository, for example a **private** GitHub repository. Private matters because the
   code-stays-secret directive applies to the source itself.
2. `git remote add origin <URL>` and push the branch. This publishes the full source and history to that host,
   including the withdrawn kit 8.3.0 ZIP committed in 4dd79e48. That is the owner's call.
3. Enable Actions for the repository. Optionally add `ironclad-prompt8-qualification` to the workflow's branch
   triggers.
4. Make the job a required status check on `main`.
5. Send the first run's URL/ID and commit SHA to a session. It records them here and flips the release gate's CI
   dimension only if that run passed.

Alternative without a hosted provider: an approved local runner (systemd timer) that runs the same command and
publishes the JSON. That would be "scheduled local CI", and would be labelled that way, not "hosted CI".
