From 9be948c17a5b0876581d00fd296c687e6fea3b71 Mon Sep 17 00:00:00 2001 From: Noah Schatz Date: Wed, 7 Oct 2026 18:07:41 +0000 Subject: [PATCH] docs: capitalize Cosyte in prose Apply the brand name rule: every prose reference to the company name reads "Cosyte" with a capital C. Identifiers are unchanged, including docs.cosyte.com and the @cosyte/fhir npm scope. Claude-Session: https://claude.ai/code/session_011dC8vE9axM3hqC8rNEX3W9 --- CHANGELOG.md | 8 ++++---- CONTRIBUTING.md | 2 +- documentation/agent-notes.md | 2 +- .../decisions/0002-fhirpath-dependency-posture.md | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 748b834..a57f5db 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -102,7 +102,7 @@ of XML, unit conversion, and executing a transaction Bundle. and a short PHI and safety section, and points to docs.cosyte.com/fhir; the full capability readout moved unchanged to `documentation/capabilities.md`. - **The installation page's clone command uses `https://github.com/cosyte/fhir`, without the `.git` - suffix.** docs.cosyte.com checks every link into a cosyte repository against the repositories its + suffix.** docs.cosyte.com checks every link into a Cosyte repository against the repositories its manifest marks public, and its matcher reads `https://github.com/cosyte/fhir.git` as a repository named `fhir.git` that the manifest does not list, which fails the site's publish run once fhir is enabled there (seen by building the site with this `docs-content/` staged). `git clone` accepts @@ -2030,7 +2030,7 @@ of XML, unit conversion, and executing a transaction Bundle. in an ``. The ``, the ``, the alt text and both image URLs are unchanged, and both URLs were re-checked on the wire before this landed (`200 image/png`). **What the anchor does differs by surface, and it was measured rather than assumed**, because the - other cosyte READMEs are expected to follow this markup. **On GitHub the anchor works and the theme + other Cosyte READMEs are expected to follow this markup. **On GitHub the anchor works and the theme switch keeps working**: GitHub's markdown API under `mode: gfm` (with or without a repository `context`; the mode is the discriminator, the context is not), handed this exact block, returns the `` intact with the `` still a direct child of ``, so @@ -2981,7 +2981,7 @@ true`, 0 `valid true -> false`, 0 `safeToSummarize false -> true`, 0 retractions ### Added -- **Em-dash CI gate (EMDASH-CONFORMANCE, part 1).** The cosyte brand rule bans `U+2014` outright +- **Em-dash CI gate (EMDASH-CONFORMANCE, part 1).** The Cosyte brand rule bans `U+2014` outright (founder directive 2026-07-24; knowledgebase `06-brand/voice-and-tone.md`), and names commit messages explicitly. It was enforced in CI in only three repos of ten; this repo was clean but ungated, so nothing stopped it regressing. Ported `knowledgebase`'s scanner @@ -3472,7 +3472,7 @@ terminology, bindings })` supplies a service and/or extra bindings (mirroring Ph profile / invariant **validation** (P2, P5–P7): Phase 1 parses and preserves, it does not validate; XML (P8); Bundle/reference **resolution** and Bulk NDJSON (P9); typed per-resource models and schema-driven `integer64` typing. -- **Repository bootstrap (P0).** Scaffolded `@cosyte/fhir` from the shared cosyte engineering +- **Repository bootstrap (P0).** Scaffolded `@cosyte/fhir` from the shared Cosyte engineering standard, mirroring the `hl7` reference layout: dual ESM + CJS + `.d.ts` build via `tsup` (`@cosyte/tsup-config`), ESLint 10 (`@cosyte/eslint-config`), Vitest 4 with v8 coverage (`@cosyte/vitest-config`), TypeScript 5.9 (`@cosyte/tsconfig`), Prettier diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 7aacaa3..1254d7b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -30,7 +30,7 @@ Before filing, please: discussion. 5. Write a descriptive commit message. Imperative mood (`feat(codec): ...`, `fix(model): ...`) is encouraged but not enforced. -6. **No em dashes (`U+2014`), anywhere.** The cosyte brand rule bans the character outright, and it +6. **No em dashes (`U+2014`), anywhere.** The Cosyte brand rule bans the character outright, and it names commit messages explicitly, so the ban covers tracked files, the PR title, the PR body, and every commit on the branch. CI enforces all four (`.github/workflows/no-emdash.yml`), and you can run the file half locally with `bash scripts/check-no-emdash.sh`. The fix is to rewrite with a diff --git a/documentation/agent-notes.md b/documentation/agent-notes.md index 0b075d6..69dd18f 100644 --- a/documentation/agent-notes.md +++ b/documentation/agent-notes.md @@ -2310,7 +2310,7 @@ the positive control's shape: The `` lockup at the top of `README.md` is now wrapped in ``. The block inside it did not change. This section records **what was measured, and how to re-measure -it**, because the same markup is expected to spread across the other cosyte READMEs and **the answer +it**, because the same markup is expected to spread across the other Cosyte READMEs and **the answer is not the same on the two surfaces it has to survive.** ### The question diff --git a/documentation/decisions/0002-fhirpath-dependency-posture.md b/documentation/decisions/0002-fhirpath-dependency-posture.md index cc7c7fb..57a65d1 100644 --- a/documentation/decisions/0002-fhirpath-dependency-posture.md +++ b/documentation/decisions/0002-fhirpath-dependency-posture.md @@ -19,7 +19,7 @@ not interchangeable: - **(a) Depend on a full third-party engine** (e.g. `fhirpath.js`). It is a complete implementation, but it is large, pulls its own transitive dependencies, and evaluates a far broader surface than - our shipped profiles use. Adopting it **violates the cosyte zero-runtime-dependency rule** that + our shipped profiles use. Adopting it **violates the Cosyte zero-runtime-dependency rule** that every parser in the suite holds (see the meta-repo `documentation/conventions.md` and the dep-cap gate in `scripts/verify.sh`). A runtime dep here would make `@cosyte/fhir` the one parser that breaks the suite's core promise.