Skip to content

Factory Studio — information architecture

Target

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

The Studio is organised by what a person is doing, not by platform. Seven work areas cover every screen of the screens catalog; each composes read models from several platforms through the BFF (GW-02) and forwards commands with their classes. Decision D35 folds the Workflow Studio prototype into these areas: one asset catalog, one run list, one source of truth.

Work areas

Work area Who Composes from Screens
Workspace everyone, requesters and reviewers first Control plane (runs, approvals, projects, environments, usage), Observability screens
Assets asset maintainers, platform admins Asset publication, agent cards, tools and MCP, model profiles, workflow definitions, templates, marketplace screens
Intelligence requesters, maintainers Knowledge sources, search and graph, memory, repository intelligence, context snapshots, artifacts screens
Quality & releases maintainers, reviewers Evaluation, evidence, feedback, datasets, learning proposals, product releases screens
Operations & usage operators, workspace admins, observers Operations projections, objectives, alerts, usage and cost, capacity, fleet screens
Governance & administration platform and workspace admins Policies, approval policy, audit, findings, secrets references, connections, connectors, registry, stores, retention, residency, orders, users, billing, preferences screens
Software Factory requesters, maintainers, operators Blueprints, DSLs, recipes, provenance, proposals, pipelines, promotions, provisioning, inventory, generated products, run graphs screens

Map

mindmap
  root((Factory Studio))
    Workspace
      My work
      Submit a run
      Run detail
      Approvals
      Project
      Environments
    Assets
      Asset catalog
      Releases
      Agent cards
      Tools and MCP
      Model profiles
      Templates
      Marketplace
    Intelligence
      Sources
      Search and graph
      Memory
      Repositories
      Context snapshots
      Artifacts
    Quality and releases
      Evaluations
      Evidence
      Feedback and datasets
      Learning proposals
      Product releases
    Operations and usage
      Runs and timelines
      Overview and status
      Alerts
      Usage and cost
      Capacity
      Fleet, rollouts, incidents
    Governance and administration
      Policies and approvals
      Audit and findings
      Secrets and connections
      Registry and stores
      Retention and residency
      Users and billing
    Software Factory
      Blueprints and DSLs
      Recipes and outputs
      Proposals and pipelines
      Promotions and provisioning
      Inventory
      Generated products
Hold "Alt" / "Option" to enable pan & zoom

From the prototype to the work areas

The Factory prototype's 48 destinations and the Workflow Studio's 28 map onto the work areas in the prototype alignment: 13 kept, 8 renamed, 42 merged, 13 retired. Retired destinations are concerns a platform owns outright (milestones and sprints are coordinator workflows; microfrontend and gateway consoles are generated from blueprints; copilot and RPA builders are agents and sandboxed tools). Retired destinations keep their content as the archived June-2026 modules.

Rules

  • A screen belongs to exactly one work area; cross-cutting objects (a run, an approval, an artifact) open in their home area from anywhere through links and the command palette.
  • Navigation entries follow the permissions catalog: a role that cannot open a screen does not see its entry.
  • Every list screen supports saved views (private, project, tenant) and the same filter vocabulary as the state families.
  • Routes are stable resource keys; browser Back restores list and filter context; a scope switch with unsaved changes asks first.