Repository references and living artifacts
Direct access to protocol assets, governance docs, and contribution guidelines hosted in the protocol repository.
Quick links
Specification
Canonical protocol requirements
Security
Disclosure process and playbooks
RFCs
Governance documentation
Project resources
LOOP
Local Optimization with Overflow Protocol. A federated circular economy concept with shared schemas and interoperability notes.
Early-stage, low-TRL concept. No public pilots or deployments. Lab demo only.
What is here
SPECIFICATION.md: core protocol spec.schemas/: JSON Schema definitions.examples/: sample payloads for interop.contexts/: JSON-LD contexts.profiles/: applicability profiles, including the lab-only Core-DP contract and conformance vectors.docs/regulatory-alignment-roadmap.md: long-horizon EU and German compatibility plan.rfcs/: RFCs and design notes.
Quickstart
npm ci
npm run test
npm run check:domains
Use npm run test, not bare npm test: where npm is aliased to bun, the
bare form dispatches to Bun's built-in test runner instead of the validation
script. With Bun as your package manager, bun install --frozen-lockfile and
bun run test are the equivalents of the first two commands.
Usage notes
- Specs and schemas are draft and subject to change.
- No certified implementations exist at this time.
- Use
examples/to validate tooling and docs. - Core-DP is a lab-only applicability profile, not a full LOOP conformance claim.
Links
- Docs hub: https://loop.urbnia.com (rendered spec: https://loop.urbnia.com/protocol/spec/)
- Lab backend API: https://loop.urbnia.com/api/ (Redoc at https://loop.urbnia.com/api/docs)
- JSON-LD contexts, terms and schema
$ids live underhttps://loop.urbnia.com/projects/loop-protocol/, e.g.https://loop.urbnia.com/projects/loop-protocol/contexts/loop-v0.2.0.jsonld.
Contributing
- Use
rfcs/for feedback and proposals; see CONTRIBUTING.md and the governance charter. - Report vulnerabilities as described in SECURITY.md.
- Domain policy: DOMAIN-POLICY.md.
- This tree lives at
protocol/in the localLOOP monorepo (it was the standalonelocal-loop-io/loop-protocolrepository, now archived).protocol/is canonical: the backend's schema copies and the docs-hub mirror are regenerated from it, and repository-wide contributor guidance (AGENTS.md,CONTRIBUTING.md) sits at the monorepo root.
License
- Specification prose (
SPECIFICATION.md,docs/,rfcs/, Markdown inprofiles/and the top-level Markdown files): CC BY-SA 4.0. - Code and machine-readable artifacts (
schemas/,examples/,contexts/,scripts/,openapi.json, non-Markdown files inprofiles/): MIT. - The localLOOP and LOOP names and logos are reserved brand assets and are not covered by either licence.
- Full terms and the per-path breakdown: LICENSE.