The laurel was exclusive. The intelligence doesn't have to be.
For 3,000 years, the laurel cinged one head — the emperor's. Intelligence was centralized, privileged, gated. LAOS dissolves the crown and distributes sovereignty to every operator: the laós.
Not a framework. Not a platform. An operating system for composable AI — 7 specialized capabilities, 1 orchestrator, zero implementation in the orchestration layer.
Explore the system → About the architect Quick start
| OLD WORLD | LAOS |
|---|---|
| Data team owns the pipeline | Every operator runs their own data |
| AI lab hoards the models | Capabilities are composed, not siloed |
| Tickets and dashboards for the rest | MCP-native tool access for every agent |
| Emperor decides | Conselho deliberates (proposals, voting, trust) |
|
LAOS
Orchestrator — this repo
|
||
|
LATADE
Data — sql · DuckDB · dbt · BI · DQ
|
LADESIGN
Design — dashboards · decks · UI · video
|
LAN8N
Automation — n8n · APIs · workflows
|
|
LACOUNCIL
Governance — proposals · voting · trust
|
LAECON
Econometrics — regressions · ML · causal
|
LAENGINE
Game Dev — simulation · match engine
|
|
LACAREEROPS
Career — job search · CV · portal scan
|
||
7 capabilities · 7 MCP servers · 0 implementation in the orchestrator
Each capability is its own repository, its own MCP server, its own lifecycle. LAOS composes them — it never owns them.
LATADE
sql · DuckDB · dbt · BI · DQ
LADESIGN
dashboards · decks · wireframes · video
LAN8N
n8n · workflows · integrations · alerts
LACOUNCIL
proposals · voting · trust · memory
LAECON
econometrics · ML · causal · interpret
LAENGINE
simulation · match engine · squad mgmt
CAREEROPS
job search · CV · portal scan
context7
Library docs · API refs
exa
Web search · Research
github
Repos · Issues · PRs · Code
LAOS dispatches 9 specialized agent types, each confined to its own MCP namespace — siloed by design, composed by the orchestrator.
| Agent | MCP Domain | Role |
|---|---|---|
| orchestrator | lacouncil.* |
Session owner, dispatcher, structural improver |
| data-architect | latade.* |
SQL, modeling, BI, DQ, docs |
| dashboard-designer | ladesign.* |
Dashboards, decks, wireframes, video |
| automation-engineer | lan8n.* |
n8n workflows, integrations, APIs |
| delivery-reviewer | (read-only) | Validates artifacts against P0-P2 checklist |
| capability-architect | lacouncil.* / github.* |
Implements LACOUNCIL-approved structural changes |
| workflow-decomposer | lacouncil.* (WDL wall) |
Read-only PM layer: plan verification, verdict tri-state |
| chief-* (3 evaluators) | (domain read-only) | Empirical consensus: data-scientist, designer, engineer |
| 1 | Brief → contract A project is born as its own repository. LAOS holds the contract ( project.yaml) — the routing table, the delivery checklist — nothing else. |
| 2 | Needs → capabilities The orchestrator resolves declared needs via the registry. Deterministic. No guessing. |
| 3 | WDL preflight The workflow-decomposer validates the plan before any specialist is dispatched. No bypass without manifest + penalty. |
| 4 | Specialist dispatch via MCP Data-architect, dashboard-designer, automation-engineer — each talks only to its capability MCP. Siloed by design. |
| 5 | Delivery review The delivery-reviewer validates every artifact against the P0-P2 checklist. No push without sign-off. |
| 6 | Artifacts land in the child repo LAOS never stores implementation. Every project is self-contained, independently forkable. |
| Project | Domain | Impact |
|---|---|---|
| abandono-academico | ML — Dropout prediction | 87.5% accuracy · 93.7% recall · 32k students |
| hospital-viana-claims | Healthcare ETL | 6 DQ checks · IFRS17-ready · daily GH Actions |
| giovanna-rupture-monitor | Retail analytics | 4,150 regions analyzed · 33% stock-out detection |
| emanuella-stock-ingestion | Retail ETL | dbt-ready · 3-stage medallion · SLA < 5 min |
| previsao-concursos | NLP — Education | 1,236 questions · 27 contests · Laplace smoothing |
| brasfoot-poc → laengine | Game dev capability | 10-team simulation · round-robin · MCP tools |
| Every project is its own repository. Contract in LAOS; everything else in the child repo. | ||
| Skill | Evidence |
|---|---|
| System architecture | Designed a meta-system orchestrating 7 independent capabilities across 4 domains |
| MCP protocol | Wired 7 MCP servers — data, design, automation, governance, econometrics, game, career |
| Declarative contracts | project.yaml as single source of truth → deterministic need-to-capability routing |
| Governance engineering | LACOUNCIL: proposals, Conselho voting (unanimity / supermajority / majority), trust scores, DuckDB memory |
| Multi-agent orchestration | 9 subagent types, WDL preflight gate, sequential / parallel / consensus dispatch modes |
| Quality automation | 12 OpenCode plugins enforce hard rules mechanically (not by prompt). Delivery-reviewer validates every project |
| SDD methodology | Every project produces 8+ SDD artifacts before any implementation code |
| CI/CD for AI systems | GitHub Actions, preflight checks, boot validation per dispatch |
| File | Purpose |
|---|---|
AGENTS.md |
Hard rules + agent topology + 12-plugin architecture |
registry/needs-to-capabilities.yaml |
Deterministic routing — 20+ needs → capabilities |
registry/capabilities.yaml |
Full capability catalog (7 domain + platform MCPs) |
knowledge/padroes-entrega.md |
P0-P2 delivery checklist — 13+ checks, SDD scaffold enforcement |
knowledge/sdd-principles.md |
Spec-Driven Development — 9-file scaffold matrix |
workflows/ |
Project archetype templates (etl, dashboard, presentation) |
projects/<name>/project.yaml |
Contract for every client project |
scripts/subagent_boot_check.py |
6-dimension validation before every specialist dispatch |
# Install dependencies uv sync # Health check uv run python scripts/preflight_check.py . # Launch the orchestrator opencode .
| Python | ≥ 3.11 |
| Package manager | uv (recommended) or pip |
| Runtime | Node.js (for LADESIGN daemon), Docker (optional, for n8n) |
| Environment | OpenCode CLI ≥ 1.0 |
| OS | Windows (primary) · macOS · Linux |
- No implementation in LAOS. SQL, dashboards, n8n flows live in capability repos — never here.
-
Reached only via MCP.
Capability repos are never
cd'd into directly. The MCP wall enforces this mechanically. - Structural changes require consensus. LACOUNCIL proposals → Conselho voting (4 subagents) → implementation. No bypass without supermajority.
- Every project has two homes. Contract in LAOS; all artifacts live in the child repo. LAOS never stores implementation.
-
WDL preflight is mandatory.
No specialist dispatch without a
READYverdict from the workflow-decomposer. Bypass requires a manifest + trust-score penalty. - Patterns repeated 3+ times trigger investigation. LACOUNCIL detects them automatically and proposes structural improvements.
LAOS is not a framework you import. It's a system you inhabit.
- Frameworks give you functions. LAOS gives you governance.
- Platforms give you lock-in. LAOS gives you MCP-native composability.
- AI agents give you answers. LAOS gives you a system that checks its own work.
"Data architecture isn't about the tools — it's about whether the C-suite trusts what it sees on the dashboard."
Each MCP server has its own documentation. Quick links:
- LATADE —
../latade/— SQL pipeline, medallion architecture (bronze → silver → gold), DuckDB, dbt integration - LADESIGN —
../ladesign/— Dashboard UX/UI, decks, design systems, HyperFrames video, 50+ skills - LAN8N —
../lan8n/— n8n automation, workflow templates, API integrations, quality gates - LACOUNCIL —
../lacouncil/— Governance engine, proposals, Conselho voting, DuckDB memory, pattern detection - LAECON —
../laecon/— Econometrics & interpretable ML, regressions, GLM, causal inference, diagnostic reports - LAENGINE —
../laengine/— Sports simulation, match engine, squad management, league standings - LACAREEROPS —
../lacareerops-hub/— Job search optimization via career-ops CLI, CV generation, portal scanning, career tracker (private repo, replaces legacylaurentaf/career-ops)
Platform MCPs:
context7(library docs),exa(web research),github(repo ops)
Data Architect & ML Engineer
Built LAOS because he couldn't find a system that composably orchestrates data, design, automation, and governance without becoming the implementation itself.
Campinas/SP · Remote-first
Open to: Data Architect, AI Data Engineer, Analytics Engineering
LAOS is an open system by design. The contribution path depends on what you want to change:
| Scope | Path |
|---|---|
| New capability | Create a LACOUNCIL proposal → Conselho supermajority → capability-architect implements |
| Workflow template | Add to workflows/ → Conselho majority approval |
| Cross-cutting convention | Add to knowledge/ → Conselho majority |
| Bug / improvement | Open an issue or submit a PR |
| Project delivery | Every project runs through the WDL gate → specialist dispatch → delivery-reviewer sign-off |
See AGENTS.md for the full governance model and plugin architecture.
MIT — see LICENSE for the full text.
LAOS is free software. You are free to use, modify, and distribute it under the terms of the MIT license. The laurel was exclusive. The intelligence doesn't have to be.
- OpenCode — The CLI that powers LAOS dispatch. Plugin architecture inspired this system's mechanical enforcement layer.
- Model Context Protocol (MCP) — The protocol standard that makes composable AI possible. Every capability in LAOS is an MCP server.
- Anthropic — For the tool-use and agent patterns that LAOS composes at scale.
- OmO — Team Mode architecture (parallel worktrees, mailbox coordination) adapted into LAOS's agentic framework modes.
- The Conselho — Data-architect, dashboard-designer, automation-engineer, delivery-reviewer — the 4 subagents that govern LAOS evolution through democratic voting.
LAOS — Laurent Agent Operating System
Crown the operator.