Build areas and feature traceability

Generated from the catalog. P0 is the foundation, P1 adds browser consent, P2 adds records and applicable regional/contract controls, P3 adds discovery/integrations, and P4 is deferred. Status is recorded per feature.

Features link to specific obligations and their planned verification scenarios. A shared mechanism can satisfy several requirements without duplicating its implementation.

P0 · FEAT-SETUP — Guided configuration and private justifications

Status: implemented.

Deliverables:

Shared versioned practice/coverage questionnaire for npx wizard and host-authorized admin UI.
Requirement-linked recommendations, unknowns/conflicts and private justifications; reviewable draft config exports with no automatic activation.
Local answer/report resume and imported inventory preservation; host-owned authorization and explicit private-note handling.
Explicit public purpose authoring in CLI/admin setup, guarded edits/removals and unresolved production-blocking facts.

Requirement links: REQ-PRODUCT-SETUP, REQ-PRODUCT-SCOPE-GUARDS, REQ-PRODUCT-CF-STARTER, REQ-PRODUCT-SERVICE-CATALOG, REQ-PRODUCT-SERVICE-DETECTION, REQ-PRODUCT-SERVICE-PROFILES.

Code references: packages/notabenda/src/setup.ts, packages/notabenda/src/setup-cli.ts, packages/notabenda/src/setup-ui.ts, packages/notabenda-cf/src/setup.ts, packages/notabenda/src/setup-purpose.ts, packages/notabenda/src/setup-purpose-ui.ts, packages/notabenda/src/setup-purpose-cli.ts, packages/notabenda/src/setup-catalog-cli.ts, packages/notabenda/src/cli-json.ts, packages/notabenda/src/catalog-node.ts

P0 · FEAT-INVENTORY — Site and processing inventory

Status: partial.

Deliverables:

Typed site, service, purpose, storage, retention, audience, and document configuration.
Separate public bundle facts from private operator metadata.
Completeness checks with requirement IDs and actionable missing-field messages.

Requirement links: REQ-EU-NOTICE, REQ-CH-PROFILING, REQ-QC-PROFILING, REQ-NZ-INDIRECT, REQ-TR-BASIS, REQ-EU-TERMS, REQ-PRODUCT-CONFIG, REQ-PRODUCT-EMBEDS, REQ-PRODUCT-PRIVACY-SIGNALS, REQ-PRODUCT-PROCESSING-CHOICES, REQ-PRODUCT-SCOPE-GUARDS, REQ-PRODUCT-SERVICE-CATALOG.

Code references: packages/notabenda/src/types.ts, packages/notabenda/src/config.ts, packages/notabenda/src/embeds.ts, packages/notabenda/src/privacy-signals.ts, packages/notabenda/src/scope-guards.ts, packages/notabenda/src/setup-purpose.ts, packages/notabenda/src/setup-purpose-ui.ts, packages/notabenda/src/setup-purpose-cli.ts

P0 · FEAT-DOCUMENTS — Privacy and cookie documents

Status: partial.

Deliverables:

Static privacy and cookie pages, semantic HTML, document links, service/storage tables, and legal-center composition.
Reviewed supplied content plus an original clause pipeline with explicit review and licensing status.
Versioned artifacts and material-change diffs; readable pages without JavaScript.

Requirement links: REQ-EU-NOTICE, REQ-CA-MEANINGFUL, REQ-AU-PIXELS, REQ-NZ-NOTICE, REQ-NZ-INDIRECT, REQ-US-CA-CHOICES, REQ-US-CO-GPC, REQ-PRODUCT-DOCUMENTS, REQ-PRODUCT-SAFE-CONTENT, REQ-PRODUCT-ARTIFACTS, REQ-PRODUCT-AUTHORING, REQ-PRODUCT-REACT, REQ-PRODUCT-ASTRO, REQ-PRODUCT-RETAINED-RELEASES, REQ-PRODUCT-COLLECTION-NOTICE, REQ-PRODUCT-RIGHTS-CENTER, REQ-PRODUCT-SERVICE-CATALOG, REQ-PRODUCT-INDIRECT-NOTICE, REQ-EU-GUARANTEE-NOTICE, REQ-EU-GUARANTEE-LABEL, REQ-PRODUCT-GUARANTEE-NOTICE.

P0 · FEAT-TERMS — Terms documents and acceptance

Status: partial.

Deliverables:

Static supplied terms first; narrowly scoped reviewed packs later.
Optional explicit terms-acceptance control linked to an exact version; independent marketing permissions.
Consumer/business and service-type configuration, with conditional rights and contract-action links.

Requirement links: REQ-EU-TERMS, REQ-EU-WITHDRAWAL, REQ-DE-CANCEL, REQ-DE-WITHDRAWAL, REQ-BR-CONTRACT, REQ-PRODUCT-DOCUMENTS, REQ-EU-ORDER-ACTION, REQ-PRODUCT-TERMS-ACCEPTANCE, REQ-PRODUCT-AUTHORING, REQ-EU-GUARANTEE-NOTICE, REQ-EU-GUARANTEE-LABEL, REQ-PRODUCT-GUARANTEE-NOTICE.

P0 · FEAT-DEPLOYMENT — Installable and restylable delivery

Status: partial.

Deliverables:

One frontend npm package with optional subpath exports and no runtime framework dependency.
Vanilla, React, static HTML, and Astro examples with fictional operators and data.
Optional Cloudflare deployment commands, same-origin configuration, and install/uninstall instructions.
Local notabenda-cf init starter and read-only doctor are implemented with host authorization boundaries and explicit generated Wrangler scripts. Remote provisioning and operational rollout verification remain separate.
Explicit headless entry, derived consent-only CSS and opt-in reproducible bundle-size reports; compatibility JavaScript size target remains open.

Requirement links: REQ-PRODUCT-A11Y, REQ-PRODUCT-MOBILE, REQ-PRODUCT-CONFIG, REQ-PRODUCT-SAFE-CONTENT, REQ-PRODUCT-PACKAGE, REQ-PRODUCT-CF-HOST, REQ-PRODUCT-AUTHORING, REQ-PRODUCT-REACT, REQ-PRODUCT-ASTRO, REQ-PRODUCT-RETAINED-RELEASES, REQ-PRODUCT-RIGHTS-CENTER, REQ-PRODUCT-CF-STARTER, REQ-PRODUCT-CF-DOCTOR, REQ-PRODUCT-SYNTAX-HIGHLIGHTING, REQ-PRODUCT-BUNDLE-BUDGET.

Code references: packages/notabenda/package.json, packages/notabenda/src/cli.ts, site/host.mjs, site/worker.mjs, site/build.mjs, packages/notabenda/src/react.ts, packages/notabenda/src/react-documents.ts, packages/notabenda/src/astro-client.ts, packages/notabenda/src/release-files.ts, packages/notabenda-cf/bin/notabenda-cf.mjs, packages/notabenda-cf/package.json, packages/notabenda-cf/templates/src/worker.mjs, packages/notabenda-cf/templates/src/host.mjs, packages/notabenda-cf/templates/src/workspace.mjs, packages/notabenda-cf/templates/src/authorize.mjs, packages/notabenda-cf/templates/src/setup.mjs, packages/notabenda-cf/templates/scripts/build-assets.mjs, packages/notabenda-cf/bin/doctor.mjs

P0 · FEAT-REQUIREMENTS — Source-linked requirements catalog

Status: partial.

Deliverables:

Versioned primary-source records, requirement IDs, applicability conditions, dates, caveats, and discovery articles.
Links from requirements to feature IDs, planned verification scenarios, and eventual code/test references.
Local validation and browseable indexes; legal review and implementation status tracked separately.

Requirement links: Product foundation; see deliverables and milestone acceptance criteria..

Code references: scripts/regulatory.py, regulatory/catalog.json

P1 · FEAT-SERVICE-CATALOG — Shared third-party catalog and passive recognition

Status: partial.

Deliverables:

Versioned provider/product schema, source-backed service facts, custom entries and operator-confirmed site use.
Shared public third-party rendering and pinned release provenance; large data stays outside normal consent bundles.
Explainable passive recognition using bounded exact/pattern/combined signals, compatible capture versions and reviewable configuration suggestions.
Reproducible licensed imports, broad service seeds, source freshness and positive/negative detector fixtures.
Initial optional reference seed: 363 provider identities, 402 product/reference entries, 2,278 imported storage hints and 39 original backend/provider references plus three browser-product references; all entries unreviewed.

Requirement links: REQ-PRODUCT-SERVICE-CATALOG, REQ-PRODUCT-SERVICE-DETECTION, REQ-PRODUCT-SERVICE-PROFILES.

P1 · FEAT-CONTROLS — Consent and preference widgets

Status: partial.

Deliverables:

Compact nonmodal bottom notice by default on mobile; clear permission request with balanced accept/reject/customize actions.
Preferences expand on deliberate tap into a bottom drawer; desktop may use a corner notice and side drawer. No automatic fullscreen dialog or initial page-blocking backdrop.
Accessible native markup, optional CSS, semantic theme tokens, light/dark and unstyled variants; optional drag gestures always have visible tap and keyboard equivalents.
Safe-area spacing, thumb-friendly controls, persistent reopening, focus restoration, and readable choices across small screens, zoom, large text, RTL, and the on-screen keyboard.

Requirement links: REQ-EU-CONSENT, REQ-EU-FAIR-CHOICE, REQ-ES-CHOICE, REQ-UK-EXCEPTIONS, REQ-BR-COOKIE-UI, REQ-US-CA-UI, REQ-PRODUCT-A11Y, REQ-PRODUCT-MOBILE, REQ-PRODUCT-REACT, REQ-PRODUCT-ASTRO, REQ-PRODUCT-EMBEDS, REQ-PRODUCT-PRIVACY-SIGNALS, REQ-PRODUCT-PROCESSING-CHOICES, REQ-PRODUCT-SCOPE-GUARDS, REQ-PRODUCT-BUNDLE-BUDGET, REQ-PRODUCT-STORAGE-EXCEPTIONS, REQ-PRODUCT-LOCALIZATION.

P1 · FEAT-ENFORCEMENT — Service gating and withdrawal

Status: partial.

Deliverables:

Declared service loaders and teardown hooks; inert scripts, images, and embeds until allowed.
Separate device-access permission from downstream processing restrictions.
Stop future work, remove accessible declared storage, and surface vendor/reload limitations after withdrawal.

Requirement links: REQ-EU-DEVICE, REQ-FR-SCOPE, REQ-DE-DEVICE, REQ-IE-DEVICE, REQ-UK-EXCEPTIONS, REQ-CA-OBA, REQ-QC-PROFILING, REQ-GOOGLE-MODE, REQ-PRODUCT-CONSENT-RUNTIME, REQ-PRODUCT-REACT, REQ-PRODUCT-ASTRO, REQ-PRODUCT-EMBEDS, REQ-PRODUCT-PRIVACY-SIGNALS, REQ-PRODUCT-PROCESSING-CHOICES, REQ-PRODUCT-STORAGE-CLEANUP, REQ-PRODUCT-SCOPE-GUARDS, REQ-PRODUCT-STORAGE-EXCEPTIONS.

P1 · FEAT-CHOICES — Preference lifetime and revisions

Status: partial.

Deliverables:

Purpose-level persisted choices, scope compatibility, expiry, and cross-tab updates.
Separate prompt suppression, grant expiry, evidence retention, and document versions.
Never convert dismissal, malformed state, missing storage, or stale scope into permission.

Requirement links: REQ-EU-CONSENT, REQ-EU-FAIR-CHOICE, REQ-FR-SCOPE, REQ-IT-REPROMPT, REQ-BR-COOKIE-UI, REQ-CA-MEANINGFUL, REQ-US-CT-GPC, REQ-PRODUCT-CONSENT-RUNTIME, REQ-PRODUCT-CONSENT-EVIDENCE, REQ-PRODUCT-REGIONAL-PROMPTS.

Code references: packages/notabenda/src/consent.ts, packages/notabenda/src/controls.ts, packages/notabenda/src/config.ts, packages/notabenda/src/prompt-policy.ts, packages/notabenda/src/consent-notice.ts, packages/notabenda/src/content.ts, packages/notabenda/src/consent-evidence.ts, packages/notabenda-cf/src/consent.ts, examples/repeat-prompts/build.mjs, examples/repeat-prompts/client.mjs

P1 · FEAT-LOCALIZATION — Versioned host-supplied localization

Status: partial.

Deliverables:

Complete versioned host-supplied messages for legal documents and consent controls, including status/accessibility text, selected language and explicit direction.
Archived selected consent copy, independent presentation/disclosure revisions, exact material scopes and frontend/backend validation parity.
Supplied structured or Markdown/MDX documents and optional complete generated-document templates. No automatic translation, language negotiation or inferred jurisdiction.
Remaining interface localization, broader plural rules, reviewed locale catalogs and multi-language routing are still open.

Requirement links: REQ-PRODUCT-LOCALIZATION.

P2 · FEAT-FORMS — Collection notices and form permissions

Status: partial.

Deliverables:

Inline collection notice, optional permission field/group, notice link, and explicit terms action.
Purpose/channel-specific choices and versioned form text; no forced privacy-policy acceptance checkbox.
Trusted application API for consent and withdrawal records; no email-sending platform.
Separate reviewed indirect-collection particulars in static HTML and plain text, with explicit phase and no delivery claim.

Requirement links: REQ-EU-NOTICE, REQ-EU-CONSENT, REQ-CA-MEANINGFUL, REQ-AU-PIXELS, REQ-NZ-NOTICE, REQ-ZA-MARKETING, REQ-US-VA-RIGHTS, REQ-TR-BASIS, REQ-PRODUCT-TERMS-ACCEPTANCE, REQ-PRODUCT-COLLECTION-NOTICE, REQ-PRODUCT-FORM-PERMISSIONS, REQ-EU-MARKETING, REQ-CA-CASL-OPTIN, REQ-PRODUCT-INDIRECT-NOTICE.

P2 · FEAT-RECORDS — Durable evidence with notabenda-cf

Status: partial.

Deliverables:

Transactional Durable Object records, artifact registration, anonymous receipts, and authenticated subject events; alternative storage adapters later.
Export, controlled erasure, retention cleanup, access controls, and evidence provenance.
Separate browser-reported actions from trusted application events; configurable transport for existing backends.

Requirement links: REQ-EU-CONSENT, REQ-ZA-MARKETING, REQ-EU-WITHDRAWAL, REQ-DE-CANCEL, REQ-PRODUCT-ARTIFACTS, REQ-PRODUCT-CF-HISTORY, REQ-PRODUCT-TERMS-ACCEPTANCE, REQ-PRODUCT-CONSENT-EVIDENCE, REQ-PRODUCT-PROCESSING-CHOICES, REQ-PRODUCT-EVIDENCE-EXPORT, REQ-PRODUCT-EVIDENCE-LIFECYCLE, REQ-EU-RETENTION-ERASURE, REQ-PRODUCT-FORM-PERMISSIONS, REQ-PRODUCT-CONTRACT-ACTIONS, REQ-PRODUCT-PAID-ORDER-ARCHIVES, REQ-PRODUCT-ORDER-CONFIRMATION.

P2 · FEAT-REGIONS — Regional requirement profiles

Status: partial.

Deliverables:

Explicit applicability facts and versioned rule packs; conservative fallback when applicability is unknown.
Explain effective behavior using requirement IDs, sources, and active pack versions.
Conditional exemptions and purpose-specific restrictions; no inference of applicability from IP geography alone.
Optional declared UK statistical/appearance objection profiles, separate from consent, with atomic browser preferences and revision-bound resume; qualification remains host review.

Requirement links: REQ-EU-DEVICE, REQ-FR-SCOPE, REQ-DE-DEVICE, REQ-IT-REPROMPT, REQ-ES-CHOICE, REQ-IE-DEVICE, REQ-UK-EXCEPTIONS, REQ-CH-PROFILING, REQ-BR-COOKIE-UI, REQ-CA-OBA, REQ-QC-PROFILING, REQ-US-CA-GPC, REQ-US-CO-GPC, REQ-US-CT-GPC, REQ-US-COPPA-SCOPE, REQ-TR-BASIS, REQ-PRODUCT-REGIONAL-PROMPTS, REQ-EU-MARKETING, REQ-CA-CASL-OPTIN, REQ-PRODUCT-STORAGE-EXCEPTIONS.

P2 · FEAT-US-CHOICES — US privacy choices and signals

Status: partial.

Deliverables:

Sale/sharing/targeted-advertising controls, applicable GPC handling, and signal-status messaging.
Notice-at-collection entry points and relevant sensitive-data restrictions.
Server-readable restrictions and adapters to stop corresponding downstream processing.

Requirement links: REQ-US-CA-CHOICES, REQ-US-CA-GPC, REQ-US-CA-UI, REQ-US-CO-GPC, REQ-US-CT-GPC, REQ-PRODUCT-PRIVACY-SIGNALS, REQ-PRODUCT-PROCESSING-CHOICES.

Code references: packages/notabenda/src/privacy-signals.ts, packages/notabenda/src/processing-choices.ts, packages/notabenda-cf/src/processing.ts

P2 · FEAT-RIGHTS — Rights entry points and application bridge

Status: partial.

Deliverables:

Configurable rights/contact page and links for access, correction, erasure, withdrawal, and applicable appeals.
Authenticated hooks to an operator's workflow; receipt exports do not pretend to export all application data.
Document verified identity and response handling as operator/application responsibilities.
Initial static core/React/Astro entry points and public contact fallback are implemented; intake, identity, request/response workflow and fulfillment remain host work.

Requirement links: REQ-EU-NOTICE, REQ-NZ-INDIRECT, REQ-ZA-MARKETING, REQ-US-CA-CHOICES, REQ-US-VA-RIGHTS, REQ-PRODUCT-RIGHTS-CENTER.

Code references: packages/notabenda/src/rights-policy.ts, packages/notabenda/src/rights.ts, packages/notabenda/src/config.ts, packages/notabenda/src/content.ts, packages/notabenda/src/documents.ts, packages/notabenda/src/react-documents.ts, packages/notabenda/src/astro/RightsCenter.astro, packages/notabenda/src/styles.css, packages/notabenda-authoring/src/index.ts, examples/rights/build.mjs

P2 · FEAT-CONTRACT-ACTIONS — Contract withdrawal and cancellation widgets

Status: partial.

Deliverables:

Separate contract-withdrawal and qualifying subscription-cancellation flows, with applicable labels and required fields.
Review step, durable confirmation output, and application-backend handoff; privacy choices stay independent. Use mobile drawers/pages with readable forms, not unsolicited fullscreen prompts.
Optional notabenda-cf record/dispatch support; no success message until handoff is durably accepted; no automatic refunds or subscription mutation.
Native/headless forms, atomic declaration/outbox APIs, isolated examples, private inspection/search and independent bounded host callback runners are implemented and locally verified, including SQLite dispatch lease restart/deduplication with simulated providers. Actual host scheduling/providers, regional review and operational acceptance remain open.

Requirement links: REQ-EU-WITHDRAWAL, REQ-DE-CANCEL, REQ-DE-WITHDRAWAL, REQ-BR-CONTRACT, REQ-EU-ORDER-ACTION, REQ-PRODUCT-CONTRACT-ACTIONS.

P2 · FEAT-SCOPE-GUARDS — Sensitive and child-related scope guards

Status: partial.

Deliverables:

Explicit sensitive-data, children, profiling, and regulated-sector flags in configuration.
Prevent unsupported scenarios from being described as covered; block optional high-risk integrations by default.
Specialized age assurance and verifiable parental consent remain deferred until separately designed and reviewed.
Initial explicit operator scope declarations and optional-runtime guards; specialized authorization and sector workflows remain unsupported.

Requirement links: REQ-CH-PROFILING, REQ-CA-OBA, REQ-AU-PIXELS, REQ-US-VA-RIGHTS, REQ-US-COPPA-SCOPE, REQ-PRODUCT-SCOPE-GUARDS.

P2 · FEAT-BACKOFFICE — Host-authorized evidence backoffice

Status: partial.

Deliverables:

Pluggable read-only worker with mandatory host authorization and host-selected store scope.
Bounded search, evidence cards, readable details, filters, and raw JSON disclosure.
Durable Object adapter; no login, credentials, arbitrary DO selectors, or consent collection.

Requirement links: REQ-PRODUCT-CF-ADMIN, REQ-PRODUCT-TERMS-ACCEPTANCE, REQ-PRODUCT-CF-HOST, REQ-PRODUCT-CONSENT-EVIDENCE, REQ-PRODUCT-EVIDENCE-EXPORT, REQ-PRODUCT-EVIDENCE-LIFECYCLE, REQ-EU-RETENTION-ERASURE, REQ-PRODUCT-DEMO-WORKSPACE, REQ-PRODUCT-CF-STARTER, REQ-PRODUCT-CONTRACT-ACTIONS, REQ-PRODUCT-PAID-ORDER-ARCHIVES, REQ-PRODUCT-ORDER-CONFIRMATION.

P2 · FEAT-DOCUMENT-HISTORY — Immutable document history and reviewable differences

Status: implemented.

Deliverables:

Explicit transactional release archival with exact content, version metadata, operator change note, and idempotent retries.
Backoffice release history and safe side-by-side structured comparisons.
Separate content and rendered-HTML digests; no automatic publication, notification, consent invalidation, or terms acceptance.

Requirement links: REQ-PRODUCT-CF-HISTORY, REQ-PRODUCT-AUTHORING, REQ-PRODUCT-RETAINED-RELEASES.

Code references: packages/notabenda-cf/src/history.ts, packages/notabenda-cf/src/render.ts, packages/notabenda/src/content.ts, packages/notabenda/src/release-files.ts

P2 · FEAT-PAID-ORDERS — Paid order information and deliberate payment action

Status: partial.

Deliverables:

Reviewed item and commitment definitions bound to host-calculated quotes, exact money, total/due-now prices, recurring and conditional charges, and product-specific guarantee labels.
Static vanilla/React/Astro information and a native/headless final action with uncertainty recovery. No implicit terms agreement, payment execution or durable contract confirmation.
Reusable Cloudflare chunked review/original-file archives, CAS quote activation, one admission per checkout intent with atomic host mutation plans, recovery, scoped admin inspection and retirement are implemented and used by the isolated demo. External payment/stock-system acceptance, actual confirmation provision and legal/national review remain open; optional complete-file archival and host delivery mechanics are tracked separately in FEAT-ORDER-CONFIRMATION.

Requirement links: REQ-EU-ORDER-ACTION, REQ-PRODUCT-PAID-ORDER-ARCHIVES, REQ-EU-ORDER-CONFIRMATION.

P2 · FEAT-ORDER-CONFIRMATION — Customer confirmation archives and host delivery

Status: partial.

Deliverables:

Immutable personally addressed plain-text confirmation and optional exact attachments, linked to the admitted review, actual host contract facts and fixed destination version.
Atomic preparation/outbox, bounded host callback attempts, recoverable uncertainty and stable provider idempotency; no built-in email provider, scheduler or contract-formation decision.
Separately authorized admin inspection and inert downloads; pending-job retirement guards and resumable scoped purge.
Complete content, real channel/destination behavior, actual provision, timing and national/linguistic acceptance remain host review work.

Requirement links: REQ-EU-ORDER-CONFIRMATION, REQ-PRODUCT-ORDER-CONFIRMATION.

Code references: packages/notabenda-cf/src/order-confirmations.ts, packages/notabenda-cf/src/order-confirmation-state.ts, packages/notabenda-cf/src/order-confirmation-dispatch.ts, packages/notabenda-cf/src/order-confirmation-render.ts, packages/notabenda-cf/src/orders.ts, packages/notabenda-cf/src/lifecycle.ts, packages/notabenda-cf/src/worker.ts, packages/notabenda-cf/src/types.ts, site/order-confirmation-seed.mjs, site/order-demo-admin.mjs

P3 · FEAT-DISCOVERY — Standalone discovery tooling

Status: partial.

Deliverables:

Browser-assisted inventory of observed requests, cookies/storage, embeds, and resource hints.
Human-readable and JSON findings with route, scenario, evidence, and candidate purpose/service mappings.
Adopters choose when to run it, whether to use CI, and which findings should block their deployments.

Requirement links: REQ-AU-PIXELS, REQ-PRODUCT-DISCOVERY, REQ-PRODUCT-SERVICE-DETECTION.

Code references: packages/notabenda/src/discovery.ts, packages/notabenda/src/discovery-ui.ts, packages/notabenda/src/discovery-cli.ts, examples/discovery/build.mjs, examples/discovery/client.mjs

P3 · FEAT-GOOGLE — Google Basic Consent Mode

Status: partial.

Deliverables:

Optional adapter setting defaults before tags and explicitly mapping all four relevant consent signals.
Basic mode tag gating and purpose mapping diagnostics.
Test fixtures demonstrating no Google requests before consent or after rejection.

Requirement links: REQ-GOOGLE-MODE.

Code references: packages/notabenda/src/google-basic.ts, packages/notabenda/src/google-basic-policy.ts, packages/notabenda/src/config.ts, packages/notabenda/src/types.ts, examples/google-basic/build.mjs, examples/google-basic/client.mjs

P4 · FEAT-AD-CMP — Certified advertising CMP path

Status: planned.

Deliverables:

Investigate current IAB TCF registration, vendor signaling, and Google certification as a separate project.
No invented CMP identity or claim that Consent Mode implies certification.
Defer shipping TCF until specification, certification, and ongoing maintenance are actually satisfied.

Requirement links: REQ-GOOGLE-CMP.

Code references: None yet.