DECISION
LAYER 03
RECORD / IMPLEMENTATION ARCHITECTURE
Choice and consent evidence
Design affirmative choices, receipts and withdrawal propagation as inspectable system events.
Engineering control
Engineering layer
not a legal conclusion
DEFAULT OWNER MODEL
Product owner with identity, platform and downstream-system owners
LEGAL / STATUS BOUNDARY
Consent provisions and the associated final Rules have phased commencement. This layer describes system patterns and must not be read as a provision map.
Open status console →SOURCE / STATUS BOUNDARY
Verify the legal status before implementation.
Engineering controlLayer verification pointers
These IDs are verification pointers to the primary-source ledger. They are not provision mappings, applicability findings or legal conclusions.
GOOD SYSTEM PATTERN
Build the path, then test the path.
Consent and withdrawal become versioned events with subject, purpose, notice version, timestamp, channel and downstream acknowledgements.
01Decision
02Owner
03System event
04Evidence
EVIDENCE THAT SHOULD EXIST
- Synthetic consent-event schema and approved production schema
- Notice version linked to each receipt
- Withdrawal propagation acknowledgement trail
- Retrieval and preference-path test results
HOW THIS LAYER FAILS
- A button click is stored without the notice or purpose context
- Withdrawal updates one interface but not downstream processing
- Bundled choices make the captured event ambiguous
ARCHITECTURE → EVIDENCE DECISION JOURNEY
Follow the dependency, then inspect the proof.
Each connection uses existing catalogue records. Source IDs remain verification pointers—not provision mappings.
Add to a review route- Layer pathwayChoice and consent evidence
- 01 · PrerequisiteNotice archive
Carry forward the reviewed evidence boundary from Notice and purpose.
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 - 02 · Implementation patternConsent event and withdrawal propagation
Treat consent and withdrawal as versioned events that downstream systems must acknowledge.
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023, dpdp-rules-2025, act-commencement-2025 - 03 · Validation / testTest CONSENT-01
Trace the sample from its trigger and owner through the implemented system to the retained evidence.
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 - 04 · Evidence artefactSynthetic consent-event schema and approved production schema
Primary retrievable output for record; inspect the full layer evidence set before drawing a conclusion.
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023, dpdp-rules-2025, act-commencement-2025 - 05 · Failure modeA button click is stored without the notice or purpose context
A visible failure case keeps a completion label from hiding an evidence gap.
Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023, dpdp-rules-2025, act-commencement-2025 - 06 · Research noteConsent Managers as infrastructure: interfaces, accountability and open questions
Interoperability, receipt semantics, revocation reliability and minimised identity binding deserve design attention before integration claims are made. Radar context: Structured consent receipts is Adopt.
Editorial analysis · reviewed 2026-08-30 · sources dpdp-rules-2025, rules-landing-2025 - 07 · Specialist propertyComparative analysis
Compare framework concepts without treating a comparison as legal advice. This route remains optional if the destination is unavailable.
Contextual external property · no affiliation or availability implied
- 01 · PrerequisiteNotice archive
Open semantic relationship table (1pathway)
| Record | Phase | Relationship | Status / boundary | Source pointers |
|---|---|---|---|---|
| Choice and consent evidence | 01 · Prerequisite | Notice archive Carry forward the reviewed evidence boundary from Notice and purpose. | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 | dpdp-act-2023 |
| Choice and consent evidence | 02 · Implementation pattern | Consent event and withdrawal propagation Treat consent and withdrawal as versioned events that downstream systems must acknowledge. | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023, dpdp-rules-2025, act-commencement-2025 | dpdp-act-2023 · dpdp-rules-2025 · act-commencement-2025 |
| Choice and consent evidence | 03 · Validation / test | Test CONSENT-01 Trace the sample from its trigger and owner through the implemented system to the retained evidence. | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023 | dpdp-act-2023 |
| Choice and consent evidence | 04 · Evidence artefact | Synthetic consent-event schema and approved production schema Primary retrievable output for record; inspect the full layer evidence set before drawing a conclusion. | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023, dpdp-rules-2025, act-commencement-2025 | dpdp-act-2023 · dpdp-rules-2025 · act-commencement-2025 |
| Choice and consent evidence | 05 · Failure mode | A button click is stored without the notice or purpose context A visible failure case keeps a completion label from hiding an evidence gap. | Engineering indicator · not a legal requirement · Verification pointers: dpdp-act-2023, dpdp-rules-2025, act-commencement-2025 | dpdp-act-2023 · dpdp-rules-2025 · act-commencement-2025 |
| Choice and consent evidence | 06 · Research note | Consent Managers as infrastructure: interfaces, accountability and open questions Interoperability, receipt semantics, revocation reliability and minimised identity binding deserve design attention before integration claims are made. Radar context: Structured consent receipts is Adopt. | Editorial analysis · reviewed 2026-08-30 · sources dpdp-rules-2025, rules-landing-2025 | dpdp-rules-2025 · rules-landing-2025 |
| Choice and consent evidence | 07 · Specialist property | Comparative analysis Compare framework concepts without treating a comparison as legal advice. This route remains optional if the destination is unavailable. | Contextual external property · no affiliation or availability implied | None · contextual external route |
LOCAL WORKSPACE NOTE
Give this work a next owner.
Nothing is sent anywhere. Avoid names, personal data or confidential incident details.