product-factory seam

Separate Product Boundary

The site is the experience layer. Link graphs, MCP bridges, CLI wrappers, APIs, and reposting engines are not built here — they live in the product layer. This page exposes the seam so teams know exactly where to plug in.

Product-Layer Responsibilities

Link Graph

separate product product-factory

Cross-links, canonical references, and adjacency surfaces live in the product layer.

MCP Bridge

separate product product-factory

Agent-facing protocol surfaces and tool adapters are not embedded in the site core.

CLI Mirror

separate product product-factory

Command-line workflows for extraction, indexing, and export live outside the site.

API Relay

separate product product-factory

Public API endpoints for cross-linking and reuse should be maintained as a standalone product.

Boundary Contract

The mocked API endpoints in this site define the contract surface. A product-factory deployment must fulfil these schemas to replace the mocks.

endpoint owner status
/api/site site-factory live (mock)
/api/references product-factory mocked
/api/collections product-factory mocked
/api/signal product-factory mocked
/api/feedback product-factory stub

The Endgame

Site-factory + product-factory operating in tandem: thought-to-public-visit in one day. The site factory owns the experience skeleton. The product factory owns the protocol, data, and automation surfaces. Both grow greedily by dog-fooding each deployment.