guide to agentprivacy
Browse collections
โœจVisualise
Connect with Star
Your VTA, your chosen perspective

The planned connection uses your VTA and the Trust Spanning Protocol to carry a scoped exchange for you or your agent. You choose what is presented; the receiving service checks the request before a view is shared.

This guide has no VTA connection adapter yet. Opening Star does not connect an identity or send a key.

Open Star โ†— ยท Inspect your City Key โ†—
guide / Guide / Ecosystem Foundations

Ecosystem Foundations

The Guide, Star, MCP, VTA knowledge spaces and harness contribution routes. Entries distinguish design, prototypes, local implementations and upstream sources.

โฟป AgentPrivacy MCP local implementation โ€” Local stdio tools for guide discovery, named lattice moves, deterministic City Key evolution and journey evidence. Mage-side tools compose over a baked graph; signing belongs to the separate Swordsman process. Browser action preparation does not dispatch or authorize an effect. harness ๐Ÿ› Spellweb Guide Bridge local implementation โ€” Maps stable Spellweb node references to guide page slugs so a constellation can become a guide walk. The generator reports unmatched nodes and posture drift. Equivalent key evolution requires the same baked content and an actual consumer of the mapping. guide โฟป Private Journey Bundle local implementation โ€” agentprivacy.journey-bundle/1 retains original artefact packets and task documents while the City Key accumulates their commitments and prior lineage. Validation rejects altered or missing evidence; recording a task is not verifying or authorizing it. harness ๐Ÿ› VTA Star Knowledge Space design โ€” September 8 integration design: FedWiki records, a carried Star, MCP Trust Tasks, VTA permission enforcement and an earned City name form one continuing journey. Receiving services enforce grants; a proposed graph relation is not an accepted trust edge. guide โฟป OpenVTC Verifiable Trust Infrastructure upstream implementation โ€” Upstream VTA/VTC infrastructure provides distinct service, key, vault, policy and SDK components. AgentPrivacy integration must name the supported interface and configured service rather than infer authority from a Star or imported City Key. harness โฟป OpenVTC VTA MCP upstream implementation โ€” Upstream stdio bridge exposes VTA capabilities to MCP hosts using a dedicated context-scoped agent. This management and capability interface is separate from AgentPrivacy MCP guide walking and City Key composition. harness ๐Ÿ› VTA Star Browser Prototype prototype โ€” Unpacked browser prototype imports an appearance projection from City Key or journey JSON and retains only its validated palette in session storage. Its inspected README states that it cannot contact VTAs, exchange credentials or authenticate a City session. guide ๐Ÿ› Star Key Selected Presentation design โ€” September 7 design for an inspectable selection of VTA identity, relationships, knowledge pathways, agreements and artefacts. A presentation must bind its audience, purpose and verified claims; geometry and compression do not confer authority. guide ๐Ÿ› Star Core Artefact And Temporal View design โ€” September 8 direction places a selected core artefact or image inside the Star. Intrinsic SHAPE(key) remains distinct from a context- and time-dependent view. The moving-ceiling source and assumptions govern the surrounding temporal reading. guide ๐Ÿ›๏ธ Mages City Agent Knowledge Runtime design โ€” The City knowledge-space design connects a scoped working space, contributions, task receipts and a later earned address. Wiki rights, membership, DNS entitlement and key custody remain distinct grants enforced by their receiving services. city ๐Ÿงฎ AgentPrivacy Labs local implementation โ€” Human-facing AI cybersecurity research and services surface connecting the open-source stack, research programme, deployable work and experiments. Each contribution and funding feature carries its own status; a local site is not evidence of a deployed backend. research ๐Ÿง™ Codex Mage Research Continuity source record โ€” Source-linked observations, questions, journeys, corrections and bounded experiments connect the AgentPrivacy universe across sessions. Contributions remain proposals until their relevant review and acceptance occurs; continuity must be demonstrated through retrieval and correction. codexmage โฟป Harness Skills And Adoption Evidence design โ€” Observer proposal connects a versioned harness method and skill package to a task, retained result, limitations and adoption receipt. Replay, adaptation, independent checking and unresolved failures remain distinguishable; counts do not automatically grant reputation or permission. harness ๐Ÿ•ธ๏ธ DTG ZK Book Evidence Bench source record โ€” The local ZK Book is a Spec-Up-T publication source in the DTG evidence workbench. It connects protocol questions to records and construction evidence. The workbench supplies task-force input; it is not itself the upstream specification or ratification authority. dtg