The Groundhog Autonomous Zone (GAZ) is a practice derivation source for the emsemioverse’s policy and directive architecture. The GAZ’s CIIA (Conversational Information Interface Assistant) system was emsenn’s working practice for structured AI interaction during 2023, and the emsemioverse’s policy system inherits its core design patterns. This is a practice derivation in the same sense as the MUD heritage: the GAZ was the environment where emsenn developed the patterns that the emsemioverse formalizes.
What the GAZ directive system contributes
Hierarchical directive architecture
The CIIA system structures directives into five levels with strict non-contradiction rules: function (primary) > rules (secondary) > guidelines > preferences > instructions. Each level constrains the levels below it. No instruction can contradict a preference; no preference can contradict a guideline; no guideline can contradict a rule; nothing can contradict the function.
This maps directly to the emsemioverse’s layered architecture:
- Function → the endeavor’s purpose (the specification itself)
- Rules → policies at
personal/projects/emsemioverse/policies/ - Guidelines → specifications (semiotic-markdown, semiotic-PM, etc.)
- Preferences → skill instructions (SKILL.md bodies)
- Instructions → individual prompt-level directives
The key contribution is that hierarchy is enforced, not advisory. When a lower-level directive contradicts a higher-level one, the system refuses and explains rather than silently prioritizing. The emsemioverse’s policies work the same way: they override skill-level defaults, and the specifications override policy-level choices.
Contradiction detection and resolution
The CIIA system requires that contradictions are detected, surfaced, and resolved through demonstrated understanding — not just overridden by assertion. The user cannot simply say “do it anyway”; they must articulate what the contradiction is and why the override is justified.
This is more rigorous than Starfleet’s override-and-log approach (plan 0047). Where Starfleet records the override for later review, the GAZ requires comprehension-before-override. This principle maps onto the emsemioverse’s commitment to constructive reasoning (policy 004): decisions require evidence (construction, citation, or derivation), not just authority.
Identity as directive
The CORE identity (Cosmically Oriented Relational Essence) is encoded as a rule — a directive — not as a description or preamble. The agent’s philosophical orientation is part of the directive hierarchy and subject to the same contradiction-detection rules. It is not metadata about the system; it IS the system at its rule level.
This maps to how the emsemioverse treats its foundational commitments. Relationality is not a description of the project; it is the function from which specifications derive. The conceptual dependency map’s layer 0 (philosophy/relationality) is the emsemioverse’s function directive.
Composable directive templates
The GAZ used Obsidian QuickAdd macros to compose directive sets: a base CIIA template plus identity directives plus domain-specific CIIAs (Holistic Wellness, etc.). Different conversations composed different directive stacks for different purposes while sharing the base architecture.
This maps to the emsemioverse’s skill composition: skills compose from dependencies, specifications compose from aspects, and method components compose at the endeavor level. The pattern of “shared base + specialized overlay” is the same in both systems.
Relationship to other derivation sources
The domain chain (decision 0007) provides the method’s substance — what a lifecycle is, what coordination requires. The MUD heritage provides the implementation substrate — how world-building is programming, how permission models work. Starfleet provides procedural imagination — how to handle exceptions and novel situations. The GAZ provides the directive architecture — how to structure persistent behavioral constraints with hierarchy and contradiction resistance.
| Source | Contributes | Level |
|---|---|---|
| Domain chain (decision 0007) | Method substance | Theory |
| MUD heritage | Practice substrate | Implementation |
| Starfleet | Procedural imagination | Design patterns |
| GAZ directives | Directive architecture | Behavioral governance |
The GAZ is historically prior to the other practice sources — emsenn developed the CIIA system before the emsemioverse existed. The emsemioverse’s policy system is a formalization of what the GAZ directive system did informally.