00Product Profile and Completeness
Fill in the product under factory control. The completeness meter, share link, and readiness tools read from this profile.
Sample loaders
Three samples drawn from the manual's Initial Portfolio table (Section 11).
Share link
Encodes the profile, checklist state, and calculator inputs into the URL hash (#d= base64 JSON). Anyone opening the link restores the same state.
01Purpose and Executive Summary
Source: Purpose block and Executive Summary, page 1 of the manual.
Purpose. Turn a precise product contract into a verified MVP through isolated Git repositories, bounded AI implementation, deterministic verification, evidence manifests, and human-controlled promotion.
Neuruh Factory is the production lane for converting the Neuruh portfolio from ideas and partially recovered tools into independently useful, testable product slices. It deliberately separates product authority, AI implementation, deterministic verification, independent audit, and production promotion.
02The Core Loop
Source: The Core Loop, page 1. Check off steps as a run proceeds. Progress is saved into the share link.
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
03What Version 2 Solves
Source: What Version 2 Solves, page 1. Seven failure modes v2 is designed to close.
- A model printing commands without executing them
- Command text accidentally becoming filenames
- Mandatory failures being swallowed
- Sessions losing context after provider or summarization failure
- Generated code being mislabeled as verified or live
- Autonomy expanding into production authority
- Products being built without customer validation or distribution plans
04Operating Boundaries
Source: Operating Boundaries, page 2. Three authority columns. Anything in the third column is never automatic.
| Autonomous | Approval Required | Never Automatic |
|---|---|---|
| Source edits in assigned repo | Paid external service | Production deployment |
| Local dependencies and containers | Private data integration | DNS changes |
| Tests, builds, local migrations | Shared schema change | Customer communication |
| Bounded repair passes | Preview environment | Destructive production migration |
| Local Git commits and evidence | Critical repository change | Production credentials |
05Factory State Machine
Source: Factory State Machine, page 2. The factory forbids GENERATED to LIVE and stops its autonomous loop before preview or production promotion.
State machine simulator
Current state: IDEA
06Build Lanes
Source: Build Lanes, page 2. Five lanes, from concept to production mutation.
Define user, pain, outcome, evidence, and kill criteria. No coding.
Fast autonomous local build in an isolated repository.
Controlled test integrations and explicit preview approval.
Exact SHA, clean worktree, bounded change, independent audit.
Backup, rollback, named approval, monitored operator window.
Lane selector
07Autonomous Operating Loop
Source: Autonomous Operating Loop, page 3. The v2 controller invokes Aider once per bounded phase. After source edits, the factory itself runs verification commands as argument arrays. Failed gates trigger a bounded repair request containing the real failure log. Exhausted repair budgets produce a blocker instead of an invented success.
- 1Contract and source census
- 2Repository bootstrap
- 3Primary vertical slice
- 4Security and operational hardening
- 5Acceptance and release evidence
Repair budget calculator
Failed gates trigger a bounded repair request with the real failure log. When the repair budget is exhausted, the factory produces a blocker, not an invented success.
08Verification and Evidence
Source: Verification and Evidence, page 3. Eight evidence items recorded for every verification run.
- Starting and ending SHA
- Branch and dirty state
- Exact command argument array
- Exit code and duration
- Complete command log
- Gate result
- Final verdict
- SHA-256 evidence manifest
Evidence manifest builder
Fill in a verification run. The builder assembles the manifest and computes a demo checksum over it. The checksum here is a simple deterministic demo hash, not a real SHA-256; see Honest Gaps.
09Product Readiness
Source: Product Readiness, page 3. A product may enter BUILDING only when all seven items are explicit.
Check each item that is explicit for the current product:
Verification commands are also listed in the manual as a readiness item; they are tracked in the profile above as field 9 of 9.
10Product Definition of Done
Source: Product Definition of Done, page 4. Nine conditions, all required.
11Initial Portfolio
Source: Initial Portfolio, page 4. Priority, product, and thin slice, exactly as listed in the manual.
| Priority | Product | Thin Slice |
|---|---|---|
| P0 | DeedSonar Core Decision Slice | One property to one defensible acquisition decision |
| P0 | CRM Jarvis | Search to evidence to recommended next action |
| P1 | N-Cell | Runtime state and provenance protocol with observer |
| P1 | Driving Property Marker | Location to parcel to captured lead |
| P1 | Land and Zoning Engine | Parcel to buildability and highest-best-use paths |
| P1 | Residential Valuation | Property facts to evidence-backed ARV and thresholds |
| P1 | Multifamily Underwriting | Rent roll to stabilized decision |
| P2 | World Emitter | Structured intent to visible scene or simulation |
Related live builds on the hub: Neuruh Hub. The Land and Zoning Engine and Residential Valuation lines connect to the E-series underwriting engines listed there.
12Operator Quickstart
Source: Operator Quickstart, page 4. Commands reproduced verbatim from the manual. Paths are the manual's paths, not this machine's.
Each command is a manual step, not a button on this page. This demo does not run shell commands and does not touch any repository.
13Recovery
Source: Recovery, page 5.
After power loss, provider failure, terminal closure, or summarization failure, preserve Git state, inspect the latest .factory run logs, verify that no controller process is active, and resume the first incomplete phase.
14Strategic Standard
Source: Strategic Standard, page 5.
The factory's north-star metric is not lines of code or repositories created. It is the number of independently demonstrable, evidence-backed product slices produced per week that change a real user decision.
North-star calculator
15Try-It Walkthrough
Six steps, about three minutes. No install, no account, nothing leaves the browser.
- 1Click "Load sample 1" above to fill the product profile with the DeedSonar Core Decision Slice.
- 2Watch the completeness meter reach 100% and the missing-fields list clear.
- 3In Section 05, advance the state machine from IDEA to GENERATED, then try the direct promotion to LIVE and watch it get blocked.
- 4In Section 09, check all seven readiness items and see the BUILDING gate open.
- 5In Section 08, build an evidence manifest and note the demo checksum.
- 6Click "Generate share link", copy it, and open it in a new tab to see the state restore.
16How It Works / What This Is Not
Plain statement of scope, per the build standard.
How it works
- This page is a single self-contained HTML file. All styling and logic are inline; it makes no network requests.
- Checklists, calculators, and the state machine simulator run locally in the browser.
- The share link stores the current profile and checklist state in the URL hash as base64 JSON and restores it on load.
- Completeness is computed from the nine profile fields; readiness from the seven readiness items; Definition of Done from the nine conditions.
What this is not
- Not the Neuruh Factory software. It cannot build, verify, or deploy anything.
- Not the manual PDF. It is a demo of the manual's structure and procedures.
- Not a live build system. No Git, no Aider, no verification commands run here.
- Not evidence. Manifests and checksums produced here are demonstrations, not factory receipts.
- Not an endorsement that the factory operates as described. The manual's claims are reproduced as source claims.
17Honest Gaps
What this demo does not do, and what the source does not establish.
Source claims on this page are labeled as source claims, not verified facts. Figures are drawn from the manual's own text and tables.
More from Neuruh: Neuruh Hub (master map of live builds). Sibling reference: the Real Estate Agent hub and E-series underwriting engines listed on the hub relate to the Land and Zoning Engine and Residential Valuation portfolio lines in Section 11.