FP/01
Intent ingestion
Accepts vague requests like "I want an app that makes me money" and converts them into a structured project candidate.
Solomon / Subsystem Roadmap
The missing layer between human intent and software execution: qualify the idea, test the business model, select architecture, manufacture the project, validate it, and never claim deployment until deployment is proven.
01 / Why it exists
Most coding tools assume the operator already understands frameworks, terminals, dependencies, and deployment. Solomon begins earlier — with business intent, constraints, proof requirements, and the question of whether the thing should be built at all. This is a governed product-builder workflow for operators and technical founders who need decisions before code.
02 / Nine governed stages
Accepts vague requests like "I want an app that makes me money" and converts them into a structured project candidate.
Asks only the minimum necessary: customer, budget, time, skills, assets, revenue model, legal limits, deadline.
Labels the opportunity feasible, risky, unprofitable, unknown-until-research, or blocked by missing proof.
Chooses between SaaS, lead generation, local service tools, internal automation, marketplaces, memberships, and CRM extensions.
Records why one path was selected, what alternatives were rejected, and which assumptions must be tested.
Produces user stories, MVP scope, data models, integrations, acceptance criteria, and deterministic stack selection.
Generates structure, frontend, backend, schema, tests, env examples, README, launchers, and proof manifest.
Runs build checks, route smoke tests, render checks, security scans, hash generation, and governed retry loops.
States stay explicit: GENERATED, TESTED, PREVIEW_RUNNING, DEPLOYMENT_READY, NOT_PERFORMED, or DEPLOYED_VERIFIED.
03 / Truth contract
The pipeline must not claim profitable, deployed, validated, online, fabricated, or production-ready unless the corresponding evidence exists.