Legible genealogy and recognition¶
This area brings together records selected to accompany the protocol, its foundations and components, allowing readers to examine who declared a formulation, which relationships were asserted and what consequences a beneficiary recognized.
The collection may remain empty until the first records are selected. It represents what was published here, not every contribution to the project.
To participate, follow the Legible contribution space. Proposals under discussion through the listed channels do not automatically enter this graph or its downloads. Preserve origin and the distinction between draft, formalized declaration and editorial selection when consulting them. Merge does not generate a Nod.
Records of this edition will appear here as they are published.
How to read the network¶
Once records have been selected, the network of circles and lines will allow readers to consult summaries, examine relationships and open the original files. While the collection is empty, there will be no network to explore.
- Appoints: blue circles.
- Traces: clickable purple lines from the source formulation to its antecedent.
- Nods: pink circles pointing to the recognized contribution.
- Drafts: dashed outlines or lines, labelled as unsigned.
Colors distinguish records without assigning value. Traces from different people remain separate lines even when they connect the same endpoints. An origin Trace embedded in an Appoint appears as part of that Appoint, not as a separately signed record. Drafts without a declared origin remain in the table; the visualization does not invent their links.
Names and contact¶
Displayed names are editorial labels. Where no name is supplied, Anonymous appears, and the identifier remains in the detail. This does not guarantee anonymity: the DID and relationships may allow records to be linked.
When an optional contact profile is selected for publication, the detail shows its channels and offers the signed file for download. The signature binds the declaration to the key corresponding to the DID; it does not prove civil identity or control of the listed account. A record can be published without a contact profile.
Declaration and verification¶
For formal records, NCO defines what a person declares when signing: they adopt the declaration as their own and make it in good faith. The signature allows its attribution to the key to be checked. The catalogue distinguishes the signatory's statement from interpretations of the record and presents technical checks separately from editorial names and titles.
Display in the archive certifies neither truth, civil identity nor asserted rights, and does not constitute unrestricted reuse authorization. Index operators remain responsible for their own collection, presentation and processing operations under the applicable conditions.
Editorial selection and correction¶
Maintainers choose the records published on this site; there is no automatic submission. Selection does not determine record validity in other environments, and Nods do not form an official score.
A valid signature allows integrity and attribution to the key to be checked. The declaration's truth and permission to disclose third-party data need their own assessment. Contacts also require specific selection and permission.
Maintainers assess correction or removal requests and take appropriate action on copies under their control; they cannot erase those already distributed by others. A person mentioned in the content or someone who has lost their key can submit a request without a signed Redaction. Removal from the publication does not automatically revoke licenses already granted; see the publication notices.
Specification · Articles and books · Reference components