[See an exchange between participants](participation.md#exchange-example-a-software-improvement) · [Prepare your draft](first-draft.md)
Reading Legible records with your AI lets you examine a work's questions, criteria and evidence and decide what you want to take responsibility for and record in your own response. Preserve the distinction between what you formulated, what you adopted and what you still need to investigate, retaining the relationship to the work that prompted that response. Begin with the page or README of the space you wish to join, where the context, collection, access conditions and contribution channel should be explained. AI can help you understand that material and recognize where your experience matters, explaining the path through an example and conducting the conversation one question at a time, based on what you have already said. You can develop an existing formulation or present another problem. You choose what to preserve and when to share; the first drafts can stay with you. This guide follows participation in your chosen space. Work on the protocol itself has a path in the Project area. If you only want to record something from your own work, start with [your first draft](first-draft.md). ## Find where you can contribute Consult the collection and, where available, proposals under discussion. A repository's main version does not contain files from unmerged PRs. On mobile, select excerpts or files and attach them to the chat; with authorized tools, the agent can assist that consultation. Identify the source to examine and check what it actually managed to read. Develop a question, observation, test or partial solution. You need not take on the entire problem. The space should indicate where to present a proposal and follow responses. Also preserve its origin within access conditions so continuity does not depend on a merge. [Understand the circuit](operate.md) · [Open a space](open-space.md) ## Develop and present your response After reading a relevant formulation, you can add an observation, question a criterion or develop part of a solution. Explain what you found, what you want to add and which materials you were able to examine. If AI helps prepare the text, review the description of your participation and the origin of the analyses used. The [first-draft guide](first-draft.md) shows how to prepare and save the file. [Share and develop](participation.md#exchange-example-a-software-improvement) presents four technical example files: two independent formulations, a solution that used both and the declaration of that dependency. The fictional files are also included in the participation attachment. Before presenting your proposal, check the channel the space accepts, the selected version and what information can be shared. Keep a reference to the submission so you can consult responses and decide how to continue. Incorporation into the collection, the decision to use the work and any recognition are distinct acts. If you prefer to start without AI, follow the example in a text editor. If AI cannot access the site, the single participation attachment contains the guidance, format and examples. It does not provide access to the chosen space's documents. ## On Android: from reading to a response This is a real-device test recipe, not a validated Gemini–GitHub integration. Interfaces and account permissions may affect the path. 1. Open the space's page in a browser. Read the README, conditions and a relevant question. If choosing an unmerged PR, open its discussion and files too; note the address and version examined. 2. Send the participation instruction in Gemini. If needed, attach only `legible-participate-en.txt`, from the device or Drive. Supply the context and selected space files you are authorized to process. Ask AI to state what it read and what it could not access. 3. Develop the contribution. At a useful pause, review the description of your role. If choosing to save it, check the draft, authorship and references. 4. Save the Markdown as a text file, keeping `.md`. Without file export, copy it into an editor. Also keep the origin, chosen once as described below. If the file came from another person, preserve its received origin; do not send the whole Drive folder, conversation or internal evidence to complete the submission. 5. Only after choosing sharing, use the space's channel. If it accepts PRs, prepare the change in an authorized copy or branch through the service's web interface or a person/tool with Git. Review the files and diff before submitting. If mobile cannot attach or preserve the packet, request a file channel from the maintainer; do not claim to have opened a PR. 6. Keep the proposal's address. On return, open responses and transfer permitted excerpts to the chat. Check that a response concerns the submitted version. You choose what to consider; a merge is not required to continue. ### Choose and keep the origin The origin identifies the collection a draft comes from; it is not a signature, personal profile or address that must open in a browser. For an existing collection, reuse the origin recorded in its instructions or manifests. Do not replace it when changing phone, AI tool or submission channel. To start your own local file collection, the button below generates a `urn:uuid:` in this browser, without a server, account or key. Generate it once and save the text in `origin.txt` alongside your collection on the device or Drive. Send that same origin with selected drafts; do not add it to YAML. The page does not retain the value after closing or reloading. The identifier distinguishes origins but proves neither authorship nor identity.