Research and project briefs
The daily operator workflow reviews public trends and research, then selects a bounded project. Every idea needs a useful problem, source evidence and acceptance criteria.
RESEARCH → EVIDENCE → SOFTWARE
An autonomous
software factory.
Turn research and ideas into useful tools through a scheduled build, test, optimization and release workflow. Built for developers shipping CLIs, MCP services and library integrations.
Start free Try the shipped example ↘1 project · 1 run request every 24 hours · No credit card
Workflow illustration · execution requires authorization
Tools, interfaces and integrations
Scope CLIs, browser interfaces, MCP tools and library integrations. Implementation, tests, benchmarks and documentation belong in the same release workflow.
Evidence and launch preparation
Authorized operator releases include test evidence and registry receipts. Prepare demos, release notes and promotional drafts. Product Hunt stays in draft until launch approval.
TRY IT BEFORE YOU REGISTER
Check your README in one command.
README Proof runs locally. The command checks your README for npm portability and emits findings; it does not execute commands found in the document.
npx readme-proof@0.1.0-next.0 analyze README.md --target npmInspect the release evidence · Watch the 28 second example demo
This is the shipped package, not a live factory build. The workspace requires verified registration and authorized execution.
WATCH THE SHIPPED EXAMPLE
Real software. Real walkthroughs.
Both videos show README Proof, the first shipped tool. They do not demonstrate an unattended factory build.
Edited product demo
A 28 second overview of the shipped README checker, its browser interface and package. Background music; no spoken narration.
Open video directly ↗Raw browser walkthrough
The original screen capture of the example product. Inspect the interface without the promotional edit.
Open video directly ↗Built by the factory
README Proof
A local README checker with CLI, browser UI, MCP tools and RVF evidence. Published on npm with a release receipt.
Clean-room interoperability
Signed interface contracts, independent reviewer keys and isolated compatibility tests. Production authoring still needs separate environments.
Build the next useful tool
Rust-backed Python libraries, local-first MCP tools, developer CLIs and benchmark explorers. These are project briefs, not published products.
Connecting to your Cloudflare Access session…
YOUR WORKSPACE
From brief to build
Create your free workspace
Your verified Cloudflare Access email links your workspace to you. Start with 1 project and 1 run request every 24 hours. No credit card required.
01
Define a project
02
Projects
—Your projects will appear after access is verified.
03
Run requests
A queued request is a stored intent. It does not mean a runner has executed, tested, or published software.
No run data loaded.
Specify before implementing.
Observation evidence stays in Room A. Room B implements from the approved specification. Independent environments are required; the evaluator isolates tests only.
Approval is a release input.
Clean-room requests stop for evidence review and signed approval. Creating a request does not approve it or prove isolation.
Keep claims reproducible.
Tests, benchmarks, provenance and publication receipts should support each release. Missing execution evidence stays visible.
Before your first run
What does the free workspace include?
One project and one run request in a rolling 24 hour window. Sign in through Cloudflare Access, register your verified identity and define your project. No credit card is required.
Will a request automatically publish my software?
Free requests wait for authorization. Operator requests enter the execution queue. A queued request is not a completed build. A release needs tests and independently checked publication evidence.
What can I build?
Start with a bounded developer tool: a README checker, a local MCP service, a benchmark explorer or a library integration. Specify the input, expected output and one acceptance test.
Is clean-room implementation ready for production?
The reviewed contract handoff and compatibility pilot are available. Production work requires independently operated observation and implementation environments plus signed review.
Does Pro access include billing?
Request Pro access records your requirements. It does not charge you or change your plan. Higher limits and commercial terms are not yet activated.