Colophon

This site was built conversationally, by application of the architecture.

Three cooperating MCP servers over one capability registry. Every page you are reading was written by an agent, checked twice against the revWorx art direction, by rule and on the rendered page, then reviewed by a person through a signed preview link before publication.

Read Section 14

01 —Three pillars, one registry

Why is trust a routing decision?

A homepage edit, a bulk catalog update and a plugin upgrade carry very different risks. Each write on this site goes to the surface that can govern that risk.

  • GOVERNED CHANGE
    Anything irreversible

    Theme changes, template edits, plugin updates, publishing. Each with a snapshot, a dry run, a design check against the art direction and automatic rollback on a failed health check.

  • BROAD BRIDGE
    Routine and bulk

    Drafting, media, bulk reads and routine writes, where breadth matters more than ceremony.

  • GROUND TRUTH
    Diagnosis

    Health checks, rendered-page inspection, file reads, and the site-side memory and skills the agent carries.

02 —Design governance

An agent that can edit a page can also make it ugly, and will do so confidently.

So design is checked, not hoped for. A named design direction carries this brand’s tokens, voice, imagery rules and a list of things that must never appear. Every write is judged against it twice: by rule before it lands, and on the rendered page after. What you are looking at passed both.

  • 1,184

    agent-reachable tools on this web surface, measured 2026-10-05

  • 3

    cooperating MCP servers, each tuned to a different level of trust

  • 1

    capability registry every pillar reads, so new extensions enrich all three at once

  • 2

    design checks per write: by rule, then on the rendered page

03 THE CONCIERGE
The WEB Agent, behind one of thirteen channel surfaces.

The chat in the corner is the WEB Agent: the public surface of the same Agent Zero instance that built this site, engaging visitors under guardrails. It can describe how a page was made, demonstrate the architecture or qualify a question, and it escalates to a human the moment a conversation needs one. Anything that needs a person goes to dale@revworx.ai.

Need more pipeline without more cost and complexity?

Start with a conversation. We map your current stack against the reference architecture and show you where the leverage is, which parts you already own and what the first ninety days would look like.