Portfolio status: Experimental reference prototype. Local preview can be verified; live connectors, external hosting and production release are not implied.
WEBFORGE explores how far a structured brief can travel through research, product modeling, design, generation and browser QA before a human has to take over.
flowchart LR
A[Brief] --> B[Research]
B --> C[Product model]
C --> D[Design DNA]
D --> E[Generate]
E --> F[Browser QA]
F --> G{Pass?}
G -- no --> H[Bounded repair]
H --> F
G -- yes --> I[Preview ready]
npm run doctor
npm test
node src/cli/webforge.mjs factory "Premium techno club in Prague with events, artists, tickets and gallery."
npm startHTTP: POST /api/factory/run with { "brief": "..." }.
Research → Product Model → Design DNA → Component Synthesis → Content/Media Fulfillment → Connector Plan → Runtime Build Gate → Chromium QA → Critique → Bounded Auto-Repair → Preview Ready → Production Gate.
Portable preview can PASS locally. Native framework dependency build, live external connector execution, external hosting and production release remain UNVERIFIED/BLOCKED until actually executed and evidenced. READY != PASS. Production requires all gates plus explicit approval.
WEBFORGE can now resolve external component candidates through a governed federated registry layer. It uses the public shadcn registry directory as a discovery bus, ranks sources against the project's capabilities and Design DNA, inspects only the selected exact item, and requires policy/license approval before installation.
npm run federated:smoke
node src/cli/webforge.mjs components sources
node src/cli/webforge.mjs components search "cinematic event hero tickets"External registry availability is never inferred from configuration alone: UNVERIFIED != PASS.