Skip to content

Product Goals

Alloy should:

  1. Capture engineering intent in a structured model that can be queried, versioned, validated, and compiled into runtime guidance.
  2. Help developers express tacit engineering knowledge through assistant-led elicitation rather than blank-form entry.
  3. Extract likely engineering intent from existing codebases as hypotheses, then let humans confirm, reject, or refine those hypotheses.
  4. Compile relevant product, design, and engineering intent into Foundry formation briefs.
  5. Generate prompt packs tailored to Foundry phases such as assessment, triage, planning, execution, retry, and summarization.
  6. Generate or select evidence requirements and gates that prove whether the engineering intent is satisfied.
  7. Feed Foundry trace outcomes back into the intent model.
  8. Keep Foundry's event and task-block runtime clean by moving situational policy into Alloy.
  9. Preserve Epilogue Tracker's product focus by keeping technical guidance out of the backlog while still making it available to tools.

Related: Vision · Non-Goals · Target Users and Jobs · Problem Statement

Source: Product Brief §7 (Product Goals).

Alloy owns meaning. Foundry owns execution.