Repository navigation
0.0.1
·
112 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
Added
- The Rust CI tier, live now that the workspace exists (#15):
rustfmt,
clippywith-D warnings,cargo nextest, doctests,rustdoc, an MSRV
check throughcargo-hack, andcargo deny, all under the one required
conclusioncheck, with SonarQube importing Rust coverage from an
instrumented run. - The Cargo workspace (#11): the eight crates of
docs/architecture.md§11,
the workspace lint table from.claude/rules/reliability.mdwith
unsafe_codeforbidden, a release profile that keepspanic = "unwind"and
overflow-checks, and a separatewasm-releaseprofile for the renderer.
deny.toml's licence exceptions now name the real crates, including the
three pinned openEHR crates that are BUSL-1.1. - How a coded field gets its codes, decided against measured evidence (#6):
97.6% of the 843 coded fields in 102 operational templates take their
membership from the template, an enumerated external code carries no rubric
there, and one code path serves every binding kind by resolving locally and
asking a terminology server only for what is missing. Archetype value sets
are emitted as FHIRCodeSystem,ValueSetandConceptMapunder a minted
URL, because no openEHR specification defines one. - The overlay key, decided against measured evidence (#8): a step chain
carrying the RM attribute, thenode_id, the archetype id, the RM type and
the pinned name, with a sibling ordinal only where those tie. Walking 102
operational templates showed an id-only path collides in 14 of them, and
that the pinned name is the only discriminator for 41% of the 427 colliding
sibling groups, which reversed the earlier decision to keep the name out of
the key. - The design of record,
docs/architecture.md(#1): the version pins, both
template generations normalized into one internal constraint model, the
field derivation table from the Reference Model and its constraints, the
layout overlay with its key normalization and its replay report, the
terminology split between local and network resolution, the ITS-REST client
rules, the workspace layout, the build order, and a decision register.
Every decision carries a citation or an explicit note that no specification
governs it. - The specification and model-crate pins in
docs/VERSIONS.md, which now
carry values instead ofpending #1, andscripts/checks/versions.shalso
checksopenehr-amandopenehr-adl(#9). - The brand: the mark, the "Rose & Iron" palette, and the lockup, favicon and
social-card set (#3). Rose was chosen by measuring worst-case CIEDE2000
distance from the other three product hues under normal, deuteranope and
protanope vision, andassets/brand/README.mdrecords the ratio for every
token against both grounds. - The repository: the working discipline in
.claude/(rules, hooks, skills,
agents, memory), the community and governance documents, the pinned version
matrix indocs/VERSIONS.md, the committed guards underscripts/checks/,
the tracker helpers underscripts/gh/, and five workflows that work on a
repository with no code (CI, CodeQL, Scorecard, SonarQube Cloud, Release).
The configuration is FerroBRIDGE's, adapted from the FHIR and OMOP oracles to
the openEHR Reference Model, the Archetype Object Model, ITS-REST, and AQL.