Docs

How the Printer Works

Manifesto Engine turns a product idea into a selected printer contract, a verified printout, matching code artifacts, sandbox verification, and a downloadable product ZIP.

1. Choose a printerSelect one of the domain modes or describe the build. The printer resolves models, handlers, persistence, and tests.

2. Print the blueprintThe deterministic contract anchors the output while DeepSeek enrichment fills in details the local side should not guess.

3. Fabricate codeFabricate writes MANIFESTO.md, models.py, core.py, store.py, verify.py, and receipts into an output folder.

4. Verify and learnSandbox tests run. Passing behaviors become learned rules for future prints and the ZIP becomes available.

Single Printer

The focused single-printer workspace lives at /printer. It is the straight path for one blueprint: print, fabricate, verify, download ZIP.

Factory Mode

Factory Mode chains multiple printers into one packet. For example, a SaaS factory can print SaaS platform, API spec, web UI, infrastructure, and security contracts together with alignment checks.

Live vs Local

The hosted site can print, fabricate, verify, and return downloads through credits or guest credits. Local mode remains useful for unlimited testing, private projects, and standalone/buy-once workflows.

How Users Get Their Stuff

Blueprints appear in the browser after generation.
Fabricated products expose a Download ZIP link and individual file links.
Signed-in users can access generated blueprint history from the dashboard.
Factory packets return downloadable packet artifacts and a full factory ZIP.
Artifact receipts keep product downloads available after the in-memory print session expires.

Current Printer Modes

Software, infrastructure, API spec, migration, web UI, SaaS platform, evolve, systems, protocol, BGP, threat intel, MMORPG, security, IoT, synthetic data, HFT orderbook, cybersecurity, bioforensics, and hardware.