> :warning: **OpenSpec-managed issue** — this content is automatically synced > from the `openspec/` directory. Manual edits will be overwritten on next sync. ## Artifacts - :white_check_mark: [Metadata](https://github.com/ConductionNL/dossiq/blob/development/openspec/changes/beschikking-chain-on-the-case/.openspec.yaml) - :white_check_mark: [Proposal](https://github.com/ConductionNL/dossiq/blob/development/openspec/changes/beschikking-chain-on-the-case/proposal.md) - :white_check_mark: [Specs](https://github.com/ConductionNL/dossiq/blob/development/openspec/changes/beschikking-chain-on-the-case/specs/) - :black_square_button: Design - :white_check_mark: [Tasks](https://github.com/ConductionNL/dossiq/blob/development/openspec/changes/beschikking-chain-on-the-case/tasks.md) - :black_square_button: Plan - :black_square_button: Review ## Specs - [:page_facing_up: beschikking-generatie](https://github.com/ConductionNL/dossiq/blob/development/openspec/changes/beschikking-chain-on-the-case/specs/beschikking-generatie/spec.md) ## Tasks - [ ] 1.1 Draw the beschikking chain on `DqZaakBesluiten`: every beschikking in issue order with its - [ ] 2.1 Render the chain on the case page as the board shows it, reading the case's - [ ] 2.2 Wire the two actions to `POST /api/beschikkingen/{id}/successor` and show a refusal's - [ ] 2.3 e2e: a case with a beschikking and two corrections lists all three in issue order with --- *Synced from `openspec/changes/beschikking-chain-on-the-case` by OpenSpec workflow* *App: `dossiq`*
Activity