Task: Remove the last xsdcpp references
Table of Contents
This page documents a task in the Decide the XML strategy for ORE documents story. It captures the goal, current status, acceptance, and any notes or results.
1. Goal
No file outside the agile pages names xsdcpp or a script it used.
2. Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Decide the XML strategy for ORE documents |
| Now | Nothing. |
| Waiting on | Nothing. |
| Next | Nothing. |
| Last touched | 2026-10-21 |
3. Acceptance
- git grep -i xsdcpp finds only doc/agile
- The memory and the runbook describe how a money member keeps its digits today
4. Plan
Search the tree outside the agile pages for xsdcpp and for the scripts and
types it produced. Delete a page that only describes the old tool. Rewrite any
other mention to the current state.
(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.)
5. Measurements
Every number this task claims about a tree, with the command that produced it
and the commit it was measured at. A number without both is not a measurement,
because a clean-up record describes a tree and trunk moves under a branch: a
consumer count, a gate's component count and a suite's size all change with no
code changing, and the reader of a bare number cannot tell which tree it came
from. Where the raw output matters, put it in an evidence/ file beside the
task and name that file in the Command column.
| What | Value | Command | Commit |
|---|---|---|---|
Files outside doc/agile that name xsdcpp, before |
8 | git grep -il xsdcpp -- . ':!doc/agile' |
5f1675d6ac |
Files outside doc/agile that name xsdcpp, after |
0 | same | this branch |
6. Notes
- Deleted:
doc/analysis/ore_xsd_schema_gaps.mdanddoc/knowledge/architecture/ore_numeric_leaf_setters.txt. Both described the old tool only. - Rewritten to the current state: the memory on exact decimals, the runbook step that carries the digits, the section of the exact numbers page on the ORE boundary, three code comments, the evidence file header and one line of each of two plans.
- The agile pages keep their mentions. They are the record of the work.
7. Test Scenarios
Manual QA scenarios (scaffolded via compass add test_scenario)
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 |
|---|---|---|
8. PRs
| PR | Title |
|---|---|
| #3602 | [doc] Remove the last xsdcpp references |
9. Review
| Comment summary | File | Decision | Notes |
|---|---|---|---|
10. Result
No file outside doc/agile names xsdcpp or a script it used.