CircleCI has been red on master for months, and it is an external CI the sovereign standard does not use

[noahgift]

Found while adding the gate context this repo needs to satisfy the org ruleset (#25, merged).

Two separate things

1. The repo was unmergeable. The org ruleset Green Main requires a status context named gate, and no workflow here emitted one. Every PR sat at mergeStateStatus: BLOCKED with nothing failing and nothing a contributor could fix. Closed by #25.

2. CircleCI is red, and has been for a long time. Independent of the above:

$ gh api repos/paiml/python_devops_book/commits/master/status --jq .state
failure

The last five commits on master are all failure on ci/circleci: build. Latest: https://circleci.com/gh/paiml/python_devops_book/426

Why this is worth more than a re-run

paiml/infra's CLAUDE.md now states the standard: sovereign tooling only — automation is forjar, CI runs on the fleet, and external services are outside the stack. A permanently-red external check is the worst of both worlds: it gates nothing, it teaches everyone to ignore a red, and nobody owns fixing it.

Two honest options:

• Migrate to the org standard. The gate job added in ci: emit the gate status check this repo is required to produce #25 already runs on the fleet. Whatever CircleCI checks should move into it, where it is visible alongside every other repo.
• Retire the CircleCI config if what it checks is already covered — rather than leaving a red that means nothing.

What should not happen is leaving it red. A check nobody acts on trains people to skip the reds that matter.