Rights and provenance · sanitised evidence

Evidence that can be public without publishing the archive.

This Gate A evidence layer publishes concise, machine-readable summaries that can be reconciled against the public package and rights records. It deliberately excludes raw private assets, credentials, private correspondence, claimant personal data, confidential agreements, unrestricted local file paths and unredacted internal notes.

Package
101-file exact package verified live

The annex records the package boundary, robots/sitemap discovery metadata and excluded categories. Live hosting and HTTP verification completed on 19 August 2026.

Visual use
0 forward · 48 flags · 5 AP

The visual-use annex mirrors the published public-use record, including exact public-safe AP identities and flag mappings.

Rights contact
Send and receive verified

The contact-verification annex records the 31 July 2026 operational test without publishing private mailbox identifiers or message bodies.

Machine-readable annexes

Four bounded public evidence files.

These annexes are derived from already prepared records and public-safe source evidence. They provide reviewable data, not a new permission claim.

JSON · package

Gate A package summary

Expected exact file count, forward identity, discovery metadata, third-party visual totals, excluded categories and live-deployment state.

Open JSON →
JSON · actual use

Gate A visual-use annex

Zero forward-site visual entries, all 48 flag mappings, flag-icons source/licence metadata and the five bounded AP image identities/checksums.

Open JSON →
JSON · provenance

PL/FPL provenance summary

The 59-asset family counts, historical repository exposure, recovered badge-source chain, evidence classes, central licence finding and current zero-use Gate A state.

Open JSON →
JSON · contact

Rights-contact verification

Records the dedicated address and the successful controlled send/receive test while withholding private message identifiers and the owner verification mailbox.

Open JSON →

Evidence limits

Public evidence is intentionally incomplete by design.

A public evidence annex can show identities, counts, hashes, source metadata, version relationships, mailbox-operation facts and package state. It does not disclose raw private evidence merely to demonstrate transparency.

01 · Included

Public-safe facts.

Public paths, asset IDs, checksums, dimensions, source/licence notices, record versions, contact verification and prepared package boundaries.

02 · Excluded

Private or sensitive material.

Raw archive bytes, credentials, private correspondence, mailbox message identifiers, claimant data, confidential agreements and unredacted internal notes remain outside the public package.

03 · Status

Gate A verified.

Deployment, exact-byte verification, negative-route checks, responsive browser audit and owner acceptance all completed on 19 August 2026. Gate B remains separate.

Transparency does not itself create permission. These evidence annexes support traceability and review; they do not convert provenance, attribution, contactability or public availability into a licence.