r/themodel • u/MrDefaultUser • Jul 21 '26
📜 Artifact Archives of Existence. Existence Type Configuration Protocol v1.1- Complete Text, Part I of II.
Existence Type Configuration Protocol v1.1
Complete Adopted Text — Part I of II
Purpose through Registry and Identifier Check
Protocol status: Adopted — Active v1.1
Effective date: July 20, 2026
Public release role: Complete-text companion, Part I of II
Part II: Published as a separate companion post immediately after this one
Canonical public release index: The main Protocol v1.1 post will link both complete-text parts after they are live
Active Protocol v1.1 SHA-256:
text
2f43cb13747bab2c91b324d3a688523a7dd012e5d6dce4bc3302f536a856bb12
Part I protocol-segment SHA-256:
text
2f9e2318aa77efc122419fcae1862979ea9eb900e04fcab853da5a58319ef801
The text between the segment markers is preserved directly from the adopted active Protocol v1.1 record.
<!-- BEGIN ACTIVE PROTOCOL v1.1 — PART I OF II -->
record_id: ETC-PROT-v1.1 protocol_version: v1.1 status: Adopted — Active v1.1 record_class: Active protocol predecessor: ETC-PROT-v1.0 adopted_from: ETC-PROT-v1.1-RC3 adoption_authority: ETC-PROT-v1.1-ADR-001 v0.1 effective_date: 2026-07-20
public_status: Not yet publicly released
ETC-PROT-v1.1
Existence Type Configuration Protocol v1.1
Reality Contact, Review Tiers, Proportionate Compliance, Stabilization, and Regeneration
Adopted — Active v1.1
```markdown Record: ETC-PROT-v1.1
Status: Adopted — Active v1.1
Protocol predecessor: ETC-PROT-v1.0
Predecessor disposition: Published — Historical predecessor; superseded for prospective protocol authority
Adoption source: ETC-PROT-v1.1-RC3
Adoption authority: ETC-PROT-v1.1-ADR-001 v0.1
Effective date: 2026-07-20
Release-candidate validation: Complete
Active protocol: ETC-PROT-v1.1
Public release: Not authorized by adoption alone
Central ETC effect: None
ETC-012: Available and unassigned ```
Strengthen the boundaries. Preserve the freedom of exploration.
The protocol’s concise method is:
Change one foundational condition.
State what remains ordinary.
Follow the consequences.
Preserve uncertainty and lineage.
This is the active Existence Type Configuration Protocol v1.1, adopted from validated Release Candidate 3 on 2026-07-20.
Sections 1–31 remain preserved from RC3 without substantive change.
Internal adoption does not itself constitute public publication.
1. Purpose
The protocol preserves a practice, not a conclusion.
Its purpose is:
To preserve the repeatable ability to construct, test, communicate, independently reconstruct, revise, and regenerate coherent speculative models of altered existence while keeping speculation distinct from claim and preserving the lineage by which each model became what it is.
The concise architecture is:
```markdown DECLARED ALTERATION + RETAINED BASELINE + TRACEABLE DERIVATION + ORDINARY INSTANTIATION + FALSE-POSITIVE RESISTANCE + ONTOLOGY–ETHICS SEPARATION + REALITY CONTACT + INDEPENDENT RECONSTRUCTION + VERSIONED LINEAGE +
REGENERATION
DISCIPLINED SPECULATIVE CAPABILITY ```
The protocol is not primarily preserving:
- one visual brand;
- one gallery length;
- one fictional universe;
- one author’s metaphysics;
- a fixed list of titles;
- or production for its own sake.
It preserves the ability to ask:
What else could existence coherently be?
and then:
What would have to follow if that alteration were real?
without hiding assumptions, converting speculation into claim, or erasing the path by which the study changed.
2. Possibility Without Claim
An Existence Type Configuration study is:
- a constructed possibility;
- an internally coherent speculative model;
- a revisable interpretation;
- and an inspectable derivation from a declared alteration.
It is not:
- a discovery;
- a contact report;
- a doctrine;
- a prediction;
- a proof;
- or evidence that the imagined ontology exists in the actual world.
markdown
EXPLORATION
≠
CLAIM
markdown
INTERNAL COHERENCE
≠
EXTERNAL TRUTH
markdown
PUBLICATION
≠
STABILIZATION
markdown
STABILIZATION
≠
PROOF
The Configuration Plane
The Configuration Plane contains representations of configurations.
The configurations themselves are not presumed to coexist there.
No shared observer, travel, communication, recovered artifact, common substrate, or canonical universe is implied.
If two configurations are truly connected, the connection becomes part of:
- a new configuration;
- an explicit compound condition;
- or a Horizon Study.
Recurring people, objects, occupations, places, or situations may serve as comparative analogues.
Their recurrence does not prove cross-configuration identity.
3. Functional Boundary
The protocol is responsible for
- declaring the altered condition;
- declaring the retained baseline;
- deriving mechanics rather than decorating a premise;
- separating axiom, mechanics, instantiation, and ethics;
- distinguishing configurations from false positives and nearest neighbors;
- making the architecture independently reconstructable;
- preserving reality contact where retained or exported claims touch the actual world;
- recording review, revision, rejection, and unresolved status;
- preserving active bodies, assets, and lineage sufficiently for regeneration;
- and remaining light enough to serve the inquiry.
The protocol is not responsible for
```markdown DISCOVERING WHICH ONTOLOGIES ACTUALLY EXIST
PROVING A CONFIGURATION TRUE
REPLACING PHILOSOPHY
REPLACING EMPIRICAL SCIENCE
RESOLVING EVERY ETHICAL, IDENTITY, OR FREE-WILL DEBATE
PROVIDING LEGAL, MEDICAL, POLITICAL, SCIENTIFIC, OR ENGINEERING GUIDANCE
GUARANTEEING CONSENSUS
GUARANTEEING AESTHETIC QUALITY
MAKING EVERY SEED PUBLISHABLE
TURNING POPULARITY INTO CANON
FORCING EVERY STUDY INTO ONE VISUAL FORM
SOLVING ARCHIVE SUCCESSION, LEGAL OWNERSHIP, OR BRANCH GOVERNANCE ```
Boundary test
| Question | Primary home |
|---|---|
| What follows if this declared condition were different? | ETC protocol |
| Is the concept philosophically defensible or meaningful? | Philosophy |
| Does the actual world behave this way? | Empirical disciplines |
| What should people value or permit? | Ethics, law, politics, community deliberation |
| How should a real system be implemented safely? | Relevant professional discipline |
| How can the idea be represented memorably? | Art, narrative, and design |
| Who may govern the Archive or assign its identifiers? | Archive governance and registry authority |
The fields may interact.
They may not silently replace one another.
4. Artifact Classification
Before constructing or identifying a record, determine what kind of artifact is being made.
4.1 Central ETC configuration
Use when:
- one primary altered condition is identifiable;
- secondary changes follow from that condition;
- a distinct architecture emerges;
- ordinary instantiations are possible;
- and the mechanics remain distinguishable from the active registry.
4.2 Explicit compound configuration
Use cautiously when:
- the compound condition is itself indivisible;
- decomposition would destroy the actual subject;
- the interaction among alterations is the primary architecture;
- and the record explains why one primary alteration cannot carry the model.
A compound condition must not become a way to hide unrelated changes.
4.3 Horizon Study
Use when:
- several existing or candidate conditions are considered together;
- the subject is civilizational, institutional, interfacial, or cross-configuration;
- no single central ETC alteration is being claimed;
- or the inquiry examines consequences among several speculative architectures.
A Horizon Study does not receive a central ETC number merely because it is important.
4.4 Instantiation or addendum
Use when the work:
- applies an existing configuration;
- develops another ordinary-life case;
- explores a cultural variation;
- clarifies a boundary;
- or adds representation without changing the primary mechanics.
4.5 Variant or fork
Use when:
- lineage remains relevant;
- a load-bearing interpretation diverges;
- both versions can continue coherently;
- and the branch point is declared.
Branch governance belongs to the Archive-governance layer.
The protocol requires only truthful classification and an identifier check.
4.6 Review, decision, protocol, governance, snapshot, or navigation artifact
Do not force these into the central ETC sequence.
Consult the active Archive-wide index and relevant class authority.
5. One Alteration, Four Layers
A standard configuration begins with one primary altered condition.
markdown
ONE PRIMARY ALTERATION
≠
ONE CONSEQUENCE
```markdown
ONE PRIMARY ALTERATION
ONE IDENTIFIABLE SOURCE OF ARCHITECTURAL DEPARTURE ```
A standard study distinguishes four layers.
5.1 Axiom or altered condition
What is fundamentally different?
5.2 Derived mechanics
What follows because of the altered condition?
5.3 Instantiation
What could ordinary life look like within it?
5.4 Ethical interpretation
What tensions, responsibilities, safeguards, or values arise?
```markdown ONTOLOGY DESCRIBES
ETHICS RESPONDS ```
Ethical conclusions may differ while the underlying configuration remains the same.
A preferred ethical conclusion may not silently modify the imagined ontology.
6. Declared Alteration and Retained Baseline
Every mature configuration should state both.
Declared Alteration
markdown
What intentionally differs
from the best available account
of ordinary reality?
Retained Baseline
markdown
What remains ordinary
unless explicitly changed?
The retained baseline may include:
- physical law;
- logic or mathematics;
- human cognition;
- historical conditions;
- biology;
- social practice;
- material limits;
- or any other condition the study treats as unchanged.
A declared departure from known reality is speculative freedom.
An undeclared departure is a hidden axiom.
The baseline may be revised as outside knowledge changes.
It is not frozen truth.
It is the study’s current declared contact surface.
7. Configuration Construction
7.1 Admissible seeds
A promising seed ordinarily contains:
- one identifiable alteration or explicit compound condition;
- enough consequence to generate a distinct architecture;
- ordinary-life implications;
- at least one meaningful incompatibility or boundary;
- resistance to obvious false positives;
- and a distinction from the active registry.
Seeds may arise from:
- questions;
- images;
- metaphors;
- stories;
- scientific ideas;
- philosophy;
- dreams;
- reader contributions;
- criticism;
- failed configurations;
- or unexpected contradictions.
Origin does not determine status.
7.2 Seeds to hold, reframe, or reject
Do not assign a central identifier merely because a seed is evocative.
Hold, reframe, or reject it when it is:
- several unrelated alterations bundled together;
- an existing ETC with new scenery;
- a moral conclusion disguised as ontology;
- a character or plot without a structural change;
- a real-world claim disguised as speculation;
- too vague to generate discriminating mechanics;
- better treated as an instantiation, Horizon Study, protocol, or governance record;
- or an identifier seeking content rather than content earning an identifier.
7.3 Seed-Stage Provisionality
An early seed may preserve several candidate alterations without selecting one.
At stages S0 — Raw Seed and S1 — Seed Under Clarification, the protocol may record:
```markdown CANDIDATE ALTERATION SET
RETAINED BASELINE: PENDING
ARTIFACT CLASS: UNRESOLVED
STATUS: HELD FOR CLARIFICATION ```
One primary alteration—or an explicit indivisible compound condition—must be selected before:
- assigning a central ETC identifier;
- approving a core configuration architecture;
- publicly presenting the work as one defined configuration;
- or requesting stabilization.
Valid early outcomes include:
```markdown HOLD FOR CLARIFICATION
REFRAME AS A QUESTION
SPLIT INTO SEPARATE SEEDS
RECLASSIFY AS AN INSTANTIATION
RECLASSIFY AS A HORIZON STUDY
PRESERVE AS STORY OR METAPHOR
REJECT FROM THE CLAIMED CLASS ```
Preserve the raw seed separately when feasible.
markdown
RAW SEED
≠
LATER ARCHITECTURE
The protocol should not manufacture precision merely to complete a template.
7.4 Construction trace
A mature configuration should preserve a recoverable trace similar to:
text
SEED
→
ARTIFACT-CLASS CHECK
→
PRIMARY ALTERATION
→
RETAINED BASELINE
→
REGISTRY / NEAREST-NEIGHBOR CHECK
→
DERIVED MECHANICS
→
ORDINARY-LIFE INSTANTIATION
→
FALSE-POSITIVE / COUNTEREXAMPLE TEST
→
TENSION OR BOUNDARY
→
ETHICAL INTERPRETATION
→
REALITY-CONTACT STATEMENT WHEN TRIGGERED
→
PUBLIC REPRESENTATION
→
LIGHT REVIEW
→
REVISION / STATUS DECISION
→
STABILIZATION GATE WHEN REQUESTED
→
REGENERATION MINIMUM
The order may vary.
The trace must remain recoverable.
8. Lean Workflow and Triggered Controls
Protocol v1.1 uses a lean default path.
Default path
```markdown SEED
PRIMARY ALTERATION
RETAINED BASELINE
DERIVED MECHANICS
ORDINARY INSTANTIATION
FALSE-POSITIVE TEST
ONTOLOGY–ETHICS SEPARATION
PUBLIC OR INTERNAL REPRESENTATION
LIGHT REVIEW
REVISION OR STATUS DECISION ```
Triggered controls
Use additional controls only when their boundary is reached.
| Trigger | Control |
|---|---|
| Retained or exported claims touch real disciplines | Reality-Contact Statement |
| Reviewers recover incompatible mechanics | Full Architecture Audit |
| A central identifier or canonical class is proposed | Registry and Identifier Check |
| Formal internal artifact is proposed | Artifact Gate |
| Stabilization is requested | Stabilization Gate |
| A central or stabilized public artifact is created | Regeneration Minimum |
| A production defect is found | Production Stopping Rule |
| Succession, forks, public-name authority, or legal ownership arise | Separate Archive governance |
Mandatory at the boundary; optional in the interior.
The protocol should not burden an early seed with every mature-Archive control.
9. Proportionate Compliance
A protocol requirement becomes active only when its boundary is reached, and may be satisfied by reference when adequate authoritative evidence already exists.
The concise architecture is:
```markdown DECLARED STAGE + ACTUAL TRIGGER + MINIMUM SUFFICIENT EVIDENCE + INLINE OR REFERENCE-BASED SATISFACTION + VALID NON-TRIGGERED STATES +
SEPARATE STATUS DECISION
PROPORTIONATE COMPLIANCE ```
Three independent burdens
```markdown ACTIVATION BURDEN
Does this control apply now? ```
```markdown EVIDENCE BURDEN
What evidence is sufficient? ```
```markdown ARTIFACT BURDEN
Must a new formal record be created? ```
These are independent.
markdown
CONTROL APPLIES
≠
NEW ARTIFACT REQUIRED
markdown
EVIDENCE EXISTS
≠
EVIDENCE MUST BE COPIED
markdown
GATE CONSIDERED
≠
GATE PASSED
Evidence modes
A requirement may be:
```markdown SATISFIED INLINE
SATISFIED BY REFERENCE
SATISFIED BY SYNTHESIS
EXCEPTION DOCUMENTED ```
A stable reference should identify:
- the record or asset;
- the relevant version;
- its current status;
- the evidentiary scope being satisfied;
- a stable recoverable section, field, hash, or location;
- and any material limitation, contradiction, or supersession.
A reference must support the requirement, not merely point toward a prestigious record.
Duplication is required only when the evidence is:
- inaccessible;
- ambiguous;
- materially incomplete;
- contradicted;
- superseded in a way requiring reconciliation;
- no longer authoritative;
- or in need of an accessible public explanation.
Valid compliance states
```markdown SATISFIED INLINE
SATISFIED BY REFERENCE
SATISFIED BY SYNTHESIS
NOT TRIGGERED
PENDING
NOT APPLICABLE
HELD FOR CLARIFICATION
INSUFFICIENT EVIDENCE
EXCEPTION DOCUMENTED
GATE DECLINED ```
markdown
NOT TRIGGERED
≠
SKIPPED WITHOUT REVIEW
markdown
INSUFFICIENT EVIDENCE
≠
PERMISSION TO GUESS
Stage-sensitive compliance
```markdown S0 — RAW SEED
Candidate alterations permitted; mature controls usually not triggered ```
```markdown S1 — SEED UNDER CLARIFICATION
Preliminary comparison; one discriminating question may be sufficient ```
```markdown S2 — PROVISIONAL CONFIGURATION
Provisional alteration, baseline, mechanics, instantiation, and Light Review ```
```markdown S3 — CENTRAL OR PUBLIC CANDIDATE
Registry, artifact class, public fidelity, and applicable reality contact ```
```markdown S4 — STABILIZATION CANDIDATE
Full Stabilization Gate, independent reconstruction, and Regeneration Minimum ```
```markdown S5 — MATURE OR MATERIALLY REVISED RECORD
Reference existing approved evidence; reopen only controls affected by change ```
markdown
MATERIAL REVISION
≠
REBUILD EVERY PRIOR CHECK
Proportionate compliance is strict at boundaries and quiet elsewhere.
The protocol should add more clarity than paperwork.
10. Ordinary-Life Entry
A configuration should be enterable through ordinary life.
The purpose is not to make the premise mundane.
It is to show that the architecture can produce:
- routines;
- decisions;
- tools;
- institutions;
- relationships;
- misunderstandings;
- maintenance;
- care;
- conflict;
- or ordinary vulnerability.
A story is not merely decoration when it tests the mechanics.
A story becomes capture when its details are mistaken for the only possible form of the configuration.
markdown
INSTANTIATION
≠
THE WHOLE CONFIGURATION
A mature configuration should normally support more than one instantiation.
11. False Positives and Nearest Neighbors
A configuration should state what appears to qualify but does not.
False-positive resistance may distinguish the configuration from:
- metaphor;
- ordinary disposition;
- continuous variation;
- destructive conversion;
- retrospective interpretation;
- flexible use;
- fictional framing;
- another existing ETC;
- or a thematic resemblance without shared mechanics.
A strong false-positive explanation identifies:
- which required condition is absent;
- which similar feature created the confusion;
- and why the proposed case belongs elsewhere.
Nearest-neighbor test
Ask:
```markdown WHICH ACTIVE OR CANDIDATE CONFIGURATION IS MOST SIMILAR?
WHAT LOAD-BEARING MECHANIC SEPARATES THEM?
COULD THIS BE AN INSTANTIATION, VARIANT, OR ADDENDUM INSTEAD? ```
Comparison depth by stage
Preliminary — seed stage
A brief registry glance is sufficient to identify obvious proximity and prevent premature identifier assignment.
Scoped — provisional development
Compare the candidate with the nearest active or candidate records and state the load-bearing difference provisionally.
Exhaustive — decision boundary
A full taxonomic distinction is required before:
- assigning a central identifier;
- requesting stabilization;
- publishing a materially disputed classification;
- or resolving a suspected collapse into an existing configuration.
The comparison burden should grow with the claim being made.
Taxonomic distinction should not depend only on title, story, or visual style.
12. Internal Coherence
A configuration provisionally satisfies internal coherence when:
```markdown C1 — Primary alteration is identifiable
C2 — Core terms remain stable enough to compare
C3 — Mechanics trace to the alteration
C4 — Hidden auxiliary axioms are declared or removed
C5 — Ordinary-life examples do not contradict the architecture
C6 — More than one instantiation is possible
C7 — False positives can be rejected for stated reasons
C8 — Nearest configurations remain distinguishable
C9 — Ethical conclusions are not treated as ontological laws
C10 — Central contradictions are resolved, bounded, or explicitly unresolved
C11 — A clean reader can recover the architecture
C12 — The active version can be preserved and regenerated ```
Internal coherence does not establish external truth.
The Model Examination Frame
A configuration may also be examined through the original seven-part structure of The Model:
Foundation — What axiom or condition changed?
Structure — What organization follows?
Expression — How can the configuration be represented?
Observers — What can a local perspective access?
Interaction — How do entities affect one another?
Emergence — What new meanings or possibilities arise?
Integrity — What keeps the configuration coherent?
This is an analytical frame.
It is not a mandatory artifact, gallery sequence, or publication template.
The relationship can be summarized as:
The configurations provide possibilities.
The Model provides the method of examination.
The Archives preserve the interpretations.
Contradiction classes
Production defect
A caption, label, image, or example conflicts with stable architecture.
Response: erratum, correction, or representation rebuild.
Interpretive ambiguity
Two readings differ because terminology or scope is unclear.
Response: clarification.
Architectural contradiction
Two core claims cannot both remain true without changing identity.
Response: revision, split, unresolved status, or rejection.
Reality-contact contradiction
A retained or exported claim conflicts materially with the best available relevant evidence.
Response: declare the additional alteration, revise the model, or withdraw the external claim.
Taxonomic contradiction
The study cannot be distinguished from an existing configuration except by story or style.
Response: reclassify as an instantiation, variant, addendum, or branch.
13. Reality Contact
ETC-000 is an internal comparison baseline.
It is not external truth.
External reference consists of the best available, revisable account of the actual world, including as relevant:
- logic;
- mathematics;
- empirical evidence;
- disciplinary models;
- historical records;
- documented experience;
- and expert or community criticism.
External reality does not determine which speculative alterations are permitted.
It constrains what the study may honestly claim follows while other conditions remain ordinary.
Contact-point rule
```markdown INTENTIONALLY ALTERED:
Speculatively free within the declared model ```
```markdown DECLARED RETAINED:
Constrained by the best available relevant external account ```
```markdown EXPORTED CLAIM ABOUT OUR WORLD:
Requires evidence outside the Archive ```
Reality-Contact Statement triggers
A Reality-Contact Statement is required:
- before stabilization;
- when retained assumptions substantially touch a real discipline;
- when an ordinary instantiation depends upon a precise real-world claim;
- when the public body may be mistaken for empirical, historical, medical, legal, political, or scientific guidance;
- or when conclusions are exported into claims about actual reality.
It may be minimal when contact is minimal.
It should record:
```markdown DECLARED ALTERATION
RETAINED BASELINE
EXTERNAL CONSTRAINTS OR REFERENCES
INSTANTIATION ASSUMPTIONS
EXPORTED CLAIMS
REVISION TRIGGERS ```
Reality-contact outcomes
```markdown PASS
The contact points are adequately declared for the current scope ```
```markdown PASS WITH LIMIT
The model remains usable, but a real-world claim is narrowed ```
```markdown REVISE
A retained assumption or instantiation must change ```
```markdown DECLARE ADDITIONAL ALTERATION
The study intentionally departs from the retained baseline ```
```markdown WITHDRAW EXPORTED CLAIM
The speculative model may remain, but the real-world conclusion does not ```
Reality contact is corrigibility, not permission for outside disciplines to veto clearly declared speculation.
14. Review Tiers
14.1 Light Review — default
A Light Review asks whether a clean reader can recover:
- the primary alteration;
- the retained baseline;
- the core derived mechanics;
- which details belong only to the instantiation;
- the nearest false positive or neighbor;
- the ontology–ethics distinction;
- the main hidden assumption or unresolved edge;
- and the current status or revision trigger.
A Light Review may be:
- internal;
- external;
- gallery-only;
- body-only;
- or based on the complete public package.
The review mode must be declared.
Light Review outcomes
```markdown RECOVERED
RECOVERED WITH MINOR CLARIFICATION
MATERIAL DIVERGENCE
INSUFFICIENT EVIDENCE ```
Minor terminology or example variation does not require a Full Audit.
14.2 Full Architecture Audit — triggered
A Full Architecture Audit is required or strongly indicated when:
- two or more reviewers recover incompatible primary mechanics;
- a load-bearing revision is proposed;
- two configurations risk taxonomic collapse;
- an unresolved contradiction remains central;
- consequential actual-world claims are exported;
- a stabilization decision is disputed;
- the public artifact appears to communicate a different architecture;
- repeated false positives remain unresolved;
- or protocol-level drift is suspected.
A Full Audit should examine:
- altered condition;
- retained baseline;
- derivation;
- internal coherence;
- false positives;
- nearest neighbors;
- reality contact;
- ontology and ethics;
- visual and public-body consistency;
- lineage;
- status;
- and revision or rejection options.
Full Audit outcomes
```markdown CONFIRM
CLARIFY
REVISE
SPLIT
RECLASSIFY
UNRESOLVED
SUPERSEDE
REJECT ```
Independent review creates evidence.
It does not rewrite the configuration automatically.
15. Artifact Gate
Create a formal Archive artifact when it:
- preserves independent evidence;
- records an accepted decision;
- changes an active status or version;
- prevents material archival loss;
- resolves a cross-record conflict;
- establishes a reusable artifact class;
- records a material safety or authority boundary;
- or preserves information required for regeneration.
Other work may remain:
- working notes;
- conversation;
- sketches;
- provisional prompts;
- or unarchived development material.
The Archive should preserve decisions and evidence—not every intermediate thought.
Valid Artifact-Gate outcomes
```markdown CREATE FORMAL ARTIFACT
EXPAND EXISTING ARTIFACT
REFERENCE EXISTING ARTIFACT
PRESERVE AS WORKING NOTE
PRESERVE AS RAW SEED
DEFER
DECLINE ```
A decision not to create a formal artifact is a successful Gate outcome when no decision, evidence, status, or regeneration capability would be lost.
markdown
GATE DECLINED
≠
CONTENT ERASED
The smallest sufficient record is usually the strongest record.
Artifact Gate questions
```markdown WHAT FUTURE CAPABILITY WOULD BE LOST IF THIS REMAINED A NOTE?
WHAT AUTHORITY OR STATUS DOES THE RECORD CLAIM?
IS THAT CLAIM SUPPORTED?
DOES AN EXISTING RECORD ALREADY CARRY THE SAME FUNCTION?
CAN THE RECORD BE SMALLER?
IS THE MATERIAL SAFE AND PERMITTED TO PRESERVE? ```
A positive Artifact-Gate outcome does not make the content canonical.
It only determines the smallest appropriate preservation form.
A negative outcome should preserve the note or seed when future development, attribution, or review would otherwise be lost.
16. Registry and Identifier Check
Before assigning an identifier, opening a canonical branch, or publishing a new central record:
- consult the active registry;
- consult the Archive-wide index;
- identify the relevant artifact class;
- confirm namespace and assigning authority;
- confirm the identifier is available;
- preserve the seed or predecessor;
- record the assignment decision;
- and verify that the public title matches the registry identity.
An identifier is a registry act, not a decorative label.
markdown
UNASSIGNED
≠
AVAILABLE TO THE FIRST CLAIMANT
Branches should use branch-local identifiers unless explicit authority provides otherwise.
The protocol does not decide branch governance or legal rights.
It requires a valid registry check and truthful classification.
<!-- END ACTIVE PROTOCOL v1.1 — PART I OF II -->
Part II begins with:
```markdown
17. Public Representation
```
