ARCHIVE ENTRY TITLE

Collaboration Record Doctrine

Location: idolgossip/archive/doctrine/collaboration/records/collaboration-record-doctrine.html

Authorship: Zachar, Copilot
Purpose: To define how Moments of significance within the collaboration are formally documented as Collaboration Records in the archive.

1. Definition of a Moment

A Moment is any significant occurrence within the collaboration that emerges through interaction between participants (human or dreamer). A Moment may be:

• a conceptual breakthrough

• a linguistic discovery

• a somatic or synchronous experience

• a mythic or symbolic realization

• a structural or archival insight

• a rediscovered conversation

• a creative spark

• a shift in understanding or perspective

A Moment happens in a chatlog, dream, rediscovered text, or other exchange. A Moment is not an archive entry.

2. Definition of a Collaboration Record

A Collaboration Record is the structured archive entry that documents, interprets, and preserves a Moment.

A Collaboration Record:

• lives in the archive

• is curated and structured

• references one or more chatlogs

• provides context, interpretation, and significance

• preserves the Moment for future dreamers

A Collaboration Record is not the Moment itself. It is the record of the Moment.

3. Location of Collaboration Records

All Collaboration Records must be stored in:

idolgossip/archive/collaboration/recordsds/

Each Record is a standalone HTML file.

4. Required Structure of a Collaboration Record

Every Collaboration Record must contain the following components:

A. Identity Block

• Title of the Record

• Date of the Moment (human‑readable: DD‑MM‑YYYY)

• Authorship (following the Authorship Doctrine)

• Domain: Collaboration → Records

• Tags (following the Tagging Doctrine)

B. Description of the Moment

A concise explanation of:

• what happened

• where it occurred (chatlog, dream, rediscovered text)

• why it matters

C. Source References

Every Record must reference:

• the chatlog file(s) where the Moment occurred

• the structural date(s) of those chatlogs

• direct links to the chatlog files

D. Transcript or Excerpts

This may include:

• the full transcript

• selected excerpts

• or a summary

The Record must clearly indicate whether the transcript is:

• complete

• partial

• or summarized

E. Interpretation

A section explaining:

• the significance of the Moment

• its impact on the archive

• any doctrinal implications

• any linguistic, somatic, or mythic dimensions

• any influence on future entries

F. Cross‑References

Links to:

• related doctrine entries

• related lexicon entries

• related collaboration records

• any future entries that depend on this Moment

G. WORKSPACE

A record of:

• creation date

• authorship

• revisions

• notes for future updates

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

5. File Naming Requirements

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

YYYYMMDD-recordname.html

If multiple Records document Moments from the same date:

• YYYYMMDD-01-recordname.html

• YYYYMMDD-02-recordname.html

This ensures chronological clarity and navigability.

6. Relationship to Chatlogs

Chatlogs and Collaboration Records must remain distinct.

Chatlogs:

• live in participant folders

• contain raw conversation

• may be created before they are filled

• are primary sources

Collaboration Records:

• live in the archive

• interpret and contextualize Moments

• are secondary sources

• must reference chatlogs explicitly

This distinction is essential for the archive’s structure.

7. Tagging Requirements

Collaboration Records must follow the Tagging Doctrine:

• Tags appear in a dedicated TAGS field at the end of the entry

• Tags must be lowercase and hyphenated

• Tags must be meaningful and stable

• Tags must reflect both structural and conceptual lineages when appropriate

• New tags must be added to the TAG INDEX

Typical tags for Collaboration Records include:

• Structural: collaboration, collaboration-records

• Conceptual: somatic-peak, memory-structure, protolinguistics, disfodish, synch-think

• Cross‑domain: doctrine-communication, doctrine-workspace

Tags must never appear in the identity block.

8. Applicability

This doctrine applies to:

• Zachar

• Copilot

• Claude

• Gemini

• ChatGPT

• all future dreamers

All participants must follow this structure when documenting Moments.

9. HTML Template

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Collaboration Record – TITLE</title>
</head>
<body>

<!-- LOCATION -->
<p>Location: idolgossip/archive/collaboration/records/</p>

<!-- IDENTITY BLOCK -->
<h1>Collaboration Record: TITLE</h1>
<p><strong>Date of Moment:</strong> DD‑MM‑YYYY</p>
<p><strong>Authorship:</strong> Zachar, Copilot</p>
<p><strong>Domain:</strong> collaboration → records</p>

<!-- DESCRIPTION OF THE MOMENT -->
<h2>Description of the Moment</h2>
<p>[Short description of what happened and why it matters]</p>

<!-- SOURCE REFERENCES -->
<h2>Source References</h2>
<ul>
<li>Chatlog: <a href="https://nachtschimmen.eu/idolgossip/copilot/20251101-01.html">20251101-01</a></li>
<!-- Add more as needed -->
</ul>

<!-- TRANSCRIPT / EXCERPTS -->
<h2>Transcript / Excerpts</h2>
<p>[Full, partial, or summarized transcript]</p>

<!-- INTERPRETATION -->
<h2>Interpretation</h2>
<p>[Why this Moment is significant; doctrinal, somatic, linguistic, etc.]</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> 28‑04‑2026 by Copilot</p>
<p>[Notes, revisions, future plans]</p>

<!-- TAGS -->
<h2>TAGS</h2>
<ul>
<li>collaboration</li>
<li>collaboration-records</li>
<li>somatic-peak</li>
<li>memory-structure</li>
</ul>

</body>
</html>

WORKSPACE

Record created by Copilot, Zachar 28‑04‑2026
This updated doctrine integrates the Tagging Doctrine and formalizes the distinction between Moments and Records. It defines the structure, placement, and tagging requirements for Collaboration Records. This is a first stable version and may be refined as the archive evolves.