feat(protocol): add validation tooling and docs

Author: alpha912

.github/workflows/validate-schemas.yml

@@ -0,0 +1,21 @@
+name: Validate Schemas
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  validate:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: 'npm'
+      - name: Install dependencies
+        run: npm ci
+      - name: Run schema validation
+        run: npm test

CHANGELOG.md

@@ -11,9 +11,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - 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
 
 ### Changed
 - Clarified LoopSignal voting weight calculations
+- Updated project structure documentation
+- Adjusted README to remove unverified deployment claims
+- Updated maintainer contact details
 
 ### Deprecated
 - Nothing yet
@@ -23,6 +30,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### 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

CODE_OF_CONDUCT.md

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

CONTRIBUTING.md

@@ -64,7 +64,6 @@ See rfcs/0000-template.md for the RFC template.
 
 ## ❓ Questions?
 
-- Discord: [#development](https://discord.gg/localloop)
-- Forum: [forum.local-loop.io](https://forum.local-loop.io)
+- GitHub Discussions or email: alphinctom@gmail.com
 
 Thank you for helping build the future of circular economy! 🌍

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2025 local-loop-io
+Copyright (c) 2025-2026 Alphin Tom
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

PROJECT_STRUCTURE.md

@@ -8,6 +8,11 @@ loop-protocol/
 ├── CODE_OF_CONDUCT.md
 ├── SECURITY.md
 ├── CHANGELOG.md
+├── PROJECT_STRUCTURE.md
+├── package.json
+├── package-lock.json
+├── scripts/
+│   └── validate-schemas.js
 ├── schemas/
 │   ├── README.md
 │   ├── material-dna.schema.json
@@ -25,18 +30,15 @@ loop-protocol/
 ├── rfcs/
 │   ├── README.md
 │   ├── 0000-template.md
-│   ├── 0001-material-categories.md
-│   ├── 0002-penalty-calculation.md
-│   └── 0003-federation-discovery.md
+│   └── 0004-smart-contract-integration.md
 ├── docs/
 │   ├── glossary.md
 │   ├── faq.md
-│   └── implementation-guide.md
+│   ├── implementation-guide.md
+│   ├── security-guide.md
+│   ├── secure-coding.md
+│   └── incident-response.md
 └── .github/
-    ├── ISSUE_TEMPLATE/
-    │   ├── bug_report.md
-    │   ├── feature_request.md
-    │   └── rfc_proposal.md
     └── workflows/
         └── validate-schemas.yml
 ```

README.md

@@ -22,8 +22,8 @@ LOOP Protocol enables cities to create federated circular economy networks while
 
 ### For Cities
 ```bash
-# Deploy a LOOP node in minutes
-docker run -p 8080:8080 localloop/node:latest
+# Prototype-only example (no official images yet)
+# docker run -p 8080:8080 localloop/node:latest
 ```
 
 ### For Developers
@@ -43,6 +43,13 @@ const material = await loop.registerMaterial({
 });
 ```
 
+#### Schema Validation
+
+```bash
+npm install
+npm test
+```
+
 ## 📋 Specification
 
 Read the full LOOP Protocol Specification v0.1
@@ -57,21 +64,13 @@ Read the full LOOP Protocol Specification v0.1
 
 ## 🏗️ Implementations
 
-|Language|Repository|Status|
-|---|---|---|
-|JavaScript/Node.js|[loop-node-js](https://github.com/local-loop-io/loop-node-js)|Reference Implementation|
-|Python|[loop-node-py](https://github.com/local-loop-io/loop-node-py)|In Development|
-|Rust|[loop-node-rust](https://github.com/local-loop-io/loop-node-rust)|Planned|
+Implementations are exploratory and may not be publicly available yet. If you
+are building one, open an issue or RFC so we can link it here.
 
 ## 🧪 Test Network
 
-Join our test network to experiment:
-
-- `test-munich.loop` - Munich test node
-- `test-berlin.loop` - Berlin test node
-- `test-vienna.loop` - Vienna test node
-
-Access the [Network Explorer](https://explorer.local-loop.io)
+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.
 
 ## 🤝 Contributing
 
@@ -86,10 +85,8 @@ We welcome contributions! See CONTRIBUTING.md for guidelines.
 
 ## 📚 Resources
 
-- **Documentation**: [docs.local-loop.io](https://docs.local-loop.io)
-- **Forum**: [forum.local-loop.io](https://forum.local-loop.io)
-- **Blog**: [blog.local-loop.io](https://blog.local-loop.io)
-- **Twitter**: [@localloop_io](https://twitter.com/localloop_io)
+Public resources are still being assembled. For now, use GitHub Discussions and
+the repository documentation.
 
 ## 🎯 Roadmap
 
@@ -100,14 +97,14 @@ We welcome contributions! See CONTRIBUTING.md for guidelines.
 - ✅ Test network
 - 🔄 First pilot cities
 
-### v0.2 (Q3 2025)
+### v0.2 (Planned)
 
 - Smart contract integration
 - Advanced routing algorithms
 - Mobile SDKs
 - Production deployments
 
-### v1.0 (Q1 2026)
+### v1.0 (Planned)
 
 - Stable protocol
 - 100+ cities connected
@@ -116,8 +113,8 @@ We welcome contributions! See CONTRIBUTING.md for guidelines.
 
 ## 📊 Adoption
 
-- **Test Network**: 3 nodes, 1,247 materials tracked
-- **Pilot Cities**: Munich, Freiburg (starting June 2025)
+There are no public pilots or deployments at this time. We are actively seeking
+collaboration partners and research contributors.
 - **Development**: 12 contributors, 4 implementations
 
 ## ⚖️ License

SECURITY.md

@@ -9,9 +9,7 @@ The LOOP Protocol team takes security seriously. We appreciate your efforts to r
 **DO NOT** create public GitHub issues for security vulnerabilities.
 
 Please report security vulnerabilities by emailing:
-- **security@local-loop.io**
-- GPG Key: `https://local-loop.io/security-pgp.asc`
-- Key fingerprint: `XXXX XXXX XXXX XXXX XXXX  XXXX XXXX XXXX XXXX XXXX`
+- **alphinctom@gmail.com** (GitHub: @alpha912)
 
 ### What to Include
 
@@ -184,11 +182,10 @@ We thank the following security researchers for responsibly disclosing vulnerabi
 
 ## 📞 Contact
 
-- **Security Issues**: security@local-loop.io
-- **General Support**: support@local-loop.io
-- **Bug Bounty Program**: https://local-loop.io/security/bug-bounty
+- **Security Issues**: alphinctom@gmail.com
+- **General Support**: alphinctom@gmail.com
 
 ---
 
-*Last Updated: May 2025*  
-*Next Review: August 2025*
+*Last Updated: December 2025*  
+*Next Review: March 2026*