theCwindLab

patrick.schur@theCwind.com http://www.theCwind.com

This document registers the "⚮" (U+26AE, DIVORCE SYMBOL) Uniform Resource Identifier (URI) scheme for the Biometric-First Communication Protocol (BCCCOP). The scheme enables privacy-first, biometric-anchored addressing of resources and invocation of peer-to-peer operations across ultrasonic, BLE, and Wi-Fi transports. This document follows the URI scheme registration guidelines of RFC 7595.

Introduction The Biometric-First Communication Protocol (BCCCOP) is a privacy-first, zero-trust protocol for peer-to-peer data exchange. It operates across three physical rails: a personal application rail (BPa), an ambient sensor rail (BPb), and a cross-device projection rail (BPc). All resources in BCCCOP are addressed through "closed atoms" — identifiers delimited by the Unicode character U+26AE (⚮). These atoms form the basis of a novel URI scheme that this document registers per the procedures defined in . The scheme character U+26AE (⚮) was selected for its visual distinctiveness, its availability in the Unicode Basic Multilingual Plane, and its conceptual resonance with the protocol's separation-of-concerns architecture: each ⚮-delimited atom represents a sovereign, independently addressable resource.

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

URI Scheme Syntax The ⚮ URI scheme supports two formats, both of which normalize to a common canonical Abstract Syntax Tree (AST).

Format A — Hierarchical Addressing Format A addresses a resource by stewardness path:

Format B — Command Invocation Format B invokes an operation through a cross-device Trojan window:

ABNF Grammar The complete ABNF grammar for the ⚮ URI scheme, per , is: All ABNF productions use the Core Rules from . The scheme delimiter is the single Unicode character U+26AE (⚮), UTF-8 encoded as 0xE2 0x9A 0xAE on the wire. When used in URIs, ⚮ MUST be percent-encoded as %E2%9A%AE per when appearing outside the scheme position.

Scheme Semantics The ⚮ URI scheme operates within the BCCCOP protocol stack. URIs resolve to one of 261 Atomic Type Inventory (ATI) elements across 38 families, classified into three tiers:

TIER_0 (System-only):

Biometric, Trojan, Gibber-Link, Break-Glass, Consent, Witness. These atoms cannot be authored from the no-code user interface. Emission requires biometric re-authentication and generates an audit frame.

TIER_1 (User flows):

Action, Resource, Sharing, Topology. These atoms form the standard user-facing command surface.

TIER_2 (Shell):

Tag, Hash, Unit, Country, Language. Top-level navigation and internationalization atoms.

The canonical ATI catalog (261 atoms, 38 families) is published at and carries a BLAKE3 content hash pinned in the screen manifest.

Encoding and Transport BCCCOP URIs are transmitted over three physical carriers, selected by the atom's tier classification:

• Ultrasonic (Gibber-Link™): 4-FSK modulation at 18.0/19.0/20.0/21.0 kHz, 100 symbols/s, 200 bps. Used for zero-trust device pairing and TIER_0 pre-verification handshakes.
• Bluetooth Low Energy (BLE 5.3): GATT service with BCCCOP-specific characteristics. Used for TIER_0 data exchange with hardware attestation.
• Wi-Fi Direct / QUIC: Sustained projection streams for TIER_1 and TIER_2 content delivery.

TIER_0 atoms are restricted to BLE and Wi-Fi Direct carriers; they MUST NOT be transmitted over ultrasonic (to prevent eavesdropping on biometric data). All other tiers may use any available carrier.

Operations The Trojan Window lifecycle drives Format B command execution through a 9-state finite state machine: Each state transition requires one or more of: biometric re-authentication (Face + Voice cascade per ), stewardness accordance check, Gibber-Link X25519 3-party key exchange, or memory-wipe attestation (BLAKE3 proof).

IANA Considerations This document requests the registration of the "⚮" URI scheme in the "Uniform Resource Identifier (URI) Schemes" registry, per the procedures of .

URI Scheme Registration Template

Scheme name:

⚮ (Unicode code point U+26AE)

Status:

Provisional

Applications/protocols that use this scheme name:

BCCCOP (Biometric-First Communication Protocol); BubblePress application; Gibber-Link ultrasonic handshake

Contact:

Patrick Schur <partnerships@theCwindLab.net>

Change controller:

Patrick Schur (theCwindLab)

References:

This document (draft-schur-bcccop-uri-scheme-00)

Security Considerations The ⚮ URI scheme is designed for biometric-first, zero-trust environments. The following security properties apply:

1. Biometric Anchoring: All TIER_0 atom emission requires a fused biometric cascade (Face + Voice + optional Fingerprint). The cascade produces a BLAKE3 hash that anchors iBubbleTag identifiers. Fresh biometric re-authentication is required for every TIER_0 operation per .
2. Consent Vault: Cross-device operations (Format B) require a consent record in the Argon2id-encrypted consent vault. Consent is per-purpose, per-recipient, and instantly revocable.
3. Transport Security: TIER_0 data is encrypted with AES-256-GCM (12-byte randomized nonce, 16-byte authentication tag) per . Transport-layer encryption uses QUIC () with TLS 1.3 ().
4. Carrier Restriction: TIER_0 atoms are restricted to BLE and Wi-Fi Direct carriers. The ultrasonic Gibber-Link channel (4-FSK, 18-21 kHz) is used only for non-sensitive pre-verification handshakes, never for biometric or consent data.
5. Memory Wipe Attestation: The terminal Wiped state of the Trojan Window FSM produces a BLAKE3 attestation proof that the session memory was zero-filled. No sensitive data persists beyond session teardown.
6. Audit Trail: Every TIER_0 operation emits a cryptographically signed SES (Screen Element Streaming) audit frame anchored to the Hedera Hashgraph consensus service.

Implementors SHOULD consult the BCCCOP RFC Conformance Audit (0RFC/OUTPUTclaude/BCCCOP_RFC_CONFORMANCE_AUDIT.md) for a detailed analysis of compliance with referenced IETF standards.

Interoperability Considerations The ⚮ URI scheme is consumed by a 41-crate Rust implementation (BCCCOP PoC BUILD, v0.1.0-lockin, 4759 passing tests). The canonical ATI catalog of 261 atoms is published as a CSV file with a BLAKE3 content hash pinned in the screen manifest, enabling independent implementations to validate their atom registry against the reference implementation. Implementations MUST support the complete ABNF grammar defined in . Format B parsers MUST correctly handle the ⚮:@authority!operation(arg) pattern with URI query and fragment components.

Normative References