Rename the system to PhenoMetrix - #27
Merged
Merged
Conversation
Branding, package scope (@phenometric/* -> @phenometrix/*), the root package name, repository URLs, and the Python service module. NOT renamed: the twenty "phenometric.<name>.vN" schema identifiers. Those are wire identifiers, not branding. Renaming them would change the pack digest and retroactively invalidate the schemaVersion stamped on every observation ever produced, for a cosmetic gain. They stay. The rename does reach one piece of pack content: AMBIENT_LOCAL_CONSENT_TEXT carries the product name, and its SHA is a field inside the pack. That is a change to the terms a participant reads, so it moves the consent digest, the pack digest, and the pack version to 3.1.0 -- exactly the deliberate bump the digest tooling exists to force. No metric, threshold, or algorithm changed; sessions measured under 3.0.0 remain comparable on every measurement, and what differs is the wording that was agreed to. Two pins had to follow: validate-structure.sh asserts the root package name, and the worklet's SHA is pinned in asset-manifest.json, so editing a comment inside it required regenerating the manifest. README rewritten for accuracy rather than only renamed. It claimed 16 metrics (27), an eight-section report (ten), that blendshapes were computed and kept inside the worker boundary (they are no longer computed at all), and listed Personal Trajectory as a retained capability (removed in July 2026). It now also states the contrast principle the measurements are built on and the three-tier substrate. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Renames branding, the package scope (
@phenometric/*→@phenometrix/*), theroot package name, repository URLs, and the Python service module.
Not renamed, deliberately
The twenty
"phenometric.<name>.vN"schema identifiers. Those are wireidentifiers, not branding. Renaming them would change the pack digest and
retroactively invalidate the
schemaVersionstamped on every observation everproduced, for a purely cosmetic gain.
One consequence worth reviewing
AMBIENT_LOCAL_CONSENT_TEXTcarries the product name, and its SHA is a fieldinside the protocol pack. So the rename is a change to the terms a
participant reads. That moves the consent digest, the pack digest, and the pack
version to 3.1.0 — the deliberate bump the digest tooling exists to force.
No metric, threshold, or algorithm changed. Sessions measured under 3.0.0 remain
comparable on every measurement; what differs is the exact wording agreed to.
README rewritten, not just renamed
It had drifted: it claimed 16 metrics (27), an eight-section report (ten), that
blendshapes were computed and held inside the worker boundary (no longer
computed at all), and listed Personal Trajectory as a retained capability
(removed in July 2026).
It now also states the principle the measurements are actually built on — every
one earns its keep by cancelling a confound, which is why the first pack targets
an indication where the finding is an asymmetry — and documents the three-tier
substrate.
Verification
269 unit tests, typecheck, structure + digest check, build, 6 browser e2e.
🤖 Generated with Claude Code