# Legant Method Library **Status / authority:** Current client-readable methodology library and public Drive entry point **Effective date:** 2026-08-05 **Dependencies:** `LEGANT_METHOD_REFERENCE.md`; `REVIEW_GUIDE.md`; current framework and applied-protocol sources; frozen ARC release **Supersedes:** The ARC-first reader route in this folder's 2026-06-02 README. Existing compatibility paths remain available. This is the single client-readable library for the Legant Method. Chris and authorized agents maintain these files directly. External readers and agents receive read-only access to those same files. **Public reader link:** [Open the Legant Method Library in Google Drive](https://drive.google.com/drive/folders/1PSWz-bzXrZs8upcQAufN3jpiDsfAoaZK) **Agent-readable web copy:** [legantlabs.com/llms.txt](https://legantlabs.com/llms.txt) indexes a plain-text copy of these files at [legantlabs.com/methodology/library/](https://legantlabs.com/methodology/library/). Agents cannot read Google Drive files directly, so they should use the web copy. It is generated from this folder, which remains the master; do not edit the web copy. The website is where people discover the method. This library contains the detailed Markdown sources, applied protocols, evidence boundary, open questions, and historical context when readers or agents need more detail. ## Start here 1. Read [the Method Reference](https://legantlabs.com/methodology/library/legant-method-reference.md) as the canonical entry for architecture, concepts and evidence boundaries. The [published Method page](https://legantlabs.com/methodology/) is a downstream public introduction. 2. Descend to [supporting architecture detail](https://legantlabs.com/methodology/library/method-architecture-detail.md) for the full six-step and five-alignment explanations; follow the reference for framework inventory, applied protocols, source lineage and compatibility. 3. Follow the current framework or applied-protocol source named in `LEGANT_METHOD_REFERENCE.md` when more detail is needed. 4. Use `ARC_Reference_Index.md` and the access notice at `ARC Methodology.docx` only for legacy ARC routing. A later current Legant source takes precedence. 5. Use `REVIEW_GUIDE.md` to have a person or agent challenge the method and return addressable feedback. ## Development notes - [A personal navigation system](https://legantlabs.com/methodology/library/personal-navigation-system.md): emerging application joining the Operating Manual, Baseline, methodology and operating instructions in a decision-and-learning loop. First implementation in Chris’s own use; not a validated general standard. ## Library map ### Current method - `LEGANT_METHOD_REFERENCE.md`: canonical architecture and primary library entry. - `METHOD_ARCHITECTURE_DETAIL.md`: supporting step/alignment explanations; source-preserving migration from the website content. - `Direction/Four Narrative Constraints.md`: legacy direction framework, replaced for new work by the Operating Manual's "What I choose" answers (Method Reference §§2–3); kept for older artifacts and its ownership check. - `Innate Edge Discovery/Tension Framework.md`: current Core Tension definition and boundaries. ### Client-readable applied protocols - `Client Agent Reply Standard.md`: shared response standard for client-owned agent workspaces. - `Navigation/`: client-agent navigation, workspace setup, and templates. - `Innate Edge Discovery/README.md`: route to current, legacy-derived, and legacy discovery sources, including the Markdown evidence-intake guide. - `Positioning/README.md`: route to the current positioning intake artifact and the open client-readable protocol gap. ### Legacy ARC record - `ARC Methodology.docx`: public compatibility notice at the historical filename. The complete ARC-era document is preserved privately because it contains client examples and obsolete production material. - `ARC_Reference_Index.md`: short legacy pointer to the current Legant sources and frozen release. - A frozen internal ARC release preserves manifests, checksums, private implementation history, and the full pre-migration record. It sits outside the public share boundary and is available through the maintainer when historical recovery is warranted. Historical client artifacts keep the terminology they originally used. ARC remains a searchable compatibility alias; it is not the name of the current method. ## Authority and access - Share this folder as `Viewer`; leave downloads enabled. - Do not share the parent `Program Docs/` folder. - External readers and agents may read, link to, and download these files. They do not edit them. - Proposed methodology changes are routed to Chris and applied to these canonical files only after approval. - Client-specific sources and context stay in each client's workspace. Client workspaces point here rather than copying the methodology. ## External review `REVIEW_GUIDE.md` gives people and agents a standard route for mapping, challenging, and citing the method. Reviews return to **c@thezag.com** as a document or email; Google Drive comments are not the review channel. ## Deliberately excluded This library excludes internal production material, private or client-specific data, and working files. Those sources may implement, test, or inform the method without becoming client-readable methodology. Their filenames and storage routes are not part of the public method. ## Change and recovery - `CHANGELOG.md` records changes to this reader library, including moves, status clarifications, validation, and rollback locations. - Current documents use explicit authority headers. - Superseded material is labelled and preserved; it is not silently rewritten or deleted. - The internal frozen ARC release is the recovery source for the exact pre-Legant system. The public library exposes only its client-readable legacy sources.