One capability at a time
Each page takes a single part of the platform and says exactly what it does and what it records.
A page in this section answers one question: what does this record, and what can be proved from it afterwards. The framing is the Act's rather than a product plan's. Sec. 8(1) makes the Data Fiduciary responsible for compliance irrespective of any agreement to the contrary and for processing carried out on its behalf, and Sec. 6(10) obliges it to prove, where a question arises in a proceeding, that a notice was given and that consent was given. A capability that cannot produce that artefact is an interface, not a control.
Consent receipts and the audit ledger is the first page here and the one the rest will refer back to. One decision produces one receipt — the purpose, the notice version and language shown, the timestamp, the identifier of the Data Principal — and each receipt carries the digest of the one before it, so altering an earlier record breaks every digest after it. That is the difference between a record you assert is accurate and a record whose accuracy can be checked by someone who does not trust you, which describes the Board precisely.
Where a capability is better understood as a place consent gets collected than as a part of the platform, it is in Solutions; where the question is how the pieces sit together, that is the architecture. The same questions, put to platforms built for another statute, are in the comparison.