Vision

Alloy is a proposed engineering intent management layer that sits above Foundry and beside Epilogue Tracker. Epilogue Tracker captures product intent (who the system helps and what goals those actors have); Foundry executes engineering work as event-driven formations of task blocks, gates, agents, and traces. Alloy fills the missing layer between them: the explicit, structured expression of Engineering Intent Records.

The central thesis is that product intent says what people need the software to make possible, while engineering intent says what capabilities the codebase and team must retain as the software changes. Alloy models that intent as records of capabilities, threats, expectations, strategies, evidence, and tradeoffs — turning tacit developer judgement into a form that agents, formations, gates, prompt packs, and humans can all use.

Positioned as an engineering intent management system and runtime control plane, Alloy borrows from requirements tools, ADRs, prompt libraries, and workflow engines but has a more specific job: it captures engineering intent from developers and codebases, compiles it into Foundry formation briefs, and carries the resulting guidance into autonomous execution. It does not replace Foundry, Epilogue Tracker, or the design intent system — it complements all three through a clear ownership boundary.

In this section

• Executive Summary — what Alloy is and the three artifacts it first produces.
• Product Thesis — why autonomous delivery needs explicit engineering intent.
• Product Positioning — category, relationships, and the one-line promise.
• Problem Statement — the abstraction gap Alloy closes.
• Target Users and Jobs — who uses Alloy and the jobs they need done.
• Product Goals — what Alloy should accomplish.
• Non-Goals — what Alloy deliberately will not be.
• Product Narrative — the short, plain-language story of Alloy.

Source: Product Brief §1, §3, §4 (Executive Summary, Product Thesis, Product Positioning).