Context Vault
Build a draft Firm DNA profile from historical input and review proposed institutional knowledge.
Start with historical evidence
Organization administrators open Settings > Context Vault to describe past investments, upload supporting material, and compare a new deal with the resulting profile. Include what was bought, what was passed on, and why. Keep conclusions traceable to the material supplied.
Uploaded excerpts and typed notes share the displayed input limit. Failed or still-reading uploads must be retried or removed; an over-limit pack is refused rather than silently shortened.
Generate a draft profile
Generate Firm DNA streams a draft profile and proposed patterns. An incomplete or failed generation cannot become a successful save. Inspect the save notice to distinguish durable persistence from a provisional result.
A generated profile stays draft. It does not automatically become active investment policy. Review and promote proposed patterns through Settings > Memory; reviewed, active patterns supply the governed Firm DNA used in relevant analysis and chat. Pattern scope and source evidence remain part of that context.
Manage patterns
| Review state | Effect |
|---|---|
| Draft | A proposal awaiting review; excluded from reviewed pattern context. |
| Reviewed | Eligible for active context when the pattern is also active and its scope matches. |
| Rejected | Excluded from reviewed context. |
Review state and lifecycle status are separate. A superseded or archived pattern is not an active rule even if it was previously reviewed. Administrators can revise a rule and its evidence when the firm's judgment changes.
Compare a deal
The comparison step accepts notes and documents for a new opportunity. Inspect the result, its evidence, and any limitations. A fit assessment is analysis, not an IC approval or permission to overwrite model assumptions.
Historical ingestion
The back-catalog step selects eligible historical memos and asks for confirmation of the selected count and estimated cost before launching. Inspect the run's completed, failed, or skipped results. A skipped scan needs a text-layer source for this workflow; it is not silently treated as read.
Draft proposals go to the existing Memory review queue. A proposed fund default requires a separate explicit Apply action. A memo's working-note approval or rejection does not automatically create a closed outcome or activate a pattern.
Related guides
- Firm memory: how reviewed knowledge and reference documents differ.
- Deal memory and outcomes: outcome capture and read-only deal context.
- IC memo: memo and decision governance.
Last updated on