Skip to content

Rewrite the org profile for the Cosyte 0.1 launch - #71

Merged
NSchatz merged 1 commit into
mainfrom
profile-readme-launch
Oct 7, 2026
Merged

NSchatz merged 1 commit into
mainfrom
profile-readme-launch

Conversation

@NSchatz

@NSchatz NSchatz commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

What & why

Rewrites profile/README.md, the page GitHub renders on github.com/cosyte, for the 0.1 launch:

  • what we build, in company voice, and that fourteen libraries are on npm at 0.1, the first release line whose public API we treat as settled
  • the install line, npm install @cosyte/hl7, and that each library installs on its own
  • the fourteen libraries, one line each, with npm, docs quickstart and repository links
  • Start here: docs, examples, Discussions (with the 0.1 announcement) and cosyte.com, then the quiet "Need it integrated? Talk to us"

Sources. Each library line comes from its README and its npm metadata at 0.1.0 (npm view @cosyte/<pkg>@0.1.0 description license engines dependencies). All fourteen are MIT; thirteen declare node >=22.0.0 and @cosyte/cli declares >=22.0.0 <26.0.0, which is what the Node line says.

Known defects. Every line was read against "Findings owed after launch" in the launch status. Removed or narrowed: the "How we build them" section (its "spec-clean on emit" and "no confident wrong values" are contradicted today), deid's "failing closed", transform's "following the implementation guide" (now: mappings taken from it), and x12 now says parse rather than build. No compliance claim: deid names its default policy, HIPAA Safe Harbor, as its own README does.

UTM. Every cosyte.com and docs.cosyte.com link carries utm_source=github&utm_medium=profile&utm_campaign=cosyte-0-1-launch&utm_content=profile. The two logo image URLs are images, not links, and stay as they are.

Checked. All 15 docs links, both site links and all 16 GitHub links answer 200 (the npm pages answer 403 to a script, as npm does; each package resolves with npm view). npm install @cosyte/hl7 in a fresh directory exits 0 and installs 0.1.0. The hl7 code sample is gone: the brief asks for the install line, and every line shown is one we ran.

Checklist

  • Only profile/README.md changes. No workflow, script or test is touched.
  • node --test "test/*.test.mjs": 1019 tests, 1019 pass.
  • node scripts/check-no-emdash.mjs passes locally.
  • No PHI anywhere in the diff.
  • One logical change per PR.

https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9

The page GitHub renders on github.com/cosyte now says what the fourteen
libraries are, one line each, with the install line and the links a
visitor needs: npm, docs and repository per library, then docs, examples,
Discussions (with the 0.1 announcement) and cosyte.com.

Every line is taken from the library's README and its npm metadata at
0.1.0, and checked against the findings owed after launch: no line claims
behaviour a known defect contradicts, and the "How we build them" section
is gone because two of its claims (spec-clean on emit, no confident wrong
values) are contradicted today. No compliance claim.

Every cosyte.com and docs.cosyte.com link carries utm_source=github,
utm_medium=profile, utm_campaign=cosyte-0-1-launch and utm_content=profile.
The hl7 code sample is replaced by the install line alone.

Claude-Session: https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9
@NSchatz
NSchatz merged commit 7ca8149 into main Oct 7, 2026
8 checks passed
@NSchatz
NSchatz deleted the profile-readme-launch branch October 7, 2026 18:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant