Automation Studio
Governed Orchestration Operating System (GOOS) — evidence-based execution across the platform, not generic task automation. Define pipelines once; run lifecycle workflows across Clinical, CRO, Markets, Translation, and what you ship next.
Governed orchestration
Build once. Execute with lifecycle accountability.
When X → run Y → generate Z → save → notify — with governed steps, telemetry, and human review where required. Sequential cross-product execution today; schedules, events, and richer runtime controls follow without generic task automation.
MVP wired: Clinical Evidence · Markets (/api/predict) · Podcast (Farah/Jordan) · CRO Workspaces · reports & summaries · in-app notify. On the roadmap: Translation · Neural Glass · external webhooks.
Automation library
Workflow builder
Run console
Recent automation runs
| Time | Automation | Status | Steps | Duration |
|---|
Platform architecture
Governed Orchestration Operating System (GOOS)
Not task automation like Zapier or n8n — a governed execution layer with the same constitutional principle as GCOS: as certainty decreases, authority decreases.
Execution primitive
Evidence → Certainty → Authority → Execution
Example (Markets): AAPL → market_predict → summary → notify → audit
Three operating systems
- GCOS — govern capital
- GOOS — govern execution (this studio)
- GEOS — govern evidence (Clinical / CRO)
Compare with other products
| Product | What it optimizes |
|---|---|
| Zapier / Make / n8n | Task & workflow automation |
| Temporal / LangGraph | Durable / agent orchestration |
| Automation Studio | Governed evidence-based execution |
Governance stack (today)
- Workflow execution ✓
- Human approval ✓
- Audit trail ✓
- Recovery ✓
- Failure handling ✓
- Evidence gating ✓
- Constitutional rules ✓
- Cross-product orchestration ✓