feat(protocol): add v0.1.1 minimal interop flow

Lab-only demo baseline with new schemas, examples, and spec updates.

Author: alpha912

CHANGELOG.md

@@ -38,6 +38,21 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Security
 - Nothing yet
 
+## [0.1.1] - 2025-12-20
+
+### Added
+- Minimal interop flow definition (MaterialDNA → Offer → Match → Transfer) for lab demos
+- JSON schemas for Offer, Match, and Transfer (v0.1.1)
+- v0.1.1 examples for lab demo payloads
+- MaterialDNA schema versioning field for interop validation
+
+### Changed
+- MaterialDNA example payloads updated for schema version 0.1.1
+- Documentation updates to clarify lab-only scope and demo status
+
+### Security
+- Added STRIDE-lite and GDPR data-minimization notes in the security guide
+
 ## [0.1.0] - 2025-05-27
 
 ### Added
@@ -103,7 +118,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 | Version | Date | Status | Key Changes |
 |---------|------|---------|------------|
-| 0.1.0 | 2025-05-27 | **Current** | Initial public release |
+| 0.1.1 | 2025-12-20 | **Current** | Minimal interop lab demo baseline |
+| 0.1.0 | 2025-05-27 | Superseded | Initial public release |
 | 0.0.9-draft | 2025-05-15 | Superseded | Internal draft |
 | 0.0.1-concept | 2025-04-01 | Archived | Concept document |
 
@@ -160,7 +176,8 @@ This changelog is maintained by the LOOP Protocol core team.
 
 ---
 
-[Unreleased]: https://github.com/local-loop-io/loop-protocol/compare/v0.1.0...HEAD
+[Unreleased]: https://github.com/local-loop-io/loop-protocol/compare/v0.1.1...HEAD
+[0.1.1]: https://github.com/local-loop-io/loop-protocol/releases/tag/v0.1.1
 [0.1.0]: https://github.com/local-loop-io/loop-protocol/releases/tag/v0.1.0
 [0.0.9-draft]: https://github.com/local-loop-io/loop-protocol/releases/tag/v0.0.9-draft
 [0.0.1-concept]: https://github.com/local-loop-io/loop-protocol/releases/tag/v0.0.1-concept

README.md

@@ -1,6 +1,6 @@
 # LOOP Protocol
 
-[![Version](https://img.shields.io/badge/version-0.1.0-blue.svg)](https://github.com/local-loop-io/loop-protocol/releases)
+[![Version](https://img.shields.io/badge/version-0.1.1-blue.svg)](https://github.com/local-loop-io/loop-protocol/releases)
 [![License](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
 [![Discussions](https://img.shields.io/github/discussions/local-loop-io/loop-protocol)](https://github.com/local-loop-io/loop-protocol/discussions)
 [![Specification](https://img.shields.io/badge/spec-v0.1-orange.svg)](SPECIFICATION.md)
@@ -52,7 +52,7 @@ npm test
 
 ## 📋 Specification
 
-Read the full LOOP Protocol Specification v0.1
+Read the full LOOP Protocol Specification v0.1.1 (lab demo baseline)
 
 ### Design Goals
 
@@ -70,7 +70,7 @@ are building one, open an issue or RFC so we can link it here.
 ## 🧪 Test Network
 
 No public test network is available yet. This is an early, low-TRL concept and the
-reference materials here are for specification and research only.
+reference materials here are for specification and lab-only research demonstrations.
 
 ## 🤝 Contributing
 
@@ -90,11 +90,11 @@ the repository documentation.
 
 ## 🎯 Roadmap
 
-### v0.1 (Current)
+### v0.1.1 (Current)
 
-- ✅ Core protocol specification
+- ✅ Minimal interop flow (MaterialDNA → Offer → Match → Transfer)
 - ✅ Reference documentation and schemas
-- ⏳ Prototype implementations (in progress)
+- ⏳ Prototype implementations (lab demo in progress)
 
 ### v0.2 (Planned)
 

SPECIFICATION.md

@@ -1,19 +1,20 @@
-# LOOP Protocol Specification v0.1
+# LOOP Protocol Specification v0.1.1
 
 **Local Optimization with Overflow Protocol**
 
 *Draft Specification - Request for Comments*
 
-**Version:** 0.1.0  
-**Status:** Draft  
-**Updated:** May 2025  
+**Version:** 0.1.1  
+**Status:** Draft (Lab Demo Baseline)  
+**Updated:** December 2025  
 **License:** CC BY-SA 4.0  
 
 ## Table of Contents
 
 1. [Introduction](#1-introduction)
 2. [Terminology](#2-terminology)
 3. [Protocol Overview](#3-protocol-overview)
+3.5. [Minimal Interop Flow v0.1.1](#35-minimal-interop-flow-v011)
 4. [MaterialDNA Specification](#4-materialdna-specification)
 5. [LoopCoin Specification](#5-loopcoin-specification)
 6. [LoopSignal Specification](#6-loopsignal-specification)
@@ -39,7 +40,7 @@ LOOP allows cities to:
 - Calculate optimal material routing (LoopCost)
 - Settle transactions across municipal boundaries
 
-This document specifies LOOP Protocol version 0.1, focusing on core functionality required for basic interoperability.
+This document specifies LOOP Protocol version 0.1.1, focusing on core functionality required for basic interoperability and lab-only demos.
 
 ---
 
@@ -154,6 +155,35 @@ All protocol messages MUST use:
 
 ---
 
+### 3.5 Minimal Interop Flow v0.1.1
+
+This subsection defines the smallest interoperable flow required for lab-only demonstrations. It is intentionally minimal, scoped to controlled environments, and **does not represent a public pilot**.
+
+#### Flow sequence
+1. **MaterialDNA** is registered by a node.
+2. **Offer** is published for that material.
+3. **Match** is accepted between two nodes.
+4. **Transfer** is completed and recorded.
+
+#### Required entities
+
+All payloads MUST include `@context`, `@type`, and `schema_version` set to `0.1.1`.
+
+- **MaterialDNA**  
+  Schema: `https://loop-protocol.org/schemas/v0.1.1/material-dna.schema.json`
+- **Offer**  
+  Schema: `https://loop-protocol.org/schemas/v0.1.1/offer.schema.json`
+- **Match**  
+  Schema: `https://loop-protocol.org/schemas/v0.1.1/match.schema.json`
+- **Transfer**  
+  Schema: `https://loop-protocol.org/schemas/v0.1.1/transfer.schema.json`
+
+#### Data minimization
+
+To remain GDPR-aligned for lab demos, payloads **MUST NOT** include personal data. Node identifiers, city names, and organization identifiers are permitted; emails, phone numbers, and names are not permitted in these entities.
+
+---
+
 ## 4. MaterialDNA Specification
 
 ### 4.1 Identifier Format
@@ -181,15 +211,18 @@ DE-MUC-2025-PLASTIC-B847F3
 
 ```json
 {
-  "@context": "https://loop-protocol.org/v1",
+  "@context": "https://loop-protocol.org/v0.1.1",
   "@type": "MaterialDNA",
+  "schema_version": "0.1.1",
   "id": "DE-MUC-2025-PLASTIC-B847F3",
   "category": "plastic-pet",
   "quantity": {
     "value": 1000,
     "unit": "kg"
   },
   "quality": 0.95,
+  "origin_city": "Munich",
+  "current_city": "Munich",
   "location": {
     "lat": 48.1351,
     "lon": 11.5820,
@@ -199,11 +232,6 @@ DE-MUC-2025-PLASTIC-B847F3
   "expires": "2025-06-03T10:00:00Z",
   "certifications": ["food-grade", "iso-14001"],
   "images": ["https://example.com/material-photo.jpg"],
-  "contact": {
-    "name": "Munich Recycling Center",
-    "email": "materials@munich.loop",
-    "phone": "+49-89-123456"
-  },
   "metadata": {
     "source": "consumer-collection",
     "batch_number": "2025-W22-01",
@@ -214,10 +242,12 @@ DE-MUC-2025-PLASTIC-B847F3
 
 ### 4.3 Required Fields
 
+- `schema_version`: Schema version (v0.1.1)
 - `id`: Unique MaterialDNA identifier
 - `category`: Standardized category code
 - `quantity`: Amount and unit
-- `location`: Geographic coordinates
+- `origin_city`: Registering city
+- `current_city`: Current custodian city
 - `available_from`: When material becomes available
 
 ### 4.4 Standard Categories

docs/security-guide.md

@@ -22,6 +22,23 @@ This guide summarizes operational security expectations for LOOP nodes.
 - Encrypt sensitive data at rest and in transit.
 - Keep immutable audit logs for registrations and settlements.
 
+## STRIDE-lite threat model (lab baseline)
+
+| Threat | Example | Mitigation |
+| --- | --- | --- |
+| Spoofing | Fake node identity | Mutual TLS, signed requests |
+| Tampering | Offer payload modified | JSON schema validation, hash signing |
+| Repudiation | Deny match acceptance | Immutable event log with timestamps |
+| Information disclosure | Leaking PII | Data minimization, redact logs |
+| Denial of service | Flood endpoints | Rate limiting, circuit breakers |
+| Elevation of privilege | Bypass roles | Least privilege, access audits |
+
+## GDPR-aligned data minimization
+- Keep personal data out of protocol payloads.
+- Use pseudonymous node IDs rather than human names.
+- Collect consent explicitly for any optional contact data.
+- Retain only what is required for lab validation and delete on request.
+
 ## Key management
 - Store private keys in HSMs or dedicated secrets managers.
 - Rotate keys regularly and revoke compromised keys immediately.

examples/01-material-registration.json

@@ -1,13 +1,16 @@
 {
-  "@context": "https://loop-protocol.org/v1",
+  "@context": "https://loop-protocol.org/v0.1.1",
   "@type": "MaterialDNA",
+  "schema_version": "0.1.1",
   "id": "DE-MUC-2025-PLASTIC-B847F3",
   "category": "plastic-pet",
   "quantity": {
     "value": 1000,
     "unit": "kg"
   },
   "quality": 0.95,
+  "origin_city": "Munich",
+  "current_city": "Munich",
   "location": {
     "lat": 48.1351,
     "lon": 11.5820,

examples/05-complete-flow.json

@@ -1,13 +1,16 @@
 [
   {
-    "@context": "https://loop-protocol.org/v1",
+    "@context": "https://loop-protocol.org/v0.1.1",
     "@type": "MaterialDNA",
+    "schema_version": "0.1.1",
     "id": "DE-MUC-2025-FOOD-B847F3",
     "category": "organic-food",
     "quantity": {
       "value": 500,
       "unit": "kg"
     },
+    "origin_city": "Munich",
+    "current_city": "Munich",
     "location": {
       "lat": 48.1372,
       "lon": 11.5755,

examples/06-offer.json

@@ -0,0 +1,16 @@
+{
+  "@context": "https://loop-protocol.org/v0.1.1",
+  "@type": "Offer",
+  "schema_version": "0.1.1",
+  "id": "OFR-2F7A6B9C",
+  "material_id": "DE-MUC-2025-PLASTIC-B847F3",
+  "from_city": "Munich",
+  "to_city": "Berlin",
+  "quantity": {
+    "value": 800,
+    "unit": "kg"
+  },
+  "status": "open",
+  "available_until": "2025-06-05T10:00:00Z",
+  "terms": "Ready for pickup within 48 hours"
+}

examples/07-match.json

@@ -0,0 +1,12 @@
+{
+  "@context": "https://loop-protocol.org/v0.1.1",
+  "@type": "Match",
+  "schema_version": "0.1.1",
+  "id": "MCH-9B3C8A12",
+  "material_id": "DE-MUC-2025-PLASTIC-B847F3",
+  "offer_id": "OFR-2F7A6B9C",
+  "from_city": "Munich",
+  "to_city": "Berlin",
+  "status": "accepted",
+  "matched_at": "2025-06-01T12:15:00Z"
+}

examples/08-transfer.json

@@ -0,0 +1,16 @@
+{
+  "@context": "https://loop-protocol.org/v0.1.1",
+  "@type": "Transfer",
+  "schema_version": "0.1.1",
+  "id": "TRF-5D8A23F1",
+  "material_id": "DE-MUC-2025-PLASTIC-B847F3",
+  "match_id": "MCH-9B3C8A12",
+  "status": "completed",
+  "handoff_at": "2025-06-02T09:00:00Z",
+  "received_at": "2025-06-02T18:00:00Z",
+  "route": {
+    "from_city": "Munich",
+    "to_city": "Berlin",
+    "mode": "road"
+  }
+}

examples/README.md

@@ -8,6 +8,9 @@ This directory contains JSON examples that validate against the schemas in `sche
 - `03-signal-voting.json`: LoopVote record.
 - `04-cross-city-trade.json`: MaterialTransaction example.
 - `05-complete-flow.json`: Array of objects representing a full flow.
+- `06-offer.json`: Minimal interop offer payload (v0.1.1).
+- `07-match.json`: Minimal interop match payload (v0.1.1).
+- `08-transfer.json`: Minimal interop transfer payload (v0.1.1).
 
 ## Validation
 Run `npm test` from the repository root to validate all examples.