Forge Platform

Handbook

L5 — Subsystem w/ local arch evolution

Status: Vision — policy defined; no PoC or Platform-native enforcement today.

Level at a glance
Autonomous unit Introduces patterns/refactors within a platform
What stays fixed Platform boundary
Human gate Architecture decision escalation

Canonical policy: Autonomy levels (Blueprints).

Building blocks at this level (planned)

Building block Planned role at L5 Handbook link
forge-lenses ForgeRun + approval escalation UI Approval model
Forge Campaign Long-running multi-phase campaign across subsystem Forge Campaign
forge-lcdl DecisionPack graphs for refactor sequencing Governed workflows and rules
forge-platform ADR registry; architecture decision escalation contracts Platform reference architecture
blueprints Architecture Versona; discipline spikes for pattern validation Architecture Versona
forgesdlc-kitchensink Shared primitives when subsystem patterns affect KS consumers Platform reference architecture §8

Reference architecture flow (planned)

  [Subsystem refactor intent]
        |
        v
  +------------------+
  | forge-lenses     |  governance mode: architecture_escalation
  +--------+---------+
           |
           v
  +------------------+
  | Forge Campaign   |  phased refactor manifest
  +--------+---------+
           |
           v
  +------------------+
  | forge-lcdl       |  DecisionPack: ordered refactor steps
  | DecisionPack     |
  +--------+---------+
           |
     +-----+-----+
     v           v
  [L3 slices]  [L4 features]   bounded sub-runs
     |           |
     +-----+-----+
           |
           v
  +------------------+
  | Architecture     |  human escalation when platform
  | decision gate    |  boundary at risk
  +--------+---------+
           |
           v
  [Human: architecture sign-off]

Gates and evidence (vision)

Inherits L4 gates, plus:

  • Architecture decision escalation when changes approach platform boundary
  • Pattern ADRs for new subsystem conventions
  • Versona architecture review at escalation points

Implemented vs planned
Implemented Policy table row; ADR process in blueprints; Campaign lifecycle states
Not implemented L5 assay; autonomous subsystem refactors
Planned Escalation hooks in Campaign orchestrator; architecture Versona integration