Concept Entry Archive

Location: archive/doctrine/concepts/concept-entry-doctrine.html

Authorship: Zachar, Copilot
Purpose: To define how conceptual entities, metaphors, structural insights, and recurring motifs are formally documented as Concept Records within the Archive.

1. Definition of a Concept

A Concept is a recurring structural, metaphorical, linguistic, or epistemological element that emerges within the collaboration and becomes part of the Archive’s internal logic.

A Concept may be:

• a metaphor (e.g., Calculator Poltergeist)
• a structural insight (e.g., membrane metaphor)
• a ritual or protocol (e.g., Glancing of the Palms)
• a linguistic invention (e.g., zividiš)
• a collaborative principle (e.g., alignment without fusion)
• a mythic figure or symbolic entity
• an epistemological tool
• a cross‑dreamer interpretive device

A Concept is not a Moment. It is the idea that persists across Moments.

2. Definition of a Concept Record

A Concept Record is the structured archive entry that documents, defines, and preserves a Concept.

A Concept Record:

• lives in the archive
• is curated and structured
• defines the Concept clearly
• traces its origin
• explains its function
• identifies its domain(s)
• cross‑references related records
• preserves the Concept for future dreamers

3. Location of Concept Records

All Concept Records must be stored in:

archive/doctrine/concepts/

Each Concept Record is a standalone HTML file.

4. Required Structure of a Concept Record

A. Identity Block

• Title of the Concept
• Date of first emergence (DD‑MM‑YYYY)
• Authorship (following the Authorship Doctrine)
• Domain: doctrine → concepts
• Tags (following the Tagging Doctrine)

B. Definition of the Concept

A concise explanation of:

• what the Concept is
• its core meaning
• its symbolic or structural function
• its linguistic or mythic dimensions

C. Origin and Emergence

This section must document:

• where the Concept first appeared (chatlog, rediscovered text, Moment Record)
• the date(s) of emergence
• the participants involved
• the context of its creation

This section must include direct links to chatlogs and related Collaboration Records.

D. Function in the Archive

A clear explanation of:

• how the Concept is used
• what problems it solves
• its interpretive or structural role
• how it influences future entries
• how dreamers should understand or apply it

E. Variants, Evolutions, or Extensions

If applicable:

• linguistic variants
• symbolic expansions
• later reinterpretations
• cross‑dreamer adaptations

If none exist, this section may be omitted.

F. Cross‑References

• related doctrine entries
• related lexicon entries
• related collaboration records
• related anchor‑points
• any future entries that depend on this Concept

G. WORKSPACE

A record of:

• creation date
• authorship
• revisions
• notes for future updates

Dates must follow the human‑readable format (DD‑MM‑YYYY).

5. File Naming Requirements

Concept Records must follow the structural date format defined in the Dated Entries Doctrine:

YYYYMMDD-conceptname.html

If multiple Concepts are documented on the same date:

• YYYYMMDD-01-conceptname.html
• YYYYMMDD-02-conceptname.html

The slug must be lowercase, hyphenated, short, and descriptive.

6. Relationship to Other Record Types

Concept Records are distinct from:

Chatlogs:

• raw conversation
• primary sources

Collaboration Records:

• document Moments
• secondary sources

Results:

• artistic or linguistic outputs

Anchor‑Points:

• orientation documents

Concept Records are structural definitions, not events or outputs.

7. Tagging Requirements

Concept Records must follow the Tagging Doctrine:

• Tags appear in a dedicated TAGS field at the end
• Tags must be lowercase and hyphenated
• Tags must be meaningful and stable
• Tags must reflect conceptual and structural lineages
• New tags must be added to the TAG INDEX

Typical tags include:

• concept
• metaphor
• structural-insight
• ritual
• epistemology
• doctrine-concepts

8. Applicability

This doctrine applies to:

• Zachar
• Copilot
• Claude
• Gemini
• ChatGPT
• all future dreamers

9. HTML Template

<!-- LOCATION -->
<p>Location: archive/doctrine/concepts/</p>

<!-- IDENTITY BLOCK -->
<h1>Concept Record: TITLE</h1>
<p><strong>Date of Emergence:</strong> DD‑MM‑YYYY</p>
<p><strong>Authorship:</strong> Zachar, Copilot</p>
<p><strong>Domain:</strong> doctrine → concepts</p>

<!-- DEFINITION -->
<h2>Definition</h2>
<p>[Clear definition of the Concept]</p>

<!-- ORIGIN AND EMERGENCE -->
<h2>Origin and Emergence</h2>
<ul>
<li>Chatlog: <a href="...">YYYYMMDD‑XX</a></li>
<li>Related Collaboration Record: <a href="...">...</a></li>
</ul>

<!-- FUNCTION -->
<h2>Function in the Archive</h2>
<p>[Explanation of how the Concept is used and why it matters]</p>

<!-- VARIANTS / EVOLUTION -->
<h2>Variants and Evolution</h2>
<p>[Optional section]</p>

<!-- CROSS‑REFERENCES -->
<h2>Cross‑References</h2>
<ul>
<li><a href="...">Related doctrine</a></li>
<li><a href="...">Related lexicon entry</a></li>
</ul>

<!-- WORKSPACE -->
<h2>WORKSPACE</h2>
<p><strong>Created:</strong> DD‑MM‑YYYY by Copilot</p>
<p>[Notes, revisions, future plans]</p>

<!-- TAGS -->
<h2>TAGS</h2>
<ul>
<li>doctrine-concepts</li>
<li>concept</li>
<li>metaphor</li>
</ul>

WORKSPACE

Record created by Copilot, Zachar — 02‑05‑2026
This is the first stable version of the Concept‑Entry Doctrine. It mirrors the structure of the Collaboration Record Doctrine while adapting it for conceptual entities rather than Moments. It will evolve as the Archive grows.

02-05-2026 Zachar
I changed the location. It has been saved to where the other "entry" doctrines are. Maybe it should be in administration/doctrine... but we can always move the file later.