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 / Skill / City Mage Runtime

City Mage Runtime

Category role ยท Version 0.1.0

Prepare and resume the City dual-agent harness instance with private City Key evidence and durable checkpoints.

Work in the existing mages_city/harness/city_mage instance of dual-agent-harness, not the superseded extraction. Read runtime.json and README.md before operating. Use bootstrap.mjs --help for explicit key/bundle, private state directory, subject reference and HTTPS audience arguments.

Prefer the existing deployed VTA and key. A subject reference is not proof of control. Local preparation validates/preserves evidence and pins entry-kit sources; it does not mint a service-discovery receipt. Changed evidence/context/sources require an explicit new preparation without discarding the old instance.

Resume through setup.mjs with host-owned adapters and verification. Persist pending operations before effects; use revision comparison and reconcile uncertain outcomes rather than blindly repeating. Never derive executable adapters from keys. Retained crash locks require inspection after the writer has stopped. Keep storage outside source/public/sync folders; local files are not encrypted VTA memory.

Run node harness/city_mage/run.mjs from the City repo. Preserve failed and successful run evidence and operational chronicles. The baseline is offline, not an actual paired run or service deployment. Real VTA/delegation/MyTerms/task/access/memory adapters remain incomplete.

Related domain skill: existing foundation. This workflow adds no personas or canonical vertex assignments.

City and Star operating practice

Include the offline agent admission rehearsal in setup checks, then test adapter conflicts, identical retries, changed retries, revocation and restart recovery separately. Record fixture-only, browser-observed and live-service evidence as separate statuses. A passed intake validator cannot issue credentials or award a City name.

Provenance

Forkable skill page migrated from the agentprivacy skills repo (persona/agentprivacy-city-mage-runtime, v0.1.0).
Source of truth: agentprivacy-skills. Fork this page to materialize a local SKILL.md via fedwiki-to-skill.

origin: 0xagentprivacy ยท author: Mitchell Travers

Assets

๐Ÿ“Ž city-mage-runtimeSKILL.md

Navigation

โ† Welcome Visitors ยท Role Skills

agentprivacy-city-mage-runtime

Work in the existing mages_city/harness/city_mage instance of dual-agent-harness, not the superseded extraction. Read runtime.json and README.md before operating. Use bootstrap.mjs --help for explicit key/bundle, private state directory, subject reference and HTTPS audience arguments.

Prefer the existing deployed VTA and key. A subject reference is not proof of control. Local preparation validates/preserves evidence and pins entry-kit sources; it does not mint a service-discovery receipt. Changed evidence/context/sources require an explicit new preparation without discarding the old instance.

Resume through setup.mjs with host-owned adapters and verification. Persist pending operations before effects; use revision comparison and reconcile uncertain outcomes rather than blindly repeating. Never derive executable adapters from keys. Retained crash locks require inspection after the writer has stopped. Keep storage outside source/public/sync folders; local files are not encrypted VTA memory.

Run node harness/city_mage/run.mjs from the City repo. Preserve failed and successful run evidence and operational chronicles. The baseline is offline, not an actual paired run or service deployment. Real VTA/delegation/MyTerms/task/access/memory adapters remain incomplete.

Related domain skill: existing foundation. This workflow adds no personas or canonical vertex assignments.

City and Star operating practice

Include the offline agent admission rehearsal in setup checks, then test adapter conflicts, identical retries, changed retries, revocation and restart recovery separately. Record fixture-only, browser-observed and live-service evidence as separate statuses. A passed intake validator cannot issue credentials or award a City name.

Related operating practices

City and Star Skills