# Product Requirements and Demo Script

## Product Requirement Summary

VaultAI must show buyers a complete enterprise software asset rather than a single landing page. The buyer should see product workflows, research context, design assets, infrastructure posture, and evidence surfaces.

## Core Demo Flow

1. Open landing page and explain the problem: large data rooms, financial-control evidence, and modernization risk are hard to evaluate quickly.
2. Open WorkspaceData and show the research-backed buyer personas.
3. Open VDR pages and show architecture, DFVL, ledger benchmarks, and migration playbook.
4. Open bank-admin or evidence pages and show ledger/audit surfaces.
5. Open acquisition listing and show conservative sale framing, evidence manifest, and public hash.
6. Explain that source review is NDA-gated and that the package is designed for a controlled acquisition process.

## UX Requirements

| Requirement | Implementation Note |
| --- | --- |
| Buyer-facing language only | No internal assistant/user prompt language should be visible. |
| No inflated certification claims | Do not claim SOC 2, patents, signed bank pilots, or regulatory approval. |
| Clear evidence links | Every major claim should point to a document, page, API route, or manifest. |
| Importable workspaces | Figma-ready and Notion-ready files must be available as downloadable artifacts. |
| Conservative price language | Public pages use USD 995k / USD 995,000 only where price is required. |

## Acceptance Criteria

- `/workspace-data` renders in production.
- `/api/workspace-data` returns clean JSON.
- Manifest is downloadable from `/assets/workspace-data/workspace-data-manifest.json`.
- Figma and Notion assets are linked from the live page.
- No public page claims completed revenue, signed customers, or formal certification.