Runner

Overview

Runner is a planned internal component of the Glounix Factory engineering pipeline. It is described in Factory's design material as the consumer of a phase document, responsible for phase decomposition, task planning, prompt generation, execution, and verification.

There is no standalone Runner repository or public product surface. The Factory build directory named for Runner is currently empty, so this page documents the intended role rather than an implemented capability.

Origin and motivation

Factory separates design authority from deterministic tooling. Runner is part of the intended execution layer that would carry an approved phase plan through controlled task execution and verification.

The problem

Long engineering phases need a repeatable way to decompose work, generate explicit task prompts, execute them, and verify outcomes without losing the governing plan.

Who it is for

Factory engineering operators and future platform users who need governed execution inside the software production pipeline.

Vision and objectives

A bounded execution component that turns an approved phase plan into traceable tasks and verification evidence.

Key capabilities

• Phase decomposition (planned)
• Task planning (planned)
• Prompt generation (planned)
• Task execution (planned)
• Verification handoff (planned)

Engineering and architecture

The only current evidence is the Factory design document that names Runner as the consumer of a phase document, plus an empty build directory. No implementation, API, schema, or test suite is claimed.

Difficult problems and solutions

Current status

Runner is a planned concept. It is presented here to preserve the portfolio's engineering narrative without inventing capabilities. Current status should be updated only when a pinned implementation and tests exist.