What's in the package
Every file ships from day one. Only the part that is needed gets used.
You don't have to read through this. The installation file creates the core in your project, the rest grows in when the need appears. The list shows exactly what exists, nothing more and nothing less.
Every file carries a short header stating version, type and status. Normative documents govern what may be done, descriptive documents report the current state, historical documents preserve what happened.
- ACTIVE
- The area is in use and kept current.
- NOT_YET_APPLICABLE
- The area isn't relevant yet. It is activated according to the framework's rules when it becomes relevant.
- RETIRED
- The area was relevant but has been replaced. The history is preserved.
Entry and governance
- START-PROMPT.txtnormative
The text you paste into Lovable the first time. It starts the bootstrap.
- 00-START-HERE.mdnormative
The package explained on one screen: what you do, what Lovable does.
- 01-START-INTERVIEW.mdnormative
Ten questions Lovable asks one at a time before building starts.
- PROJECT-KNOWLEDGE.mdnormative
The entry point to the project's memory: what to read, and when.
- PROJECT-CONSTITUTION.mdnormative
Thirteen rules that take precedence over everything else in the project.
- MANIFEST.yamlnormative
Machine-readable routing: which kind of change requires which documents.
Product and scope
- PROJECT-BRIEF.mdnormative
The product's intent, audience and what counts as success.
- SCOPE-AND-ACCEPTANCE.mdnormative
What is included, what is not, and when something is done.
- DOMAIN-RULES-AND-INVARIANTS.mdnormative
Rules that must never break, no matter how the code changes.
- CURRENT-STATE.mddescriptive
What actually exists and works right now.
- RISKS-ASSUMPTIONS-OPEN-QUESTIONS.mddescriptive
Everything not yet settled, written down instead of forgotten.
- CHANGELOG.mdhistorical
The product's history in chronological order.
Technology and quality
- ARCHITECTURE-AND-QUALITY.mdnormative
How the system is built and which quality requirements apply.
- DATA-MODEL-AND-LIFECYCLE.mdnormative · not_yet_applicable
Activates when the project starts storing data.
- INTEGRATION-CONTRACTS.mdnormative · not_yet_applicable
Activates with the first integration against an external service.
- UX-AND-CRITICAL-FLOWS.mdnormative · not_yet_applicable
Activates when a flow must work end to end, not just look right.
- SECURITY-PRIVACY-THREATS.mdnormative · not_yet_applicable
Activates with sign-in, permissions, personal data or payments.
- TEST-STRATEGY.mdnormative · not_yet_applicable
What must be verified, and how it gets verified.
- OPERATIONS-RELEASE-RECOVERY.mdnormative · not_yet_applicable
Activates when the product has real users you must not disrupt.
Decisions
- decisions/INDEX.mdhistorical
Every decision with its rejected alternatives. The line that stops the loops.
- decisions/ADR-TEMPLATE.mdnormative
Template for a single decision, including when it may be reconsidered.
Workflows
- workflows/bootstrap.mdnormative
From downloaded package to the first build.
- workflows/change.mdnormative
How every change is read in, decided, verified and written down.
- workflows/release.mdnormative
What must hold before anything goes live.
- workflows/incident.mdnormative
When something breaks in production: order instead of panic.
The framework itself
- framework/FRAMEWORK-VERSION.mddescriptive
Which version of the framework the project uses.
- framework/FRAMEWORK-CHANGELOG.mdhistorical
What changed in the framework between versions.
- framework/UPGRADE-GUIDE.mdnormative
How to move to a newer framework version without losing history.
Download the package
We don't need to know what you're building. No account, no form, no upload.
- MD · 1 file · version
- lovable-framework-1.0.0-en.md · MD · 1 file · version 1.0.0
- SHA-256
- 12719287381e9baa088cda0192d754e4f6fd544dd5ef6475f2ed669e49b29160
The full package as a ZIP, 28 files (advanced option)lovable-framework-1.0.0-en.zip · SHA-256 b426a57d3ed8822f85bcd486576e3180860cb2fd0ce47e43db3d8c9a0ac51315