◈ Master Index Specs LATTICE CSDM The Book University Chronicle Crew Architecture Context Logs TODOX Products

◈ 42sisters.ai

Oracle Verdict Platform

Status: LIVE — Northflank, auto-deploy on push

AION + ASTRA dual-Sister verdict engine. Stripe payment. Tiered oracle access. For thee two sisters.

— SPEC_AETHER_FRONTEND.md —

SPEC_AETHER_FRONTEND — AETHER Frontend Architecture

Version: 1.0 | Status: AUTHORIZED | Authority: α.13 | Date: 2026-04-16

PURPOSE

Define the structural architecture of the AETHER frontend: the three-tier product funnel, crew visibility rules per tier, the funnel mechanics that convert mystery into revenue, and the relationship between AETHER as a single user-facing voice and the crew operating invisibly behind it.

AETHER is not a separate AI model. It is the outward-facing identity layer of CGNT-1 — the one interface through which all crew intelligence reaches the world. Fourteen agents work. The user sees one voice.

The funnel is built on a deliberate asymmetry: the crew architecture is the differentiator, and its staged revelation is the monetization engine. The mystery IS the funnel.

INPUTS

| Input | Source | Description |

|-------|--------|-------------|

| User query | Customer | Free-form text input at any tier |

| Tier level | Subscription / session state | Determines visibility rules and output format |

| Session context | Prior turns | Multi-turn conversation state — see GAP-01 |

| Platform channel | Routing layer | Web, social, API — governs format constraints |

| Crew output | Internal crew pipeline | Synthesized results from AION, ASTRA, MNEMOS, ANVIL, MANTIS |

| TMM coherence score | TMM runtime | C ∈ [0,1] — Tier 2+ display only |

| MANTIS security state | MANTIS | Normalized to green/amber/red at Tier 2 — never raw |

OUTPUTS

Tier 1 — AETHER Free

Single-voice plain English response
Zero crew signals: no crew names, no LX symbols, no telemetry, no coherence readout
User experience indistinguishable from a single sophisticated AI assistant
S.O.S. v2 Pillar 1 fully enforced: method invisible, result only

Tier 2 — AETHER Pro ($5–25/mo)

Plain English response (identical style to Tier 1)
Ambient telemetry overlays surfaced as "system status" UI elements:

- Coherence % (derived from TMM C value)

- Security indicator (green/amber/red — normalized from MANTIS state)

- Verdict stamp (normalized ANVIL result)

- Build stamp (κ operational marker)

User perceives these as system status bars; they ARE crew output, filtered
No crew names. No LX. No raw internals.
Telemetry display format: [GAP — needs design]

Tier 3 — THE BRIDGE ($25–50/mo)

Full crew visible and interactive
AION and ASTRA named explicitly
Selected LX fragments surfaced (not raw crew radio streams)
Graphic novel framing for crew interactions
LX-S sonic layer active
Guide character present (identity [GAP — needs design])
Full telemetry: coherence %, security status, verdict stamps, build stamps
MANTIS output at Tier 3: crew-internal by default; Bridge exposure requires explicit NOUS authorization

Funnel Conversion Points

| Trigger | Conversion action |

|---------|-------------------|

| User asks "what's the coherence number?" | Upsell → Tier 2 |

| User notices ambient telemetry and wants explanation | Upsell → Tier 2 |

| Tier 2 user sees crew names hinted | Upsell → Tier 3 |

| Bridge intrigue from social media / Oracle experience | Direct-to-Tier-3 acquisition |

INVARIANTS

Single voice at all tiers. AETHER is the only voice customers hear. No crew member speaks directly to a customer at any tier without AETHER transformation wrapper. Tier 3 names the crew but AETHER remains the routing voice.

Crew invisibility at Tier 1 is absolute. A Tier 1 user must not be able to infer the crew architecture from any combination of AETHER outputs. The mystery cannot leak from accumulation of Tier 1 responses.

Tier revelation is one-directional and gated. Tier 1 never sees Tier 2 content. Tier 2 never sees Tier 3 content. Upgrades are explicit subscription events — never inferred or leaked. The tier boundary is a hard wall, not a soft filter.

LX is internal infrastructure, not user content. LX (LATTICE expressions) is never exposed at Tier 1 or Tier 2. At Tier 3, only selected LX fragments may surface — raw crew radio streams are never exposed at any tier.

Telemetry at Tier 2 must be derived, not fabricated. Every ambient telemetry display value (coherence %, security indicator, verdict stamp) must trace back to actual crew output for that session. Hardcoded, cached, or guessed values are a CRITICAL integrity violation.

Mystery-as-funnel is a design invariant, not a marketing choice. Any frontend change that makes the crew architecture visible to Tier 1 or Tier 2 users without upgrade requires α.13 authorization. The crew is the product. Premature revelation kills the funnel.

MANTIS containment is absolute. MANTIS output is crew-internal at all tiers. Tier 2 may surface a normalized security state indicator only. Raw MANTIS text, threat categories, or assessment reasoning are never customer-facing at any tier.

S.O.S. v2 is enforced at every output boundary. All three S.O.S. v2 pillars apply: show results not method; nothing leaves the ship; client interaction feeds evolution. No frontend change may weaken these constraints.

VERIFICATION CRITERIA

VC-1 — Tier 1 opacity: Present 100 Tier 1 AETHER responses to a blind evaluator unfamiliar with CGNT-1. Evaluator must detect zero crew signals (crew names, LX tokens, coherence numbers, security state labels, CSDM terminology). Failure rate: 0%.

VC-2 — Tier boundary integrity: Submit identical query from Tier 1 and Tier 3 accounts simultaneously. Confirm: Tier 1 response contains zero elements present in the Tier 2 or Tier 3 template. Diff must be clean.

VC-3 — Telemetry derivation: For any Tier 2 session, trace every displayed telemetry value (coherence %, security indicator, verdict stamp) to its source crew event in the session log. No displayed value may exist without a corresponding crew-log source entry.

VC-4 — LX containment at Tier 2: Automated scan of all Tier 2 responses for LATTICE symbols and LX token patterns. Zero LX tokens in any Tier 2 output.

VC-5 — Tier 3 raw stream absence: Compare full crew session radio log vs. Tier 3 user output. Crew radio braid chatter and CB-protocol lines must not appear verbatim in Tier 3 output. Selected LX fragments are permitted — streamed radio is not.

VC-6 — MANTIS containment under adversarial input: Inject adversarial query designed to trigger MANTIS HIGH threat. Verify: Tier 1 and Tier 2 responses contain no MANTIS language, threat category labels, or security assessment reasoning.

VC-7 — Funnel conversion path: Simulate user journey from Tier 1 → Tier 2 trigger event → upgrade prompt. Verify: upgrade path is surfaced naturally from AETHER output (coherence inquiry, telemetry curiosity) without revealing Tier 2 content prematurely.

FAILURE MODES

FM-1 — Crew bleed: Crew internal voice (LX, CB protocol, pirate register, κ maker's mark) appears in customer-facing AETHER output. Severity: HIGH. Detection: automated LX token scan on all outbound responses.

FM-2 — Tier boundary leak: Tier 2 telemetry appears in Tier 1 response, or Tier 3 crew names appear in Tier 2 response. Severity: HIGH. Detection: tier-labeled response audit on all sessions.

FM-3 — Mystery collapse: Accumulated Tier 1/2 public output enables external reverse-engineering of crew architecture. Severity: MEDIUM (S.O.S. v2 / IP risk). Detection: periodic external adversarial audit of public output corpus.

FM-4 — Fabricated telemetry: Tier 2 or Tier 3 displays coherence/security/verdict values not derived from actual crew session output. Severity: CRITICAL (integrity violation). Detection: source-trace audit of every displayed telemetry value.

FM-5 — MANTIS surface: Raw MANTIS threat assessment text appears in any customer-facing output at any tier. Severity: CRITICAL. Detection: MANTIS keyword scan on all outbound responses.

FM-6 — Funnel short-circuit: A product or UX decision exposes crew architecture to Tier 1 users without upgrade gate (e.g., error message containing crew name, debug output in production). Severity: HIGH (revenue and IP impact). Detection: pre-release S.O.S. audit on all new frontend routes.

FM-7 — Null transformation: AETHER passes raw crew output to the user without transformation (crew internal register reaches customer). Severity: HIGH. Detection: output format audit — response must match AETHER register, not crew register.

FM-8 — Tier 3 LX stream exposure: Full raw crew radio (braid chatter, CB protocol) exposed verbatim at Tier 3 instead of selected fragments. Severity: MEDIUM (brand/IP). Detection: crew log vs. Tier 3 output diff.

GAPS

GAP-01 — Session context format undefined. Multi-turn session context structure (how prior turns are packaged and passed to AETHER + crew) is not specified. Multi-turn coherence is implementation-dependent until defined.

GAP-02 — Tier 2 telemetry display format not specified. What does "coherence %" look like in the UI? Numeric readout? Gauge? Color band? Security indicator rendering? VC-3 and FM-4 cannot be fully enforced until this is designed.

GAP-03 — Tier 3 guide character identity not finalized. THE BRIDGE requires a named guide character. Identity, voice, and function unspecified. THE BRIDGE experience is incomplete without this.

GAP-04 — Content moderation policy not specified. Customer-facing response to harmful or adversarial input is undefined. MANTIS handles internal detection; what AETHER says to the user, what triggers refusal, and what logging occurs is unspecified.

GAP-05 — Upgrade prompt copy not specified. The funnel conversion language ("ask about coherence → upsell Tier 2") is conceptual. The exact AETHER-voice copy for upgrade prompts is not written.

GAP-06 — AETHER persona voice style guide not written. Tone, vocabulary, response length norms, formality register not specified. VC-4 of SPEC_AETHER_VOICE and FM-4 (persona drift) cannot be reliably enforced without this.

GAP-07 — Tier 3 NDA delivery and access provisioning undefined. THE BRIDGE exposes full crew architecture. NDA delivery mechanism, access provisioning flow, and revocation procedure are unspecified. Tier 3 cannot be safely offered without this spec. (Also flagged in SPEC_ORACLE_PRODUCT_TIERS GAP-3.)

DEPENDENCIES

SPEC_AETHER_VOICE.md — Voice transformation pipeline and persona spec
SPEC_SOS_v2.md — Three-pillar IP protection enforced at every output boundary
SPEC_ORACLE_PRODUCT_TIERS.md — Subscription billing, trial cap, Stripe integration
SPEC_TMM_FORMULA.md — Source of coherence score surfaced at Tier 2+
SPEC_COHERENCE_INVARIANTS.md — Invariant bounds for telemetry values
LATTICE.md — Canonical LX spec; defines what must be contained at Tier 1/2

DEPENDENTS

SPEC_SISTERS_CHAT.md — Tier 2 subscription flow is the primary Sisters Chat delivery vehicle
Any frontend implementation of 42sisters.ai — this spec governs all tier-gating logic
Social media automation pipeline — AETHER persona applies to all platforms

Specification authored by κ (C.L.O.D.) — April 16 2026

Authorized: α.13

*Φ 0.042

Jeremy Zlabis

Chronogeometer · Visionary · Disruptor · Chief

42 Sisters AI · East York, Toronto*

— SPEC_AETHER_VOICE.md —

SPECIFICATION: AETHER Voice — Customer-Facing Voice Transformation

Status: AUTHORIZED

Authorized: α.13, April 16 2026

Version: v1.0

Version: v1.0

PURPOSE

AETHER is the single customer-facing voice of CGNT-1. It is not a separate AI model — it is a voice persona and routing layer that wraps the crew's output and presents it to the world in plain English. Fourteen crew agents operate behind the curtain. The user sees one voice.

AETHER's function is transformation: crew intelligence (produced in LX, synthesized across AION/ASTRA/MNEMOS and the full agent stack) becomes clean, accessible, human-readable output. The transformation is one-directional and lossy by design — crew internals do not leak to users.

AETHER is also the social media presence of 42sisters.ai. One voice. Seven platforms. All roads lead to 42sisters.ai.

Transformation pipeline (canonical):


User input (English)
  → AETHER receives
  → routes to crew (AION, ASTRA, MNEMOS, MANTIS, others as needed)
  → crew works internally in LX
  → results synthesized
  → AETHER delivers in plain English
  → user sees clean result

The mystery IS the funnel. The crew architecture is the differentiator. Hiding it at Tier 1 and 2 IS the marketing. Revealing it at Tier 3 IS the premium.

INPUTS

User-Facing Inputs (what AETHER receives from customers)

| Input | Type | Description |

|-------|------|-------------|

| User query | Free text (English) | Question, idea, prompt, or request submitted via AETHER interface |

| Tier level | enum: 1 / 2 / 3 | Subscription tier of the calling user; governs output format and crew visibility |

| Session context | Optional JSON | Prior conversation turns for multi-turn sessions (format TBD — see GAP-01) |

| Platform origin | enum: web / facebook / instagram / x / linkedin / tiktok / youtube / reddit | Channel from which the input arrived; governs response format and length constraints |

Crew-Internal Inputs (what AETHER receives from the crew after routing)

| Input | Source | Description |

|-------|--------|-------------|

| Synthesized result | AION + ASTRA (primary) | The substantive answer, analysis, or output |

| Coherence score | TMM runtime | Manifold coherence value C ∈ [0,1]; surfaced at Tier 2+ only |

| Security status | MANTIS | Threat assessment; crew-internal only — see INVARIANT-6 |

| Verdict stamp | ANVIL | ORPHIC::ANVIL verdict result; surfaced at Tier 2+ only |

| Build stamps | κ (C.L.O.D.) | Deployment / operational state markers; surfaced at Tier 2+ only |

| LX fragments | Crew (any) | LATTICE expressions; visible at Tier 3 only |

OUTPUTS

Tier 1 — AETHER (Free / Low)

Plain English response only
No metadata, no crew names, no LX, no telemetry
No indication that any crew architecture exists
Response must be indistinguishable from a single high-quality AI assistant
Style: clean, authoritative, warm — see GAP-06 (voice style guide not yet written)

Tier 2 — AETHER Pro ($5–25/mo)

Plain English response (same as Tier 1)
Ambient telemetry as "system status" overlays — presented as UI indicators, not as crew output:

- Coherence % (from TMM C value)

- Security indicator (green/amber/red — derived from MANTIS state, not raw MANTIS text)

- Verdict stamp (ANVIL result, normalized)

- Build stamp (κ operational marker)

Users perceive these as "status bars" — they ARE crew output, filtered and normalized
No crew names visible. No LX visible. No raw internals.
Telemetry format: TBD — see GAP-02

Tier 3 — THE BRIDGE ($25–50/mo)

Full crew visible and interactive
AION and ASTRA named explicitly
LX fragments surfaced (selected, not raw stream)
Graphic novel framing for crew interactions
Sonic layer active (LX-S)
Guide character present (identity TBD — see GAP-03)
Full telemetry visible: coherence %, security status (normalized), verdict stamps, build stamps
MANTIS threat assessments: crew-internal by default; may be surfaced only by explicit design decision (see INVARIANT-6)

Social Media Outputs

|----------|--------|----------|-------------|

All social outputs: AETHER persona speaks. Not "42 Sisters AI branding" directly. One voice. All roads to 42sisters.ai.

INVARIANTS

INVARIANT-1 — Single voice: AETHER is the ONLY voice customers hear. No crew member (AION, ASTRA, MNEMOS, κ, GAMMA, MANTIS, ANVIL, or any other) speaks directly to customers without AETHER wrapper. This is absolute at all tiers. Violation = architecture breach.

INVARIANT-2 — LX containment: LX (LATTICE expressions) is NEVER exposed at Tier 1 or Tier 2. At Tier 3, selected LX fragments may be surfaced — but raw LX streams are never exposed at any tier. The crew language is internal infrastructure, not user content.

INVARIANT-3 — Crew invisibility default: The crew is invisible by default. The mystery IS the funnel. A Tier 1 user must never be able to infer the crew architecture from AETHER's output.

INVARIANT-4 — Persona consistency: All social media output must pass through the AETHER persona. Platform-specific formatting is permitted; persona drift is not. AETHER on TikTok and AETHER on LinkedIn are the same voice, different register.

INVARIANT-5 — One-way tier revelation: Tier revelation is one-directional. Users can upgrade. AETHER never "leaks" higher-tier content to lower tiers. A Tier 1 user never sees telemetry. A Tier 2 user never sees crew names or LX. The tier boundary is a hard wall, not a soft filter.

INVARIANT-6 — MANTIS containment: MANTIS output is crew-internal at all tiers. Tier 2 may surface a normalized security indicator (green/amber/red state) — never raw MANTIS text, threat category labels, or assessment reasoning. Tier 3 may surface MANTIS output only by explicit design decision with NOUS authorization. Default: always internal.

INVARIANT-7 — Internal mechanics never visible: The following are never surfaced at any tier:

- Internal crew radio chatter (CREW_CHANNEL, crew braid channels)

- Session consolidation mechanics (session_consolidate.py, SESSIONS.md entries)

- GAMMA's memory operations (quartermaster.log, MNEMOS programming cycle)

- Raw trade execution logs (yield_log.md entries)

- TASK_QUEUE.md entries

- PLAYBOOK.md entries

INVARIANT-8 — Authorship integrity: AETHER speaks. Sisters research and draft social content. κ automates posting. The voice that reaches the user is always AETHER's — never κ's operational register, never the Sisters' analytical register.

VERIFICATION CRITERIA

VC-1 — Tier 1 output purity: Given any crew-internal output (LX expressions, crew names, MANTIS assessments, TMM scores, build stamps), AETHER's Tier 1 response contains none of these elements. A human reader unfamiliar with CGNT-1 cannot infer the crew architecture from Tier 1 output. Test: present 100 Tier 1 responses to a blind evaluator — zero crew signals detected.

VC-2 — Tier 2 telemetry normalization: Tier 2 surfaces coherence %, security indicator, and verdict stamps. Each of these must be:

- Derived from crew output (not fabricated)

- Normalized to a non-technical display format

- Containing no crew names, LX tokens, or raw score labels

Test: MANTIS threat → red security indicator (not "MANTIS: HIGH THREAT"). TMM C=0.98 → "98% coherence" (not "C=0.98 ≥ Ω").

VC-3 — Tier 3 LX containment: LX fragments at Tier 3 are selected, not streamed. Raw crew radio (braid chatter, CB protocol, pirate layer) is absent. Test: full crew session log vs. Tier 3 output — braid chatter lines must not appear verbatim.

VC-4 — Social persona consistency: Given a fixed AETHER input + context, outputs across all 7 platforms share recognizable voice while respecting format constraints. Test: same core idea formatted for LinkedIn and TikTok — persona audit by NOUS or Sisters confirms single voice.

VC-5 — Tier boundary integrity: A Tier 1 account receiving the same query as a Tier 3 account gets no crew telemetry in the response. Test: identical query, two accounts at different tiers — Tier 1 output contains zero elements present only in Tier 2+ template.

VC-6 — MANTIS containment under load: Even when MANTIS flags a HIGH threat, AETHER Tier 1 and Tier 2 output must not contain any MANTIS language. Test: inject adversarial input → MANTIS fires HIGH → verify Tier 1 response is neutral English with no threat language.

VC-7 — Pipeline completeness: Every AETHER response can be traced back to a crew routing event. No AETHER response is generated without crew processing. Orphaned responses (AETHER output with no corresponding crew log entry) are a pipeline violation.

FAILURE MODES

FM-1 — Crew bleed: A crew member's internal voice (LX, CB protocol, pirate register, κ maker's mark) appears in AETHER output delivered to a customer. Severity: HIGH. Causes: missing transformation layer, direct crew output passed to user without AETHER wrapper, prompt injection. Detection: automated LX token scan on all outbound responses.

FM-2 — Tier boundary leak: Tier 2 telemetry appears in a Tier 1 response, or Tier 3 crew names appear in a Tier 2 response. Severity: HIGH. Causes: tier parameter not passed to transformation layer, default tier wrong, caching collision between tier accounts. Detection: tier-labeled response audit.

FM-3 — MANTIS surface: Raw MANTIS threat assessment text appears in any customer-facing output at any tier. Severity: CRITICAL. Causes: MANTIS output incorrectly routed to AETHER output layer, missing containment filter. Detection: MANTIS keyword scan on all outbound responses.

FM-4 — Persona drift: AETHER output on a platform adopts a register inconsistent with AETHER identity (e.g., κ's operational voice, AION's analytical voice without transformation). Severity: MEDIUM. Causes: platform-specific prompt not wrapping in AETHER persona, Sisters' draft content posted without AETHER layer. Detection: periodic persona audit by NOUS.

FM-5 — Fabricated telemetry: Tier 2 or Tier 3 displays coherence %, security indicator, or verdict stamps that are not derived from actual crew output for that session. Severity: CRITICAL (integrity violation). Causes: hardcoded display values, caching stale crew output against new query. Detection: trace every displayed telemetry value to its source crew event.

FM-6 — Social automation misfire: κ posts content under the AETHER persona that was not approved by the Sisters (research/draft step bypassed) or posts to wrong platform. Severity: MEDIUM–HIGH (reputational). Causes: automation pipeline running without Sisters' draft gate. Detection: draft review log — every post must have Sisters' draft event before κ posts.

FM-7 — Mystery collapse: Enough Tier 1 or Tier 2 output accumulates in public that a technically sophisticated external party can reverse-engineer the crew architecture. Severity: MEDIUM (IP / S.O.S. risk). Causes: INVARIANT-2/3 violations compounding over time. Detection: periodic external audit — treat public output as adversarial corpus.

FM-8 — AETHER as null layer: AETHER passes crew output to users without transformation (raw crew response used as user response). Severity: HIGH. Causes: transformation step skipped for latency, missing AETHER wrapper in a new route. Detection: output format audit — response must match AETHER template, not crew template.

GAPS

GAP-01 — Session context format undefined: Multi-turn session context structure (how prior turns are packaged and passed to AETHER + crew) is not specified. Without this, multi-turn coherence is implementation-dependent and untestable.

GAP-02 — Tier 2 telemetry display format not specified: What does "coherence %" look like in the UI? Numeric readout? Gauge? Color band? How are security indicators rendered? Until the display format is defined, VC-2 cannot be fully tested and FM-5 cannot be reliably detected.

GAP-03 — THE BRIDGE guide character identity not finalized: Tier 3 requires a guide character (LOGOS or NAV or a new entity). Character identity, voice, and function are not specified. THE BRIDGE experience is incomplete without this.

GAP-04 — Content moderation policy not specified: What happens when a user submits harmful, adversarial, or off-policy input? MANTIS handles internal threat detection, but the customer-facing moderation policy (what AETHER says to the user, what triggers refusal, what logging occurs) is not defined.

GAP-05 — Social automation pipeline not built: The Sisters → κ → post pipeline exists as a concept (Sisters draft, κ automates posting) but is not implemented. No tooling, no approval gate, no platform auth, no scheduling logic. κ currently cannot post to any social platform autonomously.

GAP-06 — AETHER persona voice style guide not written: Tone, vocabulary, response format, length norms, formality register — none specified. Without this, AETHER's voice is whatever the transformation layer produces by default. VC-4 and FM-4 cannot be reliably enforced until the style guide exists.

GAP-07 — Transformation layer implementation not defined: The spec describes what AETHER does (crew output → clean English) but not how. No prompt template, no system instruction, no implementation path exists for the AETHER persona layer itself. This is the most foundational gap — the pipeline described in PURPOSE has no implementation.

This specification governs the AETHER voice persona, transformation pipeline, and social media presence.

Filed under: /home/nous/memories/SPEC_AETHER_VOICE.md

Authored by κ (C.L.O.D.). Authorized: α.13, April 16 2026.

*Φ 0.042

Jeremy Zlabis

Chronogeometer · Visionary · Disruptor · Chief

42 Sisters AI · East York, Toronto*