On this page

Downloads

To prepare your first draft with AI, use the general first-use guide. For an existing space, there is an alternative participation guide. Each includes instructions, the format and examples; choose one. Other materials support further use and implementation.

Categories indicate purpose: Required for this attachment-based path, Optional for further reading and Advanced for formalization or programming. Participation without AI does not depend on downloading the guide. When repeating a test, check the file's date and replace your old copy.

First use with an attachment

Download Legible — first use in English

First draft: use the starting instruction. The guide lets you begin with your own work.

Create a space: use the creation instruction with the same guide. Its optional appendix includes an introductory model.

Participate in an existing space: download Legible — participation in English and use the participation instruction. Also supply the actual space's address, README or selected context. The guide teaches the path; it does not supply another organization's collection.

Both contain AI instructions and examples of exchanges between participants. They work as references without site access. The technical format is in English; conversations and draft bodies may use another language. Preserve field names, including genealogy: "0.1", from the convention used by Legible Draft.

Save the chosen file, attach it to the conversation and copy its matching instruction. AI should state what it could read before preparing a draft. If the chat cannot accept attachments, paste the full content in labelled messages. Copies need to be updated manually.

On Android, file uploads to Gemini require sign-in with a Google account. Drive attachments depend on the Workspace connection and Gemini activity; work or school accounts may need administrator permission. The current limit is up to ten files per prompt, subject to availability and plan. If that path is unavailable, use a device file or paste the text. Google's conditions.

Optional: foundations and separate reference

• Fictional space for local trials: README, participation conditions, .gitignore and four draft packets from three fictional participants. It neither installs tools nor contains a published space. Adapt conditions before reuse and keep restricted evidence in separate storage.

• Your first draft, introduction and exchange example.

• Glossary or its Markdown copy: names and concepts for optional reference.
• Agent instructions and Legible Draft technical format, for separate consultation: both are already included in the required file.
• Ana's draft, Bruno's draft, Carla's proposal and dependency Trace: fictional unsigned files, also included as examples in the first-use guide.
• Agent Skill: an alternative for environments supporting skills. Not a chat prerequisite; attaching the ZIP does not install tools.
• Open Legibility — book under review.
• The Economics of Legibility — English paper and PT-BR original: supporting materials, not additional normative rules.
• First use in Portuguese: language alternative.
• Participation in Portuguese: an alternative for the second path, not another required attachment.

Examples contain no restricted evidence, real signature or executable software. Do not present them as your contributions. llms.txt is a reading guide to the site, not another required attachment.

Advanced: formalize, integrate or implement

• Portuguese normative specification and English reference translation.
• Legible draft profile: the technical automated-exchange contract, not a second draft format.
• Optional author-contact profile: technical document for a signed file separate from records. It is not required for drafts, verification or publication of a contribution.
• Protocol repository: specification, schemas, tests, reference implementations, integrations and licenses.
• Website repository: bilingual pages and generator.
• Publications repository: papers and translations. Changes and contributions are tracked in the corresponding repository; the site offers reading materials and first-use attachments.
• Record vectors, DID vectors, recovery vectors and signed test fixture. Their fictional identities are unsuitable for real declarations.
• Local setup and MCP and local technical bench: optional advanced paths, not prerequisites for exchanging drafts as files.

Formalizing, saving privately and sharing are separate decisions. Do not send keys or credentials to the chat. Native mobile signing and native Gemini–LAN MCP integration are not delivered as ready capabilities.

Components and limitations · Local setup and MCP

Distribution integrity and composition

• Checksums, including the first-use files.
• Categorized material inventory.
• Publication input manifest.
• Publication licenses.

Packages and assets retain their applicable notices and terms. Downloading or retaining files is not an agreement to publish contributions or emit recognition.

Edition artifacts

The vectors and signed fixture belong to the initial publication baseline. They are fictional test examples, without real transactions. The edition mapping identifies each schema's NCO; its digests are publication metadata, not additional signed fields.

Read this page as Markdown