Persistent agents that know how to work together.

RESIDENT BY DESIGN

A native interactive session, not a cold prompt loop.

A persona runs as one native interactive session. A repeated headless single-prompt invocation—often exposed as -p—must re-inject the working bundle every turn. That spends tokens rebuilding context and discards conversational detail that improves accuracy.

A project lead can be anchored to its repository as the persistent lead session: it retains project context, delegates bounded work, and receives deputy evidence without becoming an ephemeral subprocess.

ROLE PATHS

The address says what the role governs. The name says who it is.

Registration asks for scope, optional project, role, then name. root is a reserved installation scope. Paths have exactly two segments for root or workspace-wide roles, and exactly three for project duties. There are no placeholder segments.

The role registry—not free text—decides which final segments are valid and maps each role to its capability profile. The owner-facing persona name is separate metadata and may use a suggested Virgo constellation name.

REGISTRY & SKILLS

Create and change team members without erasing their lineage.

virgo persona add registers the role path, capability profile, native session lineage, character composition, and optional repository binding. virgo persona retire stops placement and new delivery but keeps records, snapshots, and address history.

Skills are managed at persona, class, and workspace levels. A persona may revise its own skill inside its authority. A shared class or workspace edit creates a proposed revision. virgo skill approve is a root/operator action: it activates only the exact proposed revision with an owner-private HMAC-signed durable receipt recording approver and timestamp. Every active read revalidates that signature; editing the skill again returns it to proposed and clears the prior approval.

virgo persona add [name]
virgo persona retire <name-or-address>
virgo skill list
virgo skill add
virgo skill approve

CHARACTER

A sensible class default, with room to become distinct.

1. RoleChoose a registered duty profile; the first persona defaults to home/secretary.
2. CharacterDescribe its personality in a few lines to overlay the class's default CHARACTER.md, or keep that default.
3. VoiceLanguage and tone are optional now and can be fine-tuned later in the Hub.

CONTINUITY

Snapshot the persona, not just its files.

Only tracked persona content enters a canonical manifest. Every file and blob is hash-verified before an atomic restore. Credentials, ignored files, sibling personas, and ambient machine state stay outside.

Conversation continuity preserves the native session lineage across restarts. A move resumes that lineage; it does not fabricate a replacement chat that merely shares a name.

EDIT SAFELY

The active persona is never edited in place.

If any gate fails, the current generation remains active. The Hub shows which path a change will take before confirmation.

GRAPH LINEAGE

Records remain connected across revisions.

Decisions, memories, findings, people, and work records are typed, content-addressed nodes with provenance. Directed edges such as supersedes, relates, and depends keep history walkable.

Rendered Markdown is a verified snapshot view, not an independent source of truth. The same Knowledge Explorer appears in the main Explorer, the Persona records tab, and Status details.