Skip to content

Template & Library — UI surfaces

Target

This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.

The platform's screens form the Software Factory work area's design half: blueprints, catalog, recipes and provenance.

Screens

Screen Reads Acts Roles
Blueprints ListBlueprints, GetBlueprintVersion create a version (schema-driven form or document upload); validate; open findings by rule; view derived context map and domain model; submit Requester, Asset maintainer, Observer
Template catalog ListTemplates, GetTemplateVersion browse manifests (projects, switches, generated and preserved paths, pipelines, docs); discover now; publish a Verified version everyone; Asset maintainer and Platform admin for actions
Libraries ListLibraries browse by area and layer; see consumers everyone
Compatibility matrix QueryCompatibility filter by template, library, runtime, edition, topology; open evidence everyone
Recipes ListRecipes, GetRecipe draft from a Published blueprint; adjust the module plan; validate; approve; open the generation run Requester, Reviewer, Asset maintainer, Observer
Generated outputs ListGeneratedOutputs per module and commit: generated vs preserved files, template version, run and proposal links Requester, Reviewer, Operator, Observer

States the screens must show

  • Blueprint: Draft, Validated (with findings count by severity), Submitted, Published (release id), Deprecated.
  • Template or library version: Discovered, Verified, Published, Deprecated, Retired; manifest hash and commit.
  • Compatibility cell: Compatible, CompatibleWithWarnings, Incompatible, Unknown (no evidence) — never a blank cell.
  • Recipe: Draft, Validated, Approved, Executing (with the run), Generated, Superseded.

Other clients

  • CLI: factory blueprint validate <file>, factory blueprint submit <id> <version>, factory templates list, factory compat <template> --with <library>, factory recipe draft --blueprint <id>, factory recipe approve <id>, factory outputs list --project P.
  • VS Code extension: schema-backed editing of blueprint documents with inline findings; provenance decorations on generated files.