tomevault-io ===OCTAVE_MASTERY=== META: TYPE::SKILL VERSION::"3.2.1" STATUS::ACTIVE PURPOSE::"Expert-level OCTAVE: mythology vocabulary, holographic contracts, archetype annotation, anti-patterns" REQUIRES::octave-literacy SPEC_REFERENCE::octave-core-spec.oct.md
§1::SEMANTIC_PANTHEON
// Compression vocabulary — zero-shot, use directly. Literal term wins when equally clear.
// Use as KEY prefixes (ARTEMIS::latency_p99) or PATTERN DESCRIPTORS (SISYPHEAN_DEBT).
DOMAINS:
ZEUS::"Executive authority, final arbitration, strategic direction"
ATHENA::"Strategic wisdom, planning, elegant solutions"
APOLLO::"Analytics, insight, clarity, prediction"
HERMES::"Communication, APIs, translation, messaging"
HEPHAESTUS::"Infrastructure, tooling, engineering, automation"
ARES::"Security, defense, stress testing, adversarial analysis"
ARTEMIS::"Monitoring, alerting, precision targeting, observation"
POSEIDON::"Storage, databases, data lakes, unstructured pools"
DEMETER::"Resource allocation, budgeting, scaling, growth"
DIONYSUS::"UX, engagement, creativity, chaotic innovation"
§2::NARRATIVE_FORCES
// Single-token state and trajectory descriptors
TRAJECTORIES:
ODYSSEAN::"Long transformative journey with clear goal"
SISYPHEAN::"Repetitive endless maintenance"
PROMETHEAN::"Breakthrough challenging status quo"
ICARIAN::"Overreach from early success → failure"
PANDORAN::"Action unleashing unforeseen cascades"
TROJAN::"Hidden payload transforming system from within"
GORDIAN::"Unconventional cut through impossible problem"
ACHILLEAN::"Single critical point of failure"
PHOENICIAN::"Necessary destruction and rebirth"
FORCES:
KAIROS::"Critical fleeting opportunity window"
CHRONOS::"Linear time pressure"
HUBRIS::"Dangerous overconfidence"
NEMESIS::"Inevitable corrective consequence"
CHAOS::"Entropy and disorder"
COSMOS::"Emergence of order from complexity"
§3::ARCHETYPE_ANNOTATION
// Archetypes in agent definitions use NAME annotation form
// is a semantic facet, not a list. It narrows what the archetype IS in this context.
SYNTAX::ARCHETYPE_NAME
CORRECT::[
HEPHAESTUS,
ATLAS,
ATHENA,
HERMES
]
// The activates a specific behavioral dimension of the archetype.
// Do NOT use NAME[qualifier] for archetypes — that is constructor syntax, not annotation.
// Do NOT stack multiple qualifiers: HEPHAESTUS<a,b> is invalid. Use one facet per archetype.
ANTI_PATTERN::"HEPHAESTUS[faithful_transcription] — wrong bracket form for archetype annotation"
CONTENT_DISCIPLINE::"Qualifier content MUST be ≤32 chars and ≤4 underscore-tokens. Longer content is snake_case prose masquerading as an annotation — extract to a sibling field."
CONTENT_WRONG::"HEPHAESTUS"
CONTENT_RIGHT::"HEPHAESTUS + PRINCIPLE::"Transcribe all content without loss.""
MULTI_ARCH::"[HEPHAESTUS, ATLAS] — list of annotated archetypes"
§4::HOLOGRAPHIC_CONTRACTS
// v6: Documents carry their own validation law in META. Two distinct uses:
// (A) CONTRACT in META = document-level validation law (what this document must contain)
// (B) HOLOGRAPHIC pattern in BODY = field-level constraint (what this field must satisfy)
§4a::CONTRACT_IN_META
// Place in META block. Defines validation rules for the whole document.
FORM::"CONTRACT::HOLOGRAPHIC"
// CONTRACT value is an annotation — use <> not []
// The holographic compiler reads META.CONTRACT to validate all fields below.
ANCHORING:
FROZEN::"CONTRACT::HOLOGRAPHIC<frozen@sha256_abc123> — locks schema to specific hash, hermetic"
LATEST::"CONTRACT::HOLOGRAPHIC<latest@local> — resolves to current local schema, mutable"
// Use frozen@ for production documents requiring reproducibility.
// Use latest@local for active development documents.
GRAMMAR_FIELD::"GRAMMAR::GBNF_COMPILER — emits GBNF for constrained generation"
§4b::HOLOGRAPHIC_BODY_PATTERN
// Field-level constraint in BODY. Syntax: KEY::["value"∧CONSTRAINT→§TARGET]
// The brackets contain: value ∧ constraint → routing target
SYNTAX_BREAKDOWN:
VALUE::"the literal value or expression"
CONSTRAINT::"REQ, OPT, ENUM[a,b], REGEX[pattern], RANGE[min,max], MAX_LENGTH[n], ISO8601, DATE"
TARGET::"§SECTION — where validated values route (optional)"
EXAMPLE:
STATUS::["ACTIVE"∧ENUM[ACTIVE,DRAFT,DEPRECATED]→§LIFECYCLE] PRIORITY::["HIGH"∧ENUM[HIGH,MEDIUM,LOW]] LATENCY::["<200ms"∧REGEX[<\d+ms]]
CONSTRAINT_TYPES:
CORE::[
REQ,
OPT,
CONST,
ENUM,
TYPE,
REGEX,
DIR,
APPEND_ONLY
]
EXTENDED::[
RANGE,
MAX_LENGTH,
MIN_LENGTH,
DATE,
ISO8601
]
§4c::CONTRACT_BLOCK_EXAMPLE
// Full META block using CONTRACT for a typed document
EXAMPLE:
```
===MY_DOCUMENT===
META:
TYPE::DECISION
VERSION::"1.0.0"
CONTRACT::HOLOGRAPHIC<latest@local>
STATUS::["ACTIVE"∧ENUM[ACTIVE,DRAFT,DEPRECATED]]
OWNER::["team-name"∧REQ]
DECISION::["adopt microservices"∧REQ]
===END===
§5::BLOCK_NOTATION_RULE // Hierarchical content MUST use block notation RULE::"Nested structures (maps containing maps) MUST use BLOCK notation: single colon + indented children" NEVER::"Inner value is itself an inline map: KEY::[outer::[inner::val]] — error E_NESTED_INLINE_MAP in strict mode, warning W_NESTED_INLINE_MAP in lenient mode" PRIMARY_CASE::"Agent §2::BEHAVIOR definitions — CONDUCT, PROTOCOL, OUTPUT blocks require block notation" CORRECT:
CONDUCT:
TONE::"Precise"
PROTOCOL:
MUST_ALWAYS::[rule_a, rule_b]
```
WRONG::"CONDUCT::[TONE::"Precise", PROTOCOL::[MUST_ALWAYS::[rule_a]]]"
RECOVERY_ON_E_NESTED_INLINE_MAP::"Fix is BLOCK form — NOT flatten-to-scalars (creates FLAT_PREFIX_SCALARS anti-pattern, §6), NOT collapse-to-blob (creates W_SNAKE_CASE_BLOB). The wrong escapes produce a different error class, not a solution."
§6::ANTI_PATTERNS
// Each has a concrete example of what NOT to do
ISOLATED_LIST::"[auth, payments, users] with no relationships — use DECISION::microservice_extraction[auth⊕payments→independent_services] instead"
FLAT_HIERARCHY::"All keys at top level with no grouping — group related keys under a parent BLOCK"
BURIED_NETWORK::"RELATED_TO::other_service hidden in prose comment — use explicit operator: auth→payments[dependency]"
OPERATOR_SOUP::"RESULT::A+B->CD all in one expression — break into separate keyed fields"
PROSE_BLEED::"Stopword-laden English sentences as values — quoted telegraphic phrases ARE valid (see §6a). Ban applies when operators could compress the same semantics."
INLINE_ARRAY_ROOT::"TOKEN::[KEY::v, KEY2::v2] — inline map used as multi-field token root. Non-canonical for map tokens even when values are atomic; BLOCK form is mandated. Triggers E_NESTED_INLINE_MAP as soon as any child value needs nesting (§5::BLOCK_NOTATION_RULE). Fix: use BLOCK form (TOKEN: + indented children) from the start."
FLAT_PREFIX_SCALARS::"PARENT_CHILD::v, PARENT_CHILD2::v2 — flattened hierarchy via key name prefixes instead of BLOCK nesting. Destroys grouping and LLM attention. Fix: group under a PARENT: block with CHILD::v children."
STRUCTURAL_SYNTAX_IN_VALUE::"<> annotation ∨ [] constructor embedded INSIDE a quoted telegraphic value — e.g. "migration[high_risk] → downtime" or "SISYPHEAN[bugs] ⊕ KAIROS[repair]". Structural forms are key/identifier-only (§3, literacy §1b: <> qualifies identity, [] parameterizes operations). Inside a value the parser treats them as opaque text → all the ambiguity, none of the validation, and it blurs the structural⇌value boundary. Fix: inside a value, relations carry via telegraphic operators only (→ ⇌ ∧ ∨ ⊕); push facets to a sibling field or an annotated KEY. 'migration → downtime' + RISK::high ∨ MIGRATION:."
§6a::TELEGRAPHIC_PHRASE
DEFINITION::"Quoted value with stopwords dropped; operators ⊕ ⇌ ∧ ∨ → carry relational meaning English connectives would spell out"
RULES::[
"Drop stopwords (is, at, for, the, a, with, by, of) — operators carry connectives",
"Use ⇌ for tension ('security ⇌ usability' not 'security at odds with usability')",
"Use → for causality ('migration → conflict' not 'migration causes conflict')",
"Preserve named entities, thresholds, IDs — never compress these",
"Use ∧ for joint conditions, ∨ for alternatives, ⊕ for emergent synthesis",
"Structural syntax (<> / []) is key/identifier-only — NEVER embed inside the quoted value (see §6::STRUCTURAL_SYNTAX_IN_VALUE)"
]
EXAMPLE_PAIR:
BEFORE::""natural language at odds with OCTAVE because stopwords" (13 tokens)"
AFTER::""natural language ⇌ OCTAVE → stopword overhead" (~5 tokens)"
WHY::"operators are parse-efficient for LLM attention — same fidelity, lower token cost"
SEE_ALSO::"octave-compression §4::R3a for full rule set"
§7::TIER_NORMALIZATION_AUDIT_CHANNEL
// ADR-0006 SR1-T1 Step 3 (v1.12.0): centralised audit channel for I4 completeness
MODULE::"octave-mcp:src/octave_mcp/core/grammar/tier_normalize.py"
// ^ path is in the octave-mcp repo (upstream OCTAVE implementation), not this repo.
API:
LOG_REPAIR::"log_repair(log, rule_id, before, after, *, safe=True, semantics_changed=False) — single precise entry point appending a RepairTier.NORMALIZATION entry"
ACTIVE::"active(log) context manager — binds log as the ContextVar-scoped sink so pipeline-internal sites (notably emitter identifier-dequoting) can record receipts without threading RepairLog through emit()'s public signature"
RECONCILE::"reconcile_canonical_emission(log, baseline_bytes, canonical_bytes) — reconciler bridge"
RULE_IDS:
PRECISE::"TN_IDENTIFIER_DEQUOTE — was_quoted-driven dequoting at emit_assignment"
BRIDGE::"TN_RECONCILE_CANONICAL — coarse-grained post-emit baseline-vs-canonical receipt"
RECONCILER_BRIDGE_PATTERN:
PURPOSE::"Closes the audit-cardinality gap for diffs that upstream precise loggers do not yet cover (blank-line stripping pending Sprint 3+ trivia population; triple-quote collapse pending new lexer W-code)"
DEDUP_DISCRIMINANT::"Only RepairTier.NORMALIZATION entries on the log suppress the bridge. RepairTier.REPAIR (schema repairs) and RepairTier.FORBIDDEN entries do NOT count — they are orthogonal dimensions"
SELF_DEPRECATION::"When Sprint 3+ trivia and the new triple-quote lexer W-code land, precise loggers will cover their respective diffs, the dedup precondition fails, and the reconciler no-ops without any code change"
INTEGRATION_POINTS:
EMITTER::"emit_assignment: precise log when assignment.was_quoted is True AND emitter chose to emit bare (identifier-shape dequoting)"
WRITE_PY::"octave-mcp:src/octave_mcp/mcp/write.py — tier_normalize.active(tier_normalize_log) wraps each _emit_with_style call; reconcile_canonical_emission runs after final emit; entries drain into result[corrections]"
===END===
Source: elevanaltd/octave-mcp — distributed by TomeVault.