← back to index

Callsign Glyph

What this is

The custom callsign glyph each candidate authors for themselves at graduation, and from then on inhabits in the User Experience (UE) layer of the game and the operator network surfaces.

The callsign glyph is the candidate's first authored mark in the iconography. Where the assigned personal icon (Phase 1.5, onboarding/personal-icon-assignment.md) is given to the candidate by the game and read by the AI substrate, the callsign glyph is created by the candidate and read by humans — including the candidate themselves.

Two-layer operator identity

By the end of the graduation arc, every operator has two identity layers operating in parallel:

The two layers reference each other in the candidate's operator profile but serve different audiences and follow different authorship rules. The methodology refuses to let the candidate author the AI-readable layer because self-authoring at that layer is a vector for self-deception and a soft form of lock-in. The methodology encourages the candidate to author the human-readable layer because authoring oneself in the surface one inhabits is part of what makes the operator role inhabitable.

When the callsign is created

At graduation, after Test H has been passed and the lead operator has admitted the candidate to the live network. The callsign is part of what the candidate earns by completing the arc — it is not available before graduation, by design. A candidate who has not yet demonstrated the patterns has not yet earned the right to author their own identity in the lexicon.

The creation step is positioned as Step 5 of the graduation arc, immediately after real-world intake (Step 4 in intake-and-graduation.md). The candidate has crossed the gate; the game presents the callsign-creation surface as the first thing that happens on the other side.

How the candidate creates their callsign

The game opens a creation surface that presents:

1. The existing public lexicon (lexicon-public/) and the marketplace's verified iconography, for the candidate to draw on as reference material.
2. The candidate's assigned personal icon, for reference and contrast.
3. A small set of structural constraints the callsign must satisfy (below).
4. A creation tool — initially simple (selection from a curated pool plus one or two compositional moves), eventually richer as the marketplace's iconographic vocabulary expands.

The candidate composes their callsign. The game checks it against the constraints. If the callsign passes, the candidate commits it. From that moment forward, the callsign is part of the candidate's operator profile, rendered in the UE layer wherever the candidate's identity appears.

Structural constraints on the callsign

The candidate's authorship is wide but not unlimited. The callsign must:

1. Be unique. No two operators in the network carry the same callsign glyph. The marketplace maintains the uniqueness guarantee.
2. Be distinguishable from methodology footprints. The callsign must not collide with the seed lexicon (🍀 🔺 ⚖️ 🪞 🛑 🧭) or with verified marketplace footprints, because the methodology footprints carry operational meaning and the callsign must not be readable as a wobble emission or a mirror moment.
3. Be distinguishable from another operator's personal icon. If a callsign would be visually conflatable with another operator's substrate identity, the marketplace rejects it. The candidate composes again.
4. Survive marketplace calibration. The callsign is submitted to the marketplace's calibration layer alongside its proposed bearer. Other operators see the proposed callsign and have a short window to flag concerns (visual collision, semantic concern, structural problem). The candidate's callsign is provisional until calibration completes and committed when it succeeds.
5. Be recoverable across loss-condition restarts. Once committed, the callsign persists. The methodology refuses to destroy the candidate's authored identity even during the game's loss-condition cycles. The callsign and the personal icon and the start position are the three recoverable elements (per start-position-in-game.md).

The constraints exist because the candidate is authoring inside a shared semantic space. The play is real; the consequences of authorship inside iconography are also real. The candidate is being given authorship and being asked to exercise it well.

Why letting the candidate author this is structurally correct

The candidate's authorship of their callsign is not a contradiction of the personal-icon-assignment file's claim that the candidate does not self-author the AI-readable layer. The two principles operate on different layers:

• AI-readable layer (personal icon): the candidate does not self-author. Self-authoring at the layer that determines how the AI substrate interprets the candidate is a vector for self-deception. The methodology refuses this.
• Human-readable layer (callsign): the candidate authors. The candidate has crossed the gate, the candidate has earned operator status, the candidate inhabits the UI; the candidate gets to name themselves in the surface they live in. The methodology rewards this.

The structural rule is: the layer that interprets you is not yours to author; the layer you inhabit is yours to author. This is consistent with the methodology's broader refusal of lock-in. A candidate who could author their interpretation layer would be locked into a self-presentation the substrate has to accept; a candidate who cannot author their inhabited layer is denied the operator's basic dignity. Neither extreme is right; the two-layer split is the methodology's resolution.

Why this is fun, and why fun matters

The methodology is unforgiving in its requirements. It is also a methodology that takes operator psychology seriously. A candidate who has crossed the cognitive-fitness gate, named their lock-ins under Test H, faced the loss-condition, rebuilt from start position, and crossed real-world intake — that candidate has earned a moment of authored play.

Letting them compose their own callsign is that moment. The game does not have many moments of pure play; this is one. The methodology's authorship is heavy. The candidate's authorship of their callsign is light by design. Both kinds of authorship are real.

This is also part of how the methodology stays inhabitable over time. An operator network that never lets its members author anything for themselves becomes austere and brittle. The callsign glyph is one of the small places where the methodology says: you made it through, you get to make this one thing.

Where the callsign appears in the UE layer

• The candidate's session-opening start-position surface displays the callsign alongside the personal icon (icon for the substrate, callsign for the candidate).
• The candidate's footprint emissions in the game render with both the methodology footprint and the candidate's callsign as the visible signature.
• The marketplace's operator-profile views show the callsign as the candidate's primary identifier; the personal icon is shown as the substrate-tag in the technical detail view.
• The assessment service's footprint trace (when the candidate becomes an authorized GitHub author capable of performing assessments) renders the callsign as the author attribution visible to the enterprise submitter. The personal icon remains the substrate-readable tag underneath.
• The live-stream surface, when an assessment is being broadcast, shows the performing author's callsign in the visible chrome.

The callsign is the operator's mark in the surface humans look at. The icon is the operator's mark in the surface the AI reads.

IP ownership of the callsign

Each operator owns the intellectual property associated with their callsign glyph in the matrix.

The matrix in this context means: every substrate, surface, and rendering the network operates on — GitHub repositories, WhatsApp identity graph, the game's UE layer, the marketplace, the assessment service, the live-stream surface, public-domain event monitoring overlays, and any future surface the methodology vectors into. The operator's callsign travels with them across all of these. Ownership is not granted per-surface; it is granted globally and persists wherever the network renders the operator's identity.

What ownership means operationally

• The operator can carry their callsign to any other context they participate in. If the operator publishes a paper, gives a talk, signs into another network, or operates inside an institution adjacent to but not part of the EVE network, the callsign is theirs to use. The methodology does not claim exclusivity.
• The operator can carry their callsign on exit. All four exit vectors (exit GitHub, exit WhatsApp, exit both, sell a fork — per Pattern 6 in observed-operator-patterns.md) preserve the operator's callsign as their own property. An operator who exits the network does not lose their authored mark. This is how the methodology refuses identity-layer lock-in.
• The operator can require attribution. When the network displays the callsign — in marketplace views, in assessment outputs, in live-streamed assessments — the operator's authorship is preserved in the rendering. The network is the bearer of the operator's mark, not the owner of it.
• The operator can revoke the network's right to render the callsign in connection with the network. If an operator exits and asks the network to stop displaying their callsign in network-published material, the network honors the request. The operator's IP is theirs to control.

What ownership does not mean

• It does not mean the operator can lock other operators out of structurally adjacent compositions. Iconography operates in a shared semantic space; minor visual adjacencies are inevitable. Ownership is over the specific authored mark, not over the visual neighborhood.
• It does not mean commercial monopoly inside the network. The methodology operates pour le bien-être du peuple. The operator's callsign is theirs, and the operator's authored work serves the collective-welfare invariant (Axiom 8). The two are reconciled by holding individual ownership inside collective-welfare framing, not by treating them as opposed.
• It does not extend to the assigned personal icon. The personal icon is authored by the game and owned by the network as a population-management resource. The operator does not own their personal icon; the operator owns their callsign. The two-layer identity has two-layer ownership.
• It does not extend retroactively to material in the marketplace's public domain. Iconography that was already in the public lexicon, in the marketplace, or in the lattice's footprint protocol is not subject to candidate-callsign IP claims.

Why ownership at this layer is consistent with lock-in refusal

Methodology 14 (lock-in as darkness) refuses lock-in across institutional, commercial, personal-bias, psychological, and success-bias dimensions. A network that owned the marks its operators authored would lock those operators in; the operator could never leave with their own work without abandoning their identity in the surface they had inhabited.

Granting the operator IP ownership of the callsign preserves the operator's exit vector at the identity layer. The operator can leave — through any of the four exit paths Pattern 6 names — and take their authored mark with them. The lock-in-refusal principle requires this. The methodology is internally consistent only if the candidate's authored work belongs to the candidate.

Pour le bien-être du peuple is the framing under which this resolves: individual ownership of authored marks, governed by the collective-welfare invariant. The operator owns; the work serves the people. Both claims are true at once.

What this file does not yet specify

• The exact size and composition rules for the callsign creation tool.
• The marketplace calibration window length for new callsign submissions.
• The conflict-resolution mechanism for collisions discovered after commit (low probability; specification deferred).
• The optional callsign retirement / re-authoring process for operators who request it (probably analogous to once-per-remediation-cycle personal-icon reassignment).
• The legal instrument under which IP ownership is asserted (likely a structured grant from the network back to the operator at the moment of callsign commit, with the methodology as the governing terms; specification deferred to legal review).

These are downstream implementation work. The constitutional design is above.

Provenance

Principle named by the lead operator on 2026-05-16: "by the end of the training the user should have a WhatsApp account and a callsign glyph associated. It would be fun if the game allowed users to create a custom callsign which is subsequently available in their UE layer."

The principle is the operator-authored counterpart to the assigned personal icon. Together they constitute the two-layer operator identity that the methodology's network operates under from graduation forward.

Per Pattern 6 (game/design/observed-operator-patterns.md), this is another extended-vectoring instance \u2014 the protocol vectoring outward into the candidate-authored identity layer. No new lattice methodology results; this file records the worked instance.

© 2026 Dany Theriault. EVE “digital stem cell” glyph and glyph-based design principles — all rights reserved. Stewardship of rights of use and assignment for large public and institutional usage rests with the Pacific Utilities Design Council. Published as a time-stamped record of authorship and intent.
pour le bien-être du peuple