--- fragment_peers: an-adaptable-introductory-model: um-modelo-de-apresentacao-adaptavel choose-the-scope-before-organizing-files: escolha-o-alcance-antes-de-organizar-os-arquivos create-an-open-legibility-space: criar-um-espaco-de-legibilidade-aberta decide-what-the-first-exchange-needs: decida-o-necessario-para-a-primeira-troca establish-participation-conditions: combine-condicoes-de-participacao evaluate-continuity: avalie-a-continuidade organize-the-repository-and-its-reading: organize-o-repositorio-e-a-leitura present-the-context-and-what-people-can-add: apresente-o-contexto-e-o-que-pode-ser-acrescentado reduce-effort-as-use-develops: reduza-o-esforco-conforme-o-uso start-with-your-ai: comece-com-a-sua-ia lang: en peer: pt/open-space/ shared_fragments: false title: Create a space --- # Create an Open Legibility space An Open Legibility space lets participants preserve what they take responsibility for in their work and create conditions for others to read and develop it.

Without site access, attach only the [first-use guide](downloads/legible-first-use-en.txt){ download="legible-first-use-en.txt" }. It includes the complete draft format and, in an optional appendix, the model below.

[See the introductory template](#an-adaptable-introductory-model) · [Organize the files](#organize-the-repository-and-its-reading) · [Participation conditions](#establish-participation-conditions)

It can begin with just you and your private records; when opening collaboration, explain the context, what can be consulted and how to present new formulations, preserving authorship, relationships and evidence before deciding to use them. The space can accompany a department, a product, a company or an idea still held by one person, receiving external contributions or remaining internal. Before choosing folders and repositories, consider which collaboration you want to make possible and whether an existing space already accommodates it. ## Start with your AI Send this page's link or use the instruction above so the AI can explain Legible with an example and help understand your situation. The conversation proceeds one question at a time, using each answer before recommending a way to use it, without requiring you to know the formats or have planned the space's organization. You can begin with your own work and decide later whom to share it with. This path helps create your space; maintaining the protocol has a separate guide. ## Choose the scope before organizing files If the aim is to connect what support, product and engineering know, an ongoing product space may be more useful than a folder for each incident; if it is to develop an idea without collaborators yet, you can begin with your own work. To receive external contributions, present the context and distinguish what can circulate from what must remain internal. AI should help understand what you would like to make possible, who might participate and whether a suitable space already exists. It does so through conversation, using each answer to choose the next question. On hearing that “support observations get lost before they reach product,” the AI can ask for a recent case before recommending a shared folder. The account allows it to investigate whether the observation was never recorded, became hard to find or stopped circulating after being left out of the plan, distinguishing problems that may need different solutions. With that understanding, AI presents its reading as a hypothesis, clarifies relevant uncertainties and recommends a scope, explaining why. Then it helps prepare the introduction, explains where to save it and how to invite someone. If it cannot create folders or configure permissions, it explains the actions you need to take without claiming to have performed them. For an objective and resources already supplied, it uses that information to proceed. An introductory page, a place for preservation and a participation path may be enough. Use an existing repository or separate the space from the organization's code so contributing need not involve copying an entire project. ## Decide what the first exchange needs For the first exchange, establish who can read, where the contribution will be preserved, how it will be presented and how to consult responses, distinguishing access to records, access to evidence and processing by AI. The tool should ask only for what is missing for the next operation, leaving keys, indexers and corporate infrastructure until they are needed. The [downloadable example space](downloads/legible-space-example-en.zip) contains a README, participation conditions, Git policy and four fictional drafts from three participants with their manifests. It is a local exercise, not an already published real space. ## Present the context and what people can add Present what the organization does, which questions it can share and what information is available, describing the problem and its uncertainties before prescribing a deliverable. Someone who knows a condition of use can then contribute without knowing how to implement the solution, and another participant may identify a problem not yet formulated. Explain how to present these contributions, including those that do not answer any published question. Defined work can also be developed in the space; there is no need to reopen every decision. ## An adaptable introductory model The text below can form a page on your site or a repository README. Replace the indications with the space's actual conditions before making it available. This is an editorial model, not a new data specification or legal terms. > **Our Open Legibility space** > > We share questions about [context] here. You can add an observation, formulate > another problem, question a premise or develop a partial solution without > needing an assigned task. > > **To begin:** read [questions overview] and [access and reuse conditions]. > Read the Legible Protocol participation instructions at > > with your AI; without site access, supply `legible-participate-en.txt` > made available with the space's instructions. Or prepare your contribution > in an editor. Review what you wish to declare and choose > what to share. > > **Where to preserve and present:** [repository or collection] holds the > collection we maintain. Present your proposal through [available channel]. > You can also preserve it at your own origin, respecting applicable rights > and conditions. The path starts with drafts; formalization is a separate choice. > > **How to consider other proposals:** consult [collection] and [proposals under > discussion]. The repository's main version contains only what was incorporated. > Your search criteria may reveal something we have not used yet. > > **How we continue:** [responsible people and follow-up practice] explain how > we examine proposals. Incorporation into our collection and decisions to use, > fund or hire have their own conditions. When we recognize a received > consequence, we may record it in a Nod. > > **Rights and contact:** [licenses, disclosure limits and channel for questions > or corrections]. Share only material you can make available in this > environment. Exclude restricted evidence and unnecessary personal data.
Template for your space
View Markdown for manual copying

If offering an offline path, also provide a current copy of that attachment. The full link works outside this site, but its existence does not replace the file for offline use. ## Organize the repository and its reading The space's introduction explains its context and indicates where to consult its collection. Participation conditions describe what may be shared, which channel to use for proposals and how to follow responses. You can use a shared folder, an existing repository or a collection separate from the organization's code. In a Git workflow, the README introduces the space and `CONTRIBUTING.md` describes participation. The record storage convention is `.legible/`; context documents remain ordinary documents. Keep private drafts outside the shared collection and transfer only selected versions. Restricted evidence needs storage with its own permissions. A Git-ignored folder does not protect files that have already entered history. The [downloadable example](downloads/legible-space-example-en.zip) shows this organization with fictional files. To use the reference components, follow the procedures for [export, Git and sharing signed records](configurations.md#organize-the-repository-and-its-reading). ## Establish participation conditions Define which materials may be reused, who can access records and evidence and which providers may process them. The Git service, server or filesystem applies configured permissions; `visibility` only declares a condition in the record. Git can also expose commit names and email addresses, in addition to the files themselves. In a mixed space, keep internal evidence in a separate repository or store with its own access. Publish only authorized declarations and references in the external collection. Another branch, a file deleted from the current version or a `.gitignore` rule does not isolate content already present in distributed history. Use fictional data to check what an external participant can retrieve before opening access. Contribution, permission to use, contracting and recognition are distinct decisions. Actual relationship conditions and applicable obligations still matter. The model requires no assignment of rights, unpaid work or payment promise. Choose licenses appropriate to your materials; the Legible project's licenses do not automatically extend to your space. ## Reduce effort as use develops Start with resources your participants can use. In mobile chat, select files and references and review the result before sending. In environments with tools, an agent can assist queries, preparation, validation and comparison of changes. Publication and signing still require their specific authorizations. An index can help find context without loading the whole genealogy into AI. It need not be global or central: each participant or organization can index sources they can access. Model, cost, updates and limits need to be clear. The catalogue distinguishes [existing components and proposals](implementations.md). ## Evaluate continuity Check whether someone can present a contribution before selection, find a proposal not incorporated and develop it without erasing its origin. Also observe who does preparation and reading, what it costs and whether people have reasons to continue contributing. Compare with the usual workflow using similar access to people, models, information and time. [Operate in Open Legibility](operate.md) · [Share and develop](participation.md)