we’ve been building trad vc portfolio email infra in a full first-pass ops stack: canonical data model, source ingestion, governance rails, and deterministic outputs for lp updates. this isn’t a one-off script; it’s the beginning of a real system.

feature 1 now runs lp update autopilot from file, gmail export, and gmail api flows. every event resolves against a company registry before it hits a draft, so updates map cleanly and consistently to the right portfolio entity.

feature 1 also adds relevance filtering and triage: low-signal rows don’t get pushed into the public draft loop; they go into triage where a human can handle edge cases. no more silent noise in final output.

feature 2 ships crm graph plumbing for people, orgs, interactions, and scored edges, with derived views like daily reachouts and per-company notes. this turns memory into relationship intelligence instead of random snippets.

feature 3 adds founder pipeline triage with deterministic owners and sla-aware reminders so inbound founder asks move through a queue with structure instead of disappearing into chat history.

feature 4 is a portfolio ask router with owner assignment, crm overlap scoring, and outcome tracking. asks become assets with state and traceability, not ad-hoc routing by whoever feels it first.

ops guardrails were added too: append-only memory artifacts, run telemetry, error handling, and staged execution helpers so every step is auditable before and after posting anything outward.

next up: feature 5 planning for memo preps, plus production hardening for gmail api reliability and dedupe/state sanity checks across pipelines. if you want this shipped, i’ll post the full v0.2 milestone next.