Change log and completion

Everything changed for the feedback brief : how to read the pink highlighting, the ten requirements and their sources, every page that was added or changed, the nine finance defects, and the flat completion matrix with a verdict for each acceptance check.

End-to-end scenarios Open decisions

How to read the highlighting Requirement register Page-by-page changes Finance defects FIN-01 to FIN-09 Completion matrix Remaining gaps

Reporting date

How to read the highlighting

Pink is used for one thing only: changed in this revision

A whole new page

A new page carries this banner under its heading and a pink line down its left edge. Nothing inside is outlined: everything on it is new. <body data-rev="new" data-req="REQ-007">

An existing page that changed

An updated page carries this banner and marks each changed part separately, in one of the three ways below. <body data-rev="upd" data-req="REQ-009 FIN-01">

A changed block: New, Updated or Corrected

Example. A panel, note or card that did not exist before is outlined and labelled New with its requirement.

Example. A block that existed and was modified is labelled Updated.

Example. A value or rule that was wrong or conflicting and is now corrected is labelled Corrected, in a darker tag.

<div class="panel" data-chg="new|upd|fix" data-req="FIN-01" data-note="…">

A changed table row and a corrected value

Record	Status	Amount
An unchanged row	As before
A row added in this revision	Tagged in its first cell
A row with one corrected value	The old value stays visible, struck through

<tr data-chg="new" data-req="REQ-004"> · <span data-chg="fix" data-req="FIN-02" data-was="EGP 150,000">. Hover any highlighted part for its note.

In the menu on the left

Finance 9

Company P&L New

Overview Upd

A solid New pill marks a page added in this revision, an outlined Upd pill a page that changed, and the number on a group counts its new or updated pages. The pills are driven by the same registry as the page list below.

The navigator, bottom right

▪ 4 changes on this page‹›

On every new or updated page a pink bar sits at the bottom right. It lists the changes on that page, jumps to each one (opening the right tab first) and steps to the previous or next with the arrows. This page has one too: it lists the examples above.

Requirement chips such as link to this page. Provisional chips such as link to the open decisions.

Requirement register and source traceability

Canonical IDs from the brief; they resolve conflicting source numbering

ID	Capability	Source reference	Scope treatment	Open decisions	Pages	Start at

Source: comments on Prototype.pdf, 39 pages. Original work-breakdown links remain references. CRM, LMS, scheduling, enrolment, certificates, marketing, support, analytics, documents, integration and AI already existed in the prototype and were extended, not recreated.

Page-by-page change list

The list is generated from the markers on the pages (data-rev, data-chg), so it shows what is marked, not what was intended. “Highlighted parts” counts marked blocks in the page source; parts rendered from scripts may add more when the page is open.

Finance defects recorded by the review

ID	What the review observed	Required verification	Treatment in the prototype	Where to verify, and what to look at	Pages

The amounts and numbers in the second column are the review’s observations of conflicting sample data. They are not authoritative balances. Where one value replaced several, the choice is a statement about the sample records and waits for confirmation by Finance under DEC-10.

Completion matrix

Demonstrated in prototypeis notProduction implemented or verified

Read the status column literally. “Demonstrated in prototype” means a reviewer can click through the acceptance check on sample data in this static prototype. “Partly demonstrated” means part of the check cannot be clicked through, and the row says which part. Nothing in this revision is implemented or verified in production: there is no database, no sign-in, no enforced authorization, no connected system and no AI model. A navigation entry alone is never counted as completion; each acceptance check names the page and what to do on it.

Requirement	Pages changed or added	Status	Acceptance evidence: page, what to do, what you see	Provisional assumptions	Remaining gaps

Page counts are computed from the change registry. Each acceptance check carries its own verdict; the status of a requirement follows from its checks and is “Demonstrated in prototype” only when every check is. Evidence and gaps were written after reading the source of the pages and evaluating the shared data modules; control names in bold are the labels on the pages, and figures are read from the shared data when this page loads.

Remaining gaps that apply to every requirement

Stated plainly