Disegno

---
disegno: 1
key: CHK
title: Checkout redesign
status: draft
projects: [SHOP]
---

# Overview            <!-- kind: overview -->
Prose …

# Requirements        <!-- kind: requirements -->

::: requirement {id=CHK-R1 priority=must status=accepted tags="payments"}
### Card payment
The checkout accepts a card payment in one step.

**Acceptance criteria**
1. [automated] A valid card completes in one request.
2. [manual] A declined card shows the issuer's reason.
:::

```mermaid title="Checkout flow"
flowchart LR
  Cart --> Pay --> Done
```

One file is a whole spec. CHK-R1 is a requirement a commit can cite, and CHK-R1.AC2 is its second acceptance criterion. Importing it creates the spec in one transaction, and exporting it gives the same file back.

Read

list_specs get_spec get_section list_requirements get_requirement get_diagram list_attachments read_attachment search_specs

Build

get_build_context get_trace set_requirement_status link_requirement unlink_requirement

Write

create_spec import_spec update_spec create_section update_section move_section create_requirement update_requirement create_diagram attach_file comment

Version

list_versions diff_versions cut_version restore_section

The hosted MCP server gives an agent what the web app gives a person. A build starts with get_build_context, which returns the pinned version, the requirements it traces to and their acceptance criteria.