No fictitious secrecy · v11.0.0-GL1 · 2026-07-24
Static Access-Control Limitations
Do not mistake a static gate for secrecy. GitHub Pages publishes static files. A technically capable person can inspect, copy or modify public client code. The gate meaningfully restricts ordinary use, verifies current direct ownership for cooperating users, creates signed evidence and supports contractual enforcement; it cannot make the repository confidential or make bypass impossible.
What the gate does well
- Provides a prestigious owner-only entrance and blocks normal interface use until verification.
- Rejects delegated and indirect control.
- Relocks on ownership, account, network and session changes.
- Creates a signed, versioned access receipt.
- Supports conditional licensing and evidentiary deterrence.
What it cannot guarantee
- Confidentiality of public HTML, JavaScript, datasets or legal pages.
- Server-authoritative authentication or revocation against modified copies.
- Prevention of screenshots, manual copying, reverse engineering or redistribution.
- Identity, accreditation, beneficial ownership, sanctions status, tax residence or authority beyond the verified wallet/name relationship.
- Regulatory immunity, legal compliance, professional advice or transaction readiness.
Appropriate use
This edition is suitable as a static research and decision-support institution for current direct AGI Club owners. Confidential datasets, private package delivery, regulated execution, sensitive personal data, payments, filings and high-impact actions require a separately authenticated, contracted and professionally reviewed environment.