Code and configurations¶
Although formats make interchange possible, tools determine how much work it takes. This area brings together code and configurations to make participation easier and will grow with the needs found during tests, from local search or simpler file exchange to a setup suited to a company's environment.
Each component should address a concrete participation problem, identifying the operations it assists and the requirements for using it. To begin with a draft, follow first use with AI; the resources below serve those who want to configure or program further operations.
The reference path is operating in Open Legibility: read questions and proposals, formulate, preserve, present and continue a contribution. A configuration should explain which steps it assists and which remain manual. Repository interfaces, models and indexing may come from different tools. The existing MCP is not an automatic PR reader.
An agent with authorized file and Git access can start without MCP. The example space demonstrates a collection of selected packets, separate from the private cache. MCP is an option for scoped local operations, not a prerequisite for protocol use.
Available components¶
Each entry states the edition, requirements and existing tests. The guides accompany the code in this distribution, which you can inspect before installing anything.
Rust core and CLI¶
Prepare and verify records, read drafts and query a local genealogy projection.
Experimental · The Legible Protocol draft 0.4
Requirements: Rust/Cargo; OpenSSH for signing workflows.
Limits: Local tests cover specific operations; they do not certify every specification requirement.
Guide and source · Source · Contribute to this component
Existing tests: protocol/reference/legible-core/tests.
Python library¶
Import, search and export drafts, and use core operations from Python programs.
Experimental · The Legible Protocol draft 0.4
Requirements: Python and a compiled Rust CLI; explicit configuration of optional resources.
Limits: Signing and provider helpers must respect each deployment's authorizations.
Guide and source · Source · Contribute to this component
Existing tests: protocol/reference/legible-py/tests.
Reference MCP server¶
Let an MCP client search, read, import and prepare local contributions without signing them.
Experimental · The Legible Protocol draft 0.4
Requirements: Python, Rust CLI and a compatible MCP host; HTTP requires the configured bench.
Limits: Offers neither a signing tool nor an embedded model. External accounts and clients require testing in their actual environment.
Guide and source · Source · Contribute to this component
Existing tests: protocol/reference/legible-mcp/tests.
Git and OpenSSH workflow¶
Exercise local formalization with command-line tools.
Experimental · The Legible Protocol draft 0.4
Requirements: Git, OpenSSH and Rust CLI; the person reviews and operates signing.
Limits: Plain Ed25519 is the baseline. Automated examples use fictional identities.
Guide and source · Source · Contribute to this component
Existing tests: protocol/conformance/demos/demo_f_human_signs.sh.
Agent Skill¶
Guide contribution preparation and reading in environments that accept skills.
Available · The Legible Protocol draft 0.4
Requirements: An environment that can load instructions; tools and permissions are configured separately.
Limits: The package is documentation. Each model's response must be evaluated in use.
Guide and source · Source · Contribute to this component
Model behavior must be evaluated in the actual environment.
Local app and participant bench¶
Experiment with drafts and formal preparation using separate participant scopes.
Experimental · The Legible Protocol draft 0.4
Requirements: Python, Rust CLI and, for the Wi-Fi bench, OpenSSL and HTTPS trust on devices.
Limits: A proof of concept run by participants. Native Gemini-to-local-MCP connectivity remains unverified.
Guide and source · Source · Contribute to this component
Existing tests: protocol/adapters/legible-app/test_app.py.
Implementations that can emerge from tests¶
These are development directions, not ready components:
- A configuration for Hermes or another agent environment. A recipe should state the host version, how to load instructions, which tools will be accessible and how to diagnose failures. Having an MCP server is not enough to claim compatibility with a host.
- An independent local indexer. It could retrieve contributions from authorized folders and rebuild its index from originals. It should preserve origins and relationships and distinguish drafts from formal records. Text search and model inference need separate identification. The core already offers projection and query operations; use them before duplicating them.
- A corporate reference environment. It could combine identities, evidence access, internal storage and authorized local or external processing. The recipe needs to document the composition and isolation tests.
A small need may call for a configuration of only a few lines. The implementation's size should follow the problem found in use.
Publish and maintain a component¶
Code may live in repositories under the LegibleProtocol GitHub organization, once established, or in independent maintainers' repositories. A recipe may share a repository with other configurations; a tool with its own dependencies and development path may have a separate one.
To propose a component, describe the problem it solves, its license, installation and a reproducible example. Identify the protocol edition, tested versions and maintainer. Explain where data is held, which steps participants need to repeat and who supplies the model if inference is involved.
Maintainers select entries and update the static site. Distributing this code does not require operating users' installations. The catalogue describes capabilities and tests; the specification defines conformance.
A technical test shows whether an operation works. An account of collaboration helps establish whether it is worth using. Both can guide improvements. Appoints and relationships may accompany a component when their authors choose to prepare and share them; a code change does not require its own record.
Technical contracts · Local setup and MCP · Contribute
Project repositories¶
GitHub organization · Protocol repository — invitation required · Website repository — invitation required · Books and papers on GitHub — invitation required · Contact