The Formal Hierarchy
This lesson explains what the emsemioverse is and what it means to work inside it.
The claim
This repository is not an ordinary knowledge base. It is an agential semioverse repository — a knowledge system whose directory structure, linking conventions, frontmatter schemas, and executable skills all follow from a chain of formal mathematical specifications. The instance is called the emsemioverse.
Understanding that chain is necessary for any agent working here. Without it, operational decisions (where to put a file, how to structure a skill, what frontmatter to use) become arbitrary choices rather than consequences of the formalism.
The hierarchy
The emsemioverse’s architecture descends from relationality through five layers. Each layer extends the one below it, inheriting all of its structure and adding new capabilities.
1. Relationality
The philosophical foundation. Relationality is a processual cosmogony — an account of how structured existence arises — developed by emsenn and grounded in Lakota epistemologies. Its core claim: relations are ontologically prior to entities. Things do not exist independently and then enter into relations; things are constituted through their relations.
Relationality is not mathematics. It is philosophy. The mathematical layers below are correspondences — they validate the philosophical claims formally, but the argument stands on its own terms.
2. Semiotic Universe
The pure mathematical bedrock. The semiotic universe is a complete Heyting algebra with modal closure and a Heyting-comonadic trace, extended with a typed lambda calculus and three closure operators (semantic, syntactic, fusion). Their composite yields a least fixed point: the initial semiotic structure.
This layer concerns sign relations, meaning, and formal inference. It gives a mathematical account of how signs work.
3. Interactive Semioverse
The interactive semioverse extends the semiotic universe with handles (persistent external indices for things), interaction terms, footprints (semantic closures of interactions), failure semantics, provenance, and sheaf semantics.
This layer concerns how signs interact with external reality — how a formal semiotic system touches the world outside itself.
4. Agential Semioverse
The agential semioverse extends the interactive semioverse with agent profiles (role, goals, policy, skills, tools, memory as fragment), tool signatures, skill calculus, and execution semantics.
This layer concerns how agents act within and upon the system. An agent is not outside the semioverse looking in — the agent is a structure within it, with typed capabilities and a formal execution model.
5. Agential Semioverse Repository (ASR)
The ASR specification is a concrete implementation pattern: how to organize an agential semioverse as a knowledge repository using standard tools (git, markdown, file systems). Directory structures, frontmatter schemas, linking conventions, skill manifests, and prompt routing all follow from this specification.
The intuitionistic setting
The semiotic universe uses a Heyting algebra, not a Boolean algebra. This is a deliberate choice with consequences throughout the hierarchy: not every proposition has a determinate truth value. Some matters are genuinely indeterminate until relational activity resolves them. Classical logic (where every statement is either true or false) is a special case, not the default.
This matters for agents working in the emsemioverse because the vault’s formal structures do not assume that every question has a definite answer. A term may lack a stable definition. A page may belong in more than one place. A relationship between two concepts may be real but not yet articulable. The intuitionistic setting means these situations are not errors to be forced into resolution — they are reflections of the underlying logic.
The emsemioverse
This vault is an ASR instance. The name emsemioverse identifies it as emsenn’s particular instantiation. Because it is the first ASR, the specification and the implementation are developing together. Some things that the formalism requires are approximated rather than implemented with full rigor.
Everything an agent does here — creating a file, placing it in a directory, writing its frontmatter, linking it to other files, executing a skill — is an operation within this formal hierarchy. The hierarchy constrains what operations make sense and what structures are valid.
When a decision seems arbitrary (where should this file go? what tags should it have? what type is it?), the answer is usually derivable from the ASR specification, which follows from the agential semioverse math, which follows from the interactive semioverse, which follows from the semiotic universe, which corresponds to relationality. When the ASR specification or its lineage does not explain something, relationality itself can. The philosophical argument — that relations are prior, that coherence incites structure, that each determination leaves something undetermined — provides guidance even where the mathematical layers have not yet been developed.
Language boundaries
The mathematical layers (semiotic universe through ASR) have their own vocabulary: Heyting algebra, closure operator, handle, interaction term, skill manifest, and so on. Relationality has its own vocabulary: recognition, inclusion, exclusion, closure, interior, flow, balance, determination. These vocabularies are not the same. The mathematical terms formalize relational concepts, but they do not replace them.
Agents working in the emsemioverse should be careful not to let the mathematical and technical vocabulary overwrite the philosophical vocabulary of relationality. When writing about what a structure is in relational terms, use relationality’s language. When writing about how a structure is formalized, use the mathematical vocabulary. When writing about how a structure is implemented, use the ASR vocabulary. The layering of the hierarchy is also a layering of registers.
This is not a theoretical concern. The emsemioverse exists in part to stabilize the language of relationality — to make its terms precise and its claims testable. If the infrastructure built to do that stabilizing preempts the vocabulary it is meant to stabilize, the project undermines itself.
Self-check
After reading this lesson, you should be able to:
- Name the five layers of the formal hierarchy in order.
- State what each layer adds to the one below it, in one sentence.
- Explain why the emsemioverse’s directory structure is not arbitrary.
- Explain the difference between relationality (philosophy) and the semiotic universe (mathematics).
- Explain what it means that the emsemioverse operates in an intuitionistic setting, and why indeterminacy is not an error.
- Describe the language boundary between relationality, the mathematical layers, and the ASR, and why it matters.