Format: implementation plan / change proposal (eRegistrations)

Registered 2026-07-22, from Frank's line reviews of the Lesotho beneficial-owners plan and the capital-and-shares proposal.

The idea in one line: the SCREENS are the contract and the main content; the text is just their explanation. "Where we stand" shows the detailed screen of the current situation (BPA-faithful, rendered from a live pull); "the end situation" shows the result's screens, as many as necessary, with plain-English comments. The approved end-situation screens are the acceptance contract: done = the built service indistinguishable from them, checked by re-rendering reality side by side with the contract.

The carrier of the full method: the skill ~/.claude/skills/er-implementation-plan/SKILL.md (skeleton, mockup-contract method, style laws, verification gate). The living style law: memory feedback-er-implementation-plan-style.md. Doctrine entries: eR knowledge/patterns.md §"The faithful mockup is the build contract" and §"A derivable figure is not a field".

Exemplars: - Proposal: 2 - eR services/countries/Lesotho/services/register-a-business/capital-shares-proposal.html - Plan: 2 - eR services/countries/Lesotho/services/register-a-business/bo-implementation-plan.html - Real-look rendering pilot: …/register-a-business/specs/capital-shares-real-look.html

Visual grammar shared with the house: collapsed <details> sections, index chips, grey title qualifier, quiet grey gates and tags, OKLch tokens, token-audit 0. The two overlay chips (new · modified) are the only elements BPA itself does not have.

The final test closes the document (Frank, 2026-07-25). Section order: the analysis (where we stand, the end situation, what the change triggers, tensions, legal ground) → the phases → the final test → the technical block. The end-to-end run is not a phase: a phase is a piece of building checked before the next starts, while the end-to-end run happens once, when the build is whole, and proves the whole change. Per-phase tests stay in their phases.

Three layers, each fact in exactly one (Frank, 2026-07-25). The drawing shows WHERE, the logic annex says WHAT in one sentence per row, the technical block holds ids, dates and history. Never tell the same fact twice; an annex row that needs a paragraph is hiding a tail that belongs in the technical block.

Every element is a link (Frank, 2026-07-25). The document is a console: any named element (a certificate, a database, a bot, a screen, the labels) opens from the page in one click. The triggers table carries them first, then the drawing captions and their quiet "open in BPA" summary chips (titles carry no article: Current situation, End situation, Capital & shares tab). Verified BPA routes under https://<bpa-host>/services/<serviceId>: /forms/applicant-form · /print-documents/<documentId> · /print-documents · /bots/<botId> · /bots · /settings/databases · /formiotranslate · /roles/<roleId> · /registrations/<registrationId> · /determinantstable · /fieldstable · /messagestable; a GDB is https://<gdb-host>/database/<numericId>. Read from the BPA frontend's route table on 2026-07-25; never invent one, an unverified route becomes the nearest verified parent page. Reference implementation: the capital-and-shares plan.