Governed growth operating system
Marketing Machine
See every initiative move from thesis to evidence, activation, revenue, and learning—without losing authority at the critical transitions.
ResponsibilityStable agent color
LifecycleL · queued to complete
HealthH · verified or issue
ApprovalA · authority state
EvidenceE · proof strength
PerformanceP · measured result
Drag nodes · drag empty space to pan · scroll to zoom · select ports to connect
Current reference run
Pest Control · Offline production rehearsal
MODEResearch + design only
OUTBOUNDLocked
Dedicated project · external activation lockedPortfolio
Initiatives, not disconnected campaigns
Each initiative can contain campaigns, content programs, launches, partnerships, experiments, and reusable operating templates.
End-to-end operating path
Blueprint to governed receipt
- 01IntakeBuilt · draft initiative capture
- 02ResearchBuilt · evidence and provenance records
- 03Proposal + assetsPartial · package assembly remains local
- 04ApprovalBuilt · immutable packet and authority gate
- 05Dry-run executionApproval-blocked · real providers disconnected
- 06ReceiptsBuilt · durable run and evidence lineage
Durable execution
Live Run Console
Every attempt is bound to one release, environment, manifest, event history, artifact set, and current interrupt. This initial run is a synthetic no-side-effect fixture.
Learning system
Evidence, artifact, and decision lineage
Trace every conclusion from its source through generated artifacts, approvals, activations, outcomes, and reusable learning. Upstream changes propagate staleness without rewriting history.
Execution model
Agents reason. Workers enforce.
Sterling 2.0 is the sole business orchestrator; temporary specialists recommend while deterministic workers own durable state and guarded mutations.
SOLE ORCHESTRATOR
ActiveSterling 2.0
Intent · policy · dispatch · approvals · exceptions · executive reporting
Connection truth
Every tool earns its place
Connected is not the same as authorized, and authorized is not the same as approved for live execution.
Adapter safety and readiness
Simulation is available. Provider action is not.
The product exposes three deterministic dry-run adapters while every real provider mutation remains disconnected and fail-closed.
| Adapter | Available mode | External/provider behavior | Fail-closed proof | Readiness |
|---|---|---|---|---|
| CSV source intakeNormalized cohort import + receipt | Dry run | No provider call; internal records only | externalActionPerformed: false | Local ready |
| HubSpot snapshotExclusion and handoff simulation | Dry run | No provider read; no CRM mutation | providerReadPerformed: falsecrmMutationPerformed: false | Guarded |
| Cold emailEligibility and package simulation | Dry run only | No provider call; no message sent | activationLocked: trueexternalActionsAuthorized: false | Live blocked |
| Real providersEmail, social, spend, CRM, registrations | Disconnected | No route has launch authority | POST control plane → 423 Locked | Approval required |
Mode lock
Cold email rejects any request that is not explicitly dry_run with activation locked.
Eligibility gate
Unresolved identity, ineligible channel, suppression, or invalid approval blocks the simulation.
Idempotency
Reused keys with changed payloads fail instead of creating ambiguous receipts.
Receipt truth
Receipts record whether a provider was called, a CRM changed, a message sent, or any external action occurred.
Precedent library
Capabilities + cases + implementation proof
Full research records will include source class, architecture, outcomes, limitations, transferable patterns, and proof tests.
Blueprint coverage
Source requirements mapped to product truth
Verified features, partial foundations, and approval-blocked execution are kept separate so product completeness is never confused with launch authority.
3 verified4 partial3 blocked
| ID | Source requirement | Status | Current evidence | Remaining gap |
|---|---|---|---|---|
| R01 | Dedicated mobile product shell | Verified | Standalone root, mobile navigation, D1 read surface | Future releases still require scoped deploy approval |
| R02 | Persistent visual workflow builder | Partial | Node canvas + browser-local initiative drafts | Cross-browser durable draft persistence |
| R03 | Intake-to-receipt operating workflow | Partial | Six-stage status map + durable run model | Proposal and asset assembly remains local |
| R04 | Research intelligence with provenance | Partial | Evidence, lineage, and source-class records | Broader industry execution and enrichment |
| R05 | Immutable approvals and receipts | Verified | Approval packet, hash, gates, event lineage | None for local safety contract |
| R06 | Dry-run adapters with fail-closed guards | Verified | CSV, HubSpot, and cold-email simulations | Real providers remain intentionally disconnected |
| R07 | Real outbound, CRM, social, and spend integrations | Approval blocked | Provider boundary is explicit and locked | Action-specific approval, credentials, safety isolation |
| R08 | HubSpot nurture correction | Separate lane | Known risk retained in launch-readiness packet | Read-only audit then correction approval |
| R09 | MailSuite tracking confirmation | Manual UI | API limitation recorded | Authenticated Gmail composer inspection; no send |
| R10 | Launch-readiness separation | Partial | Built, tested, live, and blocked states separated | Refresh after all safe local increments complete |
Activation room
First-run approval packet
Walk the exact proposed Pest Control canary before any sender, spend, CRM, or outreach action is permitted.
Loading immutable review packet…
Control-plane gates
Existing activation requirements
Loading D1 control-plane state…