release: LOOP v0.2.0 — DPP-compatible lab baseline

- Unify all 10 schemas under v0.2.0 (eliminate v0.1.1/v1 split)
- Add ~40 optional DPP extension fields (ESPR, UNTP, Battery, PPWR, NKWS)
- Create JSON-LD context v0.2.0 with 169 term mappings
- Establish dual license: MIT for code, CC BY-SA 4.0 for spec prose
- Fix Green Claims Directive hallucination (withdrawn June 2025)
- Fix BMUV URL (ministry renamed to BMUKN)
- Remove stale future release dates from changelog
- Add conformity_claims, EPCIS refs, W3C VC pointers to MaterialDNA
- Add traceability/passport extensions to Transfer schema
- Create RFC-0003 (schema versioning policy)
- Add DPP extension examples (12, 13) and fix numbering collision (09→10, 10→11)
- Update naming: "LOOP Protocol" → "LOOP", "LocalLoop" → "localLOOP"
- Update contact to alphin@mycel-ai.de / Mycel UG
- Migrate spec API paths to /api/v1/ prefix

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: alpha912

CHANGELOG.md

@@ -1,45 +1,45 @@
 # Changelog
 
-All notable changes to the LOOP Protocol specification will be documented in this file.
+All notable changes to the LOOP specification will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [0.2.0] - 2026-03-08
+
 ### Added
-- Smart contract integration planning in RFC-004
-- Multi-material bundle specification draft
-- WebSocket support for real-time updates
-- Schema validation script and CI workflow
-- Example JSON payloads for schemas
-- RFC template and RFC 0004 draft
-- Documentation: glossary, FAQ, implementation guide, security guides
-- Governance RFC workflow and RFC-0001 process
-- Compliance docs: threat model and DPIA-lite baseline
-- Lab-only federation handshake schema + RFC-0002
+- Comprehensive DPP extension fields in MaterialDNA passport block (GTIN, economic operator, carbon footprint, recycled content, repair score, substances of concern, hazardous flag, verified ratio)
+- Classification extensions (PRODCOM, TARIC, NACE, SCIP, Waste Framework codes)
+- Traceability extensions (EPCIS event references, chain of custody URL, W3C VC credential ID/issuer)
+- Conformity claims top-level array (UNTP-aligned: claim ID, standards, regulations, topics, declared values, evidence)
+- Transfer schema extensions (traceability, passport subset, waste shipment doc ref, environmental conditions)
+- JSON-LD context v0.2.0 with all 16+ type mappings and 30+ DPP term mappings
+- RFC-0003: Schema Versioning Policy
+- DPP extension example (12-material-dna-dpp-extensions.json)
+- Conformity claims example (13-conformity-claims.json)
+- LICENSES/ directory with MIT.txt and CC-BY-SA-4.0.txt
+- ESPR (EU) 2024/1781, UNTP DPP, and Germany NKWS references
 
 ### Changed
-- Clarified LoopSignal voting weight calculations
-- Updated project structure documentation
-- Adjusted README to remove unverified deployment claims
-- Updated maintainer contact details
-- Updated roadmap to remove unverified test network/pilot claims
-
-### Deprecated
-- Nothing yet
-
-### Removed
-- Nothing yet
+- Unified all 10 schemas under v0.2.0 (eliminated v0.1.1/v1 split)
+- Widened schema_version pattern to accept `0.x.y` (both 0.1.1 and 0.2.0)
+- Changed @context from const to enum (accepts both v0.1.1 and v0.2.0)
+- Changed additionalProperties from false to true on v1-origin schemas
+- Added optional schema_version to LoopCoin, LoopSignal, Transaction, NodeInfo schemas
+- Clarified dual batch fields (metadata.batch_number vs traceability.batch_id)
+- Updated specification header to v0.2.0 with DPP-Compatible Lab Baseline status
+- License clarified as dual: MIT for code, CC BY-SA 4.0 for specification prose
+- Renumbered examples: 09-material-status → 10, 10-handshake-response → 11
+- Backend API paths aligned to /api/v1/ to match specification
 
 ### Fixed
-- Typo in MaterialDNA regex pattern example
-- Repaired truncated MaterialDNA schema JSON
-- Corrected LoopCost reference implementation variables
-- Aligned specification examples with schema-required fields and types
-
-### Security
-- Nothing yet
+- Green Claims Directive hallucination: corrected to withdrawn June 2025
+- Stale BMUV URL: updated to bundesumweltministerium.de (ministry renamed to BMUKN)
+- Removed stale future release dates (0.2.0 "Q3 2025", 0.3.0 "Q4 2025", 1.0.0 "Q1 2026")
+- Removed invalid JSON comments in specification Section 12 examples
+- Updated specification date from December 2025 to March 2026
 
 ## [0.1.1] - 2025-12-20
 
@@ -59,7 +59,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.0] - 2025-05-27
 
 ### Added
-- Initial LOOP Protocol specification v0.1
+- Initial LOOP specification v0.1
 - Core protocol definition with four main components:
   - MaterialDNA universal identification system
   - LoopCoin expiring local currency specification
@@ -121,7 +121,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 | Version | Date | Status | Key Changes |
 |---------|------|---------|------------|
-| 0.1.1 | 2025-12-20 | **Current** | Minimal interop lab demo baseline |
+| 0.2.0 | 2026-03-08 | **Current** | DPP extensions, schema consolidation, context completion |
+| 0.1.1 | 2025-12-20 | Superseded | 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 |
@@ -135,33 +136,20 @@ This is the first implementable version. Key changes:
 3. Federation protocol established
 4. MaterialDNA format finalized
 
-## Future Releases
-
-### [0.2.0] - Planned Q3 2025
-Expected additions:
-- Smart contract templates
-- Advanced routing algorithms
-- Mobile SDK specifications
-- Reputation system
-
-### [0.3.0] - Planned Q4 2025
-Expected additions:
-- IoT integration standards
-- Carbon credit calculations
-- Multi-language support
-- Batch operations
+## Future Direction
 
-### [1.0.0] - Planned Q1 2026
-- Stable API guarantee
-- Production-ready specification
-- Full test suite
-- Compliance certification program
+Future releases may include:
+- Smart contract integration (see RFC-0004)
+- IoT and sensor integration
+- Profile-based extension guidance for product-specific DPP delegated acts
+- Conformance test suites for additive patch releases
+- Advanced routing and batch operations
 
 ---
 
 ## Maintenance
 
-This changelog is maintained by the LOOP Protocol core team. 
+This changelog is maintained by the LOOP core team. 
 
 **How to contribute:**
 1. Fork the repository
@@ -179,7 +167,8 @@ This changelog is maintained by the LOOP Protocol core team.
 
 ---
 
-[Unreleased]: https://github.com/local-loop-io/loop-protocol/compare/v0.1.1...HEAD
+[Unreleased]: https://github.com/local-loop-io/loop-protocol/compare/v0.2.0...HEAD
+[0.2.0]: https://github.com/local-loop-io/loop-protocol/compare/v0.1.1...v0.2.0
 [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

CODE_OF_CONDUCT.md

@@ -26,7 +26,7 @@ Project maintainers will remove, edit, or reject contributions that violate this
 
 ## Reporting
 
-Report violations to: alphinctom@gmail.com (GitHub: @alpha912)
+Report violations to: alphin@mycel-ai.de (GitHub: @alpha912)
 
 ## Attribution
 

CONTRIBUTING.md

@@ -1,6 +1,6 @@
-# Contributing to LOOP Protocol
+# Contributing to LOOP
 
-Thank you for your interest in contributing to LOOP Protocol! We're building this together as a community.
+Thank you for your interest in contributing to LOOP! We're building this together as a community.
 
 ## 🤝 Code of Conduct
 
@@ -64,6 +64,6 @@ See rfcs/0000-template.md for the RFC template.
 
 ## ❓ Questions?
 
-- GitHub Discussions or email: alphinctom@gmail.com
+- GitHub Discussions or email: alphin@mycel-ai.de
 
 Thank you for helping build the future of circular economy! 🌍

DOMAIN-POLICY.md

@@ -1,6 +1,6 @@
 # Domain Policy
 
-This repository defines the LocalLoop protocol assets and example payloads.
+This repository defines the localLOOP protocol assets and example payloads.
 
 ## Canonical domains
 

LICENSE

@@ -1,21 +1,13 @@
-MIT License
+LOOP — Dual License
 
-Copyright (c) 2025-2026 Alphin Tom
+Copyright (c) 2025-2026 Alphin Tom / Mycel UG (haftungsbeschränkt)
 
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
+This repository uses a dual-license model:
 
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
+1. Code (schemas/, scripts/, examples/, CI config, package.json):
+   MIT License — see LICENSES/MIT.txt
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+2. Specification prose (SPECIFICATION.md, docs/, rfcs/):
+   Creative Commons Attribution-ShareAlike 4.0 International — see LICENSES/CC-BY-SA-4.0.txt
+
+Full text of each license is in the LICENSES/ directory.

LICENSES/CC-BY-SA-4.0.txt

@@ -0,0 +1,30 @@
+Creative Commons Attribution-ShareAlike 4.0 International
+
+Copyright (c) 2025-2026 Alphin Tom / Mycel UG (haftungsbeschränkt)
+
+This work (SPECIFICATION.md, docs/, rfcs/) is licensed under the Creative
+Commons Attribution-ShareAlike 4.0 International License.
+
+You are free to:
+
+  Share - copy and redistribute the material in any medium or format for any
+  purpose, even commercially.
+
+  Adapt - remix, transform, and build upon the material for any purpose, even
+  commercially.
+
+Under the following terms:
+
+  Attribution - You must give appropriate credit, provide a link to the
+  license, and indicate if changes were made. You may do so in any reasonable
+  manner, but not in any way that suggests the licensor endorses you or your
+  use.
+
+  ShareAlike - If you remix, transform, or build upon the material, you must
+  distribute your contributions under the same license as the original.
+
+  No additional restrictions - You may not apply legal terms or technological
+  measures that legally restrict others from doing anything the license
+  permits.
+
+Full license text: https://creativecommons.org/licenses/by-sa/4.0/legalcode

LICENSES/MIT.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025-2026 Alphin Tom / Mycel UG (haftungsbeschränkt)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -1,9 +1,9 @@
-# LOOP Protocol
+# LOOP
 
-[![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)
+[![Version](https://img.shields.io/badge/version-0.2.0-blue.svg)](https://github.com/local-loop-io/loop-protocol/releases)
+[![License](https://img.shields.io/badge/license-MIT%20%2B%20CC--BY--SA--4.0-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)
+[![Specification](https://img.shields.io/badge/spec-v0.2-orange.svg)](SPECIFICATION.md)
 
 Local Optimization with Overflow Protocol. A federated circular economy concept with shared schemas and interoperability notes.
 

SECURITY.md

@@ -2,14 +2,14 @@
 
 ## 🔐 Reporting Security Vulnerabilities
 
-The LOOP Protocol team takes security seriously. We appreciate your efforts to responsibly disclose your findings.
+The LOOP team takes security seriously. We appreciate your efforts to responsibly disclose your findings.
 
 ### Where to Report
 
 **DO NOT** create public GitHub issues for security vulnerabilities.
 
 Please report security vulnerabilities by emailing:
-- **alphinctom@gmail.com** (GitHub: @alpha912)
+- **alphin@mycel-ai.de** (GitHub: @alpha912)
 
 ### What to Include
 
@@ -182,8 +182,8 @@ We thank the following security researchers for responsibly disclosing vulnerabi
 
 ## 📞 Contact
 
-- **Security Issues**: alphinctom@gmail.com
-- **General Support**: alphinctom@gmail.com
+- **Security Issues**: alphin@mycel-ai.de
+- **General Support**: alphin@mycel-ai.de
 
 ---