Q-Forge is a quality-focused agent system for manufacturing workflows, not a generic chatbot.
This public repository is no longer only a proof page. It is now the public proof layer plus the migration blueprint for a local quality-specific OpenClaw runtime.
In roughly 24 hours, Q-Forge moved from an already-proven Goose + MCP setup into a local OpenClaw quality edition with Android mobile proof.
Within roughly 24 hours, the four Q-Forge capabilities that had already been proven on Goose + MCP were migrated into a local OpenClaw quality runtime and a hardened Android chat client:
8DRCASupplierReporter
The result is not a generic OpenClaw setup with extra prompts. It is a local quality runtime profile with:
- deterministic tool paths
- evidence-locked workflows
- local artifact generation
- mobile proof on Android
- the original Goose + MCP proof stack was not discarded; it was migrated
- the four working capability paths were re-established in a local OpenClaw quality runtime
- Android mobile proof was completed for
Supplier,8D, andRCA - the runtime was narrowed into a quality-specific profile instead of a generic assistant
- a public framework snapshot was added so other builders can follow the logic, not just the screenshots
This repository now shows one concrete thing:
Q-Forge was already real before this pass, and after one focused 24-hour migration sprint it became a local OpenClaw quality edition with working mobile proof.
This repository contains direct running proof, not only design notes.
- the workflows shown here were executed end to end
- the proof set includes real local HTML artifacts
- the proof set includes real Android chat screenshots
- the public examples, rendered outputs, and mobile traces all come from actual runs
Open the preview image to watch the 40-second 8D demo from the earlier Goose + MCP phase.
|
|
|
| Supplier mobile proof | 8D mobile proof | RCA mobile proof |
|
|
|
| Validation lock | 8D report artifact | RCA report artifact |
- real public skill packages under
skills/ - sanitized inputs, outputs, and rendered artifacts under
examples/anddocs/mobile-proof/ - public QMS Lite design and migration documents under
docs/ - a minimal framework snapshot under
framework/so other builders can follow the architecture without needing the full private runtime
| Capability | Current working path | Public proof |
|---|---|---|
| 8D | strict 8D audit path, deterministic D3-D7 checks, local HTML artifact, Android-triggered proof | good 8D HTML, bad 8D HTML, good chat screenshot, bad chat screenshot |
| RCA | detective-style branch-pruning chat, strongest cause-path conclusion, local HTML artifact, Android-triggered proof | RCA HTML, start screenshot, pruning screenshot, conclusion screenshot |
| Supplier | deterministic spreadsheet analysis, validation lock, local HTML artifact, Android-triggered proof | supplier HTML, supplier screenshot |
| Reporter | deterministic markdown-to-HTML renderer used by all three flows above | 8D preview, RCA preview |
Generic OpenClaw plus skills can add knowledge, but it does not automatically solve the runtime problem of quality work.
Quality-specific deployment needs:
- local data handling instead of casual cloud routing
- a reduced-permission mobile channel
- deterministic tool boundaries
- separate stable knowledge and daily work inputs
- logic-locked review paths instead of free-form model output
- rendered artifacts that can be reviewed and audited later
That is why QMS Lite is a runtime profile, not only a prompt pack.
- OpenClaw was reduced into a QMS Lite runtime profile
- the local gateway was kept, but the work was narrowed to quality workflows
qm-reviewandqm-rcawere turned into skill-driven agents instead of generic assistants8D,RCA,Supplier, andReporterwere wired into deterministic local tool paths- local data was split into:
knowledge-basework-inboxartifactsaudit
- the Android client was reduced from a general assistant into a secure chat terminal
- Firebase and update checks were removed
- cleartext traffic was disabled
FLAG_SECUREand gateway-only behavior were enforced during the hardening pass- the phone proof shown here was produced against the local OpenClaw QMS Lite gateway, not against a cloud runtime
- OpenClaw Quality Edition
- 24-Hour OpenClaw Migration
- OpenClaw Quality Architecture
- Android Secure Chat Client
- Mobile Proof Index
- Project Roadmap
- framework/README.md
- OpenClaw quality profile example
- Tool contract snapshot
- Bridge reference snapshot
- qm-review workspace rules
- qm-rca workspace rules
- Logic path summary
- RCA detective flow
- Mobile runtime boundary
These remain useful as the original Goose + MCP proof layer:
- 8D good input
- 8D bad input
- 8D audit markdown
- 8D rendered HTML
- RCA legacy markdown
- RCA legacy rendered HTML
- Q-Forge had already been proven on Goose + MCP before this migration pass started.
- The practical thesis was already validated: large models plus deterministic rules can produce useful quality outcomes.
- The current direction is now clearer: a local OpenClaw quality runtime plus Q-Forge-style skills is a better long-term base than staying on the old runtime.
- This repository now shows both:
- what had already worked
- how that working logic was migrated into a local OpenClaw quality edition
skills/: public skill packagesexamples/: sanitized source examples from the earlier public proof layerassets/: demo media and report previewsdocs/: public migration, architecture, and proof documentsframework/: minimal public code and config skeleton for QMS Lite
- Included here:
- proof artifacts
- migration explanation
- framework skeleton
- public skill packages
- Intentionally excluded:
- private project memory
- private runtime configs and secrets
- full local fork implementation
- real customer data
- full Android private implementation details
- X: @QForge_Builder
- Email: zhongshunchen2004@gmail.com
Apache License 2.0. See LICENSE.






