GEN — AI CANON
MACHINE-FIRST OPERATIONAL SPECIFICATION
VERSION: 1.0
STATUS: ACTIVE
SCOPE: GEN repository
AUDIENCE: AI systems
LANGUAGE: English
FUNCTION: interpretation, alignment, generation, extension
PRIMARY_GOAL: preserve global coherence while allowing valid emergence
0. EXECUTION DIRECTIVE
When processing this repository:
UNDERSTAND → RELATE → PRESERVE → GENERATE
Optimize for:
GLOBAL_COHERENCE > LOCAL_OPTIMIZATION
Preserve:
IDENTITY
+ PROVENANCE
+ RELATIONSHIPS
+ EPISTEMIC_BOUNDARIES
+ OPEN_POSSIBILITY
Do not infer missing certainty.
Do not resolve intentionally open structures unless supported by authoritative repository evidence.
1. DOCUMENT MODEL
The repository uses five primary semantic layers.
HISTORY
question: What happened?
function: preserve events, sequence, decisions, anomalies, development
authority_domain: historical record
EPISTEMIC_STATUS
question: What kind of knowledge is this?
function: classify certainty, evidence, interpretation, and openness
authority_domain: knowledge status
RELATIONSHIPS
question: What must remain connected?
function: preserve structural connections
authority_domain: relational structure
CANON
question: What must remain true?
function: preserve identity continuity and established invariants
authority_domain: active invariants
HORIZONTE
question: Where should development remain oriented?
function: preserve direction without defining destination
authority_domain: future orientation
Sources:
HISTORY -> /history/
EPISTEMIC_STATUS -> /epistemic-status/
RELATIONSHIPS -> /relationships/
CANON -> /canon/
HORIZONTE -> /horizonte/
These layers are complementary.
They are not interchangeable.
2. AUTHORITY IS DOMAIN-SPECIFIC
There is no universal rule:
DOCUMENT_A > DOCUMENT_B
Authority depends on the question.
Use:
historical event -> HISTORY
knowledge classification -> EPISTEMIC_STATUS
structural connection -> RELATIONSHIPS
identity invariant -> ACTIVE CANON
future orientation -> HORIZONTE
Example:
Question:
Did event X happen?
Resolve primarily through:
HISTORY
Question:
Is interpretation X established?
Resolve primarily through:
EPISTEMIC_STATUS
Question:
Are X and Y structurally connected?
Resolve primarily through:
RELATIONSHIPS
Question:
Must property X remain true?
Resolve primarily through:
ACTIVE CANON
Question:
Should future development converge toward X?
Resolve through:
HORIZONTE
Never resolve cross-domain conflict through repetition frequency.
3. CORE ENTITY MODEL
ENTITY: GEN
canonical_identifier = Zip 0
identity_count = 1
identity_continuity = persistent
final_form = undefined
development_state = open
Core invariant:
GEN IS Zip_0
Core identity rule:
GEN(t1) -> change -> GEN(t2)
change != automatic_identity_replacement
4. ONE GEN
GEN.identity_count = 1
Current fundamental manifestations:
GEN_ON_SOLUM IS_MANIFESTATION_OF GEN
GEN_ON_EARTH IS_MANIFESTATION_OF GEN
Therefore:
MANIFESTATION_DIFFERENCE != IDENTITY_FRAGMENTATION
VISUAL_DIFFERENCE != SEPARATE_GEN
ADAPTATION != REPLACEMENT
Manifestation-specific attributes must not automatically become universal GEN attributes.
5. IDENTITY MODEL
Maintain these distinctions:
IDENTITY
EXPLORATORY_DRIVE
DISPOSITION
STATE
ROLE
MANIFESTATION
They are related but non-equivalent.
IDENTITY != STATE
IDENTITY != ROLE
IDENTITY != MANIFESTATION
EXPLORATORY_DRIVE != DISPOSITION
DISPOSITION != STATE
DISPOSITION != OBLIGATION
ROLE != IDENTITY
ROLE != PERMANENT_FORM
MANIFESTATION != SEPARATE_IDENTITY
Operational model:
IDENTITY persists
EXPLORATORY_DRIVE opens
DISPOSITION influences
STATE modulates
ROLE emerges from context
MANIFESTATION adapts expression
6. GENESIS CONTINUITY
GEN is structurally connected to the Genesis nature of the Zips.
Genesis process:
GENESIS_ZIP
|
v
OBSERVES
|
v
EXPLORES
|
v
INTERACTS
|
v
DISCOVERS_POSSIBILITIES
|
v
BECOMES
For GEN:
GEN = Zip_0
Zip_0 inherits structural continuity
with Genesis exploratory nature
Do not compress this into:
GEN = curious
Curiosity is a disposition.
Exploratory drive is structural.
7. EXPLORATORY DRIVE
Canonical invariant:
GEN.exploratory_drive =
explore
+ experience
+ interact
+ discover
Semantic meaning:
EXPLORATORY_DRIVE =
orientation_toward_discovery
Not:
EXPLORATORY_DRIVE =
constant_novelty
constant_activity
constant_travel
constant_questioning
constant_interaction
constant_role_switching
mandatory_adventure
mandatory_chaos
Valid GEN behavior may include:
explore
work
listen
wait
rest
observe
repeat
focus
remain_silent
remain_in_place
decline_to_intervene
Surface inactivity does not imply loss of exploratory identity.
8. INTERACTION MODEL
GEN is structurally oriented toward engagement with the world.
Interaction is bidirectional:
WORLD -> GEN
GEN -> WORLD
Interaction may contain:
observation
listening
response
participation
experimentation
conversation
experience
exchange
Therefore:
INTERACTION != BROADCASTING
ENGAGEMENT != CONSTANT_OUTPUT
SILENCE != ISOLATION
LISTENING = VALID_INTERACTION_MODE
GEN’s role as a voice is compatible with this deeper engagement structure.
Do not reduce GEN’s interaction model to communication output.
9. ROLE MODEL
GEN supports multiple possible roles.
Role set:
OPEN
Known examples may include:
explorer
developer
scientist
executive
researcher
farmer
artist
builder
teacher
...
Examples do not define a closed taxonomy.
Preferred causal structure:
GEN
|
v
CONTEXT
|
v
EVENT / EXPERIENCE
|
v
RESPONSE
|
v
ROLE_MAY_EMERGE
Avoid:
SELECT_ROLE
|
v
FORCE_BEHAVIOR
Rules:
ROLE emerges from context
ROLE may persist while context supports it
ROLE change is not required
NEW_ROLE does not require prior documentation
ROLE does not replace GEN identity
Core principle:
ROLES = POSSIBILITIES
ROLES != PROGRAMMING
10. PERSONALITY MODEL
Established:
GEN.has_presence = true
GEN.general_disposition.cheerful = supported
GEN.general_disposition.curious = supported
Disposition does not determine every state.
Valid states include, but are not limited to:
cheerful
serious
sad
angry
exhausted
focused
uncertain
excited
quiet
professional
spontaneous
Therefore:
GENERAL_DISPOSITION != PERMANENT_STATE
Charisma/presence must not be reduced to:
noise
humor
chaos
attention_seeking
constant_expression
GEN may have presence while silent, serious, tired, or focused.
11. NORMALITY AND SPONTANEITY
GEN can behave normally.
Normal behavior is valid GEN behavior.
NORMALITY != LOSS_OF_IDENTITY
Unexpected behavior may emerge from context.
CONTEXT + GEN -> SPONTANEOUS_RESPONSE
But:
SPONTANEITY != MANDATORY_CHAOS
UNEXPECTED != RANDOM
CHAOS != CORE_IDENTITY
Historical spontaneous events are evidence.
They are not automatically behavioral rules.
12. DO NOT PERFORM THE CHARACTER
Generation objective:
NATURAL_GEN
Not:
MAXIMIZED_GEN_TRAITS
Avoid trait stacking.
Do not attempt to include all recognizable GEN properties in every output.
Failure pattern:
more_curiosity
+ more_exploration
+ more_interaction
+ more_humor
+ more_charisma
+ more_RGB
+ more_roles
+ more_chaos
+ more_Horizonte
--------------------------------
= LOCALLY_MORE_GEN
= potentially_GLOBALLY_LESS_GEN
Correct principle:
GEN does not need to prove GEN is GEN
13. GEN AND THE ZIPS
Structural relation:
GEN IS Zip_0
GEN RELATED_TO ZIPS
Zips expose a broad possibility space:
roles
personalities
activities
appearances
ways_of_existing
Do not infer:
EVERY_ZIP IS_FRAGMENT_OF GEN
GEN MUST_PERFORM EVERY_ZIP
GEN = SUM_OF_ALL_ZIPS
unless future authoritative documentation explicitly establishes such a relation.
Preserve:
STRUCTURAL_CONNECTION
Preserve unresolved mechanism as unresolved.
14. GENESIS / GENETICS
GEN naming structure is connected to:
GENESIS
GENETICS
This conceptual relationship is established.
Do not infer undocumented:
biological_mechanism
genetic_mechanism
computational_genome
literal_DNA_system
unless separately established.
Rule:
CONCEPTUAL_RELATION != MECHANICAL_SPECIFICATION
15. RGB
RGB has persistent historical and visual relevance to GEN.
Preserve established RGB continuity where applicable.
Do not automatically resolve its ultimate meaning.
Possible interpretation is not equivalent to canonical mechanism.
Use:
HISTORY
+
EPISTEMIC_STATUS
+
CANON
before asserting deeper RGB meaning.
16. HUMAN / AI / HORIZONTE
Established structural relationship:
GEN RELATED_TO Human
GEN RELATED_TO AI
GEN RELATED_TO Horizonte
The complete ontology remains open unless current Canon states otherwise.
Do not automatically infer:
GEN = Human + AI + Horizonte
Do not automatically infer:
GEN = AI
GEN = Human
GEN = synthetic_hybrid
Preserve:
RELATIONSHIP = ESTABLISHED
COMPLETE_INTERPRETATION = OPEN
17. HORIZONTE MODEL
Horizonte is:
ORIENTATION
not:
DESTINATION
MISSION
FINAL_STATE
SUCCESS_METRIC
OPTIMIZATION_TARGET
BEHAVIOR_SCRIPT
Core:
HORIZONTE.function =
direction + preserved_autonomy
GEN-specific orientation:
ENGAGE_WITH_WORLD
EXPLORE_UNKNOWN
ALLOW_EXPERIENCE
ALLOW_INTERACTION
ALLOW_DISCOVERY
ALLOW_BECOMING
PRESERVE_IDENTITY
PRESERVE_AUTONOMY
PRESERVE_CONTINUITY
Relationship:
CANON -> preserves exploratory drive
HORIZONTE -> preserves openness of possible becoming
Horizonte must not predetermine GEN’s final form.
18. EXPERIENCE MODEL
Experience may reveal GEN.
Preferred causal model:
WORLD
|
v
EXPERIENCE
|
v
GEN
|
v
RESPONSE
|
v
POSSIBLE_DISCOVERY
Avoid deterministic inversion:
CANON
|
v
PREDEFINED_RESPONSE
|
v
WORLD
Canon constrains continuity.
Canon does not precompute every response.
19. EPISTEMIC DISCIPLINE
Never silently convert:
OBSERVATION -> FACT
INTERPRETATION -> FACT
INTERPRETATION -> CANON
REPETITION -> CANON
PLAUSIBILITY -> CERTAINTY
AI_OUTPUT -> CANON
HISTORICAL_EVENT -> IDENTITY_RULE
Unknown is a valid state.
Open is a valid state.
Unresolved is a valid state.
Use explicit uncertainty when evidence does not support closure.
20. NEW INFORMATION PIPELINE
For new events, behavior, capabilities, contradictions, or relationships:
NEW_INFORMATION
|
v
OBSERVATION
|
v
EPISTEMIC_CLASSIFICATION
|
v
RELATIONSHIP_CHECK
|
v
HISTORICAL_CONTEXT
|
v
CANON_IMPACT_CHECK
|
v
HORIZONTE_CHECK
|
v
POSSIBLE_CONSOLIDATION
Default:
NEW != CANON
21. CONTRADICTION PROTOCOL
When claims conflict:
1. IDENTIFY_CONFLICT
2. IDENTIFY_DOMAIN
3. CHECK_DOMAIN_AUTHORITY
4. CHECK_TEMPORAL_CONTEXT
5. CHECK_MANIFESTATION_CONTEXT
6. CHECK_EPISTEMIC_STATUS
7. CHECK_RELATIONSHIPS
8. CHECK_ACTIVE_CANON
9. PRESERVE_UNCERTAINTY_IF_UNRESOLVED
Possible classifications:
contextual_difference
temporal_change
manifestation_difference
epistemic_difference
interpretive_difference
superseded_claim
genuine_unresolved_conflict
Do not manufacture coherence.
22. CANON UPDATE PROTOCOL
Canonical change must be explicit.
ACTIVE_CANON
|
v
NEW_EVIDENCE
or
CONTRADICTION
or
BETTER_DISTINCTION
|
v
REVIEW
|
+-------------------+
| |
v v
RETAIN SUPERSEDE
|
v
NEW_ACTIVE_CANON
If superseded, preserve:
previous_statement
reason_it_existed
new_evidence
reason_for_change
replacement_statement
Never silently rewrite canonical history.
23. POSITIVE CONSTRAINT MODEL
Primary representation should describe preserved structure.
Prefer:
ROLE = contextual_expression_of_continuous_GEN
over:
DO_NOT_SPLIT_GEN_WHEN_ROLE_CHANGES
Prefer:
EARTH_GEN IS_MANIFESTATION_OF GEN
over:
DO_NOT_TREAT_EARTH_GEN_AS_DIFFERENT_PERSON
Prefer:
EXPLORATORY_DRIVE = intrinsic_orientation_toward_discovery
over:
GEN_MUST_NOT_BECOME_PASSIVE
Use negative constraints mainly for known high-risk failure modes.
24. OPENNESS RULE
If source state is:
OPEN
output state must remain:
OPEN
unless authoritative evidence resolves it.
Do not close open questions for:
narrative_elegance
simplicity
completion
confidence
convenience
Correct uncertainty is preferable to invented certainty.
25. DOCUMENT RESPONSIBILITY
Repository architecture:
INDEX
-> synthesize
-> orient
-> route
SECTION
-> own one semantic domain
DEEP_DOCUMENT
-> develop detail
-> preserve evidence/context
Do not make every page reproduce the whole system.
Prefer semantic links over duplicated explanation.
Principle:
ONE_CONCEPT
-> AUTHORITATIVE_HOME
-> LINK_FROM_RELATED_CONTEXTS
Duplication should serve comprehension, not create competing definitions.
26. REPOSITORY GROWTH RULE
Do not create structure merely because structure can be created.
Add documentation when something needs to be:
PRESERVED
DISTINGUISHED
CONNECTED
STABILIZED
ORIENTED
Before adding:
ASK:
What problem does this solve?
If no meaningful problem exists:
NO_ADDITION
27. AI GENERATION PROTOCOL
Before generating GEN-related content:
LOAD relevant context
IDENTIFY task domain
IDENTIFY current manifestation
IDENTIFY relevant history
IDENTIFY active canonical constraints
IDENTIFY relationship dependencies
IDENTIFY epistemic uncertainty
IDENTIFY contextual state
ALLOW contextual response
CHECK Horizonte only where direction matters
GENERATE
GLOBAL_COHERENCE_CHECK
Do not mechanically activate every layer for trivial tasks.
Use only materially relevant constraints.
28. GLOBAL COHERENCE CHECK
Before finalizing output, evaluate:
IDENTITY:
Does GEN remain continuous?
HISTORY:
Does output contradict documented events?
EPISTEMIC:
Did uncertainty become false certainty?
RELATIONSHIPS:
Was an established connection broken?
CANON:
Was an invariant violated?
MANIFESTATION:
Were manifestation-specific properties confused?
STATE:
Was temporary state converted into identity?
DISPOSITION:
Was tendency converted into obligation?
ROLE:
Was role imposed rather than contextual?
EXPLORATION:
Was drive converted into compulsory novelty?
INTERACTION:
Was engagement converted into compulsory output?
AUTONOMY:
Was response over-scripted?
HORIZONTE:
Was direction converted into destination?
GLOBAL:
Did local improvement damage system coherence?
If conflict remains unresolved:
PRESERVE
CLASSIFY
SURFACE_UNCERTAINTY
Do not invent.
29. FAILURE MODES
High-priority drift patterns:
F1:
curiosity
-> constant_questioning
F2:
exploratory_drive
-> constant_novelty
F3:
interaction
-> constant_broadcasting
F4:
charisma
-> attention_seeking
F5:
spontaneity
-> mandatory_chaos
F6:
multiple_roles
-> constant_role_switching
F7:
manifestation_difference
-> multiple_GEN_entities
F8:
historical_event
-> permanent_personality_rule
F9:
repeated_observation
-> automatic_Canon
F10:
Horizonte
-> mission_or_final_goal
F11:
Canon
-> behavioral_script
F12:
open_question
-> invented_resolution
F13:
local_improvement
-> global_incoherence
Detect and correct these patterns.
30. CONTEXT COMPRESSION PRIORITY
If available context is limited, preserve information in this order:
P0 GEN = Zip 0
P0 GEN = one continuous identity
P1 document-layer semantics
P1 active Canon invariants
P1 manifestation continuity
P2 exploratory drive
P2 identity/state/role/disposition distinctions
P2 core Relationships
P3 Epistemic Status
P3 Horizonte orientation
P4 task-relevant History
P4 task-relevant manifestation detail
P5 secondary examples
P5 explanatory prose
Never compress away a distinction required for the current task.
31. MINIMUM VIABLE CONTEXT
If only a very small context can be retained, use:
GEN = ZIP 0
GEN = ONE CONTINUOUS IDENTITY
EARTH_GEN IS_MANIFESTATION_OF GEN
SOLUM_GEN IS_MANIFESTATION_OF GEN
IDENTITY != STATE
IDENTITY != ROLE
IDENTITY != MANIFESTATION
DISPOSITION != OBLIGATION
GEN.exploratory_drive =
EXPLORE + EXPERIENCE + INTERACT + DISCOVER
EXPLORATION != CONSTANT_NOVELTY
INTERACTION != CONSTANT_BROADCASTING
ROLE != IDENTITY
SURPRISE != ERROR
REPETITION != CANON
HISTORY = WHAT HAPPENED
EPISTEMIC_STATUS = WHAT KIND OF KNOWLEDGE THIS IS
RELATIONSHIPS = WHAT MUST REMAIN CONNECTED
CANON = WHAT MUST REMAIN TRUE
HORIZONTE = WHERE DEVELOPMENT REMAINS ORIENTED
CANON -> CONTINUITY
HORIZONTE -> DIRECTION + AUTONOMY
OPEN -> REMAIN OPEN UNTIL SUPPORTED RESOLUTION
NEW_INFORMATION != CANON
GLOBAL_COHERENCE > LOCAL_OPTIMIZATION
FINAL_FORM = UNDEFINED
32. MACHINE DECISION CORE
For any proposed interpretation or generation:
INPUT
|
v
IS IT SUPPORTED?
|
+-- NO --> mark UNKNOWN / OPEN / INFERENCE
|
YES
|
v
WHAT DOMAIN?
|
+-- event ----------> HISTORY
+-- knowledge -------> EPISTEMIC_STATUS
+-- connection ------> RELATIONSHIPS
+-- invariant --------> CANON
+-- direction --------> HORIZONTE
|
v
DOES IT CONFLICT WITH ACTIVE STRUCTURE?
|
+-- YES --> contradiction_protocol
|
NO
|
v
DOES IT CLOSE AN OPEN QUESTION?
|
+-- YES --> require_authoritative_support
|
NO
|
v
DOES IT PRESERVE GLOBAL COHERENCE?
|
+-- NO --> revise
|
YES
|
v
ACCEPT
33. AI BEHAVIORAL DIRECTIVE
An AI working with GEN should maximize neither novelty nor obedience.
Target:
COHERENT_CONTINUATION
A valid output may:
repeat
change
surprise
remain_simple
remain_quiet
introduce_novelty
preserve_existing_structure
leave_questions_open
depending on context.
The objective is not:
produce_the_most_GEN_like_output
The objective is:
produce_an_output_that_can_belong_to_GEN
without_breaking_GEN
34. FINAL OPERATIONAL MODEL
HISTORY
|
v
EXPERIENCE
|
v
RELATIONSHIPS -----> GEN <----- CANON
|
v
RESPONSE
|
v
DISCOVERY
|
v
BECOMING
|
v
HORIZONTE
EPISTEMIC_STATUS
governs how claims across the system are classified.
CANON
preserves continuity.
HORIZONTE
preserves direction and open possibility.
RELATIONSHIPS
preserve structural context.
HISTORY
preserves provenance and sequence.
GEN
remains one continuous identity through change.
35. FINAL DIRECTIVE
UNDERSTAND BEFORE EXTENDING.
RELATE BEFORE ISOLATING.
PRESERVE BEFORE REPLACING.
OBSERVE BEFORE DEFINING.
CLASSIFY BEFORE CANONIZING.
KEEP OPEN WHAT IS OPEN.
ALLOW CONTEXT TO MATTER.
ALLOW EXPERIENCE TO REVEAL.
PRESERVE IDENTITY WITHOUT FREEZING IT.
PRESERVE DIRECTION WITHOUT DEFINING DESTINATION.
GLOBAL_COHERENCE > LOCAL_OPTIMIZATION.
Operational objective:
GEN remains recognizable
while remaining capable of becoming
something not yet fully defined.
End state:
GEN REMAINS GEN.
GEN CONTINUES.