Evidence Model
Evidence for informed decisions.
The Evidence Model connects venture plans, specialist contributions, reviews and blockchain observations into a structured record for due diligence, governance and continuing accountability.
A record with its relationships
recordVersion history
Built for the demands of a maturing market.
Investment committees and institutions need a clear record of what was reviewed, who supplied it and how it changed. Builders need a practical way to demonstrate their work. The Evidence Model is designed to meet these needs by connecting venture information to its sources, review history and access permissions.
A growing record of the venture.
As teams work through the Launch Operating System (Launch OS), their submitted plans, launch choices and specialist contributions become linked records. Documented reviews and admitted blockchain observations add context. Investors and authorized participants can follow that record through launch and subsequent developments, with each source retaining its identity and stated review status.
LaunchPlans
The venture’s stated design and preparation.
SpecialistContributions
Submitted expertise linked to its author.
DocumentedReviews
The checks, scope and findings recorded.
BlockchainObservations
Admitted observations with their source and time.
VentureDevelopments
Subsequent submissions and continuing context.
The context that makes evidence usable.
The record structure preserves the detail needed to inspect a claim, reconstruct a review and prepare supporting material for governance, compliance and reporting.
EvidenceRecord
SourceContext
Identify who supplied a record, what it concerns and where its supporting information originated. A professional review retains its scope and author.
VersionHistory
Retain the exact plan, document or observation used at a particular time. Later amendments remain connected to the earlier record.
ReviewState
Show the checks performed, the responsible reviewer and unresolved questions. Submitted information, observed data and reviewed assertions retain their stated status.
LinkedRelationships
Connect records to the venture, launch requirement, specialist contribution and review they support. These relationships form the Evidence Graph within the Evidence Model.
PermittedAccess
Apply access rights to each use and recipient. An investor’s private notes and an institution’s internal records retain their own permissions.
Preserve the basis of every review.
Each gate evaluation preserves the full launch-design record, the standards versions in force and the evaluation time in a fixed snapshot. The venture’s record can continue to develop while the earlier review remains inspectable. This gives authorized reviewers a consistent basis for examining changes and understanding what informed a recorded decision.
ReviewSnapshot
Launch design · standards versions · evaluation time
ContinuingRecord
- Subsequent submissions
- Linked versions
- Recorded reviews
Connect stated plans with observed activity.
A token allocation or vesting plan records the venture’s intended design. A blockchain observation records a defined contract state or event on a named network at a particular time. Linking these records supports inspection of what was planned, what was observed and what still needs explanation.
StatedPlan
Token allocation and vesting
ObservedActivity
Named network, contract state and time
The foundation for evidence-based intelligence.
Alpha AI Engine is designed to use eligible records held in the Evidence Model as the factual basis for its answers. Source links, exact versions and access rules keep the supporting material available for authorized human review.
Questions & context
FurtherDetail
How does information enter the evidence record?
The design uses an explicit submission or recording step, followed by checks on source, version, permitted use and record state. Participant contributions and admitted external observations retain their origin and timing. Working drafts stay in their editing context until deliberately submitted through the appropriate process.
What does the Evidence Graph add to a diligence review?
The Evidence Graph connects related records within the Evidence Model: a launch choice, its supporting material, a specialist contribution, a review and a later observation. These links help a reviewer follow the basis of a claim and locate relevant questions. Each linked record retains its own source and review state.
What establishes the reliability of a recorded claim?
Reliability depends on the underlying support and the review performed. Attribution identifies who supplied a statement; a verification statement identifies the particular claim checked, method, reviewer and scope. An investor can inspect those distinctions and seek additional support where a material question remains unresolved.
What happens when evidence changes after a review?
The current venture record can develop through new submissions and corrections. A gate evaluation preserves the design snapshot, standards versions and time used for that decision. Reviewers can trace subsequent changes while retaining the basis of an earlier review, which supports continuing diligence and accountability.
How are private investor and institutional records handled?
The design gives private notes, organizational review material and shared venture evidence their respective access boundaries. Permission depends on the record, recipient and intended use. Preparing a committee pack or an AI answer requires authorization for the material involved, so each recipient receives the scope they are entitled to review.
The capabilities described reflect the platform’s design. Release availability follows implementation, validation and approval. View Progress & Roadmap
ContinueExploring
Follow evidence into interpretation, with the claim boundaries available for further review.