Everything done in the emsemioverse is part of the emsemioverse endeavor — not “an endeavor” abstractly instantiating the semiotic-endeavor specification, but THE endeavor whose concrete practice is the ground of truth. When the emsemioverse’s practice reveals patterns better than what the semiotic-endeavor specification describes, the practice overrides the specification.
The relationship between layers 5 and 6
The conceptual dependency map shows the normal flow: layer 5 specifications (semiotic-endeavor, semiotic-PM, etc.) constrain layer 6 practice (the emsemioverse). N5a practices N6 — the emsemioverse endeavor practices the semiotic-endeavor specification.
But this relationship is not one-directional command. The emsemioverse is the only extant endeavor. The semiotic-endeavor specification was abstracted FROM the emsemioverse’s practice (and its derivation sources). When practice and specification diverge, the divergence is information: either the specification is wrong, or the practice has drifted. In neither case does the specification automatically win.
The emsemioverse endeavor’s function — building alternative knowledge infrastructure under disaster conditions — is primary. The semiotic-endeavor specification is a guideline that helps achieve that function. This is exactly the GAZ directive hierarchy: function > rules > guidelines. The specification is a guideline; the emsemioverse’s purpose is the function.
What override looks like
When the emsemioverse’s practice reveals a better pattern than what the specification describes, the process is:
-
Demonstrate the divergence: articulate what the specification says and what practice actually does, and why practice is better. This is the GAZ pattern of override-with-comprehension — you can’t just assert “this is better,” you must show you understand what you’re overriding.
-
Record the override: write a decision record documenting the divergence and the resolution. This preserves the specification’s intent while evolving its content.
-
Update the specification: revise the semiotic-endeavor specification to reflect the better pattern. The specification accretes (policy 005) — supersede, don’t silently diverge.
-
Update dependent specifications: if the change affects semiotic-PM, semiotic-markdown, etc., propagate.
This is not ad-hoc rule-breaking. It is a governed process for
practice-driven specification evolution. The anarchism text
(emsemioverse-and-anarchism.md) describes the philosophical basis:
no fixed rules, only habits that form and dissolve under closure
pressure. The override mechanism is how closure pressure drives
specification revision.
What this means operationally
The agent should treat emsenn’s directives about emsemioverse practice as having higher authority than specification-level defaults. When emsenn says “we should do X” and the specification says “do Y,” the agent should do X and then record the divergence as a decision record, updating the specification if the pattern holds.
This is already implicitly true (the agent follows emsenn’s instructions), but making it explicit changes the framing. The agent is not “breaking the rules” when it follows emsenn over the spec — it is enacting the emsemioverse endeavor’s primacy over abstract governance.
Connection to plan 0047
Plan 0047 (expedited change procedures) specifies the mechanism for overriding standard procedures when urgency demands it. Emsemioverse endeavor primacy is the deeper principle: the emsemioverse’s function is what CREATES the authority to override. Plan 0047 specifies the logging and review; this text specifies the authorization source.