Task: File Wt and HTTP backlog captures for business_centre
Table of Contents
This page documents a task in the Commission: business_centre story. It captures the goal, current status, acceptance, and any notes or results.
Goal
business_centre's Wt and HTTP gaps are tracked in the backlog so the top-level commissioning stories pick them up.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Commission: business_centre |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-07-12 |
Acceptance
- One capture filed for Wt support, one for HTTP support, each linked back to this story.
Plan
(Implementation strategy. Written when work starts; key decisions
are distilled into the parent story's * Decisions at close, but the
plan itself stays — it is the historical record of what we did.)
Notes
Test Scenarios
Manual QA scenarios (scaffolded via compass add test_scenario, run
through the QA Validation Runner panel) that verify this task. Link
new ones here as they're created; the scenario doc itself links back
via its "Verifies task" field.
| Scenario | State | Notes |
|---|---|---|
PRs
| PR | Title |
|---|---|
| #1582 | [agile] File Wt/HTTP backlog captures, close business_centre story |
Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|
Result
Filed two backlog captures in the inbox: Wt web UI support for business_centre and HTTP REST endpoints for business_centre, both linked back to this story and to the Entity commissioning process reference's gap protocol. Also checked chapter_6b_business_centres.org against the latest business_centre.org/business_unit.org/currency knowledge docs (post PR #1580) — no stale terminology or contradictions found; the chapter's Wt/HTTP callout in the Conclusion already points at exactly this backlog work.