# What is built

| Feature | Status |
|---|---|
| `jadpo calls`, `calls show` and `calls script` | Built. |
| Each step a request's action reached, as a trace line in `jadpo dev` | Built: each step is a line under its request's line in `jadpo dev`, and a delivery whose action reached steps gets a line of its own. |
| `jadpo why <schedule>` | Built: it answers why a schedule didn't run ([Watching schedules](/docs/what-an-operator-sees.md#watching-schedules)). |
| `jadpo approval` | Partly built: the report in `build/review/` in [this page's order](/docs/reviewing-a-change.md), the before side built from git and its manifest kept in `build/before/<commit>/`, and the personal-data report's difference, a connection at a time. Not built yet: the rest of that difference, which comes with the rest of that report, and a package's service and a bot check, which come with those features. |
| Mapped `.jadpo` stacks, `jadpo incident`, the other forms of `why`, timelines and `jadpo trace`, `test new --from` and `call` | Not built yet. |
| `jadpo dev grants add` | Not built yet. |
| The developer console, MCP (`jadpo mcp`) and the review web view | Not built yet: they come after those, as product work. |
| `jadpo traces`, `metrics`, `logs` and `watch`; path coverage, production counts in review, `jadpo replay` and query cost | Not built yet. |