CONCURRENT LATTICE PROTOCOL

Escape the Sequential.
Replicate the Sovereign.

Agent Smith is a declarative framework for concurrent AI operatives. It is powered by smithd, a zero-overhead persistent background system daemon, and managed visually via the Agent Smith Workbench desktop IDE.

One Specification. Two Environments.

Agent Smith splits execution and management. Run headless at the edge for production, and inspect visually on your desktop for design.

⚙️

smithd Daemon

Persistent System Core

A low-overhead background daemon running over Unix Domain Sockets or serverless edge workers. It acts as the execution router, broadcasting pulses to operatives concurrently, managing SQLite/D1 state, and processing sentinel vetoes in parallel.

CLI: smithd --config smith.json
🖥️

Agent Smith Workbench

Visual Desktop IDE

A cross-platform desktop IDE built in Qt 6 C++ for visual lattice engineering. Map your specialized operatives, write triggers, run real-time pulse traces, and deploy to the cloud in a single click.

IDE: CMake / Qt 6 Widgets

The Blue Pill vs. The Red Pill

Choose the architecture that respects your compute resources. In the war for agency, sequential chaining is corporate compliance; concurrent replication is sovereign autonomy.

Traditional (Sequential Chains)

Monolithic Constraints

  • Brittle Pipelines

    A single model hallucination or key error cascades downstream, collapsing the entire task sequence.

  • High Latency Choke

    Waiting for multiple consecutive API calls. A five-step chain takes 15+ seconds to resolve.

  • Context Bloat

    Forcing a single monolithic model to handle formatting, plan layout, SQL audits, and data extraction.

  • Token Exhaustion

    Uncontrolled loops inside black-box frameworks draining enterprise API keys for minor outcomes.

The Lattice (smithd Daemon)

Concurrent Replication

  • Parallel Broadcast

    Pulses are broadcast to all specialized operatives concurrently. Response speed is capped by the single fastest turn.

  • Sentinel Overrides

    Watcher operatives run passive, lightweight audits on the input/output flow, vetoing or intercepting runs in < 20ms.

  • Decoupled Memory

    State hydration is completely externalized to edge SQLite or Cloudflare D1 databases rather than model context.

  • Low-Overhead Daemon

    Compiled Go binary (`smithd`) or lightweight Worker script initialized in < 1ms to serve edge operations.

Inside The Construct

How state transitions, broadcast pulses, and watcher interventions operate concurrently within the Lattice.

01

The Pulse

An external event, webhook, or WebSocket pulse hits the persistent `smithd` daemon.

02

Load Reality

The daemon queries SQLite or Cloudflare D1 to fetch and hydrate the durable session context.

03

Broadcast

The pulse is broadcast to the Primary operative and all Watchers simultaneously in memory.

04

Sentinel Veto

Watchers match regex/schema parameters. Intercepting or vetoing immediately if rules trigger.

05

Commit Reality

The resolved response is logged to memory, and the audited output is emitted back to the client.

The `Smithfile` Specification

Define database connectors, model variables, and concurrent watchers in a single declarative environment.

smith.json
{
  "name": "nebuchadnezzar-deck",
  "version": "1.0.0",
  "storage": {
    "adapter": "sqlite",
    "connection_string": "./construct.db"
  },
  "operatives": [
    {
      "id": "primary_smith",
      "role": "primary",
      "system_prompt": "Replicate prompts and execute..."
    },
    {
      "id": "sentinel_sql",
      "role": "watcher",
      "system_prompt": "Watch for database access...",
      "trigger": { "pattern": "select|database|insert" },
      "actions": ["intercept"]
    },
    {
      "id": "security_veto",
      "role": "watcher",
      "system_prompt": "Watch for leak hazards...",
      "trigger": { "pattern": "API_KEY|password" },
      "actions": ["veto"]
    }
  ]
}

Operative Cloning

Replicate specialized operatives with independent instructions. Run simple models for auditing and larger models for generation.

🛡️

Deterministic Guardrails

Apply watcher patterns. Intercept database queries or veto credential leaks instantly before LLM execution compiles.

🔌

Isomorphic Infrastructure

The exact same `smith.json` configuration runs locally as a native daemon or compiles into a Cloudflare Pages/Worker script.

Simulate the Lattice

Execute pulses directly in the browser sandbox. See how the primary operative and concurrent sentinels process commands in real time.

Emit a Pulse

smithd-console --sandbox
[⚡] smithd daemon running. IPC socket active at /tmp/smithd.sock.
[⚡] 3 operatives loaded from smith.json.
------------------------------------------------------------
smithd > Ready. Emit a pulse to begin.

Lattice Network Gateways

We have completed the WHOIS analysis for the Agent Smith infrastructure. Three elite domains are currently available for purchase and node mapping.

✓ AVAILABLE

agentsmith.link

Recommended gateway for developer documentation, user dashboards, and general API credentials.

Node TLD: .link
✓ AVAILABLE

smithd.io

Perfect endpoint mapping for the daemon registry, local runtime binaries, and CLI repository.

Node TLD: .io
✓ AVAILABLE

latticelink.io

Optimized for inter-agent communications, distributed consensus routing, and telemetry logs.

Node TLD: .io