Alloy Documentation
Alloy is a proposed engineering-intent management layer that sits aboveFoundry and beside Epilogue Tracker. Epilogue Tracker captures product intent (who the system helps, what goals they have). Foundry executes engineering work as event-driven formations. Alloy fills the missing layer between them: the explicit, structured expression of engineering intent — the capabilities a team must preserve as the software changes.
Product intent says what people need the software to make possible. Engineering intent says what capabilities the codebase and team must retain as the software changes.
The guiding architectural principle across this wiki:
Alloy owns meaning. Foundry owns execution. Formation Briefs are the boundary.
This documentation is split from two source documents — the Alloy Product Brief (Draft v0.2) and the Alloy / Foundry Runtime Integration Architecture (Draft v0.1) — and reorganized into a layered wiki. Each page below is an overview that links down into detailed leaf pages.
Map of the territory
1. Vision & Positioning
Why Alloy exists, who it is for, and what it is not. The product thesis, problem statement, positioning, users, goals, and narrative.
→ Executive Summary · Product Thesis · Product Positioning · Problem Statement · Target Users & Jobs · Product Goals · Non-Goals · Product Narrative
2. Engineering Intent Model
The core object: the Engineering Intent Record and its six fields, its lifecycle, and worked examples.
→ Engineering Intent Record · Why Tradeoffs Matter · Record Lifecycle · Example Intent Records
3. Intent Capture
How Alloy elicits tacit engineering judgement instead of demanding blank-form entry: assistant-led interviews and codebase archaeology.
→ Elicitation Assistants · Codebase Archaeology · Archaeology Signals · Hypothesis Format
4. Ecosystem & Boundaries
How Alloy relates to the systems around it and what each owns.
→ Ownership Boundary · Alloy & Epilogue Tracker · Alloy & Foundry · Design Intent System
5. Runtime Artifacts
The compiled artifacts that form the stable seam between Alloy and Foundry.
→ Formation Brief · Formation Brief Sections · Formation Brief Lifecycle · Prompt Pack · Prompt Pack Compilation · Gate Overlay · Evidence Plan · Evidence & Gates · Foundry Execution Request · Foundry Run Result · Capability Manifest
6. Agent Formations
Choosing the social shape of agent work from the intent at stake.
7. Integration Architecture
The Phoenix/LiveView Alloy ↔ Rust Foundry boundary in depth.
→ Architectural Decision · Boundary Principles · System Roles · Runtime Topology · Integration Modes · Idempotency & Correlation · Security & Authority · Failure Handling · Observability & Audit · Versioning & Compatibility
8. Trace Feedback & Learning
Turning Foundry traces back into intent updates.
→ Learning Loop · Drift Detection · Contradiction Detection
9. Data Model
The PostgreSQL-backed entities behind the intent graph and the runtime.
→ Core Entities · Runtime Entities · Search & Retrieval
10. Interfaces
How humans and machines drive Alloy.
11. Workflows
The end-to-end journeys Alloy supports.
→ Capture from Conversation · Extract from Codebase · Implement Epilogue Interaction · Detect & Resolve Drift · Create Foundry Formation · End-to-End Flows
12. Delivery Plan
From MVP through the later roadmap and phased integration.
→ MVP · Roadmap · Phased Integration Plan · Specification Backlog · Immediate Next Steps
13. Reference
Requirements, risks, open questions, sources, and a glossary.
→ Functional Requirements · Non-Functional Requirements · Risks & Countermeasures · Open Questions · Source Grounding · Glossary
How to read this wiki
- Home → Section → Leaf. This page is the top layer. Each numbered link is a section overview. Each section overview summarizes and links to leaf pages that hold the detail.
- Wikilinks. Pages reference each other with
[[double-bracket]]links. Filenames are globally unique, so[[slug]]resolves regardless of folder. Follow them laterally to related ideas. - Provenance. Each leaf page notes which source document and section it was split from, so the original briefs remain traceable.
Source documents: Alloy Product Brief (Draft v0.2) and Alloy / Foundry Runtime Integration Architecture (Draft v0.1), Mojility / Stacey Vetzal, 2026-06-06.