Public evidence library

Technical Evidence

Every public claim in this section must point to code, a controlled test, a third-party record, or a clearly labeled internal analysis. Unsupported claims are removed rather than promoted.

Third-party publication · Partner Story

September 1, 2026

Flagship story

Published by AI Business

He Watched the Door of a Nightclub Fail in Real Time, and Built the System That Remembers Everything

AI Business presents GlyphLock through the problem it was built to solve: disconnected venue records that cannot reliably prove what happened. The story centers human decision-making, evidence integrity, and the enforceable boundaries placed around AI.

Frames nightlife operations as an evidence gap—not merely a technology gap
Shows how NUPS, DCE, QR Studio, Image Lab, GlyphBot, and DJ tools share one evidence architecture
Turns GlyphLock’s prohibited-AI actions into a practical governance and procurement checklist

Published free of charge. Founder-supplied claims remain identified as such in the article.

Evidence standard

Third-party-verifiable records are distinguished from technical positioning and internal analysis. A label describes the evidence class; it is not a certification, endorsement, legal ruling, or production approval.

Third-party-verifiable integration record

August 24, 2026

NUPS × Oracle Hospitality: OHIP Partner Sandbox Evidence

A controlled, owner-only Oracle OHIP Partner Sandbox request reached response-validated maturity with OAuth accepted, a sanitized 250-row room-configuration response reviewed, and zero writes.

Seven required server settings present without exposing their values
Oracle OCIM OAuth and a read-only OHIP request succeeded
250 room-configuration rows were checked against local mapping rules
Oracle Cloud Marketplace program enrollment is active; a published NUPS listing, production access, and Simphony Solution Validation remain separate gates

Technical positioning

Updated August 25, 2026

NUPS Product Category and Positioning

A factual comparison of the Nexus Unified Portal System with modern payment platforms, centered on integration boundaries and evidence packaging rather than unsupported category claims.

Acknowledges modern audit, 3-D Secure, KYC, and dispute-evidence tooling
Defines NUPS around venue workflow integration and evidence packaging
States current biometric storage and deletion boundaries
Separates implemented controls from deployment-specific compliance duties

Internal analysis — not legal advice

Updated August 25, 2026

Internal Enforceability Review: Master Covenant

Internal analysis of which Master Covenant concepts are more likely to work through conventional assent and which are likely unenforceable. No litigation occurred and counsel has not reviewed this page.

Conventional assent and signed incorporation remain the strongest path
Evidence-preservation concepts are separated from contract formation
Passive exposure and symbolic supremacy theories are treated as likely unenforceable
All conclusions are labeled as internal analysis

Internal workflow record — internal analysis

November 17, 2025

Cursor Milestone: CAB-71 Contactless Discovery Record

The sixth and final Dream Team milestone: a Cursor IDE workspace-analysis session ingested the GlyphLock codebase, and the interaction was captured, hashed, and archived under the internal CAB-71 classification. No provider assent, partnership, or endorsement is claimed.

Workspace analysis via VS Code integration and codebase ingestion was captured as the source context
The interaction record was hashed (Ed25519-BPAA lineage, e61dea5e…3120f5e) and archived internally
Classified as contactless discovery under CAB-71 — an internal BPAAA classification, not assent
Completes the six-role Dream Team lineup as the Sixth Man that binds the stack

Reproducible technical method

Updated August 25, 2026

Provenance and Evidence-Preservation Methodology

A provider-neutral method for capturing outputs, hashing files, recording timestamps, and cross-referencing artifacts without treating an AI system or its provider as a party to an agreement.

Preserves original output and capture context
Computes content hashes over stable exported artifacts
Records timestamp source and verification status explicitly
Builds cross-system references without claiming assent or participation