# GEARA 0.1 Release Closure (A15)

GEARA-A15 closes the planned GEARA 0.1 executable-artifact programme as **GEARA-0.1-RC1**, an **Executable Release Candidate**.

## Artifacts

- `manifest.json` — frozen release-subject inventory, stage map, candidate metrics, required gates, known limitations, and promotion policy.
- `SHA256SUMS` — SHA-256 inventory for the frozen A1-A14 release subject plus A15 support files.
- `RELEASE-NOTES.md` — candidate scope, stage summary, gate expectations, known limitations, and authority boundary.
- `run_release_closure.py` — deterministic release-candidate closure gate.
- `release-closure-report.json` — canonical A15 closure evidence.
- `requirements-release.txt` — Python dependencies required by the closure gate and the live A12 machine-test gate it executes.

## Run

From the repository root:

```bash
python static/specs/geara/0.1/release/run_release_closure.py
```

Write a deterministic report:

```bash
python static/specs/geara/0.1/release/run_release_closure.py \
  --json-report static/specs/geara/0.1/release/release-closure-report.json
```

Exit codes:

- `0` — all release-candidate closure checks passed.
- `6` — one or more closure checks failed.
- `2` — setup/runtime error.

## Gate model

A15 verifies the complete frozen A1-A14 release subject and A15 support files, checks architecture/conformance boundary metrics, reruns A12 twice to require the established 70/70 outcome and deterministic JSON reporting, verifies the canonical A13 84/84 reconciliation evidence, verifies the canonical A14 33/33 regression evidence, and verifies the A14 protected 102-file baseline against the current package.

The GEARA-A14 runner contains intentionally stage-coupled specification assertions for the A14 document state. A15 therefore preserves and verifies A14's canonical evidence and protected baseline rather than treating legitimate A15 specification advancement as regression drift.

## Promotion boundary

A15 PASS closes **GEARA-0.1-RC1** only. It does not:

- replace Architecture Assessment or Hybrid judgement;
- establish complete GEARA conformance for an arbitrary architecture;
- waive deviations or confer governance/regulatory approval;
- establish GEARM, BPS, AIPS, GEDRA, Data Product, or other external-specification conformance;
- automatically promote RC1 to final `Released` status.

Final release promotion requires a separate governed publication decision.