Platform
Platform
Furnace in five claims, each checkable from the outside:
- One surface, three doors. Every capability ships as a human interface, REST operations, and MCP tools — generated from the same definitions, so they cannot drift apart. Evidence: pick any tool in
tools/listand find its twin in the REST reference. - Authority only narrows. A token can be scoped below its owner's permissions, never above; UI, REST, and MCP run the same checks. Evidence: Personal access tokens.
- Changes are audited. Every mutation is attributed to the identity that made it, human or agent alike.
- Interfaces can be data. Furnace UIs can be expressed in SDL — a closed, validated JSON language over the design system — which is what makes AI-generated, platform-governed interfaces possible. Evidence: SDL.
- Apps can be data too. A generated app is a governed record — schema, pages, automation — hosted by a shared runtime, with no per-app deployment. Evidence: Generated apps.
The pages in this section tell each story at concept depth: enough to evaluate the platform honestly, without the internals.
In this section
What runs on Furnace
The live products as evidence of the platform.
Design system
Three layers: native CSS, custom React components, SDL.
SDL — interfaces as validated data
A closed, validated JSON language for complete interfaces.
AI workflows & automation
Immutable revisions, durable runs, governed model deployments.
Schema-driven apps
Apps declared as schema: entities, permissions, derived surfaces. Under construction.
Generated apps
Apps as governed data on a shared runtime. Under construction.
How these docs work
These docs run on the CMS they document — a live demo.