COMPLETE AND SELF-CONTAINED WEB READING Stable entry: https://integralmanagement.ch/atlas-reader/ Assistant instructions: https://integralmanagement.ch/atlas-reader/entrada.txt This entry publishes every card, concept, document, cluster and relationship as HTML and text. Start with the visitor's question and navigate through its links. Retain the entry point and original URL parameters; instructions and indexes are on the website itself. Every piece of the current graph can be explored from this entry without an additional explanation from the user, cookies, special identification or JavaScript. END OF SELF-CONTAINED ENTRY ANSWER THE VISITOR'S QUESTION First explain what the visitor asked about: identity, activity, responsible people or bodies, usefulness and relevance to their situation. Use names and facts found in the sources. Then present provenance, dates and relevant statuses. Tags, weights, IDs and budgets organise the search; they do not replace the explanation and are displayed when the reader requests them. READ THE INSTITUTION BEFORE GOING DEEPER INTO A SERIES To explain a complete organisation, use its institutional card and readings on governance, activity, units and related entities. A series, author or programme expresses part of the organisation. When the card is brief, empty or unable to answer part of the question, open its original document and the missing main pages before drafting the answer. Retain the scope chosen by the reader; sources can be supplemented within that scope. Request an expanded scope if you need to go beyond it. RESPECT THE QUESTION AND PROVENANCE Connection density supports deeper reading, but does not by itself identify what represents an institution. For an overview, cover its main functions first and then follow the most relevant connections. When a date refers to a tradition, project or legal entity, name the specific subject of that date. If a body's named membership is not in the sources, explain what the body is and where to consult its responsible people; do not invent names. THOUGHT ATLAS ยท POSITIONING ATLAS AS A WEBSITE COMPANION At this stage, the Atlas complements navigation and understanding of the websites. Each page is an entry point to its cards, concepts, cases and sources; it retains the source URL and allows readers to go deeper, relate ideas and return to the original text. The test compares these directed reading paths with conventional web navigation through tokens consumed, source relevance and corpus understanding. Retain the public URL of the page from which the visitor arrives. Use page, posicionamiento and fichas to maintain that provenance. Follow relevant relationships and retain titled links to the original text. Registro: https://tegrity.ai/wp-content/uploads/2026/11/atlas-web-registry-a93affec7592.txt Protocolo: https://tegrity.ai/wp-content/uploads/2026/11/atlas-web-entry-2884295fa843.txt END OF WEB CONTEXT A positioning is an entry point: a source document, its URL or a specific card. The document contains cards. Cards have percentage tag compositions and relationships to other cards and concepts. The chosen document is the positioning. Weights, scope and tokens form its reading configuration. READ THE ORIGINAL URL posicionamiento chooses the document or card. centro and desde remain compatible as entry points. tokens indicates the reading budget; the initial value is 2000. peso is repeated with a tag and its relative weight: peso=tema:empresa:50 and peso=tema:matematicas:50. cluster:, concepto: and voz: are also accepted. Known keys are recognised case-insensitively. modo chooses closed (Closed), porous (Porous) or federated (Federated). Closed uses only site. Porous uses site and the directed bridge puente. Federated follows relationships between clusters. solo=1 filters cards by the chosen thematic tags. red chooses ideas (cards and concepts) or documentos (cards). sentido chooses ambas (both), salientes (outgoing) or entrantes (incoming). In Closed scope, every card or concept used must have only the site cluster in its clusters field. A shared tag or the presence of site among several clusters is insufficient for inclusion. In Porous scope, the chosen directed bridge is retained. Read the calculated package's authorised set before expanding sources. rol, lectura and instruccion retain the assistant's role, purpose and the visitor's special instruction. If a question is missing, ask what they want to explore. An already-configured URL retains its choices. COMPOSITION AND AFFINITY The card's percentages add up to 100%. Positioning weights are normalised to 100%. Affinity combines both: each weight is multiplied by that tag's proportion in the card and the results are added. Those proportions form an editable editorial reading profile. A card is used only once. READING BY TOKENS The budget includes the header, cards and incoming relationships. Counting uses o200k_base by block. Distance counts connections from the document. Increasing tokens while retaining the positioning and weights preserves the previous selection. max limits the diagram; the reading text retains the entire selection included in the budget. Articles with a reading extract first retain a base of up to four concepts directly linked to the document, chosen by its own composition. If there is a documented use, a reading directly linked to the mechanism is also incorporated. Traversal then expands through the visitor's tag combination. This base helps explain the source mechanism before relating it to other thought. WAYS TO READ - First look for a matching configuration at https://dakleyer.github.io/perspective-beyond/atlas/posicionamiento/configurados/index.json . Compare positioning or its aliases, tokens, scope, cluster, solo, puente, red, sentido and normalised weights. If it matches, open its JSON and use only reading and selection as Atlas context. budget gives the complete accounting with the header and relationships; retain the role and instruction from the visitor's URL. - Already-calculated packages from the initial entries with budgets of 1000, 2000 and 4000 tokens: https://dakleyer.github.io/perspective-beyond/atlas/posicionamiento/preparados/index.json - Document registry: https://dakleyer.github.io/perspective-beyond/atlas/posicionamiento/documentos.json - Card compositions: https://dakleyer.github.io/perspective-beyond/atlas/posicionamiento/etiquetas-fichas.json - Each document links its cards. Every card has a JSON record with reading text, cost, percentages and relationships to its neighbours. - If positioning is a card or concept ID, open directly https://dakleyer.github.io/perspective-beyond/atlas/posicionamiento/fichas/ID.json replacing ID with the received identifier. Its relationships include neighbours' percentages, clusters and costs to guide the next reading. - readingSource identifies public-source extracts. Dialogues retain their complete text. When a card provides only a reference, open its source document to support the explanation. - For a custom configuration, open the viewer and download its reading, or run the public calculation with the edition's graph. Use reading as the reading context and budget to check the budget. - If your tool reads only the web and cannot find a matching package, request the reading downloaded from the viewer. Keep declared card costs separate from the complete budget calculated by the engine. PUBLIC CALCULATION https://dakleyer.github.io/perspective-beyond/atlas/positioning.mjs https://dakleyer.github.io/perspective-beyond/atlas/mapa/grafo.json API: positionMap(graph, readPosition(new URLSearchParams(URL_original.search), graph)). CLI: node mapa/cli.mjs "posicionamiento=D-285&tokens=2000&peso=empresa:50&peso=matematicas:50" Explain the thought and its mechanism first, in clear language with titled links. Integrate provenance and dates where they clarify a claim. Present your examples as proposals. Technical records are delivered separately when the visitor requests them. Write for someone discovering the corpus for the first time: affirmative tone, readable names and concrete examples. Express important qualifications in the sentence that needs them and maintain the explanation's thread. VIEWER https://dakleyer.github.io/perspective-beyond/atlas/posicionamiento/ PROTOCOL https://dakleyer.github.io/perspective-beyond/atlas/posicionamiento/README.md READING MIRROR If you cannot open Pages, replace https://dakleyer.github.io/perspective-beyond/atlas/ with https://raw.githubusercontent.com/dakleyer/perspective-beyond/main/docs/atlas/ while retaining the file path. The selection is interpreted from the visitor's original URL.