Discuss one product area

Longer-term direction

Build a closed loop from intent to software, evidence, and the next decision.

Loft is the first pillar of the Software Plant. Today it takes a product contract, the customer-ratified specification that roles and agents share, through coding-agent implementation and an evidence check to a human acceptance decision. Yard and Berth extend that loop.

Three jobs, at different stages of maturity.

Loft: product contract, implementation, reconciliation, and acceptance

Loft is the current product focus. Its product layer gives product, architecture, engineering, and assurance work a shared contract, connects the approved version to bounded coding-agent work, and brings the implementation revision and evidence back for human acceptance.

Yard: production coordination

Yard is the pillar for coordinating production. Its first part, Yard Client, comes with the open-source edition: on each branch it records what a coding agent planned, asked, and decided, and what people answered, beside the specification and the code. The pillar's wider aim is coordinating production across more workstreams, agents, repositories, and engineering systems.

Berth: operational feedback

Berth is the proposed pillar for runtime behavior, technical and business measurements, incidents, defects, and customer signals.

The current Loft loop is: Author the intended behavior, constraints, acceptance criteria, sources, and known gaps; Ratify the version of the contract that will govern the work; Implement the approved scope with a coding agent in the selected repository; Reconcile the implementation revision, test results, measurements, and other evidence against the contract; and Decide whether to accept, reject, or reopen the work. The longer-term Software Plant extends that same loop with Yard for broader production coordination and Berth for operational feedback into later product decisions.

People remain responsible for consequential decisions.

Agents may handle more investigation, generation, and testing inside each professional discipline. People still contribute the expertise of that discipline, resolve ambiguity across roles, designate authority, approve consequential changes, and decide whether the evidence is sufficient for acceptance.

The product contract should remain separate from the executor.

Models, coding agents, and engineering tools can act on the contract. Loft keeps the ratified contract, authority, and acceptance record outside any single agent transcript or model runtime.

Current product and future direction.

Loft's local edition, with Yard Client, is public and open source, and hosted Loft is in early access. Broader production coordination in Yard, and Berth's operational feedback, are the Software Plant's direction.