55. Corrective operational profiles, release bundles, migration, and agent discovery

Version 1.4 is a bounded correctness release. It keeps rtracer.record-core/1.3 canonical bytes and digests unchanged while versioning broken proof, receipt, ledger, event, projection, cursor, control, and action-dispatch profiles independently. Exact v1.4 operational profiles supersede conflicting illustrative shapes in earlier sections and Appendix D.

#55.1 Profile precedence

The exact profiles are rtracer.proof-target/1.4, rtracer.ingest-receipt/1.4, rtracer.canonical-event/1.4, rtracer.ledger-checkpoint/1.4, rtracer.projection-checkpoint/1.4, rtracer.cursor/1.4, rtracer.authority-lease/1.4, rtracer.control-command/1.4, rtracer.command-disposition/1.4, and rtracer.action-dispatch/1.4. Implementations MUST NOT combine fields or digest rules from different profile versions.

#55.2 Immutable release identity

The human edition is 1.4, the exact release is 1.4.0, and the documentation schema is 2.0.0. Exact release routes are immutable and canonical. Mutable discovery aliases identify themselves as aliases and expose the exact target. Accepted v1.3 bytes remain preserved and addressable.

#55.3 Stable identities and semantic digests

Sections, headings, requirements, recipes, fixtures, schemas, and migrations use registered stable identifiers that are never recycled. A semantic digest covers schema version, stable ID, title, normative status, and blocks under the declared canonical JSON profile. Artifact SHA-256 covers exact published bytes. Release time and local build paths are excluded from semantic identity.

#55.4 Migration classes

Every prior stable ID is classified exactly once as unchanged, modified, renamed, moved, split, merged, deprecated, or removed. Added IDs are listed separately. Changed content cannot be called unchanged. The migration record includes old/new titles and URLs, semantic digests, compatibility impact, replacements, affected fixtures, and explanation.

#55.5 Human and agent entrypoints

Humans enter through the living /substrate/ landing page or an exact release route. Agents first resolve /substrate/versions.json, then the exact release manifest, section JSON/Markdown, schema, migration, and fixture artifacts. Agents cite stable ID, release version, semantic digest, and canonical exact URL. Scraping presentation HTML is a fallback, not the contract.

#55.6 Release gates and two-implementation proof

A release is accepted only after deterministic double build, artifact hash verification, schema validation, fixture uniqueness and execution, legacy-byte preservation, cross-release migration coverage, full-text search tests, exact canonical routes, accessibility checks, and two independent implementations reproducing normative golden bytes and state results. A prose-only fixture list does not satisfy executable conformance.