QUIET UTILITY DERIVATION P0 IMPLEMENTATION PROMPT PRE RATIFICATION

STATUS: DO NOT DISPATCH UNTIL QUIET_UTILITY_EXECUTABLE_PILOT_CONTRACT_CANDIDATE_v0_1.md RECEIVES OPERATOR RATIFICATION.

Repository: thelaplage/counterpedia

Last reconnaissance base: d0ef484eafc84148277c1d81dd1ac600d0449cdc

Do not trust this SHA at dispatch. Re-check origin/main; if it moved, bind to the new main only after reviewing intervening changes for overlap.

Goal

Implement one additive, pure, deterministic proving lane for two Quiet Utility derivation families:

1. USB-C capability/requirement intersection.

2. Warbling Vireo observation/taxonomy reprojection.

Non-negotiable boundaries

• no network;

• no LLM;

• no source capture;

• no dagr-ingest changes;

• no SRS;

• no canonical cp:* minting;

• no claim admission;

• no standing mutation;

• no refusal mutation;

• no composition admission;

• no reader-route cutover;

• no counterpedia.content/v0.2 schema change.

This is computation only.

Read first

• lib/activity/activityPublicProjection.ts

• lib/counterpedia/compositionIntake.ts

• packages/contracts/src/types/counterpediaContentV02.ts

• relevant existing digest/canonicalization helpers

• QUIET_UTILITY_EXECUTABLE_PILOT_CONTRACT_CANDIDATE_v0_1.md

Required posture

Reuse current Counterpedia doctrine:

deterministic projection != authority
deterministic evaluation != admission

A derived result MUST have zero authority and zero standing effect.

Implementation shape

Prefer an additive directory:

lib/counterpedia/derivations/

Do not create generic abstractions beyond what both proving fixtures actually need.

Expected small modules:

types.ts
compatibilityIntersection.ts
classificationReprojection.ts

If a separate canonicalization helper is truly required, keep it local and explicit.

Fixture strategy

Use synthetic governed-input fixtures.

Do NOT pretend the Quiet Corpus research dossiers are admitted graph state.

Every fixture must make its synthetic status obvious.

USB acceptance cases

• charge-only 240W cable: connector compatible; video incompatible; power ceiling derived from 96W Studio Display; overall display use incompatible.

• Thunderbolt 4 Pro cable: transport/video compatible; power ceiling 96W; overall compatible.

• missing cable video fact: outcome unknown.

• swapping cable: old result preserved; new result differs only from changed input.

• higher wattage must never imply global “better” score.

Bird acceptance cases

• broad 2024 taxonomy: historical observation projects to broad Warbling Vireo concept.

• eBird/Clements 2025: same immutable synthetic BC observation projects to Western Warbling Vireo under an explicit geographic conversion rule.

• AviList v2025b: same observation remains projected under that edition's broader concept.

• ambiguous migrant: post-split projection becomes ambiguous pair; never forced to East/West.

• exact same scientific name string with different circumscriptions must remain distinct concept identities.

• pending proposal cannot be used as a current published taxonomy.

Shared hard tests

• no network/model imports or calls;

• same semantic inputs + same rule version => same semantic output;

• unknown derivation kind/version fails closed if a registry/discriminator is implemented;

• missing required input => typed unknown/unresolved;

• input digest mismatch => fail closed;

• no output field can assert admission/standing authority;

• no mutation of passed fixtures;

• deterministic ordering;

• git diff --check.

Important ratification HOLDs

Unless the operator expressly resolves them before dispatch, DO NOT:

• mint counterpedia.derivation-result/v0.1 as a production/public schema;

• mint canonical derivation IDs;

• create a derivation-family registry;

• define ADJ1 handoff;

• modify reader UI.

The first code lane may use internal TypeScript types needed for the proof, but must not represent those internal types as ratified public schema authority.

End state

One focused commit.

Run focused tests + full applicable local suite.

Open a DRAFT PR.

No merge.

Report:

• exact base SHA;

• exact head SHA;

• files changed;

• focused/full test counts;

• whether any existing derivation/projection surface was reused;

• every HOLD left unresolved.