Goal of this doc

• Simplest, most coherent definition of what we’re creating + why + how
• Document intended to be evolved as MVP solution design evolves
• Core point of alignment between collaborators (reduce complexity + fragmented design)

Questions

• What do we do with these documents? A bit long and perhaps not optimized for coherence

  https://docs.google.com/document/d/1pfp5jarF-30fkozdgD_gbYsietI88lFui24-7FOMNEU/edit?usp=sharing

  https://docs.google.com/document/d/1h5i5C6X7iOHZ5BzhuI7AWYAgLFKYVUsmUy2OE2uBWlU/edit?usp=sharing

  https://docs.google.com/document/d/1MhzvQmsMsvs9Ki3wWdoiqbdCB2o-ApPnrX4xxefaDNc/edit?tab=t.0#heading=h.zg5d8e943gj0

• Technical Spec created by Ron Turetzky to be integrated into this doc, where relevant

  https://docs.google.com/document/d/17w_AiezXmZ3ry86n8i0iQMB6bKvbOo4mGS5d3Vu1BDg/edit?tab=t.0

The Open Protocol Library (OPL) is a decentralized, federated knowledge commons enabling communities to capture, federate, and mobilize diverse forms of knowledge without imposing a single ontology. It combines structured, universal metadata with customizable local schemas, federated through GitHub-based workflows.

Functional Requirements

Minimum Viable Product (MVP)

Incremental Additions

WikiLink Stability Strategy

MVP Requirements

Incremental Enhancements

Detailed Workflow

MVP Workflow Steps

Incremental Workflow Enhancements