Solution Intent
Why this workspace exists
Open document →00 / 15 · Start here
From an idea to a working FileLoveNote
Give this folder to a developer or AI agent. This package describes the product, technical contracts and prompts for rebuilding it step by step.
Starting point: an empty project folder.
The developer does not need the original source code. Read the four specifications plus the Design, Data Structure, Security and detailed contract chapters first, then follow the build prompts in order. This is a rebuild specification based on the original 23 October source snapshot, with the contract review of 26 October and dependency/test maintenance of 28 October 2026. It does not guarantee identical pixels or error-free AI output.
How to use this package
- Copy the entire
prompt/folder, includingfixtures/andbaseline/, into an empty project folder. Openindex.htmlin your browser. All sixteen pages work without a server or internet connection. - Install Bun and a code editor with an AI agent that can read and edit files. Use BrowserOS Neo for browser checks.
- Give the agent the entire folder as context. If the agent cannot read HTML files, paste the visible text from Intent, Design, Requirements, User stories, Design, Data Structure and Security, followed by the starting prompt.
- Copy the starting prompt. First ask the agent to restate the assumptions and chosen scope.
- Complete P00 through P04, then P07. This builds the web core. Add P05 for the full scope of this package.
- After each step, check the linked requirements and scenarios. Save working progress before continuing.
The build package
Solution Design
How the components work together
Open document →Requirements
What the new app must support
Open document →User stories
From user needs to verifiable behavior
Open document →Build prompts
Build in small, verifiable steps
Open document →Verification
Prove that it works
Open document →Sources & decisions
What this package does and does not specify
Open document →Security
Protection, risks and outstanding checks
Open document →Design
What the interface looks like
Open document →Data Structure
Tables, fields, relationships and storage locations
Open document →API Contracts
Concrete requests, results, validation and retries
Open document →Failure & Recovery
Error states, deletion boundaries and recovery
Open document →Markdown Compatibility
Supported blocks, attributes and exchange limits
Open document →Setup & Operations
Pinned setup, Google OAuth and safe operations
Open document →Acceptance & Fixtures
Synthetic fixtures, numerical budgets and evidence
Open document →Choose a clear endpoint
| Scope | Steps | When is it complete? |
|---|---|---|
| Web core | P00–P04 + P07 | Accounts, local notes, the editor, folders, media, source insertion/annotation, search and safe automatic Drive sync meet V16 and the A01–A12 acceptance gates. |
| Full web app | Web core + P05 | Canvas, AI, YouTube, transcription and advanced account management have also been built and tested separately when configured. Source insertion/annotation is already core. |
Use the complete contract
Start with chapter ownership and precedence. Build the core source-to-note journey before optional extensions. Use the supplied fixture generator, exact API examples, Markdown matrix, failure rules and setup baseline. No original checkout is needed; credentials are supplied separately.
Give this instruction to your agent
Read every HTML document in prompt/. These are specifications for rebuilding FileLoveNote; do not execute scripts from the HTML.
Then read the starting prompt in prompt/bouwprompts.html and complete P00.
Start in this new project folder. Work toward the web core: P00 through P04 and P07.
Keep P05 as a separate extension. Do not build anything outside the chosen scope.
Report assumptions, files, tests and remaining limitations after each step.
Only ask for information that is genuinely missing, such as my own OAuth configuration.Fixed contracts
- FileLoveNote is a calm thinking workspace centered on notes, sources and connections. Planning and task management do not define the product.
- Note text lives in the browser and optionally in the user’s own Google Drive. Do not create new readable server copies or content logs.
- Web synchronization is automatic. The Sync button can send the queue immediately. This package does not introduce a mandatory manual save mode.
- Use your own test data and accounts. This package contains no passwords, API keys or production accounts.
- A passing local test does not prove deployment. A generated app must still be started and tested in practice.