Repeatable processes for reasoning across the portfolio over the _REFERENCE/ knowledgebase — the manual, markdown proto-version of the future KSVGPS business-side graph-DB (see ../_REFERENCE/PROJECT-ORGANIZATION-MODEL.md and ../PLAN-new-ventures-from-portfolio-knowledgebase.md). These are the MetaProject's own cross-venture workflows — distinct from each managed repo's intra-project _workflows/.
Status: rough-draft v1 (2026-06-21). These evolve every time we run them; each run should also improve the workflow doc itself — the feedback loop is the point.
| Workflow | What it does | When to use |
|---|---|---|
workflow_new_venture_intro_brief.md |
Produce a two-file (business + engineering) intro brief for a venture/project: reason across every facet, pull in everything known/inferable from all sources (no-invention + TBD), and embed per-section "Additional Questions for John" so it reads as a partial brief that interviews the owner section-by-section. |
Standing up a new (or under-documented) venture; the John×Claude interview loop that fills it in. |
workflow_cross_venture_future_scenario.md |
Future-scenario reasoning: given a dated user-story snapshot ("…in January 2030"), request a scoped projection of every venture's state as of that date (±3 mo), brainstorm the cross-venture feature interplay wildly, then write conclusions back as facts + backlog items. | Stress-testing the portfolio's future coherence; generating cross-venture feature ideas; deriving backlog from a Triangulation Target. |
- Structural model the workflows assume:
../_REFERENCE/PROJECT-ORGANIZATION-MODEL.md. - Research topics surfaced while running these land in
../_backlog_TODOs/RESEARCH-BACKLOG.md(the[Backlog:RESEARCH]shorthand). - Orchestrator-context discipline (delegate the heavy source-reading to subagents):
../_backlog_TODOs/LATER-005-context-preserving-search-workflow.md.