Repository navigation
docs: scope the tagline and fail-safe wording - #59
Merged
Merged
Conversation
- README tagline: "IG-grounded, fail-safe, value-free diagnostics; never a confident wrong FHIR value" becomes "IG-grounded, with value-free diagnostics". - README: the per-segment issue sentence ends at "raises one value-free issue naming it:". - intro: the opening ends at "without hand-writing a ConceptMap"; "The fail-safe promise" becomes "The fail-safe rule", and the rule's list stays as written. - concepts: "the library's whole promise is: never emit a confident wrong FHIR value" becomes "the converters refuse to guess"; the segment-coverage sentence ends at "did reach the bundle". - troubleshooting: a missing element "can" come with a diagnostic. Checked on the published 0.1.0 from a clean install: the four ambiguities the fail-safe rule lists each raise their typed, value-free code. Claude-Session: https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9
NSchatz
changed the title
NSchatz
force-pushed
the
docs/claims-0-1-0-holds
branch
from
October 7, 2026 22:41
73ae0d2 to
091e631
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scopes the README tagline and a few docs-content sentences to the rules the package states. Checked on the published
@cosyte/transform0.1.0 (with@cosyte/hl7and@cosyte/fhir0.1.0) from a clean install outside any repository, on synthetic messages: the four ambiguities the fail-safe rule lists (a timestamp with no timezone, an unresolvable assigning authority, an unrecognized coding system, a non-UCUM unit) each raise their typed, value-free code, and the per-segmentTRANSFORM_SEGMENT_NOT_EMITTED/TRANSFORM_SEGMENT_NO_IG_MAPissues fire as the README says.No runnable block, and none of the phrases
readme-claim.test.tsorsegment-completeness.test.tsrequire, is touched.prettier --check README.mdpasses. The package.jsondescriptionchanges only with a release.https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9