On 28-09-2026 Frank reshaped the eA 2.0 short specifications page by page, and received Nelson Pérez’s skill on writing register. He then asked, about the Lesotho recovery plan written the same day:
frame.md in the eA 2.0 folder. No skill carries them, and analysis-doc still describes their first form, with “It is possible to:” in place of Functions.frame.md for the short specifications only.Each change Frank made on 28-09-2026, and what it means for the plan to rebuild the Lesotho recovery service.
| Change of 28-09-2026 | For the plan | Why |
|---|---|---|
| The footer says “Updated · date · time”, never “Draft” | applies | It reads “Draft · 28-09-2026 · 11:36 · for Frank’s go”; the call for his go already sits in Decisions. |
| The stamp is set at each publish, by a script | applies | The plan will be republished at each step; a hand-written time goes stale, as the short specifications’ did until today. |
| A Fold all switch beside the title | applies | Five long sections; the reader folds them one by one today. |
| Direct functional register, no opening that announces size (Nelson’s skill) | applies | Two tiles give a count as their answer, “Six steps, each proven” and “Four questions”; they should name the steps and the questions. The closing “In short:” repeats section 1. |
| Every section and every subsection folds | already | All five sections fold, open by default. |
| Section titles in red; groups inside them in blue, folding | already | Same template; the plan has no groups inside its sections. |
| No text outside a section | already | Only the opening, the tiles and the chips stand above the sections, as the form wants. |
| The back link names where it leads | already | It names the test review it came from. |
| A table repeats no column | already | Its tables carry distinct columns. |
| “Definition and examples” opens, folding | specifications only | An analysis opens on its answers, which stay in view. |
| “Functions” as the list’s title; every feature specified, the phases decide when | specifications only | The plan lists steps, not a product’s functions. |
| A named page, panel or part is defined where it first appears | specifications only | The plan names BPA elements its readers, Frank and Dariusz, already know. |
| Modules numbered and grouped by who uses them | specifications only | The plan’s steps are a sequence, already numbered. |
| “Current users”, not a count of users | specifications only | No user count in the plan. |
The rules that held for both documents today belong to every page the sessions write, whatever its kind. A base skill would hold them once, with the scripts that apply them; analysis-doc, a new short-spec skill, topic-index and progress-page would point to it and keep only what is theirs.
frame.md: definition and examples, Functions in groups, Rules, Related documents, Decisions, the level of about 450 words. The line in analysis-doc that describes the old form goes.Effort: Agent: about 1 session (estimate) for the base skill, the short-spec skill and the edits to the four skills · People: none.
Sources