Loft 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; they are not required to make today's Loft workflow useful.

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 proposed pillar for decomposing and coordinating production across more workstreams, agents, repositories, and engineering systems. Yard is not offered as a product today. It extends the bounded implementation workflow already present in Loft rather than creating the first connection between the contract and code.

Berth: operational feedback

Berth is the proposed pillar for runtime behavior, technical and business measurements, incidents, defects, and customer signals. Berth is not offered as a product today.

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's product direction keeps the ratified contract, authority, and acceptance record outside any single agent transcript or model runtime. This is an architectural direction, not a promise of universal compatibility, export rights, or continuity after termination.

Current product and future direction.

Loft has substantial implementation work across contract authoring, packaged agent skills, and reconciliation and is being prepared for bounded external use. Most evidence is internal. Yard and Berth are future pillars with partial or conceptual groundwork, not available products or roadmap commitments.