Objective and architecture
Workshop presents operational context through Pulse, Work, Review, Workshop and Record. Its implemented interface work includes a mission surface, navigation hierarchy, review sidecar, bounded console seam and reusable Qt/QML components. The architecture is intended to hold approved objectives, their evidence and a human decision path rather than to automate development authority.
Scheduler Core
Designed to organise bounded work and dependency handling; it does not self-authorise objectives.
Approval Gate
Review-required state and explicit human decisions are the governing boundary.
Production Organ Harness
A future bounded-worker connection point, not evidence of unrestricted agent control.
Observatory seam
Read-only state presentation can be linked to observability without turning telemetry into authority.
Governed work flow
Workshop governed-work flow
Implementation history and validation
Forge Prime R0 recorded eight reusable interface components, the Pulse composition, Review governance sidecar and a console visual seam. The recorded test result was 383 passing tests across runtime and Workshop suites, with Qt/QML lint completed for the changed components. Live feedback also informed layout, navigation and hierarchy refinements.
- Claim
- A bounded Forge Workshop interface was implemented and tested.
- Method
- Runtime and application test suites, QML linting and live interaction review.
- Result
- Recorded implementation and test evidence supports the interface components and review presentation.
- Limitation
- This does not establish autonomous software development, a completed R&D Sector, Core Forge, or unrestricted organ authority.
- Source period
- 2026 implementation record.
Current state, failure and recovery
Workshop supports meaningful interface and review work. Bounded retries, restart safety and evidence return are design and infrastructure concerns; they must remain explicit in each authorised workflow. A failed or incomplete task is a state to surface and review, not a reason to silently continue or promote work.
Known gaps include complete dependency execution, a fully connected Production Organ Harness, completed R&D work and Core Forge. Those items remain separately governed.
Related systems and provenance
Workshop depends on human-governed agent orchestration for its authority boundary, evidence and external memory for decision lineage, and Observatory for read-only analysis.
Sources: public casefile implementation evidence; canonical Forge Prime result record; Workshop authority model. Internal source paths and operational configuration are intentionally excluded.