[elasticdotventures]

The semantic-graph layer (iso_ir → ontology → sysml_model/view) landed on main via #20/#21/#22 but was never tagged — v0.12.0/v0.13.0/v0.14.0 sat as - pending tag in the CHANGELOG, so kr0ki and m0ltis have no clean pin. This dates them for a consolidated v0.14.0 tag and documents what "release" means for a pre-1.0 crate.

Changes (docs only, no code)

• CHANGELOG.md — date the three pending headings (2026-09-07); fix v0.11.0's stale pending tag (the tag exists, 2026-08-30); add a versioning preamble.
• README.md
  • new § "Versioning & stability" — 0.x carries no SemVer guarantee; a 0.MINOR bump MAY reverse capability; "additive, non-breaking" in the CHANGELOG is intent, not a contract, until 1.0.0. Pin exact (="=0.14.0") or by git tag. The strict canonical FromStr is the stable surface; UfoRelation::from_synonym may be re-tuned between 0.MINORs. Non-numeric IDs are a hard invariant.
  • new § "Downstream consumers" — table of projects cleared to depend on it directly, with crates / modules used / pin guidance: b00t, ledgrrr, kr0ki, m0ltis (planned), critter-keeper, cim-gridy mission-engine.
  • refreshed the module bullet list to include the semantic-graph layer (was stale vs lib.rs).
• AGENTS.md (new) — module map with the graph layering, hard invariants (non-numeric ids, no wall-clock, strict-FromStr-is-stable, keep sysml optional), the pre-1.0 release procedure, build/check commands, downstream pins.

1.0.0 is gated on a production downstream consumer of the semantic-graph layer (kr0ki's model-ingestion path).

After merge

git tag -a v0.12.0 -m "ufo-types v0.12.0" <sha of #20>   # optional, for history
git tag -a v0.13.0 -m "ufo-types v0.13.0" <sha of #21>   # optional, for history
git tag -a v0.14.0 -m "ufo-types v0.14.0" main
git push origin v0.14.0
gh release create v0.14.0 --title "v0.14.0 — semantic-graph layer" --notes-file <CHANGELOG excerpt>

cargo publish is a separate, per-release call — git-tag consumers do not need it.

🤖 Generated with Claude Code