Every well-designed security framework eventually runs into the same problem: how do you compare a typing error in a config file with a kernel-level privilege escalation? They are both "bugs," but treating them equally gives you either constant false alarms or constant misses. SCBE-AETHERMOORE answers this question with the Six Sacred Tongues — six named domains, each with a fixed numeric weight drawn from the Fibonacci/golden-ratio sequence.
| Code | Name | Domain | Weight |
|---|---|---|---|
| KO | Kor'aelin | Control & Orchestration | 1.000 |
| AV | Avali | I/O & Messaging | 1.618 |
| RU | Runethic | Policy & Constraints | 2.618 |
| CA | Cassisivadan | Logic & Computation | 4.236 |
| UM | Umbroth | Security & Privacy | 6.854 |
| DR | Draumric | Types & Structures | 11.090 |
If you stare at the numbers for a second they click into place: φ&sup0; = 1.000, φ¹ = 1.618, φ² = 2.618, φ³ = 4.236, φ⁴ = 6.854, φ⁵ = 11.09. Each tongue's weight is the next power of the golden ratio. That choice does three useful things at once.
φⁿ + φⁿ⁺¹ = φⁿ⁺². Any two adjacent tongue costs automatically sum to the next one. When you combine a policy violation (RU) with an I/O violation (AV), you get exactly one "Cassisivadan unit" of cost — the framework does not need special-case addition rules.H(d, R). Each tongue's weight becomes its realm radius R in the 14-layer pipeline. Plugging golden-ratio powers into H(d, R) = R^(d²) gives smooth cost surfaces with no awkward discontinuities between domains.Because the weights are φⁿ, the jump from "low-sensitivity I/O error" (AV, 1.618) to "security invariant violation" (UM, 6.854) is not a 4x bump — it is a 4.24x bump exactly, and that ratio is preserved no matter what realm you are comparing.
The baseline tongue. Scheduling, task routing, agent lifecycle. KO is the reference weight — everything else is measured relative to it.
Anything that crosses a process boundary: file descriptors, sockets, RPC, chat messages, tool calls. AV is slightly heavier than KO because a wrong byte on the wire can cascade in ways a wrong byte in a local variable cannot.
Declarative rules, ACLs, rate limits, consent requirements. RU violations are the first sign that something is acting outside its sanctioned envelope, which is why they cost 2.618 — enough to dominate AV noise but still well below logic bugs.
Pure computation — state transitions, math, control flow. A bug in CA is usually an incorrect answer, which is worse than a policy drift because it contaminates everything downstream.
Authentication, encryption, secrets handling, sandbox invariants. This is the realm where hostile actors live, and the 6.854 weight guarantees that a UM alert will always outrank stacked KO/AV/RU/CA concerns combined.
The heaviest tongue. Type systems, schema invariants, serialization contracts. A DR violation means the ground under every other tongue just shifted — if types are wrong, then the assumptions that UM relied on are wrong, which means UM's security claims are also wrong. DR has to be the largest weight in the stack, and φ⁵ just happens to fit.
The Tongue Encoder demo lets you paste code, prose, or a JSON payload and watch SCBE tag each token with its tongue and weight. For the full philosophical treatment — including why the tongues have those names — see the Aethermoore book.