Presence Protocol Source Pack

Source pack 0.1 — verified 2 August 2026
This pack supplements the Foundation Source Registry. It records current platform behavior, not permanent guarantees. Browser stores, tag platforms, and privacy requirements change and must be rechecked before each production release.

Source policy

Presence implementation decisions should prefer:

current official browser or platform documentation;
current store and distribution policies;
adopted web standards;
official framework documentation;
current qualified legal guidance where platform behavior intersects law.

A successful HTTP response is not enough. The linked source must support the exact claim.

Chrome extensions

`activeTab`

Publisher: Chrome for Developers
URL: The activeTab permission
State: Normative platform reference
Used for: Temporary page access after an explicit user gesture and the recommendation to avoid persistent broad access when not required.
Key behavior checked: Access is temporary for the active tab and is revoked when the user leaves the origin or closes the tab.
Checked: 2 August 2026

Declare permissions

Publisher: Chrome for Developers
URL: Declare permissions
State: Normative platform reference
Used for: Required, optional, host, and optional host permissions.
Design implication: Prefer optional permissions and request them in context.
Checked: 2 August 2026

Permission warning guidelines

Publisher: Chrome for Developers
URL: Permission warning guidelines
State: Normative platform guidance
Used for: Minimum relevant permissions, optional runtime requests, and use of activeTab.
Checked: 2 August 2026

Manifest V3 remote-hosted-code requirements

Publisher: Chrome Web Store / Chrome for Developers
URL: Additional Requirements for Manifest V3
State: Store-policy baseline
Used for: The rule that extension executable logic must be self-contained, while remote data and configuration may be fetched under stated limits.
Important limitation: Policies can change; recheck before every submission.
Checked: 2 August 2026

Chrome Web Store Program Policies

Publisher: Chrome Web Store
URL: Program Policies
State: Store-policy baseline
Used for: Quality, code readability, API use, spam, abuse, and technical requirements.
Checked: 2 August 2026

Minimum functionality

Publisher: Chrome Web Store
URL: Minimum Functionality
State: Store-policy baseline
Used for: Requirement that an extension provide real utility rather than merely launch a website.
Checked: 2 August 2026

Declarative Content API

Publisher: Chrome for Developers
URL: chrome.declarativeContent
State: Implementation reference
Used for: Showing or enabling an extension action based on page state with reduced content access.
Compatibility note: Exact behavior must be tested across browsers.
Checked: 2 August 2026

Mozilla WebExtensions

Content scripts

Publisher: MDN / Mozilla
URL: Content scripts
State: Normative browser reference
Used for: Content-script execution, host permissions, runtime injection, messaging, and restricted domains.
Checked: 2 August 2026

Permissions API

Publisher: MDN / Mozilla
URL: permissions API
State: Normative browser reference
Used for: Runtime optional permissions and browser-specific data-collection permissions.
Checked: 2 August 2026

Host permissions

Publisher: MDN / Mozilla
URL: host_permissions
State: Normative browser reference
Used for: Origin match patterns and privileges granted by host permissions.
Checked: 2 August 2026

Extension anatomy

Publisher: MDN / Mozilla
URL: Anatomy of a WebExtension
State: Implementation reference
Used for: Manifest, background scripts, content scripts, extension pages, and web-accessible resources.
Checked: 2 August 2026

Microsoft Edge

Port a Chrome extension to Edge

Publisher: Microsoft Learn
URL: Port a Chrome extension to Microsoft Edge
State: Normative platform reference
Used for: Chromium compatibility, store-specific testing, manifest differences, and publishing workflow.
Checked: 2 August 2026

Publish an Edge extension

Publisher: Microsoft Learn
URL: Publish a Microsoft Edge extension
State: Distribution reference
Used for: Partner Center packaging and publication requirements.
Checked: 2 August 2026

Safari

Safari web extensions

Publisher: Apple Developer
URL: Safari web extensions
State: Normative platform reference
Used for: Common JavaScript, HTML, CSS, and extension formats across Safari and other browsers.
Important limitation: Packaging, signing, testing, and App Store distribution remain Apple-specific.
Checked: 2 August 2026

WXT

WXT introduction

Publisher: WXT
URL: Welcome to WXT
License observed: MIT
State: Implementation candidate
Used for: Cross-browser extension framework selection.
Claim checked: WXT presents itself as a modern open-source framework with first-class major-browser support.
Checked: 2 August 2026

WXT manifest generation

Publisher: WXT
URL: Manifest
State: Implementation reference
Used for: Target-specific manifest generation from one source project.
Checked: 2 August 2026

Google Tag Manager

Custom templates

Publisher: Google for Developers
URL: Custom templates quick start
State: Normative platform reference
Used for: Sandboxed JavaScript, template fields, permissions, preview, export, and sharing.
Key claim checked: Google presents custom templates as a safer and more efficient alternative to Custom HTML and custom JavaScript variables.
Checked: 2 August 2026

Web custom-template permissions

Publisher: Google for Developers
URL: Custom template permissions
State: Normative platform reference
Used for: Permission-controlled access to URLs, global variables, storage, cookies, and the data layer.
Checked: 2 August 2026

Server-side custom-template permissions

Publisher: Google for Developers
URL: Server-side custom template permissions
State: Implementation reference
Used for: Future server-side adapter design and permission boundaries.
Checked: 2 August 2026

Community Template Gallery submission

Publisher: Google for Developers
URL: Submit a template to the Community Template Gallery
State: Distribution baseline
Used for: Required repository artifacts, GitHub submission, commit-SHA versioning, and update process.
Checked: 2 August 2026

Template style guide

Publisher: Google for Developers
URL: Template style guide
State: Distribution baseline
Used for: Template naming, field labels, descriptions, icons, and user-facing copy.
Checked: 2 August 2026

Community Template Gallery developer terms

Publisher: Google LLC
URL: Gallery Developer Terms of Service
State: Legal and distribution watch
Used for: Submission rights and obligations, Google distribution license, and Apache License 2.0 terms for users.
Important limitation: Terms must be reviewed again immediately before submission.
Checked: 2 August 2026

Publisher: Google for Developers
URL: Consent mode overview
State: Implementation reference
Used for: Basic and advanced consent modes and adjustment of tag behavior based on user choices.
Important limitation: Consent Mode is a technical mechanism for Google tags, not a universal legal-compliance determination.
Checked: 2 August 2026

Publisher: Google for Developers
URL: Set up consent mode on websites
State: Implementation reference
Used for: Default and update states, GTM consent-template APIs, and CMP integration.
Checked: 2 August 2026

NIST Privacy Framework

Publisher: U.S. National Institute of Standards and Technology
URL: NIST Privacy Framework
State: Privacy-risk baseline
Used for: Risk-based privacy governance beyond checkbox consent.
Checked: 2 August 2026

Web security and discovery

RFC 8615 — Well-Known URIs

Publisher: IETF / RFC Editor
URL: RFC 8615
Status: Standards Track, May 2019
State: Normative web reference
Used for: The /.well-known/ path convention.
Important limitation: A production ANUKA well-known name requires governance and potentially registry work before claiming standards-level recognition.
Checked: 2 August 2026

`window.postMessage()`

Publisher: MDN
URL: window.postMessage()
State: Normative web reference
Used for: Cross-context communication and mandatory sender-origin and message validation.
Checked: 2 August 2026

Subresource Integrity

Publisher: MDN
URL: Subresource Integrity
State: Normative web-security reference
Used for: Pinned third-party script integrity hashes.
Checked: 2 August 2026

Content Security Policy Level 3

Publisher: W3C
URL: Content Security Policy Level 3
Status observed: Working Draft / current technical report page
State: Web-security reference
Used for: Restricting script origins and mitigating injection risks.
Checked: 2 August 2026

Advertising and public claims

FTC Advertising Substantiation Policy

Publisher: U.S. Federal Trade Commission
URL: FTC Policy Statement Regarding Advertising Substantiation
State: Legal watch
Used for: Prior support for objective quality, growth, performance, and verification claims.
Checked: 2 August 2026

Release review checklist

Before publishing a browser extension or GTM template:

reopen all relevant store-policy links;
verify browser manifest and permission requirements;
compare shipped permissions with store copy and privacy notice;
confirm no remotely hosted executable extension logic;
test every supported browser separately;
validate GTM template permissions and Gallery artifacts;
validate consent behavior with a real CMP or test harness;
verify CDN, CSP, SRI, and rollback instructions;
verify public claims and screenshots against current behavior;
record release-specific dates and platform versions.

Known follow-up research

Chrome Web Store user-data and Limited Use policies;
Firefox Add-ons review and data-consent requirements;
Apple App Store and Safari-extension privacy disclosures;
Edge Add-ons certification policies;
state and international privacy requirements for extension and widget telemetry;
WCAG and platform accessibility requirements;
GTM server-side tagging and first-party data architecture;
browser-store automated publishing and signing;
well-known URI registration strategy;
extension supply-chain and update compromise controls.

Pack maintenance

Last manual validation: 2 August 2026
Next review: Before first public extension or GTM submission, and at least every 60 days during active development
Status: Founding implementation research