Creytix Frontier Bind
Name and ship a scoped tool set for a site — not unlimited custom software.
A binding step that attaches named, pre-built Creytix tools to a site in a single operation, so the site goes from scaffold to operating system without a full custom build.
From scaffold to OS in one bind.
What it does for you
Named tools, not forks
Frontier Bind attaches tools from the Creytix catalog to a site — it does not fork or clone tool code into the site repo. The catalog stays the SSOT.
Scoped, not unlimited
Each site gets a defined Frontier Tool set (FTS) — the tools it actually needs, registered and authorized, not an open-ended custom software contract.
Documented handoff
The bind step writes a FRONTIER_TOOLS_BY_SITE manifest so future sessions can see exactly which tools are live on which site without reading code.
Capabilities
- Catalog tool attachment (no fork)
- Scoped Frontier Tool Set per site
- FRONTIER_TOOLS_BY_SITE manifest
- CLI: npm run creytix:site:complete
- Pipeline follow integration (PRC-028)
Proof, not adjectives
- Creytix's own site is bound
- The creytix.com site runs through Frontier Bind — its Frontier Tool set is the reference implementation for the bind format.
- Process PRC-026 registered
- Site post and Frontier Bind are registered under PRC-026 in the Creytix process registry, with a pipeline and a CLI command.
Related tools
Built with Creytix, on Creytix
This page itself was produced by the platform it describes — the same design tokens, module pipeline, and review gates used for every Creytix client site. Nothing here is a mockup of the product; it is the product.
Frontier Bind
Name the tools a site needs — then bind them, don’t fork them.
Site Complete wires the catalog. We do not claim unlimited custom software.
Frontier Bind