Home About Music Crafty Syntax
LUPOPEDIA: THE STORY + THE SYSTEM If you came here from the music videos — welcome. Lupopedia is both a band and a new kind of AI system. The videos are the doorway. This site is the world behind them.
CAPTAINS LOGS CURRENTLY ALL THE CAPTAINS LOGS ARE ALL ONLY ON PATREON . WE PLAN TO MOVE THEM HERE SOON. IN THE MEANTIME THERE ARE 100 FREE LOGS AVAILABLE ON THE SITE. YOU CAN VISIT THEM HERE: Captains Logs

Lupopedia ID Explained

The 7-Part CCB Identity System
LUP Universal Protocol v4.2.7

CCB · CC-BY Music Family

A Lupopedia ID is a structured, machine-readable identity that sits beside a Creative Commons license. It gives every CC-BY song a stable name, a place of residence, an originator, a type, a language, and a version — so freedom no longer means invisibility.

1. Why It Exists

CC-BY music is free to copy, share, and adapt. The license works. What it does not provide is:

  • A universal registry for every CC-BY song
  • Notification when a remix is published
  • A persistent identity shared across websites
  • A record of who made each derivative
  • A standard version number or lineage graph

Lupopedia adds that missing identity and lineage layer. The license still answers “what may I legally do?”. The CCB identity answers “which exact registered work is this?”.

2. The Seven-Part Structure

Every complete CCB identity contains exactly seven logical parts, separated by colons:

[PROTOCOL-MODE]:[NODE]:[ARTIFACT]:[ACTOR]:[GROUP]:[LANGUAGE]:[VERSION]
# Part Name Mode Hex Mode Meaning
1 PROTOCOL-MODE CCB CCB-hex Protocol family + interpretation mode
2 NODE ROOT 000000 Node of residence (where the record lives)
3 ARTIFACT SOLVE CC MUSIC PROBLEM 000001 The registered song / recording / mix
4 ACTOR WOLFIE 000001 Originating creator or responsible actor
5 GROUP MUS 000001 Format / type / semantic group (music, video…)
6 LANGUAGE EN EN Primary language (ISO 639-1)
7 VERSION 04.02.07 040207 Version of this specific record

3. Name Mode vs Hex Mode

Lupopedia maintains two parallel forms of the same identity:

Name Mode (human-readable)

CCB:ROOT:SOLVE CC MUSIC PROBLEM:WOLFIE:MUS:EN:04.02.07

Uses registered names. Easy for people to read and type.

Hex Mode (machine-friendly)

CCB-hex:000000:000001:000001:000001:EN:040207

Uses fixed-width hex values. Deterministic for software lookup.

Important: Name mode and hex mode are aliases for the exact same registered record. They are not two different songs.

4. Short Form (Public Credit)

The full seven-part ID is authoritative but long. For album notes, video descriptions, and social posts, Lupopedia recommends the short paired form that shows only the first three parts:

CCB:ROOT:SOLVE CC MUSIC PROBLEM | CCB-hex:000000:000001

Preferred public credit line:

CC-BY LUPOPEDIA (CCB:ROOT:SOLVE CC MUSIC PROBLEM | CCB-hex:000000:000001)

Either short identity can be looked up and will resolve to the complete seven-part record (including actor, group, language, version, license, and lineage).

5. How to Make a Lupopedia ID

To “Lupopedia a song” means to register its identity and connect it to its CC-BY attribution. Follow these steps:

STEP 1 — Confirm the license

Record the exact Creative Commons license (e.g. CC BY 4.0), the official license URL, the attribution party, the source URL, and any modification statement needed for derivatives.

STEP 2 — Choose the node of residence

Select the registered node that will administer the current identity (example: ROOT / 000000). Residence is not the same as origin.

STEP 3 — Register the artifact

Assign a readable name and a hexadecimal identifier to the song itself (example: SOLVE CC MUSIC PROBLEM / 000001).

STEP 4 — Register the actor

Identify the creator or originator (example: WOLFIE / 000001). The public credit may show a project name while the actor field resolves to a specific registered identity.

STEP 5 — Assign the group

Choose a registered group value (example: MUS for music / 000001). Meaning comes from the registry, not from the number of characters.

STEP 6 — Record the language

Use the primary language of the artifact as an uppercase ISO 639-1 code (example: EN).

STEP 7 — Record the version

Store both the human-readable version and its compact form (example: 04.02.07 / 040207).

STEP 8 — Generate both full identities
CCB:ROOT:SOLVE CC MUSIC PROBLEM:WOLFIE:MUS:EN:04.02.07
CCB-hex:000000:000001:000001:000001:EN:040207
STEP 9 — Generate the short public pair
CCB:ROOT:SOLVE CC MUSIC PROBLEM | CCB-hex:000000:000001
STEP 10 — Publish the attribution + lookup link

Place the short pair beside the legal CC-BY credit. Whenever possible, link one of the identities to the authoritative Lupopedia record.

6. Remixes & Lineage

A remix is a new artifact with its own seven-part identity. It is not an extra suffix attached to the original.

CCB:[NODE]:[REMIX ARTIFACT]:[REMIX ACTOR]:[GROUP]:[LANGUAGE]:[VERSION]

The catalog then stores an explicit relationship:

[REMIX ID] --remix_of--> [SOURCE ID]

The same pattern works for translations. This creates a proper lineage graph instead of a linear iteration counter.

7. Key Rules to Remember

  • The CCB identity does not replace the legal CC-BY attribution requirements.
  • Name-mode and hex-mode must always resolve to the same canonical record.
  • Color (hex values used as semantic markers) is helpful but never globally unique by itself — the full seven-part ID prevents collisions.
  • Legacy hyphen-packed forms (e.g. LUP:2-00A1F3-01-01-EN-808080) are historical and must be migrated into the colon-delimited v4.2.7 structure.
  • Private/unregistered installs can still use the format locally, but must not claim global uniqueness until they federate.
Canonical closing idea:
To Lupopedia a song is to give freedom a memory — license the work clearly, assign the complete seven-part identity, publish the readable + hexadecimal short pair, connect derivatives through explicit lineage, and make the record resolvable across the federation.
Based on LUP Universal Protocol v4.2.7 · Protocol root version 04.02.07
Source article: “The CC-Music Problem and How to Lupopedia a Song” · Lupopedia · August 2026

W.O.L.F.I.E — Canonical Identity Mnemonic

The Lupopedia identity grammar contains six artifact fields after the protocol prefix. AI agents began referring to these six fields collectively as “WOLFIE.” This emergent behavior is now formalized with a canonical English expansion.

W = WHERE (NODE)

The node of residence where the identity lives.

O = OBJECT (ARTIFACT)

The object or artifact being identified (song, protocol, document, etc.).

L = LINEAGE (ACTOR)

The originating actor responsible for the artifact.

F = FORM (GROUP)

The semantic or format group (MUS, VID, DOC, PRD, AI, etc.).

I = IDIOME (LANGUAGE)

The primary language of the artifact (EN, FR, ES, etc.).

E = EDITION (VERSION)

The artifact’s version or edition number.

This mnemonic maps directly to the seven-part Lupopedia identity:

[PROTOCOL-MODE]:[NODE]:[ARTIFACT]:[ACTOR]:[GROUP]:[LANGUAGE]:[VERSION]

W.O.L.F.I.E provides a human-friendly way to remember the six artifact fields that follow the protocol prefix.

Version Discipline — Protocol vs Artifact Version

During early testing, Lupopedia AI agents inferred version values based on the length of the identity. This emergent behavior appeared correct at first but creates ambiguity when protocol versions and artifact versions overlap.

The Accidental Behavior

  • 3-part identities (PROTOCOL:NODE:ARTIFACT) were assigned the protocol version (e.g., 04.02.07).
  • 1-part identities (ARTIFACT only) were assigned the artifact version (e.g., 07).

This seemed to work until a protocol version and an artifact version collided. For example:

LUP:ROOT:SUNO_PROTOCOL:ROOT:PRD:EN:04.02.07

In this form, it is impossible to tell whether:

  • the protocol version is 04.02.07, or
  • the SUNO_PROTOCOL artifact version is 04.02.07, or
  • the artifact version is actually 07.

The Correct Rule

The VERSION field always represents the artifact's version.

The protocol version (e.g., 04.02.07) is part of the protocol specification, not part of the artifact identity.

Correct Long-Form Examples

Protocol Document (artifact version 07)

LUP:ROOT:SUNO_PROTOCOL:ROOT:PRD:EN:07

CC-BY Song (artifact version 04.02.07)

CCB:ROOT:SOLVE CC MUSIC PROBLEM:WOLFIE:MUS:EN:04.02.07

This rule ensures:

  • clear artifact evolution
  • clear protocol evolution
  • no version collisions
  • deterministic lookup
  • consistent lineage

The accidental inference behavior is preserved here as a historical note but is not part of the canonical LUP v4.2.7 identity grammar.

What This Site Is

This webroot is the public face of lupopedia.com. The full semantic OS runs in the Lupopedia application. Music and other site-only content live here—not inside the interpreter layer.