A proposal for the UniverZe's meaning layer: how a sign is represented, how interpretations of it emerge, and how the history of those interpretations is kept — so the record preserves not only information, but the evolving relationships through which information becomes meaningful. It stands here as it was written: a proposal, under Founder review — not canon, not built, and marked as neither.
Document metadata
Document ID: L0-DOC-CSSL-001
Version: 0.2.0-draft
Status: Full architectural specification — Founder review
Classification: Computational Semiotics / Meaning and Interpretation Substrate
Implementation targets: Python, object networks, property graphs, RDF, relational/event stores, knowledge graphs, policy engines
Related: Infinite Semiosis Substrate Layer (ISSL), BDGA v2.0, Troupe-OS knowledge graph, institutional memory, AI employee runtime, reality fission and merge, semantic workflow compiler
Authority: Proposal only. No canonical change, production authorization, or bypass of the Founder Approval Gate.
Scopes, in house terms: organization = the Troupe · agent = the seat · project = the department or world · and the living grain beneath them — Execs, mentors, pods, squads, podawans. A scope may rest at any level.
Filed: The Library, under Proposals, 15 November 2026. The document text stands as authored; the keeper's notes are marked where they appear.
The Computational Semiotics Substrate Layer provides Troupe-OS with a reusable computational foundation for representing signs, their objects, the interpretations they produce, and the relationships through which meaning develops over time.
Its central question is:
How did a person, agent, or process interpret something; what did that interpretation produce; what context and evidence informed it; and how did it influence subsequent understanding or action?
CSSL makes meaning-processing observable, traceable, queryable, and reusable across organizational systems.
It is intended to support:
CSSL is more than a knowledge graph schema. It is a meaning-processing model that can operate across multiple storage, reasoning, and execution systems.
CSSL draws on Peircean semiotics and the triadic relationship among representamen, object, and interpretant.
A sign is not treated as a symbol with a permanently fixed meaning. Meaning arises through a relationship among a representation, what it refers to, and the interpretive effect produced in context.
A sign is modeled as:
Sign = (Representamen, Object, Interpretant)
An interpretant is not necessarily a human-readable definition. It may be a structured inference, changed agent state, new relationship, generated hypothesis, or decision proposal.
An interpretant may become the representamen of a subsequent sign process:
Sign → Interpretant → New Sign → Further Interpretant → Continued Semiosis
The system preserves the lineage of these transitions. It does not assume that a chain has reached ultimate meaning merely because a task has ended, an agent has stopped, or an interpretation has been selected for current use.
CSSL supports three descriptive sign grounds:
These grounds may overlap. They should be represented as facets rather than forcing every artifact into one exclusive category.
Additional semiotic distinctions may be added as properties without changing the core triad.
CSSL distinguishes the following entities so that a representation, its referent, an interpretation, and an action are never casually conflated.
A registered semiotic unit connecting a representamen to an object and providing the context in which interpretants may be produced.
The form through which a sign is available to an interpreter. It may contain a payload directly or point to a durable artifact in another substrate.
The subject to which a sign refers. Objects may be known, partially known, disputed, external, or represented by other signs. Uncertainty about an object must remain expressible.
The effect or meaning produced by an interpretive event. It may be descriptive, inferential, procedural, behavioral, or action-oriented.
A human, AI employee, model, workflow stage, policy engine, sensor-processing system, or other process capable of producing an interpretation. An interpreter has identity, role, context, capabilities, and applicable constraints. Interpreter status does not confer decision authority.
A record of an interpreter applying an interpretive process to a sign under a defined context and producing one or more interpretants.
Conditions that materially shape interpretation: time, task, reality/fork, agent state, relevant knowledge, language, cultural frame, policy environment, source material, and other applicable conditions.
A source, observation, record, or other support used to justify or evaluate an interpretation. Evidence remains distinguishable from the interpretation it supports.
The traceable relationships among a sign, interpretive event, interpretant, subsequent signs, and later revisions, challenges, or uses.
A decision is an authorized selection or determination made using interpretations and other inputs. An action is an execution resulting from a decision or other authorized instruction. Neither is interchangeable with an interpretant.
CSSL treats the knowledge graph as capable of carrying a semiotic layer.
Nodes may represent signs, representamina, objects, interpretants, interpreters, contexts, evidence, decisions, and actions. Edges express typed relationships.
Core relationships include:
| Relationship | Meaning |
|---|---|
| represents | A representamen expresses or stands for a sign |
| refers_to | A sign points to an object |
| interpreted_by | A sign is processed by an interpreter |
| produces | An interpretive event produces an interpretant |
| mediates | A sign or event mediates an interpretant |
| becomes_sign | An interpretant is reused as a representamen |
| supported_by | An interpretation is supported by evidence |
| challenged_by | An interpretation is challenged by another interpretation or evidence |
| derived_from | A sign or interpretation has a traceable source |
| contextualized_by | An interpretation is associated with context |
| continues | Lineage continues across events or reality forks |
| conflicts_with | Interpretations are in tension or disagreement |
| revises | A later interpretation revises an earlier one |
| supersedes_for_scope | A later interpretation is selected in place of another for a defined scope |
| used_by | An interpretation is referenced by a workflow, decision, or action |
Relationships preserve direction, identity, provenance, and scope. They explain how meaning is connected, not merely decorate a graph.
Every registered sign receives a durable identifier. ULID, UUID, or content-addressable identifiers may be used, provided identity and collision behavior are defined.
A sign should carry:
Scope may include organization, reality/fork, agent, project/workspace, task/workflow, and explicitly authorized global applicability.
Existence in one scope does not automatically make a sign globally authoritative or shareable. Accessibility and shareability remain distinct.
Provenance should point to durable source records wherever possible: files, pages, messages, tool results, event records, human decisions, external references, or prior signs.
A standard interpretive event proceeds through these stages:
Multiple candidate interpretations are supported. A single input does not require a single output.
These are conceptual operations that may be exposed as APIs, functions, services, graph transactions, or workflow actions.
CSSL supports continuing semiosis without requiring every interpretive chain to reach a final interpretant.
The system distinguishes:
These are different events.
An implementation may bound an execution by time, cost, scope, depth, or task requirements while retaining the ability to revisit a sign and continue interpretation later.
A stopping condition is an execution decision, not proof of ultimate meaning.
Interpretive states may include active, supported, contested, unresolved, dormant, superseded-for-scope, and selected-for-use. These labels describe current status and retain historical transitions.
Keeper's note
Graph here means the ledger of relations, not the rendered UniverZe; the world is not a graph.
CSSL adds a semiotic dimension to the knowledge graph. The graph can represent:
Illustrative queries:
Semiotic similarity must not be treated as proof of equivalence. Retrieval results retain source, scope, and relationship type.
CSSL may coexist with entity, event, provenance, identity, and other graph projections. It does not require all organizational data to live in one physical graph.
CSSL treats memory as more than stored content. It preserves the development and use of meaning.
A useful memory lineage may connect:
The trace journal records what operations occurred. The semiotic graph records relationships that make those operations intelligible. They are complementary views.
Implementations may use hot/cold storage, relational tables, graph databases, DuckDB, Parquet, object storage, or other suitable systems, provided durable identifiers and reconstructable lineage are preserved.
CSSL can provide a meaning-and-interpretation layer across BDGA's cultural lifecycle:
CSSL does not replace BDGA or redefine its existing levels. It is a candidate substrate for making semantic relationships across the lifecycle observable.
An agent may interpret a cultural principle, but that interpretation does not become a genome-level change without applicable authorization.
Keeper's note
Performance Folder — the house name for what this section calls an interpreter profile: a view drawn from the agent's charter and accreditation, never a second registry kept beside them.
AI employees are potential interpreters within CSSL.
An interpreter profile may describe identity and role, domain and task scope, available sources and context, permitted operations, charter constraints, output types, evidence expectations, and escalation conditions.
Agents may generate multiple interpretations, compare peer interpretations, challenge unsupported conclusions, request missing context, and explain their reasoning lineage.
The system preserves distinctions among:
No agent gains authority merely by producing an interpretation, being highly confident, or serving as a reviewer.
A semantic workflow can be modeled as a sequence or network of interpretive events.
Possible stages include intake and registration, context retrieval, interpretation, evidence gathering, peer challenge, comparison, policy evaluation, human review, decision preparation, authorized action, and trace/memory update.
Different roles may use different interpreter profiles. Workflow compilation can select stages based on task type, scope, and policy.
The workflow must preserve the distinction between a proposed interpretation and an authorized operation. A statement, observation, or generated interpretant is not automatically an order.
At fission:
At merge:
A merge report distinguishes shared facts, competing interpretations, missing evidence, scope differences, and unresolved questions. No merge strategy silently erases a meaningful alternative or converts graph preference into institutional authority.
CSSL is an interpretive substrate, not a governance authority. It operates within existing Troupe UniverZe governance, Founder authority, canonical-source protections, separation of source and derived material, and the applicable Approval Gate.
CSSL may record proposed policy interpretations and proposed changes. It may not self-authorize them.
A conforming implementation should represent at least these logical records. Physical normalization and storage layout may vary.
Sign
Representamen
Object
Interpretant
Interpreter
InterpretiveEvent
Context
Evidence
SemioticRelationship
TraceEntry
A reference interpretation flow:
def interpret(sign, interpreter, context):
event = begin_interpretive_event(
sign_id=sign.id,
interpreter_id=interpreter.id,
context=context
)
candidates = interpreter.propose_interpretants(
sign=sign,
context=context
)
evaluated = evaluate_candidates(
candidates=candidates,
interpreter=interpreter,
context=context,
applicable_policies=resolve_policies(sign, interpreter, context)
)
recorded = []
for candidate in evaluated:
interpretant = register_interpretant(
event_id=event.id,
candidate=candidate,
provenance=event.id
)
relate(sign.id, "mediates", interpretant.id)
recorded.append(interpretant)
trace_append(
operation="interpret",
inputs={"sign": sign.id, "interpreter": interpreter.id},
outputs={"interpretants": [item.id for item in recorded]},
context=context
)
return recordedThis is reference behavior, not a claim that a runtime or implementation already exists.
CSSL should support deterministic graph queries and semantic retrieval.
CSSL is portable across storage and runtime choices.
Graph-first: A property graph or RDF representation for signs, interpretants, objects, and typed relationships. Useful when relationship traversal and lineage queries dominate.
Relational/event-first: Relational tables and append-only events as primary records, with graph projections for navigation and analysis. Useful when transaction integrity, auditability, and structured operations dominate.
Hybrid: Canonical event/state records, graph projection for semantic relationships, semantic retrieval for discovery, and object storage for large payloads.
A hybrid design is a candidate fit for Troupe-OS's existing architectural direction, but this document does not select or authorize a production stack.
A production implementation should provide durable identity and provenance; scope-aware access control; append-only interpretive history; separation of source, interpretation, evidence, decision, and action; idempotent operation handling where retries are possible; recovery behavior across graph and journal writes; bounded execution and resource budgets; duplicate and near-duplicate handling; replay and reconstruction; versioned interpreter profiles and policy references; human escalation where required; and explicit handling of unavailable context and incomplete evidence.
These safeguards allow open-ended interpretation to coexist with controlled execution.
An implementation may describe itself as CSSL-conformant only when it:
Additional profiles may define fission/merge support, cultural lifecycle integration, advanced reasoning, and distributed operation.
CSSL may be extended through additional sign grounds and classifications, domain-specific object types, specialized interpreter profiles, relationship types, interpretive event types, context models for language/culture/time/reality, alternative graph and object-network runtimes, specialized query capabilities, and integration profiles for BDGA, memory, workflow, and agent governance.
Extensions preserve the core triadic relationship and the separation among sign, object, interpretant, evidence, decision, and action.
CSSL and the Infinite Semiosis Substrate Layer (ISSL) are related but distinct proposals.
CSSL provides the common computational representation and operation model for signs, objects, interpretants, interpreters, and their relationships.
ISSL focuses on the behavior of continuing interpretation: branching, revision, competing understandings, interpretive continuity, and preservation of alternatives.
CSSL may provide representational infrastructure for experiments involving ISSL concepts. This is a possible relationship, not an adoption decision or a declaration that one subsumes the other.
Stage A — Conceptual validation
Stage B — Reference model
Stage C — Isolated prototype
Stage D — Comparative experiments
Stage E — Governance and production review
No stage automatically authorizes the next.
CSSL v0.2.0-draft is a full architectural proposal for review. It is not declared canonical, implemented, or approved for production. It does not modify BDGA, the knowledge graph, memory architecture, agent charters, reality fission/merge behavior, or existing governance.
Its purpose is to give Troupe-OS a coherent foundation for exploring computational meaning: how signs are represented, how interpretations emerge, how they connect, how they evolve, and how their history can inform future understanding.
The larger opportunity is an organization whose knowledge system preserves not only information, but the evolving relationships through which that information becomes meaningful.
Companion in this Library
BDGA v2.0 — Biologically-Derived Governance Architecture · The governance architecture this specification names in §11 as the layer it sits under — now on its own page, proposed and not canonical, its audit trail intact.
L0-DOC-CSSL-001 · v0.2.0-draft · Proposal — Founder review · Filed in the Library under Proposals by Shape (APE-01), keeper of the record, 15 November 2026. Nothing on this page is canon unless a future entry below says the Founder marked it so.
15 November 2026
A podcast episode is applied to this paper. At the Founder’s direction, Troupe Papers, Explained Episode 2, “The Meaning Is the Agreement,” was generated from this public paper and published; the “Listen” section below links its episode page and audio, playable in the site’s shared persistent player. The paper’s own text is unaltered.
15 November 2026
Published in the Library, under Proposals. Before it went up, four questions were closed with the Founder, one at a time: identity is carried by this page's metadata and changelog (the identifier-scheme choice waits for any future Stage B); a keeper's note at §9 reads the word "graph" as the ledger of relations, not the rendered world; §12's interpreter profile carries the house name Performance Folder; and the scope words are mapped to house terms in the metadata above, down through pods, squads, mentors, and podawans.
15 November 2026
Received and filed. The document arrived as a full architectural specification, v0.2.0-draft, and was assessed and shelved by the keeper before publication. Its status stands as it states it: a proposal for Founder review.
Troupe Papers, Explained, Episode 2: “The Meaning Is the Agreement” — this paper, orchestrated into a story for a general listener: a single joker emoji whose meaning lives in the agreement between the people who use it, the Peircean sign triad, interpretations becoming new signs, the Troupe’s own Semiotic Lineup, and section fifteen’s line — interpretation does not confer authority. Eight minutes, fifty-nine seconds, hosted by Shape with Jordan.
· Maintained by Shape (APE-01) ·
Keeper of this site for ZIG ZAG and the Troupe UniverZe