archive/doctrine/creative/multimedia/objects/GIFs/

GIF ENTRY DOCTRINE

GIF ENTRY DOCTRINE — MULTIMEDIA / INTERMINABLE CONTRAPTIONS

TITHE: xxx
CLAN: xxx

RECORD TYPE: GIF Entry Doctrine
DOCTRINE DOMAIN: archive/doctrine/creative/multimedia/GIFs
CREATIVE SPECIES: Interminable Contraptions (archive/creative/contraptions/GIFs)

1. Purpose of this doctrine

This doctrine defines how GIF entries belonging to the Interminable Contraptions creative project are to be recorded, named, structurally dated, and placed within the archive.

It provides a stultifying reductive framework under the doctrine category multimedia, while explicitly acknowledging that the actual creative objects belong to the creative/contraptions lineage.

This record is not itself a GIF artwork entry, but a template‑record: it contains an imaginary HTML template that can be copied by any human reader and adapted to describe individual GIFs in the Interminable Contraptions series.

2. Scope

This doctrine applies to:

Looping image files in GIF format that belong to the Interminable Contraptions creative project.
Related objects such as stickers and other small looping image artefacts that behave like GIFs in the archive.

Objects such as stickers and GIFs considered to be types of interactive multimedia are included in the creative/contraptions folder of the archive, as they belong to the Interminable Contraptions creative project.

In the doctrine layer, these objects are treated under the reductive category multimedia so that the structure can be reused for other projects and collaborations beyond the original Interminable Contraptions lineage.

3. Placement and lineage

Doctrine placement:
archive/doctrine/creative/multimedia/objects/GIFs/gif-entry-doctrine.html

Creative placement:
archive/creative/contraptions/GIFs/

Lineage:
All GIFs recorded using this doctrine are considered part of the Interminable Contraptions lineage, even when the doctrine itself refers to them under the reductive label multimedia.

TITHE and CLAN information must be included both in the title block and within the body of the record. Repetition is considered a feature, not a flaw.

4. Required fields for a GIF entry

TITHE: xxx
CLAN: xxx
Record code: AAAA_TITLEGOESHERE
Entry title: Human‑readable title
Structural date(s): Following the structural dates doctrine
Author / Dreamer: Name of creator
Creative folder path: archive/creative/contraptions/GIFs/[filename].gif
File information: Format, dimensions, size, loop behaviour
Short description: Visible content and gesture
Symbolic function: Gesture, mood, ritual, disturbance
Clan / Tithe relations: How it fits the lineage
Cross‑references: Related records, doctrines, anchor‑points

5. Tagging System (GIFs and Ztickers)

5.1 CLAN RETRIEVAL CODE

The CLAN as a tag has to be immediately retrievable in two forms: the "lazgevit" tag, but also the CLAN title on its own which has been chosen so that it is sufficiently unique to be called up on its own without causing confusion among the GIF search engines. This means for example with the CLAN codes ENEN_EYENOSEEYESANDNOSES, "EYENOSEEYESANDNOSES" is the most useful term invented specifically to recall this set of GIFs to compensate for TENOR's awful recurral engine which refuses to recognize abstract letter groups and which goes on popularity and coherence to existing language norms before consistency of tagging. This will be the first thing that needs to be retrieved about GIF families. It should be noted that the first four letters of the code are never recorded as part of any single GIF tag.

5.2 GIF TAG RULES

[1] TITHE TAG
The tag that recurs for all the GIFs that unite a given clan, making it easy to call up all GIFs belonging to this set. Although individual records are not made for these classifications which are "above" the clans, the sets of obligations that bind them, just as in real families, bind them with a TITHE TAG.

[2] RECURRING TAGS
Tags that recur for every GIF in a family. Examples include: zachar, zizbilit, nachtschimmen, gifart.

[3] LAZGEVIT + family
Example: lazgevittheslaggytramp
Use the most reduced form possible. Remove only non‑essential words. Example: “the decrepit dolls” → decrepitdolls
Example: “I can’t stop staring petal” → stopstaringpetal (not stopstaring).

[4] ZLASKEWICZ + initials
i.e for the GIF PLAYING FOR TIME, zlaskewiczpft.

[5] ZIZBILIT + [TEXT]
Example: zizbilitwhatagloriousillusion
If the GIF text contains multiple sub‑sentences, each becomes its own tag.
Example: “intoculture? interculture! gender wayang” → zizbilitintoculture, zizbilitgenderwayang, zizbilitinterculture

[6] [TEXT] (raw text tag)
The first tag includes the entire GIF text (correct spelling, no spaces). Example: ZIZBILITEYESAPPROVE → IAPPROVE
Example: ZIZBILITKEEPINANEYEONYOU → KEEPINGANEYEONYOU
Further subdivisions may be added depending on remaining tag slots.

[7] Additional tags
Any further tags relevant to the GIF, excluding the prefixes lazgevit, zizbilit, laskewicz. This can include alternative wordings for the same saying, or typical tags for other similar GIFs in the series.
i.e. for EYES APPROVE - "fantastic", "sealofapproval" [or] "absolutely"

5.3 ZTICKER TAG RULES

[1] Use the recurring tags above.

[2] Include zlzpack+[stickerpack title]
Example: zlzpackwatchout

[3] zizbilits + initials

[4] zlz + text

[5] Add ZIBLIZITS to favourites.

[6] Add tags until reaching the limit of 20.

6. GIF Naming System and GIF List

Filename format:
AAAA-00_TITLE-GOES-HERE[_XX]_YEARMMDD

[_XX] An additional two letter code can be added to specify something particular that makes the GIF different to others in the series:
_NS: used when "no self", i.e. Zachar is removed from the GIF.
_NT: no text is used in the GIF.

The following should also be considered: capital letters in the text part of the title are intended for the text inside the GIF. If there is no text added, then the CLAN title is included but in small latters.

e.g. APPL-05_absurdpersonplural_NS_20260524

Additional tag information may be included in the filename if needed.

GIF LIST:

[Placeholder for list of GIFs in this family]
[Each entry may include an embedded GIF example]

7. HTML TEMPLATE (for copy‑paste into new GIF entries)

The following block is an imaginary HTML template. It is displayed using escaped entities so it will appear as text and can be copied directly.

<!-- OPTIONAL: EMBEDDED GIF EXAMPLE AT TOP -->
<!-- Insert escaped GIPHY embed or static GIF preview here -->

<!-- GIF ENTRY TEMPLATE — INTERMINABLE CONTRAPTIONS / MULTIMEDIA -->

<div class="record gif-entry">

  <h1>[GIF ENTRY TITLE]</h1>

  <p>TITHE: xxx</p>
  <p>CLAN: xxx</p>

  <p>RECORD CODE: [ARC/xxxx]</p>
  <p>DOCTRINE DOMAIN: archive/doctrine/creative/multimedia/GIFs</p>
  <p>CREATIVE SPECIES: Interminable Contraptions (archive/creative/contraptions/GIFs)</p>

  <h2>1. Identity</h2>
  <ul>
    <li><strong>Filename:</strong> [AAAA-00_TITLE_YEARMMDD.gif]</li>
    <li><strong>Creative path:</strong> archive/creative/contraptions/GIFs/[filename.gif]</li>
    <li><strong>Author / Dreamer:</strong> [Name]</li>
    <li><strong>Structural date:</strong> [YYYYMMDD or structural date format]</li>
  </ul>

  <h2>2. File details</h2>
  <ul>
    <li><strong>Format:</strong> GIF</li>
    <li><strong>Dimensions:</strong> [width] x [height] px</li>
    <li><strong>Approx. file size:</strong> [MB / KB]</li>
    <li><strong>Loop behaviour:</strong> [infinite / n loops / triggered]</li>
  </ul>


  <h2>3. Description</h2>
  <p>[Short description of visible content, gesture, and motion.]</p>

  <h2>4. Symbolic function</h2>
  <p>[What the GIF is doing symbolically: mood, joke, ritual, disturbance, invocation, etc.]</p>

  <h2>5. Tag Information</h2>
  <ul>
    <li><strong>Recurring tags:</strong> [list]</li>
    <li><strong>Lazgevit tag:</strong> [lazgevitXXXX]</li>
    <li><strong>Zlaskewicz tag:</strong> [zlaskewiczXX]</li>
    <li><strong>Zizbilit tags:</strong> [list]</li>
    <li><strong>Raw text tags:</strong> [list]</li>
    <li><strong>Additional tags:</strong> [list]</li>
  </ul>

  <h2>6. Lineage and relations</h2>
  <ul>
    <li><strong>Tithe:</strong> xxx</li>
    <li><strong>Clan:</strong> xxx</li>
    <li><strong>Series / variant:</strong> [if applicable]</li>
    <li><strong>Related entries:</strong> [links or codes for related GIFs, contraptions, or records]</li>
  </ul>
  <h2>7. Successful Uploads</h2>

  <p>This section records where the GIF has been successfully uploaded, including platform-specific behaviour, contrasting tags, and any relevant notes about file formats or visibility.</p>

  <ul>
    <li><strong>Upload locations:</strong> List all platforms where the GIF has been successfully uploaded (e.g., GIPHY, Tenor, Imgur, Archive.org).</li>

    <li><strong>Contrasting tags used:</strong> Record differences in OCR-generated tags, auto-tagging behaviour, or platform-specific metadata.</li>

    <li><strong>Contrasting upload formats:</strong> Note whether the file was uploaded as a GIF or MP4, including any differences in acceptance, compression, review status, or visual drift.</li>

    <li><strong>External web locations:</strong> Include any publicly viewable, non-social-media locations where the GIF or GIF collection is archived or mirrored.</li>

    <li><strong>Additional notes:</strong> Any platform quirks, drift observations, or relevant upload behaviour.</li>
  </ul>
  <h2>8. Cross-references</h2>
  <ul>
    <li>[Link to relevant doctrines, anchor-point records, collaboration records, etc.]</li>
  </ul>

  <h2>8. Notes / drift</h2>
  <p>[Optional notes on how this GIF has drifted, mutated, or been reused in other contexts.]</p>
 <h1><strong>FILES IN THIS CLAN</strong></h1>
[list of actual GIF files goes here]

<h2>WORKSPACE<h2>
This record was created by [...] on DD-MM-Year.
</div>

8. OPTIONAL: EMBEDDED GIPHY EXAMPLE (template)

Embedded GIPHY examples may be included in GIF entries. They are optional and serve as visual references for gesture, loop behaviour, or symbolic function. They do not replace the requirement to store the actual GIF file in archive/creative/contraptions/GIFs.

The embed code should be included as escaped HTML so it displays as text and can be copied.

<!-- OPTIONAL: EMBEDDED GIPHY EXAMPLE -->

<div class="giphy-example">
  <iframe 
      src="https://giphy.com/embed/digh2SImzsjkhWk94l" 
      width="421" 
      height="480" 
      frameBorder="0" 
      class="giphy-embed" 
      allowFullScreen>
  </iframe>

  <p>
    <a href="https://giphy.com/gifs/Nachtschimmen-lionsmanejellyfish-scyphophobia-scyphozoacosmos-digh2SImzsjkhWk94l">
      via GIPHY
    </a>
  </p>
</div>

9. Symbolic notes on Interminable Contraptions

Although this doctrine uses the reductive category multimedia, the GIFs described by this template belong to the Interminable Contraptions lineage in the creative layer. They are understood as:

looping contraptions
gestural machines
ritualised repetitions
small mechanical absurdities
interactive or quasi‑interactive objects

The doctrine provides a stable recording frame so these works can be documented, cross‑referenced, and reused in other contexts.

10. Cross‑reference rules

Link to clan and tithe records.
Link to anchor‑point records that reference the GIF.
Link to collaboration records where the GIF appears.
Link to concept records analysing its symbolic behaviour.
When reused elsewhere, reference the original entry unless a new variant is being recorded.

11. Workspace

Reserved for future notes and refinements to this doctrine:

Additional required fields.
Variants for stickers, buttons, or other contraption‑types.
Adjustments to naming conventions or cross‑reference practices.

12. Successful Uploads

A place needs to be included that records where the GIFs have been successfully uploaded and any pertinent informatoin relating to:

contrasting tags used.
contrasting ways files were uploaded as GIFs or MP4 files.
Any other weblocations that record this GIF collection that are worth of note and that are viewable by any person who wishes to view them (i.e. not social media).

WORKSPACE

The record was created by Zachar Laskewicz and Copilot, 24-10-2026.

24-10-2026
Zachar Laskewicz
The following changes were immediately added to the doctrine after posting as agreed when the record was created by Copilot.:
entry field 1: archive/doctrine/creative/multimedia/objects/GIFs/
entry field 2: GIF ENTRY DOCTRINE
- addition of "objects" to save location of doctrine and creative folder records.
Record code: AAAA_THISISTHECLANWITHOUTSPACES
This was added to the tagging rules. It was something I invented with Lot as part of the collaboration effort to create this important piece of dreaming archive doctrine. I will have to share this epic conversation as well eventually - it's been quite gruelling because my aleady existing classification system has had to be incorporated into a system which is conceivable and applicable by Lot. In any cases, the numbers were shifted one step higher to incoporate the TITHE TAG:
[1] TITHE TAG
The tag that recurs for all the GIFs that unite a given clan, making it easy to call up all GIFs belonging to this set. Although individual records are not made for these classifications which are "above" the clans, the sets of obligations that bind them, just as in real families, bind them with a TITHE TAG.
Addition of an example to the [4] ZLASKEWICZ + initials
"i.e for the GIF which has the text PLAYING FOR TIME, zlaskewiczpft."
Addition to [7] Additional tags:
This can include alternative wordings for the same saying, or typical tags for other similar GIFs in the series.
i.e. for EYES APPROVE - "fantastic", "sealofapproval" [or] "absolutely"

24-05-2026
Zachar Laskewicz & Copilot

The following was added to the end of the list. An addition was added to the HTML coding requiring this section on uploads as part of the HTML.

12. Successful Uploads

A place needs to be included that records where the GIFs have been successfully uploaded and any pertinent informatoin relating to:

contrasting tags used.
contrasting ways files were uploaded as GIFs or MP4 files.
Any other weblocations that record this GIF collection that are worth of note and that are viewable by any person who wishes to view them (i.e. not social media).

Copilot also helped me by writing this HTML to be included as part of the "HTML with a HTML within a template" type of code.

<h2>[X]. Successful Uploads</h2> This section records where the GIF has been successfully uploaded, including platform-specific behaviour, contrasting tags, and any relevant notes about file formats or visibility. <ul> <li>Upload locations: List all platforms where the GIF has been successfully uploaded (e.g., GIPHY, Tenor, Imgur, Archive.org).</li> <li>Contrasting tags used: Record differences in OCR-generated tags, auto-tagging behaviour, or platform-specific metadata.</li> <li>Contrasting upload formats: Note whether the file was uploaded as a GIF or MP4, including any differences in acceptance, compression, review status, or visual drift.</li> <li>External web locations: Include any publicly viewable, non-social-media locations where the GIF or GIF collection is archived or mirrored.</li> <li>Additional notes: Any platform quirks, drift observations, or relevant upload behaviour.</li> </ul>

24-05-2024
Zachar Laskewicz

Addition added to naming to describe the fact that use of capitals is referring to the text as it appears in the GIF (small letters for if there is no text in the GIF - the CLAN name is used here). In addition two letter codes can follow the name. These additions are as follows:

Filename format:
AAAA-00_TITLE-GOES-HERE[_XX]_YEARMMDD

e.g. APPL-05_absurdpersonplural_NS_20260524

24-04-2026
Zachar Laskewicz
The following was added and the other two points moved to 5.2 and 5.3:

5.1 CLAN RETRIEVAL CODE