S/BAI SYSTEM / 02

For Adrian + the Lifestyle REI room

Open the stack ↓
FERNDALE FIELD SYSTEM PUBLIC SHOWCASE

Not achatbot.A crew.

Adrian—this is the technical companion to the first Ferndale field report: the AI architecture, structured artifacts, release system, and control gates underneath the visible work.

THE TECHNICAL THESIS

AI becomes useful when it can carry state, produce artifacts, and stop at the right gate.

The breakthrough was not a clever prompt. It was turning a chain of specialized decisions into a reusable operating system: each role has a job, each handoff has a format, and every public action has a verification or approval boundary.

SYSTEM ARCHITECTURE

One objective.
Four layers.

Information moves forward only after it becomes reliable enough for the next layer.

01INPUT

A real market

  • Ferndale businesses
  • Public web evidence
  • One $500 offer
  • Jeff’s judgment
→
02INTELLIGENCE

Structured reasoning

  • Identity resolution
  • Evidence ledger
  • Qualification score
  • Positioning brief
→
03PRODUCTION

Working artifacts

  • Distinct website concepts
  • Static release packages
  • Letters + QR cards
  • Creative matrix
→
04DELIVERY

Controlled release

  • Isolated subdomains
  • Individual HTTPS
  • Paused ad objects
  • Human approval gates
SPECIALIZED AI ROLES

Small jobs.
Explicit handoffs.

The system behaves less like one all-knowing assistant and more like a coordinated team with written scopes.

01

ORCHESTRATOR

Dorothy

Holds the brief, chooses the next specialist, checks continuity, and refuses to advance past a broken gate.
↘
02

RESEARCH

Evidence engine

Resolves business identity, gathers public facts, records sources, flags conflicts, and separates evidence from inference.
↘
03

STRATEGY

Offer logic

Connects audience, problem, promise, price, next step, fulfillment, and measurement into one transaction.
↘
04

PRODUCTION

Site builder

Turns the verified brief into distinct copy, art direction, responsive code, assets, metadata, and conversion paths.
↘
05

DELIVERY

Deployment system

Packages static releases, isolates each subdomain, provisions HTTPS, preserves rollback copies, and checks the live host.
↘
06

DISTRIBUTION

Outreach + ads

Builds personalized letters, email drafts, QR routes, tracked destinations, and paused campaign test cells.
↘
07

CONTROL

QA gates

Checks mobile layout, links, facts, legal continuity, security headers, placement crops, and approval boundaries.
↘
STRUCTURED ARTIFACTS

Not vibes.
Inspectable files.

The output of each stage becomes a durable input to the next: facts, manifests, builds, and release evidence.

campaign-manifest.jsonVERIFIED EXAMPLE
{
  "design": "2x2x2_full_factorial",
  "factors": {
    "headline": ["H1", "H2"],
    "primary_text": ["T1", "T2"],
    "style_bundle": ["S1", "S2"]
  },
  "cells": 8,
  "status": "PAUSED",
  "approval_required_before_spend": true
}

Two headlines × two text angles × two visual/landing-page bundles produced eight traceable test cells. The system prepared them; spending still required a human decision.

evidence-record.jsonWORKING CONTRACT
{
  "field": "official_website",
  "value": "https://example.com/",
  "source": "first_party",
  "confidence": "high",
  "checked_at": "2026-07-22",
  "conflict": null
}

Customer-facing facts carry source, confidence, and conflict status. Missing evidence is omitted or routed to owner confirmation—not filled with plausible-sounding copy.

RELEASE ENGINEERING

From generated code to a host we can trust.

The deployment path was designed for real public previews, not screenshots that disappear after a demo.

VALIDATED SOURCE→STATIC PACKAGE→ISOLATED SUBDOMAIN→INDIVIDUAL TLS→LIVE QA→ROLLBACK READY
Exact-host protection

Preview releases reject unauthorized copies and cannot be embedded in another site.

Release rotation

A new version replaces the active package while the prior version is retained for recovery.

Live verification

The job is incomplete until the public HTTPS page returns the expected title, assets, links, and responsive layout.

EXPERIMENT DESIGN

Eight cells.
Three variables.

The Ferndale campaign encoded a directional 2×2×2 test while preserving a primary business outcome and an approval-gated budget.

01H1·T1·S1PAUSED
02H1·T1·S2PAUSED
03H1·T2·S1PAUSED
04H1·T2·S2PAUSED
05H2·T1·S1PAUSED
06H2·T1·S2PAUSED
07H2·T2·S1PAUSED
08H2·T2·S2PAUSED
PRIMARY OUTCOMECost per completed website request

Not clicks. Not applause. A business event.

THE CONTROL PLANE

Autonomous work.
Bounded authority.

AI can research, draft, build, inspect, and prepare. Publishing, contacting people, changing customer property, and spending money are separate authority classes.

01

Truth

Can every material claim be traced to evidence?

PASS / HOLD
02

Rights

Are imagery, logos, and personal details safe to publish?

PASS / HOLD
03

Continuity

Do offer, page, outreach, and ads describe the same transaction?

PASS / HOLD
04

Function

Do links, forms, mobile layouts, tracking, and HTTPS work live?

PASS / HOLD
05

Authority

Is the next external action actually approved?

PASS / HOLD
06

Learning

Is the outcome measurable without confusing the variables?

PASS / HOLD
OPEN THE WORK
01The first field reportadrian.slashnburngrowth.biz ↗02The Ferndale offerferndale.slashnburngrowth.biz ↗03Personalized proofals-downtown-diner.slashnburngrowth.biz ↗

For Adrian and the room: the opportunity is not “use AI.” It is deciding which repeatable judgment should become a system.

What should we systemize next?↗