vibemarketervibemarketer

Inside the architecture: one engine, two heads

How vibemarketer shares Memory, scoring, and traces between the marketing fleet and VC Brain — with diagrams.
← Blog2026-07-19 · architecturediagrams

Anand Vashishtha · @AnandVashisht15

Most products bolt AI onto a calendar or a CRM. We built a shared engine first: ingest public signal, persist Memory, reason with deterministic scores, and leave an agent trace. Then we attached two heads — marketing for SaaS founders, VC Brain for investors.

System map

Mermaid · shared engine

Rendering diagram…

Ingest and Memory are shared. Heads only differ at the last mile: publish a draft vs write a $100K decision-support memo.

Brief pillars → product layers
  1. 01

    Memory

    Signals, Founder Score history, brand context, claims. Append-only where it matters — Postgres dual-write when enabled.

  2. 02

    Intelligence

    Distribution gravity, 3-axis screening (never averaged), per-claim Trust, thesis fit, conviction thresholds.

  3. 03

    Experience

    Radar → compare → screen theater → memo for investors. Studio → HITL queue for the marketing fleet.

Mapped from The VC Brain brief: Memory · Intelligence · Experience. Marketing reuses the same stack with a HITL gate.

Request path and persistence

Demo mode can run entirely in-process. When DATABASE_URL is set, the same write path dual-writes to Postgres so Radar, memos, and traces survive restarts — without inventing a second source of truth for the UI.

Mermaid · dual-write

Rendering diagram…

Store stays the fast read path for the hackathon demo. Postgres is the durable ledger when configured.

Pipeline · investor spine
  1. 01

    Identify

    GH · HN · arXiv

  2. 02

    Score

    Gravity + Founder Score

  3. 03

    Screen

    3 axes, never averaged

  4. 04

    Diligence

    Claims + Trust probes

  5. 05

    Memo

    $100K YES / NO / WATCH

Five screens judges can walk without a script.

Why this shape wins the hackathon and the company

  1. Sourcing depth lives in connectors + Memory — not in a single LLM call.
  2. Trust is claim-level with contradictions; memos flag Cap table: not disclosed instead of inventing numbers.
  3. The marketing head dogfoods the same loop: drafts, gates, learns.

If you only remember one picture from this post, remember the fork after Reason: same evidence spine, two action vocabularies.

More like this, less feed noise

Newsletter for builders — or open Gravity Audit / the app.

More notes