Practice III — AI Architecture

Verdi · Nabucco · Omero

Operating Layer

Three-component operating layer: unified inbox, autopilot scheduler, landing-page builder.

01

Overview

The Consistory stack would be incomplete without an operating layer that handles the workhorse functions — inbox management, scheduled task execution, landing-page generation — at the same schema and audit standard as the rest of the system. Off-the-shelf solutions (Helpscout for inbox, cron-job.org for scheduling, WordPress page-builder plugins for landings) each introduce their own data ownership and audit problem.

Verdi handles inbox unification (IMAP/SMTP integrated with Parsifal). Nabucco runs the autopilot scheduler on five-minute cron ticks, redeployed from infrastructure-as-code. Omero generates landing pages and templates linked to lead audiences. Together they remove three categories of vendor dependency.

02

Specifications

  • Verdi — Stack: IMAP · SMTP · Parsifal integration
  • Verdi — Unified inbox, multi-account, schema-aligned
  • Nabucco — Stack: CRON · IaC · 5-minute tick
  • Nabucco — Autopilot scheduler with rollback observability
  • Omero — Stack: CMS · template engine · audience-link
  • Omero — Landing-page builder linked to lead audiences
  • Common: full audit trail, role-based access, version control
  • Removes three categories of off-the-shelf vendor dependency

03

Engagement

Engagements within this module proceed by written brief. Submissions are evaluated within five business days. Acceptance opens a scoping conversation; mandate is governed by bilateral contract.