feat: add Groove Protocol standard — universal plug-and-play composition

Groove Protocol specification for type-safe, zero-config system composition:

spec/SPEC.adoc — Full protocol specification covering:
  - Discovery (local port probing + distributed mDNS/BEAM)
  - Capability negotiation (structural matching, SemVer versioning)
  - Idris2 dependent type proofs (match safety, linear handles,
    capability authenticity, composition soundness)
  - Connection lifecycle (states, heartbeat, graceful degradation)
  - Attestation (VeriSimDB provenance hash-chains)
  - Groove Mesh (transitive composition with type-safety proofs)
  - Groove Bridge (legacy adaptation, BoJ as reference)
  - Security (mTLS, capability requirements, blocklists)

spec/CONFORMANCE.adoc — Four conformance levels:
  Level 1 Groove-Aware, Level 2 Connected, Level 3 Proven, Level 4 Native

spec/MODULARITY.adoc — Module architecture following ABI/FFI/API triple:
  Idris2 ABI → Zig FFI → V API. Dependency graph, user journeys,
  stripping-back guide. Each module is self-contained.

docs/POSITIONING.adoc — Market positioning strategy:
  Five audience channels, phased rollout, one-line pitches per audience.
  "Groove occupies unclaimed space — it doesn't compete with anything."

harness/groove-harness.js — Universal Groove Harness:
  Copy-paste boilerplate that handles discovery, connection lifecycle,
  heartbeat, FLI provisioning, and attestation. Panel authors only write
  their capabilities, UI, and handlers.

harness/groove-panel-template/ — Mintable panel template:
  Three-step panel creation (declare capabilities, write handlers,
  write UI). Everything else is automatic.

examples/ — Burble manifest (full) and minimal manifest

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

.tool-versions

@@ -5,5 +5,3 @@
 # Primary runtime
 deno 2.1.4
 
-# Build tools
-just 1.36.0

Justfile

@@ -26,11 +26,6 @@ lint:
 clean:
     @echo "Clean not configured yet"
 
-# [AUTO-GENERATED] Multi-arch / RISC-V target
-build-riscv:
-	@echo "Building for RISC-V..."
-	cross build --target riscv64gc-unknown-linux-gnu
-
 # Run panic-attacker pre-commit scan
 assail:
     @command -v panic-attack >/dev/null 2>&1 && panic-attack assail . || echo "panic-attack not found — install from https://github.com/hyperpolymath/panic-attacker"

consent-aware-http/justfile

@@ -0,0 +1,74 @@
+// SPDX-License-Identifier: PMPL-1.0-or-later
+// SPDX-FileCopyrightText: 2026 Jonathan D.A. Jewell
+= Groove Protocol
+Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
+:toc: left
+:toclevels: 3
+:icons: font
+:source-highlighter: rouge
+
+== What Is Groove?
+
+Groove is a protocol where independent systems discover each other at runtime,
+negotiate capabilities through type-safe interfaces, and compose — or don't —
+without either side needing configuration or the other to function.
+
+A groove is the shape cut into the surface of a system. It is passive until
+engaged. It guides without constraining. Fit is structural, not negotiated —
+the Idris2 dependent types make compatibility a compile-time property, not a
+runtime handshake that might fail.
+
+== Quick Example
+
+Start two groove-aware systems:
+
+[source,bash]
+----
+# Terminal 1: start Burble (voice/text comms)
+burble start --port 6473
+
+# Terminal 2: start Gossamer (desktop app shell)
+gossamer start --port 6470
+----
+
+Gossamer probes nearby ports. Port 6473 responds with Burble's capability
+manifest. Burble offers `voice`, `text`, `presence`, `spatial-audio`, `tts`,
+`stt`. Gossamer consumes `voice` and `text`. Types match. Voice UI appears in
+Gossamer. No configuration was written. No plugin was installed.
+
+Stop Burble. Gossamer keeps working — voice UI disappears gracefully.
+
+== Design Principles
+
+. **Bare by default** — every system works alone, unplugged
+. **Structural fit** — compatibility is a type property, not a config option
+. **Zero configuration** — start services, they find each other
+. **Graceful degradation** — losing a groove partner is not an error
+. **Linear safety** — connection handles are consumed exactly once
+. **Provenance** — every groove connection is attestable
+
+== Specification
+
+See link:spec/SPEC.adoc[SPEC.adoc] for the full protocol specification.
+
+== Status
+
+[cols="1,3"]
+|===
+| Stage | Working Draft
+| Version | 0.1.0
+| Media Type | `application/groove+a2ml` (registration pending)
+| Reference Impl | Burble, Gossamer, VeriSimDB, Vext
+| Formal Proofs | Idris2 ABI in `src/abi/`
+|===
+
+== Related Standards
+
+- link:../a2ml/[A2ML] — capability manifests are encoded in A2ML
+- link:../axel-protocol/[Axel Protocol] — age-gating can groove with content systems
+- https://github.com/hyperpolymath/burble[Burble] — reference groove provider (voice/text)
+- https://github.com/hyperpolymath/gossamer[Gossamer] — reference groove consumer (desktop shell)
+
+== License
+
+PMPL-1.0-or-later