Skip to content

The part that does not change when the vertical does.

Substrate topology. Applications sit on the substrate; adapter seams connect it to swappable model, memory and voice backends.

Scroll to see the full diagram

Memory, orchestration, tool discovery and provenance belong below the application, not inside it.

Swap a layer, keep the agent.

Model

Selected: Groq

Memory

Selected: SGM (native)

Voice

Selected: Sarvam Bulbul

One config file selects every backend. Swapping a vector database is a config change.

Six primitives, described as they are.

  • Categorized memory (SGM)

    Beyond vector RAG. Memories typed by role, trust and recency.

    Recalled across calls in production, in SuryaSetu. No DB query in the prompt.

  • Orchestrator with halt and escalation

    A LangGraph state machine with halt and escalation nodes.

    Live.

  • MCP-native tool discovery

    No hardcoded registries.

    Tools register at runtime. No redeploy, no schema drift.

  • Multimodal grounding

    MediaPipe and RT-DETR pipeline.

    Scene state reaches the LLM as primitives, not raw bytes.

  • Event backbone

    Async-first. Multi-agent coordination without polling.

    Background lookups and analytics run off the hot path.

  • Five enforced guards

    Each guard has a script that fails the build if a call site skips it.

    • safeFetch
    • safeRegExp
    • assertWithinBudget
    • decryptSecretStrict
    • Fail-closed middleware
  • partial

    Provenance is partial

    Trust and provenance stamping is designed and partially implemented. It is on the roadmap, not in production.

Five choices that are load-bearing.

  1. One config file selects every backend

    Memory store, embedder, vision processor, event publisher, and orchestrator are chosen in a single config and instantiated lazily behind four abstract interfaces. Swapping a vector database is a config change, not a migration.

    Why

    Vendor lock-in in the AI stack is not hypothetical — providers change pricing, terms, and availability on short notice.

  2. Verticals are configuration packs

    Solar and real estate share one agent runtime and differ only in knowledge, persona, qualification logic, and compliance rules. A regression suite runs the packs on every change.

    Why

    If a second industry needs a fork, the substrate claim is false. This is the test that keeps it honest.

  3. Two coordination topologies, deliberately

    Agent teams run as parallel deliberation or as an ordered pipeline. Both bound their own control flow, so neither can loop indefinitely.

    Why

    Every additional topology multiplies the states the runtime has to be correct in — and unbounded agent loops fail as an invoice, not an error.

  4. Security guards, not security conventions

    Outbound requests, model-supplied regex, secret decryption, and inference spend each pass through one enforced guard, and each guard has a script that fails when a call site skips it.

    Why

    A convention is something people remember. Agentic systems execute far too fast for anyone to be remembering anything.

  5. Migrate by wrapping, never by rewriting

    New capability is added as an additive layer over seams that already take the relevant parameters, so the working path keeps working byte-for-byte while the new one is proven.

    Why

    A rewrite of a system that has live users is a bet that pays out only at the very end.

What is not built yet.

Anyone evaluating this seriously will find the gaps, so they are stated here instead.

  • BLOCKED

    Scale is unproven

    Everything here runs correctly at the volume it has seen, which is small. Nothing on this site should be read as a claim about behaviour under load.

  • BLOCKED

    Live, but not yet at market scale

    SuryaSetu carries real homeowner demand, and Maya and SIOS are live for anyone to try. None of the three has yet been run at market scale.

  • BLOCKED

    No outside developers on the substrate

    Every system on this site is built by the same person who built the substrate. That is the strongest possible test of coherence and the weakest possible test of developer experience.

  • BLOCKED

    Provenance is partial

    Trust and provenance stamping is designed and partially implemented. It is on the roadmap, not in production, and is described that way everywhere on this site.

Why publish this

Every one of these would surface in a serious technical conversation within twenty minutes. Publishing them costs nothing and buys the only thing that matters when the numbers are still small.