Oracle Vision

an Oracle Vision

METHOD MOIRAI

✦ ✦ ✦

GUIDE

Governed multi-model orchestration. One brief. Every medium. Every cost visible.

Multiple AI stages review your brief in sequence, with quality checks & a saved archive — no single model writes the final output alone.

Part 1 · The Flow

From brief to sealed output

1

Workshop — Intake

Before any run starts, the draws out your actual intent through a conversational intake. As you describe what you need, MOIRAI builds a structured beside the chat — title, summary, deliverables, approach, constraints, feasibility.

Talk or type. The Oracle voice reads back each Workshop reply so you can have a fully spoken intake conversation.

2

Cauldron — Review & Approve

The Cauldron surfaces on the right column once enough context is gathered. You review it, edit any field, & either Approve or reject before a weave can begin. Approval is required — the seal gate enforces it.

3

Ship the Weave

Submitting fires the three-fate orchestration pipeline. A streaming feed shows each stage completing in real time — cipher glyphs reveal each character as the AI writes. The run is archived on completion.

Creative outputs — image, video, voice, music, sound effects — ship alongside the written synthesis in the same run.

4

Seal Gate (Atropos)

After the weave, the QA pass grades the output. State machine: draft → pending_approval → approved → pending_review → sealed. Sealed runs are immutable — export-ready.

5

Archive & Export

Every run lands in /archive. Export as branded HTML, Markdown, or PDF-ready. Soft delete → trash → permanent. Full search.

✦ · ✦

Even the thread begins somewhere: what is spun is not yet fate, only possibility.
The Spinner Codex · Part I

✦ · ✦

Part 2 · Orchestration Tiers

Three tiers, one pipeline

Each tier runs the same three-fate chain — (gather), (measure), (refine) — with increasing isolation & adversarial pressure.

Tier 1
FREE · STARTER · PRO

Sequential pass: Clotho → Lachesis → Eunoia. Faster cycles, lighter cost. Each stage sees the prior output.

Tier 2
PRO · BUSINESS

Blind parallel isolates — each fate runs without seeing the others — then two reconciliation passes, Eunoia final refinement, optional adversarial critique. Reduces model confirmation bias.

Legacy
All plans

All three providers run in parallel then synthesized. Historical mode; Tier 2 is generally stronger.

Full invocation — Business plan only. Routes Eunoia to its highest-capacity mode for maximum quality. Gated by operator environment variable. Cost preview shown before each run.

✦ · ✦

Every run is a question posed to three minds. The Seal is their answer, reconciled.
The Spinner Codex · On Orchestration

✦ · ✦

Part 3 · Creative Outputs

One brief. Every medium.

A single run can generate written synthesis alongside any combination of creative outputs. Plan access controls which media are available.

WriteImageVideoVoiceMusicSound Effects
Every creative output is logged with provider & estimated cost so usage stays transparent & traceable across your runs.

Part 4 · Tools

Intake & research utilities

Link & Intake/tools/link-analysisFetch URLs — YouTube transcripts, articles — & classify them against a brief goal. Returns structured Markdown.
Classify Intake/tools/link-analysisPaste messy raw text → structured intake classification with intent, constraints, & delivery format.
Capability Request/tools/link-analysisSubmit a request for a workflow the platform does not yet support — logged for operator review.
Audio Transcribe/tools/link-analysisUpload a local audio file → clean text transcript. Paste the result directly into a MOIRAI run.

Part 5 · Governance

Observable, auditable, cost-bounded

Every run emits structured audit events — model routing decisions, token share fractions, creative COGS, escalation flags. Operators view these via the internal usage observability endpoint & governance alerts dashboard.

The system parks runs that contain escalation-flagged content for operator review before delivery. Accept continues; revise marks the run for rework.

Billing is Stripe-backed with a nightly cron reconciler. Usage limits, unseal caps, & plan-gated features are enforced server-side — not by frontend flags.

Part 6 · External API

Integrate MOIRAI into your stack

Use the external API when you need the pipeline inside your own application — batch processing, automated workflows, or programmatic delivery to your clients. The same three-stage weave runs server-to-server, with identical governance gates & audit trail as a manual run. Nothing changes about what runs; only how you trigger it.

Server-to-server access via POST /api/v1/generate — synchronous or async with a callback URL. API key auth via Authorization: Bearer. Keys are rotated server-side without a code deploy.

POST /api/v1/generate
Authorization: Bearer <MOIRAI_API_KEY>

{
  "prompt": "string",
  "moiraiTier": "tier1" | "tier2" | "legacy",
  "collaborationMode": "synthesize" | "compare" | "debate"
}

// Sync response
{ "ok": true, "output": "...", "moiraiTier": "tier1", "durationMs": 12400 }

// Streaming (SSE)
POST /api/v1/generate/stream → text/event-stream

Timing-safe key comparison. MOIRAI_API_KEY is scoped per-account & never logged.

✦ · ✦

Bring the strand to the Loom. What you receive will be what was already there — made clear.
The Spinner Codex · On the Loom

✦ · ✦

Get started

Open MOIRAI, describe what you need in the Workshop, & review the plan before you run. Every run is saved, exportable, & traceable.