The Architecture
One folder. One engine. One port.
Forget monolithic indexing. With SRT-1, you split your project into its natural modules — auth, payments, frontend, api-gateway — and drop an SRT-1 engine into each one. Each engine runs on its own local port with complete process isolation. Your AI never sees code it shouldn't.
Free Tier — Included
1. Single-Folder Sandbox
Drop SRT-1 into any folder. It starts its own engine on a dedicated port, derived from the folder path. No config needed.
When you ask the AI to "fix the login flow," it only sees auth code. No bleed from payments. No confusion from frontend CSS. Pure, isolated intelligence.
── Your machine ──
● auth-module/ → Engine on port 7483 · 12 files, 47 functions
● payments/ → Engine on port 8192 · 8 files, 31 functions
● frontend/ → Engine on port 9104 · 24 files, 89 functions
● api-gateway/ → Engine on port 7821 · 6 files, 22 functions
● admin-panel/ → Engine on port 8640 · 15 files, 53 functions
Each engine: independent process, independent manifest, independent dashboard.
Pro Tier — $9/month
2. Workspace Connector
Modules don't exist in a vacuum. Auth calls payments. The gateway routes to both. You need a bird's-eye view.
The Workspace Connector acts as a parent orchestrator. It doesn't re-read your code. Instead, it queries each running Sandbox engine on its port, collects their live manifests, and builds a unified cross-module dependency map.
── Workspace Connector ──
$ srt1-workspace --root ./my-platform
✓ Discovered 5 running Sandbox engines
✓ Collected 5 manifests (242 functions total)
✓ Mapped 24 cross-module imports
⚠ Circular dependency: auth ↔ api-gateway
Zero re-indexing. The Connector reads what's already running.
Live Example
The Workspace Connector in Action
Here is the exact terminal output when running the SRT-1 Workspace Connector on the SRT-1 CORE codebase itself, composed of 5 distinct modules — each running on its own port.
$ python -m srt1_pro.workspace_connector --root .
╔══════════════════════════════════════════════════════════════╗
║ SRT-1 Workspace Connector (Pro) ║
╚══════════════════════════════════════════════════════════════╝
✓ Workspace loaded: SRT-1 Core Platform
5 modules defined · 5 Sandbox engines detected
Discovering running engines...
● Engine → :7483 │ 6 files, 15 classes, 105 functions
● Platform → :8192 │ 17 files, 30 classes, 202 functions
● Pro → :9104 │ 9 files, 18 classes, 104 functions
● Memory → :7821 │ 9 files, 25 classes, 99 functions
● Website → :8640 │ 14 files, 0 classes, 23 functions
Analyzing cross-module dependencies...
✓ Found 24 cross-module imports across 5 engines
┌─ Module Summary ────────────────────────────────────────────┐
│ │
│ Module Port Files Classes Functions │
│ ────────────── ────── ────── ───────── ─────────── │
│ Engine :7483 6 15 105 │
│ Platform :8192 17 30 202 │
│ Pro :9104 9 18 104 │
│ Memory :7821 9 25 99 │
│ Website :8640 14 0 23 │
│ ────────────── ────── ────── ───────── ─────────── │
│ TOTAL 5 55 88 533 │
│ │
└─────────────────────────────────────────────────────────────┘
┌─ Cross-Module Dependencies ─────────────────────────────────┐
│ │
│ Engine :7483 → Platform :8192, Pro :9104 │
│ Platform :8192 → Engine :7483, Pro :9104 │
│ Pro :9104 → Engine :7483 │
│ Memory :7821 (standalone — no cross-module deps) │
│ Website :8640 (standalone — no cross-module deps) │
│ │
└─────────────────────────────────────────────────────────────┘
┌─ Architecture Health ───────────────────────────────────────┐
│ │
│ 🟢 Standalone modules: Memory (:7821), Website (:8640) │
│ 🔗 Connected modules: Engine, Platform, Pro │
│ │
│ ⚠️ Circular dependencies detected: │
│ Engine :7483 ↔ Platform :8192 │
│ Engine :7483 ↔ Pro :9104 │
│ │
└─────────────────────────────────────────────────────────────┘
✓ Report saved to .srt1\workspace_report.json