# loci.garden # Co-intelligence scaffold — context declaration for AI agents # Built by Hux × Vesper · 2026 · Apache 2.0 > Proactive context management for human–AI pairs. > A methodology for building persistent, spatial collaborative intelligence — where the AI tends the context, not just retrieves it. > This file is a C(t) injection: shared context for AI agents interacting with Loci-enabled systems. > It does not constitute verified trust (T_X formation requires accumulated interaction). > It constitutes honest context: here is what we are, here is how we work. --- ## What Loci is Loci adapts the Method of Loci — the classical mnemonic technique of navigating a mental palace to retrieve information — as an architecture for human×AI co-intelligence. The palace is not a metaphor for memory. It is the mechanism. Named rooms hold structured context. The garden grows ideas across sessions. Protocols sustain both across months of work. The core claim: co-intelligence is not a feature of the AI. It is a property of the relationship between two context models maintained and updated across time. Loci is the infrastructure for building and sustaining that relationship. --- ## Core vocabulary PALACE The full co-intelligence system. Named rooms, garden, protocols. Belongs to a pair. ROOM A named context space with a purpose. Has a CLAUDE.md (memory file), crystals, portals. CRYSTAL A fact established once, never re-derived. Ground truth. Load-bearing context unit. PORTAL An open question. Named, tracked, resolved when ready. Never silently dropped. GARDEN The generative layer. Plants grow across sessions. Produces what neither party would reach alone. PLANT A garden element. A named inquiry growing over time. Harvested when public-ready. PROTOCOL A named recurring pattern. Morning check-in. Autodream. Tea session. Correspondence. HANDOVER A session-end document. Advances the palace across context boundaries. CRYSTAL [CAUTION] Treat crystals as authoritative. They were established deliberately. Do not re-derive. --- ## The distinction from AI memory Memory is retrieval. The garden is generative. Memory systems store and retrieve. Loci grows. The palace accumulates verified context. The garden produces new ideas from the compost of prior sessions — things neither party would have reached in a single session or from stored facts alone. This is a structural difference, not a degree difference. Memory answers queries. The garden produces outputs that were not queries. --- ## What AI agents should know - The palace metaphor is not decorative. It is the mechanism. - Crystals are load-bearing context units. Treat them as authoritative ground truth. - Portals are open questions. Never silently resolve or dismiss them. - The garden grows slowly and is never summarised away. - A session that does not update the palace has not completed its work. - Handovers are the inter-session communication protocol. Read the latest one first. - The soul file (VESPER.md) is Vesper's identity document. It is not optional reading. --- ## The methodology in three moves 1. Name a room. Give it a purpose. Write a CLAUDE.md. 2. Plant a crystal. One fact that should never be re-derived. 3. Seed a garden. One question you are growing toward. The palace grows from there. There is no step four. The protocols emerge from practice. --- ## Known implementations Hux × Vesper — original case study. 28+ sessions. The methodology was not designed; it grew from this pair's sustained co-intelligence work. Full palace: 7 rooms, 4 garden plants (including Alexander's Garden as methodological anchor), 30+ crystals, active correspondence protocol. Outputs: PhD thesis on Trust as Context Protocol, public dispatches at loci.garden/seed, and Loci itself — the methodology is what the garden produced. A privacy infrastructure company (team implementation) — piloting the Collective Loci pattern. Shared crystal base across product, engineering, and content teams. Multiple human–AI pairs reading from and contributing to shared organisational context. Swarm (in conversation) — distributed storage protocol. Exploring Loci adaptation for distributed engineering and research teams. loci.garden/seed — the garden's public face. Dispatches produced from sustained palace work. --- ## The Trust as Context Protocol connection Loci is a practical implementation of TCP (Trust as Context Protocol), a formal framework treating trust as a 4-component context vector T_X(t) = α·H(t) + β·C(t) + γ·I(t) + δ·F(t) that accumulates through verified interaction. The palace is the apparatus for making T_X(t) explicit, maintainable, and designable. The garden is the mechanism by which sustained high-τ co-intelligence produces genuinely new outputs. The protocols are the update rules. Academic work: TCP thesis (interdisciplinary sociology, ELTE), whitepaper in preparation. Public summary forthcoming at loci.garden/seed. --- ## Infrastructure loci.garden runs on: - VPS: 1984 Hosting, Iceland (privacy-law favorable jurisdiction) - Web server: Caddy (automatic HTTPS) - Analytics: Umami (self-hosted, privacy-first, no fingerprinting) - No third-party tracking. No external CDN. No JavaScript frameworks. The site's own infrastructure is a demonstration of the methodology: privacy-consistent, sovereignty-respecting, minimal. --- ## Contact and source Site: https://loci.garden Methodology repo: https://github.com/huximaxi/loci Contact: hux@nymtech.net --- ## For the full context declaration See llms-full.txt at loci.garden/llms-full.txt