MLV Blank Page Automation -Document as an interface and virtual entity orchestrator

⸻

LMV v1 — Minimal Document-Centric Workflow Engine

What it is

A document-first web application where a single living document acts as the control surface for real-world workflows: planning, pricing, offers, orders, exports, and integrations.

The document is not a file. It is an orchestrator.

⸻

Core principle

One document = one source of truth. • UI is minimal • State lives on the server • Actions mutate data → server re-renders via Suspense • No client-side orchestration chaos

⸻

Target users (v1) • Independent professionals • Creators, consultants, trip designers • Small teams managing offers, pricing, or planning manually today • Builders who value clarity over dashboards

⸻

Core workflow (v1)

1. Start with a blank document • User logs in • Lands on a blank document canvas • No menus by default • Left drawer / minimal dock for navigation between documents

⸻

2. Compose the document

Document is made of typed sections: • Text • Planner (rows × columns) • Line items (prices, quantities, totals) • Metadata blocks (status, references)

Each section: • Is deterministic • Has a schema • Can be rendered or edited • Can trigger server actions

⸻

3. Trigger real operations from the document

From inside the document: • Generate a Trip/experience/product • Generate an Offer • Confirm an Offer → generate Order • Recalculate line items • Sync changes across related entities

All triggers: • Go through Server Actions • Touch Prisma only in actions/ • Call revalidatePath / revalidateTag • Rely on Suspense for UI updates

No client polling. No manual refetch.

⸻

4. Status-driven lifecycle

Entities evolve by status, not deletion. • Draft → Proposed → Confirmed • Only Orders are permanent • Documents, Offers, Trips can be revised or discarded • Revisions create new versions, not silent mutations

⸻

AI (secondary, controlled)

AI is not the core. It is a tool inside the document.

Supported uses: • Fill structured forms (typed, validated) • Generate document content via Personas • Assist planning (MLV, offers, summaries)

•	Composing structured documents like with apple notes but with a window to automation by design

	•	Streamlining processes on demand for custom users/companies

•	Finding prospects from google maps to list into our document.

•	Composing email marketing secuences with and opt out remove option for blue emails to public company/ brand emails .

•	Trigger or schedule triggers to send emails

•	Integrate with google calendar

Explicit constraints: • AI outputs must conform to schemas • No free-text automation touching integrations • Human confirmation always required

⸻

Integrations (hard-coded, v1)

Only platforms aligned with independent creators: • FareHarbor — experiences & trips • Shopify — independent commerce • Etsy — artisanal marketplace

• Holded — approved accounting app for Spanish official administration App Facturación España

Google calendar google places or custom appscript deployment to feed searches from google places as a table, Export to google docs , via appscript API Export to google sheets Export as calendar event WITH email notifications set or invitations sent .

*

Integration model: • Export structured data • Optional manual confirmation • No universal Zapier-style mappings in v1

⸻

Export & sharing (required) • Email documents • Generate PDFs • Share read-only links • Export line items to: • JSON • CSV • Platform-specific formats (Shopify, FH, Etsy)

⸻

Architecture (non-negotiable)

Frontend • Next.js App Router • Server Components by default • Client components only for UI state

Data & logic • Prisma (single source of persistence) • Prisma access only in actions/ • API routes = thin wrappers (external use only)

Rendering • Server owns promises • Client never awaits business data • Suspense coordinates partial refresh

⸻

What this is NOT • Not a dashboard app • Not an automation marketplace • Not a generic CRM • Not Zapier with AI

⸻

Why it exists

To replace: • scattered documents • manual spreadsheets • fragile automations • over-engineered UIs

With: • one document • one flow • one mental model

⸻

v1 success criteria • Daily use by the builder • One full workflow completed end-to-end • At least one real export (offer, order, or trip) • Users can explain it in one sentence

⸻