Repository navigation
Write Cosyte with a capital C; correct the build270 note; drop the HIPAA-capable line - #71
Merged
Merged
Conversation
README.md, docs-content/intro.md, docs-content/concepts-archetype.md, docs-content/limitations.md and docs-content/guides-deid.md named "the cosyte parsers" in prose; each now writes Cosyte. The operator, in their own words: "Uppercased C on Cosyte everywhere. Fix any location that has it as lowercase" The launch-ready name search now gives its cli-subcommand exclusion a word boundary, so prose such as "cosyte parser" no longer passes as the cli binary. Identifiers are unchanged: the @cosyte scope, cosyte/<repo> paths, heading anchors and URLs. Claude-Session: https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9
README.md, docs-content/guides-x12.md, docs-content/limitations.md and documentation/agent-notes.md said @cosyte/x12 ships no build270. It does from 0.1.0 (exported by the published 0.1.0 and 0.1.1; absent from 0.0.18). synth 0.1.0 still generates no 270, so each now says that x12 ships build270 and synth does not generate a 270 yet. The CHANGELOG line below "Released before this file was generated" is history and is unchanged. docs-content/limitations.md opened a bullet with "HIPAA-capable, not HIPAA-compliant, and here that framing is nearly vacuous". That compliance wording is removed; the bullet now opens "No real PHI." and the rest is unchanged. Claude-Session: https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9
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
1 participant
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.
Write Cosyte with a capital C in the parser prose
README.md, docs-content/intro.md, docs-content/concepts-archetype.md, docs-content/limitations.md and docs-content/guides-deid.md named "the cosyte parsers" in prose; each now writes Cosyte.
The operator, in their own words: "Uppercased C on Cosyte everywhere. Fix any location that has it as lowercase"
The launch-ready name search now gives its cli-subcommand exclusion a word
boundary, so prose such as "cosyte parser" no longer passes as the cli
binary. Identifiers are unchanged: the @cosyte scope, cosyte/ paths,
heading anchors and URLs.
Correct the build270 note; drop the HIPAA-capable line
README.md, docs-content/guides-x12.md, docs-content/limitations.md and
documentation/agent-notes.md said @cosyte/x12 ships no build270. It does
from 0.1.0 (exported by the published 0.1.0 and 0.1.1; absent from 0.0.18).
synth 0.1.0 still generates no 270, so each now says that x12 ships
build270 and synth does not generate a 270 yet. The CHANGELOG line below
"Released before this file was generated" is history and is unchanged.
docs-content/limitations.md opened a bullet with "HIPAA-capable, not
HIPAA-compliant, and here that framing is nearly vacuous". That compliance
wording is removed; the bullet now opens "No real PHI." and the rest is
unchanged.
https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9