# GEARM 0.1 Cross-Artifact Reconciliation — GEARM-A13

GEARM-A13 validates consistency across the established GEARM 0.1 machine-readable artifact stack and its normative human-readable source.

The reconciliation scope spans:

- **A1** Concept Registry
- **A2** Relationship Registry
- **A3** Semantic Invariant Catalogue
- **A4** RDF / OWL representation
- **A5** JSON-LD context
- **A6** SHACL constraints
- **A7** Structural JSON / JSON-LD Schema
- **A8** Profile Schema
- **A9** canonical examples
- **A10/A11** positive and negative testcase inventory
- **A12** automated conformance runner
- the normative `gearm-0.1-specification.md`

A reconciliation `PASS` means the checked artifacts are mutually consistent according to the A13 checks. It does **not** replace semantic assessment and does not by itself establish complete GEARM conformance.

## Run

From `static/specs/gearm/0.1/`:

```bash
python reconciliation/run_reconciliation.py
```

Write a deterministic JSON report:

```bash
python reconciliation/run_reconciliation.py \
  --json-report reconciliation/reconciliation-report.json
```

Quiet mode is useful in CI:

```bash
python reconciliation/run_reconciliation.py \
  --quiet \
  --json-report reconciliation/reconciliation-report.json
```

## Exit status

- `0` — all reconciliation checks passed
- `2` — dependency, package, parsing, or runtime failure
- `4` — one or more cross-artifact reconciliation defects were found

## Reconciliation policy

A13 checks identities, counts, references, namespace alignment, semantic-source parity, RDF/OWL representation, SHACL coverage, JSON/JSON-LD schema enumeration, Profile derivation, example validity, testcase integrity, A12 regression execution, and documentation references.

A13 is deliberately fail-closed. A mismatch is treated as an artifact defect to be reconciled rather than as permission for a downstream artifact to redefine the human-readable GEARM semantics.

## A13 reconciliation correction

During initial A13 execution, the A3 `machineConstraintStatus` metadata still reflected its pre-A6 creation state (`not-yet-implemented`) even though A6 had subsequently established executable/assessment coverage for all 180 invariants. A13 reconciled this metadata without changing any invariant statement or semantic meaning:

- `partial-executable` — 85 invariants with an A6 executable portion;
- `assessment-required` — 35 Hybrid invariants with no safe A6 executable reduction;
- `assessment-only` — 60 Semantic-Assessment invariants.

The corresponding A4 invariant metadata was updated in lockstep so A3 and A4 remain mutually consistent. This is a machine-artifact metadata correction, not a normative semantic change.

## Current baseline

The packaged A13 report contains **51 checks** with **51 PASS**, **0 warnings**, and **0 failures**. A13 also invokes the A12 46-case suite and requires its machine regression to remain `PASS` with zero expectation mismatches.