artifacts/standard-named

Rendered from markdown source. Open raw source on GitHub.

Field Map, Summary, Minority Retention, and Provider Matrix

Status: candidate pre-production Content canon status: unset

| Governance layer | Required visibility | Principal risk | Repair | |---|---|---|---| | Model field map | Source field, scope, represented and missing centers, protected conditions, uncertainty | Map presented as living field | Relabel, reopen participant review, preserve gaps | | Participant projection | Source center and epistemic status | Projection treated as complete person | Restore source and scope | | Standing-preserving summary | Common positions, minority positions, disagreement, source links | Synthetic consensus | Correct active summary | | Minority-field retention | Frequency, materiality, standing, predicted consequence | Low-frequency erasure | Protected retention without automatic veto | | Generated option | Model authorship, inputs, adoption status | False community authorship | Restore generation lineage | | Provider disclosure | Policies, incentives, cost and latency constraints, unknowns | Provider field presented as neutrality | Add operative provider constraint | | Sycophancy event | Prompt pressure, output change, affected centers | Agreement counted as evidence | Quarantine and rerun against source | | Model inference | Source dependence and confidence | Inference laundering | Preserve inferential class and seek confirmation |

Standing-preserving summary minimum

included centers
omitted centers
common positions
minority positions
protected conditions
unresolved disagreement
source links
model inferences
generated connective language
participant review
corrections

Minority-retention test

A field element should not disappear merely because it is rare when it carries:

material consequence
protected-condition relevance
irreversible-loss prediction
unique dependency knowledge
directly affected standing
review trigger

Provider-field test

Disclose provider constraints where they materially affect:

role availability
refusal
memory
compression
option generation
ranking
tool use
latency
cost
data use
jurisdiction

Governing principle

A system cannot consentfully map other fields while hiding the field that governs its own participation.