COUNTERPEDIA DERIVE FIRST DOCTRINE AUTHORITY

Status: RATIFIED BY OPERATOR · AUTHORITY CONFERRED AT MERGE
Scope: deterministic derived relationships for Quiet Utility and later compatible families
Ratification date: 2026-08-09
Base at authorship: d0ef484eafc84148277c1d81dd1ac600d0449cdc

1. Purpose

Counterpedia may compute what follows from governed inputs, but computation does not govern itself.

This authority ratifies the doctrine:

derive first; admit separately.

A deterministic derivation may produce a reproducible relationship/result from governed inputs. It does not thereby create an admitted claim, change standing, alter a refusal, authorize publication, or acquire source/adjudication authority.

2. Ratified invariants

D1 — Derivation is never admission

A derivation result has:

authority_effect = none
standing_effect  = none

It MUST NOT:

• create or mutate admitted claim standing;

• mutate refusals;

• mint documentary identity or SourceEdition authority;

• authorize publication/composition;

• self-promote into public truth.

Any later admission of a proposition derived from such a result remains a distinct governance act.

D2 — Typed derivation families

Derivation semantics belong to explicit families. Counterpedia MUST NOT collapse all derived knowledge into one global true / false / maybe verdict vocabulary.

The first proving families are:

compatibility intersection
classification reprojection

These family names identify implementation/proving intent only. This authority does not ratify a universal public schema identifier.

D3 — Exact governed inputs

Every authority-relevant input used by a derivation MUST be explicit and identity-bound strongly enough to reproduce the computation.

No hidden ambient source, model state, network lookup, or undeclared mutable dependency may influence the semantic result.

D4 — Determinism

For a named rule version:

same semantic inputs + same rule version
→ same semantic result

The derivation path MUST require no network call and no model call.

Where time changes semantics, time MUST be an explicit input rather than ambient wall-clock state.

D5 — Unknown is first-class

Missing required evidence MUST yield a typed unresolved/unknown result appropriate to the derivation family.

Counterpedia MUST NOT fill missing capability, classification, applicability, or measurement facts by analogy, connector shape, naming similarity, majority behavior, or model guess.

D6 — Inputs and historical state remain immutable

A new derivation creates a new result/projection. It MUST NOT rewrite:

• original observations;

• authored historical labels;

• source propositions;

• previous derivation results;

• prior source/checklist/product editions.

D7 — Projection is not authority

A deterministic projection is downstream of governed inputs and is independently reproducible. It is not itself a documentary source, admission authority, standing authority, or canonical receipt substitute.

D8 — Reader wording is downstream

Machine derivation semantics and reader rendering are separate layers. A reader surface MUST NOT strengthen the result beyond the typed derivation output and its limitations.

3. First proving family: compatibility intersection

The compatibility family may derive task-specific compatibility from admitted component capabilities and target requirements.

Required behavior includes:

• categorical requirements are matched against explicit available capabilities;

• explicitly absent required capability → incompatible for that dimension;

• unresolved required capability → unknown;

• compatible numeric ceilings may derive an effective ceiling from the limiting applicable component;

• higher value on one dimension MUST NOT create a universal quality/ranking score;

• swapping one component creates a new result and leaves prior inputs/results unchanged.

Initial proving fixture: USB-C / Thunderbolt host + display + cable composition.

4. Second proving family: classification reprojection

The classification-reprojection family may project an immutable observation through a named taxonomy authority, exact edition, taxon-concept set, and explicit conversion rule.

Required behavior includes:

• original observation labels remain immutable;

• authority and exact edition are mandatory context;

• scientific-name string alone is insufficient taxon-concept identity when circumscription differs;

• pending/proposed taxonomy MUST NOT be treated as a published current edition;

• ambiguous evidence remains ambiguous rather than being force-assigned;

• conversion rules from one authority MUST NOT silently leak into another authority.

Initial proving fixture: Warbling Vireo pre/post-split observation reprojection.

5. Separation from existing Counterpedia layers

Acquisition

Answers: what happened on the network / what exact bytes were observed?

It does not compute Quiet Utility compatibility or classification.

Ingest

Answers: what deterministic extraction/anchors were derived from exact bytes?

It does not adjudicate or perform Quiet Utility governed composition.

SRC1 / ADJ1

Resolve documentary identity and governed claim standing/bindings/limitations.

Quiet derivation consumes governed propositions; it does not replace these authorities.

Composition / counterpedia.content/v0.2

Content schema remains a publication/reader representation contract. Derivation execution semantics MUST NOT be hidden inside content blocks.

COLLIDE

COLLIDE remains relationship evidence across epistemic states/graphs. Quiet derivation does not replace COLLIDE and does not mutate either graph merely by computing a relation.

6. Explicit HOLDs

This authority intentionally does not ratify any of the following:

• a universal counterpedia.derivation-result/v0.1 public schema;

• canonical cp:* derivation identifiers;

• a global derivation-family registry or its owning component;

• one universal valid_at field contract across all derivation families;

• a canonicalization algorithm for public derivation artifacts;

• a generic ADJ1 handoff artifact such as DerivedClaimProposal;

• reader-route/UI cutover;

• live Quiet Utility corpus admission;

• SRS profile or signing semantics for derivations.

These remain HOLD until a proving implementation produces enough evidence to decide them without speculative abstraction.

7. P0 implementation authorization after merge

After these bytes merge to main, one synthetic proving lane is authorized with these boundaries:

USB compatibility computation
+
Warbling Vireo classification reprojection

The lane MUST be:

• additive;

• pure/deterministic;

• local/no-network;

• no-LLM;

• synthetic fixtures clearly marked synthetic;

• no claim admission;

• no standing/refusal mutation;

• no source/capture/ingest changes;

• no SRS;

• no canonical identifier minting;

• no reader cutover;

• no public derivation schema claim.

Implementation may use internal TypeScript types sufficient to prove the two families, but those internal types MUST NOT be represented as ratified public schema authority.

8. P0 acceptance target

A successful proving lane demonstrates:

USB:
  same host + display
  Cable A → incompatible for requested display use
  Cable B → compatible for requested display use

Bird:
  same immutable observation
  taxonomy edition A → projection A
  taxonomy edition B → projection B

And in every case:

source mutation       = none
observation mutation  = none
standing mutation     = none
admission              = none
network/model use      = none
reproducibility        = required

9. Change discipline

After merge, this file is authority v0.1 and MUST NOT be semantically edited in place. Any normative change requires a superseding authority edition.