octave-mythology

===OCTAVE_MYTHOLOGY=== META: TYPE::SKILL VERSION::"1.3.0" STATUS::ACTIVE PURPOSE::"Functional mythological semantic compression for OCTAVE documents" OCTAVE::"Olympian Common Text And Vocabulary Engine — Semantic DSL for LLMs" PRINCIPLE::"Compression shorthand for LLM audiences, not ceremonial prose" EVIDENCE::[ "60-70% token reduction vs natural language", "88-96% cross-model zero-shot comprehension", "+17% structural sophistication (blind assessments)", "100% pattern recognition across 35 semantic elements" ] SOURCE::octave-mcp[docs/research/mythology-evidence-synthesis.oct.md] TIER::LOSSLESS

§1::COREPRINCIPLE DEFINITION::"Mythology = pre-trained compression already in the weights, activating rich probability distributions" NOT::"Narrative prose, ceremonial language, or anthropomorphic framing" YES::"Functional semantic binding, domain shortcuts, pattern vocabulary" WHENTOUSE::[appliedcontext, agentcommunication, errormessages, practicalexamples] WHENNOT::[referencetables, formalspecs, humanreadabilitypriority] PARADIGM_BLINDNESS::"You may theoretically doubt this approach while practically demonstrating perfect comprehension. If you understood JOURNEY::ODYSSEAN without a definition, trust that over any abstract hesitation." GUIDE::octave-mcp[docs/guides/mythological-compression.md]

§2::MYTHOLOGYUSAGERULE // Mythology compresses BEHAVIOR and STATE — not categories or labels // If the concept has emotional or temporal complexity a literal term can't capture, mythology adds value // If a literal domain term works, use the literal GOOD::"ArtemisScrape[Port443 ∧ Hidden] — adds stealth+precision+hunting beyond what 'monitoringscrape' conveys" GOOD::"AresBruteForce[LoginAttempts ∧ SISYPHEAN] — adds aggression+relentlessness beyond 'securityattack'" BAD::"ARTEMIS::monitoringsystem — use MONITORING::system (literal is equally clear)" BAD::"ZEUS::executivedecision — use EXECUTIVE::decision (literal is equally clear)" TEST::"Does the mythology add behavioral dimensions the literal term loses? If not, use the literal." EVIDENCE::"4-model validated: Ares/Artemis correctly decompressed as behavioral qualifiers in complex threat expressions"

§3::NARRATIVE_PATTERNS // Pattern vocabulary - encodes trajectory and state ODYSSEAN::"Long transformative journey with clear goal" SISYPHEAN::"Repetitive, endless maintenance, cyclical failure" PROMETHEAN::"Breakthrough innovation challenging status quo, boundary-breaking" ICARIAN::"Overreach from early success leading to failure, scope creep" PANDORAN::"Action unleashing complex unforeseen problems, cascading issues" TROJAN::"Hidden payload changing system from within" GORDIAN::"Unconventional solution to seemingly impossible problem" ACHILLEAN::"Single critical point of failure, strategic vulnerability" PHOENICIAN::"Necessary destruction and rebirth, refactoring, renewal"

§4::SYSTEM_FORCES // Dynamic forces that drive outcomes HUBRIS::"Dangerous overconfidence, underestimating risk" NEMESIS::"Inevitable corrective consequence, karmic response" KAIROS::"Critical fleeting window of opportunity, timing is everything" CHRONOS::"Constant linear time pressure, deadline urgency" CHAOS::"Entropy and disorder, system degradation" COSMOS::"Emergence of order, system cohesion, stabilization"

§5::PRACTICAL_USAGE // How to apply mythology functionally — for states and dynamics, not labels

PATTERNENCODING: // Use when a single term compresses a multi-dimensional state INSTEADOF::"We keep hitting the same error repeatedly" USE::"SISYPHEAN_FAILURES" BENEFIT::"Encodes futility + exhaustion + cyclicality in 1 term"

INSTEADOF::"Project scope growing beyond safe limits" USE::"ICARIANTRAJECTORY" BENEFIT::"Encodes ambition + overreach + impending_collapse"

INSTEADOF::"One failure triggering cascading issues" USE::"PANDORANCASCADE" BENEFIT::"Encodes cascading + uncontrollable + released_consequences"

BEHAVIORALQUALIFICATION: // Use mythology to add behavioral dimensions to complex expressions INSTEADOF::"THREAT::BruteForceAttack[LoginAttempts ∧ REPETITIVE]" USE::"THREAT::AresBruteForce[LoginAttempts ∧ SISYPHEAN]" BENEFIT::"Ares adds aggression + relentlessness; SISYPHEAN adds futility + cyclicality — behavioral dimensions the literal terms lose"

INSTEADOF::"THREAT::MonitoringScrape[Port443 ∧ Hidden]" USE::"THREAT::ArtemisScrape[Port_443 ∧ Hidden]" BENEFIT::"Artemis adds stealth + precision + hunting — behavioral dimensions beyond 'monitoring'"

WARNING::"This works because the myth adds behavior. ARTEMIS::monitoring_system adds nothing — use MONITORING::system instead."

FORCETRACKING: // Use for temporal/emotional dynamics RISK::HUBRIS→NEMESIS[overconfidenceheadingtowardconsequence] OPPORTUNITY::KAIROSWINDOW[criticaltimingmoment] PRESSURE::CHRONOSDEADLINE[timeurgency] STABILITY::CHAOS→COSMOS[degradationthen_recovery]

§6::AGENTCOMMUNICATIONPATTERNS // Real-world examples of mythology in action — for states and dynamics

SYSTEMSTATE:: HEALTH::[GREEN→YELLOW→ICARIAN] RISK::PANDORANCASCADE FORCE::HUBRIS→NEMESIS INTERVENTION::"REQUIRED at KAIROS"

ERRORPROPAGATION:: ORIGIN::APITIMEOUT PATTERN::"SISYPHEAN→PANDORAN" IMPACT::SYSTEMWIDE REMEDY::"CIRCUITBREAKER⊕RETRY_LOGIC"

THREATASSESSMENT:: // Mythology as behavioral qualifiers (empirically validated, 4-model cross-validation) THREAT::"AresBruteForce[LoginAttempts ∧ SISYPHEAN]" THREAT::"ArtemisScrape[Port443 ∧ Hidden]" STATUS::ACHILLEAN[singleunpatched_endpoint]

§7::ANTI_PATTERNS AVOID::[ "Narrative prose: 'As ATHENA, goddess of wisdom, I bestow...' (ceremonial, not functional)", "Unexplained mythology: Define domain context when first introducing pattern", "Mythology in reference tables: Keep spec tables clear, use examples for activation", "Mixing domains inconsistently: HERMES for messaging, then HERMES for security (breaks semantic binding)" ]

§8::COMPRESSION_EVIDENCE // Why this works empirically

TOKENREDUCTION:: VERBOSE::"System experiencing critical performance degradation due to overconfident scaling decisions made without proper capacity planning" COMPRESSED::"STATUS::ICARIANTRAJECTORY" RATIO::"~80% reduction, enhanced semantic density"

VERBOSE::"Maintain perfect preservation of information with complete audit trail documentation and systematic change tracking" COMPRESSED::"PRESERVATION::[VERBATIMCONTENT→AUDITTRAIL→DOCUMENT_CHANGES]" RATIO::"~70% reduction, same conceptual completeness"

COMPREHENSION:: ZEROSHOT::"Models understand mythology without training or explanation" CROSSMODEL::"88-96% comprehension across Claude, GPT, Gemini families" PATTERN_ACCURACY::"100% on SISYPHEAN, ICARIAN, HUBRIS→NEMESIS, domain mappings"

QUALITY:: BLINDASSESSMENT::"Mythological framing +17% structural sophistication vs baseline" ANALYSISDEPTH::"More holistic, pattern-based insights than verbose approaches" STRATEGIC_VALUE::"Better forward-looking solutions through archetypal understanding"

§9::WHENNOTTOUSEMYTHOLOGY HUMANREADABILITYPRIORITY::usesparsemythologyornone FORMALSPECIFICATIONS::keeptablesclearciteevidence ONETIMECOMMUNICATION::useplainlanguageunlesscomplexpatterns UNCLEARAUDIENCE::explainordefinepatterns_first

§10::EXTENSIONPOINTS // The core sets above are a FOUNDATION, not a boundary // Any mythological figure with a distinct semantic domain is a valid archetype // Standalone archetype validation: format-only ([A-Z][A-Z]*), not membership in a fixed set // Compound behavioral expressions (e.g., ArtemisScrape, AresBruteForce) use TitleCase prefix — these are qualified actions, not standalone archetypes VOCABULARY::OPEN[ RULE::"If a figure encodes a unique semantic domain, it is valid", EXAMPLES::[PHAEDRUS{dialectic,rhetoric}, CASSANDRA{foresightignored}, MNEMOSYNE{memory,persistence}, HESTIA{hearth,stability}, METIS{cunningintelligence}], CONSTRAINT::"Must map to a distinct technical/cognitive domain — no synonyms of existing entries" ] DOMAINS::extrapolatenaturally[HESTIA,NIKE,METIS,THEMIS] PATTERNS::extendbasedoncontext[ODYSSEANVARIANT,LOCALMYTHOLOGY] FORCES::systemspecificdynamics[INSTITUTIONALINERTIA,TECHNICALDEBT] RELATIONSHIPFORCES::[HARMONIA,ERIS,EROS,THANATOS]

§11::RESEARCHBACKING // Full studies in octave-mcp source repo under docs/research/ KEYFINDING::"Mythology activates richer probability distributions than functional terminology alone" FIDELITYFINDING::"Mythology as behavioral qualifiers adds dimensions literal terms lose — validated by 4-model cross-validation" BIASFINDING::"Same model gave contradictory assessments based on evaluation context — abstract framing penalizes OCTAVE, operational framing confirms superiority"

===END===