14-module foundation
Screening, trust operations, Scout, graph, founder/team, signals, memos, maps, funding, screeners, analytics, valuation, marketplace, and data products now have production surfaces.
Current view
Venture Decision OS
Startup Screener now has a production Venture OS foundation around the evidence graph: the durable record of decks, claims, reviewer decisions, annotations, benchmarks, signals, sources, and human judgment that explains why a venture decision was made.
North-star metric
Evidence-backed decisions completed per organization per month
Reduce time from raw startup material to evidence-backed decision.
Attach citations, confidence, source provenance, and model metadata to AI-assisted outputs.
Turn decks, reviewer decisions, annotations, signals, and benchmarks into reusable venture intelligence.
Screening, trust operations, Scout, graph, founder/team, signals, memos, maps, funding, screeners, analytics, valuation, marketplace, and data products now have production surfaces.
CSV/JSON imports and internal evidence are live now; licensed private-market data providers and CRM sync remain governed adapter paths.
A demo-safe preview shows all modules with sample records, graph nodes, analytics, valuation caveats, marketplace governance, and data products.
Predictive and valuation examples carry confidence, sample size, calibration status, limitation text, and no investment-advice framing.
Super-app strategy
All 14 modules now have production foundations in the authenticated workspace and API surface. Public examples use demo-safe data. External private-market data, CRM sync, webhooks, and other third-party adapters remain governed integration records until licensing, provenance, scopes, and entitlements are configured.
Current wedge: Screening OS with evidence-linked reports and cohorts.
Compounding layer: Venture Graph, Scout, decisions, signals, and benchmarks.
Platform layer: APIs, plugins, integrations, data products, and governance.
Module foundations
All 14 modules now have production foundations in the authenticated workspace and API surface. Public examples use demo-safe data. External private-market data, CRM sync, webhooks, and other third-party adapters remain governed integration records until licensing, provenance, scopes, and entitlements are configured.
Venture Constellation
12 nodes / 9 edges. Filter by entity, search evidence, then inspect why each node matters.
Strongest match when the thesis prioritizes industrial workflow automation, measurable customer ROI, and evidence-backed enterprise conversion.
Why this matters
SignalForge is a high-confidence company node with 1 source and 2 graph relationships. It matters because downstream screening decisions become more defensible when this node stays tied to permission scope, citations, and reviewer-visible context.
Sources
1
Edges
2
Scope
public demo
Connected relationships
supports - 86% confidence
maps to - 70% confidence
Evaluation harness
No accessible workspace reports were evaluated, so the harness is showing public demo and roadmap checks.
Demo Scout candidates include cited sample-report evidence with freshness, permission, confidence, and origin metadata.
A stronger evaluation run requires completed workspace reports with human decisions and feedback labels.
Conceptual architecture
Personas -> Super-App Shell -> Product Modules: Screen | Scout | Profiles | Signals | Market Maps | Memos | Exports | Admin -> Platform APIs: BFF | public API | webhooks | plugin SDK | entitlement checks -> Domain Services: identity | intake | entity resolution | scout | scoring | audit -> Data Foundation: DB | object storage | search | vector store | graph | warehouse -> AI Layer: model gateway | prompt registry | eval harness | provenance ledger
Evidence contract
The current report surface already exposes citations, confidence, provider metadata, fallback markers, and reviewer annotations. The Venture OS layer now extends that provenance model to Scout, market maps, founder profiles, signals, memos, APIs, and benchmark products.
Evidence contract
Persona value flows
Revise deck evidence, track readiness, and opt into sharing paths.
Convert a thesis into a ranked shortlist and diligence memo.
Standardize scoring, decisions, mentor notes, and exports across cohorts.
Map buy/build/partner options with cited startup evidence.
Maintain reusable screens, market maps, and decision-ready deliverables.
Control retention, permissions, providers, audit, integrations, and data policy.
Platform interfaces
Expose canonical nodes, edges, claims, sources, decisions, and permission scopes.
Every node and edge must preserve source, timestamp, confidence, permission scope, and origin.
Accept thesis input and return ranked results with rationale, gaps, freshness, and cited evidence.
Reviewer access is required; results must not cross organization or cohort boundaries.
Publish company events, freshness, source, confidence, and alert subscriptions.
External signals remain gated until licensing, freshness, and source provenance are configured.
Return market taxonomy, company clusters, competitors, emerging spaces, and map exports.
Maps should disclose evidence coverage and not imply exhaustive market coverage.
Generate editable cited memos for diligence, selection, rejection, mentoring, and partnerships.
Memos cannot introduce uncited factual claims and should separate human decisions from AI drafts.
Notify approved integrations when reports complete, decisions are created, signals fire, or exports are ready.
Payloads require signatures, idempotency keys, retries, and scoped delivery.
Allow governed UI and workflow extensions inside the super-app shell.
Plugins need sandboxing, scope approval, audit logging, and tenant-level enablement.
Sync approved evidence to CRMs and ingest licensed external market, company, funding, and people data.
Adapters can enrich canonical entities but cannot overwrite uploaded or reviewer provenance.
AI governance
Production foundations are live. Claims that depend on licensed external data, calibrated prediction, or third-party sync remain gated by provenance, entitlement, and adapter governance.
No displayed factual claim appears without cited evidence or an explicit missing-evidence marker.
Human decisions remain stored separately from AI-generated scores and recommendations.
Provider, model, fallback, warning, confidence, and source metadata stay visible downstream.
Predictions, valuations, and benchmarks remain gated until sample size, calibration, and bias checks are defensible.
External adapter records must keep source freshness, permission scope, and origin metadata.
Key risk gates
Phase licensed adapters after provenance, entitlement, and entity-resolution foundations.
Keep citations, confidence, warnings, model metadata, fallback status, and human decisions visible.
Preserve minimum-sample gates and benchmark confidence labels.
Require adapter scopes, source-level permissions, audit logs, data-use policies, and admin approval.
Scout foundation
The reviewer-only Scout flow accepts a thesis and ranks completed workspace reports the reviewer can access. Each result returns fit score, confidence, decision hint, gaps, and cited source freshness. External provider adapters remain intentionally gated behind licensing and governance work.
Example thesis
AI workflow automation for industrial manufacturing.
Expected top result
SignalForge, ranked for traction evidence, industrial AI fit, and diligence-ready customer proof.