Automation and Business Systems
Opus Vela Growth
Marketing operations for the Opus Vela family: a governed workspace that watches real market signals, turns them into growth opportunities that have to show their evidence, and leaves every campaign decision to a person.
Outcome
The first two steps of the marketing signal-to-learning loop work in source — tenant-scoped observation that deduplicates incoming signals deterministically, then growth opportunities that carry their citations and confidence into an explicit, auditable human decision.
Media
Screenshots and demo clips for this project will appear here once they're added.
Case study
The problem
Marketing and growth work is often split across disconnected dashboards, campaign tools and generated content, making it difficult to show why an opportunity existed, who approved the response or whether the result taught the system anything reliable. Opus Vela Growth treats evidence and decision history as part of the product rather than as notes added after an action.
Architecture
The current foundation is an independent TypeScript and pnpm modular monolith with separate web, API and worker processes. PostgreSQL is the intended system of record, with tenant context, row-level security, transactional outbox records, idempotency and versioned JSON Schema and OpenAPI contracts kept behind explicit application ports.
What is implemented
M0 established the repository, tenant-aware persistence foundation, health surfaces, contracts and bounded local web. Source now also covers workspace membership, append-oriented signal observation with deterministic deduplication, and opportunity proposal and terminal human decisions with audit and outbox evidence.
Where it is now
In development. Signal and opportunity are implemented in source; hypothesis, campaign, asset, activation, outcome and learning remain future loop stages. The public Opus Vela site intentionally returns a not-found page at /growth, so ChaseInTech does not publish a Growth domain link or imply deployment readiness.
Technology
- TypeScript
- pnpm
- PostgreSQL
- Fastify
- React
- JSON Schema
- OpenAPI 3.1
What's shipped inside it
Signal observation
In DevelopmentValidates authority, freshness, provenance and trust classification, then deduplicates observations within the tenant and workspace boundary.
Opportunity proposal and decision
In DevelopmentRequires cited signals and an explained confidence, then records a terminal human decision with auditable evidence.
Campaign-to-learning loop
PlannedHypothesis, campaign, asset, activation, outcome and learning stages remain designed but are not yet implemented.
Scope and boundaries
The independent monorepo, tenancy foundation, audit/outbox path, signal observation and opportunity proposal/decision flows are implemented in source. There is no public Growth route, production identity, connector, model provider, billing, deployment or external publishing path. PostgreSQL runtime proof for the newer membership, signal and opportunity slices remains gated on an approved host.