Extract the claim
Break broad project language into specific, testable statements.
Turn every project in motion into a verifiable, living business story.
ViseCraft connects project activity, founder review and claim-level verification so every update shows what happened, what supports it and what remains unproven.
Evidence-backed by ViseCraft Proof Engine
VerificationClaim-level
RecordContinuously updated
ControlFounder reviewed
Proof Engine
Claims under review
3
Verification report
The ViseCraft launch surface is implemented.
Verdict
Code-backed
Evidence
3 sources
Freshness
Historical
Supporting evidence
Repository commit
Repository records support that the independent product surface was implemented.
Limitations
Code confirms implementation. It does not establish active user adoption.
Checked by · Proof Engine v0.xOpen full report
01
Verify the claim, not the company.
Proof Engine separates each important statement, checks connected evidence and returns a scoped verdict with freshness and limitations.
Inspect the evidence
Check source identity, status, time alignment, integrity and availability.
Issue a scoped verdict
Show what the evidence supports, what it does not and when to recheck.
Claim
The current product version has been deployed.
Partially supported
Medium confidence
Supporting evidence
Release recordVersion exists
Deployment recordProduction target
Commit correlationNeeds confirmation
What this does not prove
The available evidence does not confirm active usage, customer adoption or revenue.
Freshness
Recheck required within 24 hours
ViseCraft Proof Engine v0.x
Verification evaluates whether connected evidence supports a specific claim. It is not an audit, certification or investment recommendation.
02
One project record. Different jobs to be done.
Capabilities are grouped around the moment a founder needs them, not around a list of disconnected features.
Review with evidence
Make project claims easier to trust and faster to inspect.
Keep material statements connected to source context, freshness and an explicit evidence boundary.
Scope01
Claim catalog
Separate implementation, deployment, adoption and revenue statements before review.
Review02
Review report
Prioritize verdicts, sources, freshness, evidence gaps and limitations.
Proof03
Claim reports
Let a reader inspect verdict, supporting evidence, freshness and limitations.
03
ViseCraft, told as an evidence-framed company record.
Twelve inspectable chapters explain the product through current records, explicit limitations and repository-linked change history. This is ViseCraft's own narrative, not a BP-authoring feature.
ViseCraft company record / CurrentEvidence-aware
Selected chapter · 01
Purpose
Why project progress needs a durable, inspectable record.
Evidence-framed summary
Turn activity into a record people can understand and verify.
Source-linkedFounder reviewed
Record views
Founder record
Full activity, decisions, blockers, risks and evidence gaps.
Review report
Selected claims, verdicts, sources, freshness and limitations.
Public summary
Only owner-authorized milestones and evidence summaries.
04
Connect the sources where progress already happens.
ViseCraft starts with repository activity and founder input, then expands into the product, deployment and business stack.
MVP focus
GitHub
MVP focusRepository metadata, commits, pull requests, issues, releases, tags and contributors.
Founder notes
MVP focusAdd decisions, risks, business events and context that do not exist in code.
Integration roadmap
VercelPlanned
LinearPlanned
NotionPlanned
FigmaPlanned
SupabasePlanned
StripePlanned
01Connect
02Collect
03Review
04Verify
05Export
05
From raw activity to a reviewable project record.
Create
Add the company, product, market and visibility defaults.
Connect
Bring repository activity and founder context into one project stream.
Review
Promote only meaningful events into the formal project record.
Verify
Check important claims against evidence, freshness and contradictions.
Export
Share an authorized report, badge or evidence packet with a defined scope.
06
Seven releases. One product record anyone can inspect.
Each report separates what shipped, why it matters and which repository evidence supports it. The sequence records completed work without turning activity into unsupported business claims.
v1.0.5
Engineering governance
What shipped
Added the pull-request quality gate, evidence-bounded changelog and synchronized project handoff records.
Product meaning
Every change now has a repeatable path from implementation to documented verification.
Release evidence
Code-backedCI workflow and repository documentation
v1.0.6
Application boundaries
What shipped
Separated marketing, authenticated application and reserved public routes while keeping shared concerns explicit.
Product meaning
Public storytelling and private project workflows can evolve without sharing accidental route behavior.
Release evidence
Code-backedApp Router restructuring
v1.0.7
Shared product states
What shipped
Introduced reusable loading, empty, error, notification, field and submission primitives.
Product meaning
Core workflows now communicate progress and failure through one consistent interaction language.
Release evidence
Code-backedShared UI state primitives
v1.0.8
Browser acceptance coverage
What shipped
Added Playwright coverage for public entry, preview authentication, workspace protection and Proof Engine reports.
Product meaning
The main investor-facing and authenticated paths are checked in a real browser before release.
Release evidence
Code-backedChromium smoke suite
v1.0.9
Commercial product narrative
What shipped
Rebuilt the homepage around Proof Engine, scenario-led capabilities, BP Studio, integrations, plans and evidence-aware FAQs.
Product meaning
Visitors can understand verification, BP production and publishing as one connected SaaS workflow.
Release evidence
Code-backedHomepage workflow release
v1.0.10
Apple interaction refinement
What shipped
Added immediate press feedback, functional floating materials, optical typography and a product-continuous auth layout.
Product meaning
The public site and application now feel like one focused, responsive product across desktop and mobile.
Release evidence
Code-backedFrontend design release
v1.0.11
Versioned product reports
What shipped
Published a bilingual, evidence-linked report for every release from v1.0.5 through the current version.
Product meaning
ViseCraft now demonstrates its own living-project-story model through an inspectable product history.
Release evidence
Source-linkedCurrent repository release
v1.0.12Current release
Product boundary correction
What shipped
Separated ViseCraft's evidence-record and verification responsibilities from VisePitch's independent dynamic-BP product.
Product meaning
The homepage now demonstrates ViseCraft through its own twelve-chapter evidence record without promising BP authoring or publishing.
Release evidence
Source-linkedCurrent repository release
07
Start with one project. Upgrade when the reporting load grows.
The M1 plan structure is defined; paid pricing will be published when billing opens.
Early access · pricing pending
Free
For one live project
$0
Build the first evidence-aware project record.
Included
- 1 project
- Manual activity review
- Claim verification
- Scoped report preview
Pro
For repeat reporting
Pricing at launch
Operate multiple project stories with more verification capacity.
Included
- Up to 10 projects
- Higher verification frequency
- Evidence packet exports
- Team review planned
08
Inspect ViseCraft through its own product record.
This homepage keeps delivery, product meaning and evidence boundaries separate. The repository remains the source for code and release history.
01TimelineVersioned project events
02EvidenceSource context and evidence levels
03RoadmapCurrent and next-stage work
04BoundaryNo unsupported business outcomes
09
Questions before you trust a project claim.
What does Proof Engine actually verify?
It evaluates whether connected evidence supports a specific claim. It does not verify an entire company, guarantee performance or make an investment recommendation.
Does code prove that a product is live or used?
No. Code can support implementation. Deployment needs deployment evidence; usage needs usage evidence; revenue needs separate financial evidence.
Will private repository evidence become public?
No. Projects and evidence remain private by default. A report or evidence packet exposes only the claims and source summaries the project owner explicitly authorizes.
Does ViseCraft create or publish dynamic BPs?
No. ViseCraft owns project records, evidence and verification. Dynamic BP authoring and web publishing belong to the independent VisePitch product.
Can VisePitch use ViseCraft evidence later?
A future integration may pass a bounded, authorized and revocable evidence packet. The products do not share a database, session or business logic.
Give real progress a story people can inspect.
Create the project record once. Keep claims, evidence, freshness and authorized reports moving together.