agent-spec 1.2.0

Intent compiler for AI agent coding: human intent compiles through requirement IR into verifiable task contracts, mechanically verified against the code
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54

## Roadmap Specs

`specs/roadmap/` contains staged self-hosting task specs for future `agent-spec` work.

These files are real task contracts, but they are not part of the default top-level
`agent-spec guard --spec-dir specs --code .` run until they are promoted into
the top-level `specs/` directory.

Promotion rule:

- draft or future-phase contracts stay in `specs/roadmap/`
- active implementation contracts move to top-level `specs/`
- implemented contracts whose lifecycle passes are tagged `done` and moved out via
  `agent-spec archive --spec-dir specs/roadmap --run-log-dir .` (archived copies live in
  `.agent-spec/archive/specs/`, summary in `knowledge/context/spec-archives.md`)

Nested roadmap specs still inherit the top-level [`project.spec`](../project.spec.md).

## Current Status (triaged 2026-07-12)

20 legacy roadmap specs (across two triage passes) (phase0–6, plan-command, goal-gate, checkpoint-resume,
complexity-gate, human-review, optimize-scenario-mode, scenario-dependencies,
spec-dependency-graph, support-scenario-verification-metadata) verified passing
and were archived — the features shipped long ago.

Remaining staged contracts:

| Spec | State | Gap |
|------|-------|-----|
| `task-atlas-mir-layer.spec.md` | planned (Phase 2) | depends on Phase 1 |
| `task-atlas-kll-integration.spec.md` | planned (Phase 3) | depends on Phase 1 |
| `task-code-graph-ir-bindings.spec.md` | planned (boundary 2) | depends on atlas Phase 1 (done) |
| `task-quality-planning-bundles.spec.md` | planned (boundary 4) | depends on boundary 2 |

## Target-Architecture Delivery Boundaries

`docs/intent-compiler/architecture.md` stages the target intent-compiler
architecture as five contracts:

| Boundary | Contract |
|----------|----------|
| 1. Requirement governance gate + explicit transitions | `specs/task-requirement-governance-transitions.spec.md` (active) |
| 2. Provider-neutral Code Graph IR + typed code bindings | staged: `specs/roadmap/task-code-graph-ir-bindings.spec.md` |
| 3. Rust Atlas through the Intent-Code Linker | `specs/roadmap/task-atlas-kll-integration.spec.md` |
| 4. Quality Providers, profiles, Execution Bundles | staged: `specs/roadmap/task-quality-planning-bundles.spec.md` |
| 5. Aggregate status/evidence queries + full dogfood | first slice shipped: `specs/task-requirement-status-query.spec.md` (`requirements status <ID>`) |

Use:

```bash
agent-spec contract specs/roadmap/task-rust-atlas-code-graph.spec.md
```

when you want to inspect or refine a staged roadmap contract before promotion.