BAST · Olimpo · The cycle that runs the studio

How we ship.
From brief to live, with a verifier loop in between.

The Olimpo is a multi-agent creative system. This is the cycle behind every run — inspired by SDD, adapted to creative production, and progressively formalized over six validated packages. Below: the loop, the offers, and the infrastructure that makes minute-scale deploys possible.

v1 · 2026-05-03 6 ofertable packages 1 paradigmatic case (ESIM) Inspired by SDD · LIDR
scroll
Layer 01 · The Cycle

One loop. Two gates. Six artifacts.

Every run starts as a User Story and ends as a Published Feature. Between them, two gates — Verifier and Coherence Check — keep the work from drifting. The first asks does this match the spec? The second, only emitted by Ariadna, asks does the whole sustain the contract?

The Olimpo cycle: from User Story to Feature Published. 01 · INPUT User Story 02 · DECISION Decision-closed Refinement 03 · GATE — ARIADNA Contract 04 · SPEC Implementation Spec 05 · ITERATION LOOP Implementer → Verifier → fail/pass Lime · Nyx · Sibila Brigid Cross-model · QA visual 06 · ARTIFACTS BRANCH TESTS DOCUMENTATION CODE TESTING REPORT PROPOSAL UPDATE GATE — ARIADNA Coherence Check Feature Ready Feature for PR Feature Published
01 · INPUT
User Story
The client's ask, translated to one sentence: as [ICP] I want [output] for [outcome].
02 · DECISION
Decision-closed Refinement
Explicit decisions cleared before a deliverable is promised. What's open gets flagged, never assumed.
03 · GATE — ARIADNA
Contract
Narrative coherence + visual cohesion + strategic alignment. The semantic north of the package.
04 · SPEC
Implementation Spec
The contract concretized in tokens, components, copy, motion, schemas. What the implementers execute.
05 · LOOP
Implementer → Verifier
An agent produces the artifact. A different agent verifies against spec and blocks if it fails.
06 · ARTIFACTS
Six auditable outputs
Branch · Tests · Documentation · Code · Testing Report · Proposal Update.
07 · GATE — ARIADNA
Coherence Check
Only Ariadna emits this. It blocks even if every artifact passed verifier — when the whole stops sustaining the contract.
08–10 · OUTPUT
Feature → PR → Published
Ready (local passes) → For PR (public preview) → Published (client received).
Layer 02 · The Packages

Six offers running on the same cycle.

Each package is the same cycle with a different contract. Same vocabulary, same gates, different ICP and output. The number isn't fixed — these are the six already validated against real runs.

01 Strategic Sprint + Founders / hiring managers who posted a senior role and want to see real capacity before inviting to interview.

Output

Strategic diagnostic + 1 live landing (public URL) + cold pitch / application.

Ariadna's Contract

The proposal sustains a "design partnership long-run" frame, not "freelance in passing". Diagnosis is auditable claim, not flattery.

Verifier loop

  • Lime (visual) → Brigid (cross-browser + brand defense)
  • Sibila (copy) → Ariadna (frame check)
  • Nyx (build) → Brigid (deploy + tildes + reduced-motion)

Acceptance criteria

  • Public URL sustains cold-email claim with no gaps
  • Diagnosis doesn't contradict target's positioning
  • Zero invented data — everything cited or flagged

Validated in

POLY (5 deploys + case study) · ESIM (paradigmatic) · Bitpanda (Atelligo flag = unintended compliment) · Convergent · Mercor (in flight) — Skill /sprint · SOP SOP_STRATEGIC_SPRINT

02 Mockup Web + Live Deploy + Solo-founders / pre-seed startups that need to show something viable to investors or users now, without fighting frameworks.

Output

Live site at <slug>.pages.dev with preview per iteration + reusable base tokens + Cloudflare headers.

Ariadna's Contract

The page communicates the product promise in 8 seconds without off-page explanation. Mobile-first real, not responsive-as-joke.

Verifier loop

  • Lime (wireframe) → Ariadna (mandatory gate if UX open)
  • Nyx (build) → Brigid (curl-check + iOS Safari + viewers + tildes)
  • Lime (visual) → Brigid (cross-device render)

Acceptance criteria

  • Lighthouse pass + visual diff vs mockup
  • Render OK on real iOS Safari (no simulator)
  • Spanish accents correct + reduced-motion fallback

Validated in

bast-olimpo.pages.dev v3 · perla-encuesta.pages.dev · malabartista.com · save-for-life-mockup.pages.dev — Skill /landing-pages

03 Live Design System + Startups that already have product and need to scale UI without hiring an in-house designer.

Output

Figma library + deployable prototype + tokens.json + documented components + internal-use SOP.

Ariadna's Contract

The DS resolves the 8 recurring bugs already paid in past runs. The prototype is deployable, not decorative.

Verifier loop

  • Lime (tokens) → Brigid (consistency + naming)
  • Nyx (components) → Lime (visual fidelity)
  • Nyx (prototype) → Ariadna (sustains use contract)

Acceptance criteria

  • Prototype opens at public URL without auth
  • Tokens validate against client's brand-guide
  • Zero failures in the 8 canonical bugs

Validated in

Brasador DSS (in flight) · SURI tratamientos (PROPUESTA_FINAL) — Skill /design-system · SOP SOP_DESIGN_SYSTEM with Claude Design

04 WhatsApp Agent / Conversational Bot + Businesses operating on WhatsApp (clinics, retailers, D2C brands) that want to automate care/booking/sales without losing brand voice.

Output

Live n8n workflow + Supabase schema + system prompt + tools + protocoled human handoff + E2E tests.

Ariadna's Contract

It's not a bot — it's a conversational agent with brand voice. Identity pliego and sensitive-operations pliego (with confirmation) are non-negotiable.

Verifier loop

  • Nyx (schema) → Brigid (post-migration information_schema.routines)
  • Brigid (workflow) → Nyx (cross-check Meta docs + dedup + locks)
  • Ariadna (prompt) → cross-model review (Claude + Gemini + GPT, 3 approved gate)

Acceptance criteria

  • E2E happy path passes
  • Cross-model returns 0 real GAPs
  • Lock TTL ≤ 90s · dedup by message.id active

Validated in

Perla Nanatka v3.0.1 (E2E successful 2026-04-28) · Conect.ia · Brand Scout — Skill /croquis-agente · SOP SOP_AGENTE_n8n_WHATSAPP (12 patterns)

05 Automated Survey / Form + Founders / brands that need to validate product or feedback with data in their own DB and a brand-voiced email — not generic SaaS with someone else's branding.

Output

Deployable HTML + SQL migration + 2 JS Code nodes + n8n workflow + deploy plan + humanized Resend email.

Ariadna's Contract

The form doesn't feel like a form — it feels like a conversation with the brand. The post-response email is editorial, not transactional.

Verifier loop

  • Lime + Nyx (HTML) → Brigid (mobile + tildes + 14 SOP gotchas)
  • Nyx (SQL/JS) → Brigid (autoMap rejects extras → split fields)
  • Sibila + Lime (email) → Ariadna (tone + accents + ñ)

Acceptance criteria

  • Form inserts into DB with all schema fields
  • Email arrives with HTML + plain-text fallback
  • Next survey of the domain ships in ≤30 min wall-time, zero manual edits outside brief

Validated in

Perla beta v02 · Brasador NPS pilot — Skill /encuesta · SOP SOP_ENCUESTA_AUTOMATIZADA_v2 (38 rules + 14 gotchas)

06 Ad Creatives with narrative bible + D2C brands that need creatives for Meta Ads without dropping craft to AI slop, with a narrative bible every ad respects.

Output

Structured JSON brief + ad creative variants (statics + reels) + shot list with 7 narrative beats + .meta.json sidecar per asset.

Ariadna's Contract

Every ad respects the 7 beats: Hook → Setup → Tension → Idealization → Climax → Resolution → Aftertaste. No AI slop. No recycled hooks.

Verifier loop

  • Scraper (brief) → Ariadna (frame check)
  • Lime + nano-banana (images), SOP phase 0+1 mandatory → Brigid (real-reference -r when product carries brand)
  • Lime + Nyx (reel edit) → Ariadna (7 beats compliance)

Acceptance criteria

  • Ad pack contains identifiable 7 beats
  • Branded product photos use real reference, never invented
  • Sidecar .meta.json complete per asset

Validated in

Brasador (Hola Brasador · Esencial preventa · Vernola Ambassador) — Skills /scraper · /forge · /ad + SOP_ADS bible + SOP_IMAGE_GEN

Layer 03 · The Infrastructure

Why a deploy ships in minutes.

The cycle isn't theoretical — it runs on layered infrastructure that's been built up run by run. Auth channels, creative pipelines, agent memory, canonical SOPs, MCP servers, owned servers. Each layer is what turns "spec" into "live URL" in minutes, not weeks.

Deploy & auth channels

always-on credentials
  • Cloudflare Pages with authenticated CLI
  • GitHub CLI authenticated · scopes ready
  • Self-hosted n8n with public webhooks
  • Managed databases · multi-environment
  • WhatsApp Cloud API · verified tenant
  • Transactional email · root domain verified
  • Server-side Drive sync (no upload/download cycles)
  • Vertex AI access without explicit API keys
  • OpenAI · Anthropic · Gemini · in parallel for cross-model gates

Creative stack

image · audio · video · OCR
  • AI image generation CLI (Flash + Pro, multi-resolution, real-reference, green-screen workflow)
  • Local audio transcription with Whisper
  • Video pipelines via ffmpeg
  • OCR on bilingual documents
  • PDF tools that don't destroy color profiles
  • Image optimization for production weight
  • Lime-specific architecture: skill suite + agent memory + outfit system

Olimpo memory layer

how the agents "know"
  • Six specialized agents (Director, Visual, Copy, Dev, Troubleshoot, Analyst)
  • Twenty-plus skills as invocable commands
  • Indexed global memory with 140+ entries
  • Per-project layer: CLAUDE / STATE / MEMORIA / HANDOFF
  • Per-agent memory inside each project folder
  • Append-only activity log + session brief command
  • Plan files as durable design artifacts

Canonical SOPs

six packages, six SOPs
  • Image generation SOP (mandatory phases 0+1)
  • Ads narrative bible (7 beats, 18 rules)
  • Design System SOP with Claude Design
  • Survey automation SOP v2 (38 rules + 14 gotchas)
  • WhatsApp agent SOP (12 patterns)
  • Strategic Sprint SOP
  • Parametrized templates per SOP

MCP servers

extended tooling
  • UI component search & examples
  • Browser automation
  • Sequential thinking
  • Design tool integration
  • Calendar & mail productivity
  • Drive document access

Owned servers

always-on infra
  • Primary Linux server with Docker (n8n, bots, workflows)
  • Secondary Linux server with Coolify
  • Color-coded terminal profiles per project
  • Subagent invocation by file path