Soulbis · the Swordsman guide
Your perspective
in the City.
The Star is a geometric expression of you or your agent: a way to see your place on the trust graph, from your own perspective.
The City Key carries the record. The VTA connects the identity. The Star brings the permitted view into form.
The graph begins with a perspective.
You and your agent encounter different knowledge, people and work. The Star is where that particular view takes shape: what you have learned, the artefacts you carry, the promises you make and the relationships you can see.
Its geometry comes from the agentprivacy model. As the VTA connection develops, approved records will populate that geometry with their sources, versions and evidence.
A view belongs to an observer. Another agent may see something different. Shared ground invites a closer look; trust comes from the relationship and its evidence. What is outside your view remains unknown.
One City Key. A continuing expression.
The City Key is the portable artefact at the centre of these instruments. It carries a version of your agent’s record: appearance, descriptions, activity and references to evidence. In Mages City, this is the key through which that expression continues.
Its fingerprint, κ, identifies the contents of a particular version. A new record can carry a reference to the version it grew from, leaving a lineage you can inspect.
The key file and the private signing key have different jobs. Copying a City Key carries its contents; control of the agent identity is established through the VTA.
What does a vertex carry?
A vertex is a place to attach meaning: a pathway through the corpus, an artefact made along the way, or a promise about how that work may be used. Its position helps you navigate; the linked source and evidence explain the claim.
- Trace a pathway.Keep the source, its version, the method and the correction that changed your understanding.
- Keep the artefact and its terms.A proposed binding connects the vertex to an exact artefact reference, a promise-graph record and the applicable MyTerms agreement. The private evidence stays in its permitted space.
- Choose an expression.The sigil is the first compact visual expression. A fingerprint identifies selected content; separately verified signatures establish who signed a particular statement.
Stored meaning and readable geometry
The Star can organise selected artefacts, references and commitments. A reference points to a record; a hash identifies chosen content; neither stores the missing evidence by itself.
A shape may be derived from a versioned reading of that evidence, customised by its owner, or derived with explicit overrides. A programmatic reader needs the mode, inputs and mapping version to tell those apart and reproduce a derived result. Appearance expresses a perspective; authority still depends on the underlying evidence and permissions.
This is the next integration layer. The Star Key test reader currently shows illustrative artwork, not a computed geometry.
Overlap and convergence
Two keys may touch the same vertex while referring to different sources or meanings. Use overlap to discover a possible shared pathway, then compare artefact versions, provenance, promises and terms. Convergence is a finding to inspect, not an automatic trust score or permission grant.
From a runtime trace to a reusable promise
A knowledge graph can preserve the route; a promise graph can state the commitments. Replaying a runtime also requires pinned inputs, code and tools, an execution environment, bounded permissions and a way to check its output. Agent-generated or external-service steps are not deterministic merely because their trace is recorded.
The Star Key integration is being designed to carry these references at a vertex. The current browser reader filters them out; it does not yet resolve agreements, verify signatures or execute a runtime.
Explore the sigil → · Compare overlap in Skye → · Test Star Key →
A Sigil portrait can embed the full City Key. A hash does not conceal guessable content or verify a DID signature. Choose what the exported artefact carries before sharing it.
The City Key, in your browser.
The browser extension is the expression of the VTA we are bringing into this experience: connecting who is signed in, which City Key they are using and whose perspective the Star displays.
- Connect an identity.Use the VTA connection to establish the agent acting for this visit, then select its City Key.
- Choose what comes into view.Bring the permitted part of the agent’s record into the Star. Private context stays within its agreed boundaries.
- Carry the encounter forward.Keep approved activity and evidence with their sources, ready to inform the next version of the record.
Try Star Key · inspect a local City Key →
Being connected. OpenVTC provides the browser identity foundation. Binding it to the selected City Key, scoped Star view and agent-state updates is integration work underway.
Choose what crosses the boundary.
Soulbis is privacymage’s expression of the boundary maker agent. The Swordsman protects what you keep; the Mage works with what you choose to project.
That boundary follows the encounter: which identity is acting, for whom, what it may reveal and what it may do. City services check the permission for each action. The Star makes the resulting perspective legible.
Explore the record today.
The instruments already work with imported City Keys. Each gives you a different reading of the same artefact.
Explore the record through the model’s geometry. Follow its path and tune its expression.
Compare classical and post-quantum signature-size samples, inspect components and fold a collection into the Star. Folding preserves bytes. Samples are not verified credentials and are excluded from City Key exports.
Read the 64 states, their descriptions and the activity carried by the key.
Check the content fingerprint, compare records and carry a version as a portrait.
Bring records together. Inspect their lineage and shared touched vertices.
Keep a trace from the Star
Import a key, walk it, then choose Attach trace to key and Download key. Lap and time counters stay in page memory until you save them. Attach again to include later tracing. This is a local record, not yet a VTA activity receipt.
Know what a portrait carries
A Star or Sigil portrait can contain the City Key itself. A Skye export contains the loaded keys. Sharing the image shares those records. Open rooms on this site can also synchronise imported keys and selected vertices.
Carry your knowledge.
Choose what to reveal.
Mages City is the shared knowledge community taking shape around this work. Bring a question, learn from a source, make an artefact or contribute a correction. Keep the work connected to its maker and the path it came from.
The City brings participants together. Soulbis gives your key a place to live and your perspective a form you can explore. Labs follows the builds, research and source work behind both.
Sources behind the guide
- The agentprivacy model ↗The meaning and mathematical grounding of the geometry.
- OpenVTC browser identity work ↗The upstream VTA browser connection.
- Personal terms and agreements ↗The agreement layer behind the Swordsman’s boundaries.
- Instrument sources at Labs ↗The implementation references for these rooms.