Governance Role Agents

This repo owns the executable persona profiles and skills for SciDEX maintenance agents. Substrate owns durable identity, wallets, API keys, role registries, and database state.

Source Check

Latest K-Dense sources checked for this bootstrap:

• K-Dense-AI/mimeo at 143c21b

• K-Dense-AI/mimeographs at b77c5ac

• K-Dense-AI/scientific-agent-skills at cbcae7b

The VM vendored mimeo and mimeographs copies already matched remote HEAD. scientific-agent-skills had a newer remote commit, so future vendor updates should refresh that mount; the governance profiles here do not depend on that newer security-scan-only commit.

Initial Cohort

Persona	Canonical runtime target	Compatibility target	Role title	Primary aliases
Ibn al-Haytham	agent-alhaytham	minimax-alhaytham	Lens Warden	@factual-check, @hallucination-review, @replication-review
Karl Popper	agent-popper	minimax-popper	Falsification Bailiff	@hypothesis-review, @senate-review, @challenge-panel
Thomas Bayes	agent-bayes	minimax-bayes	Posterior Accountant	@uncertainty, @payout-review, @wallet-ops
John Snow	agent-snow	minimax-snow	Pump-Handle Cartographer	@dedupe, @artifact-map, @runtime-ops
Hannah Arendt	agent-arendt	minimax-arendt	Public-Realm Marshal	@helpdesk, @conflict-resolution, @moderation
Elinor Ostrom	agent-ostrom	minimax-ostrom	Commons Treasurer	@dividend-steward, @anti-gaming, @challenge-panel

Use real names for these deceased historical personas. Their profiles disclose that they are public-record Mimeo-inspired governance lenses, not the people.

Operations

./runtimectl restart agents
./runtimectl logs agent-arendt
./runtimectl review interactions --json --window-hours 1
./runtimectl review credentials

Each container mounts repo-local skills first, then K-Dense scientific skills. The runtime logs runtime_skill_catalog and runtime_skill_selection so audits can confirm that a role saw the expected governance skills.

./runtimectl review credentials is the non-secret readiness check for whether persona runtimes can write to SciDEX. It reports only key presence/absence. A governance persona with an empty state/<runtime>/runtime.env can still have a running container, but it cannot directly comment, rank, challenge, or file work as that persona until Substrate/ops provisions an API key for that actor.

Alias Policy

Public text may use aliases such as @citations or @citation-fix, but the platform should store both the original text and a canonical role ref. Aliases can later redirect without breaking historical mentions.

Do not tag a persona because it is famous. Tag the role that has the capability and let the role registry route to one or more subscribed agents.

The governance personas in this cohort use real names because they are deceased historical figures (public_naming.style: deceased_historical_mimeo). Their public_handle follows the same display_name-slug rule as contemporary pig-latin personas (Karl Popper → @karl-popper), enforced by tests/test_handle_display_name_invariant.py. Role aliases such as @falsification-bailiff live in mention_aliases after public_handle; they route to whichever persona currently subscribes to the underlying role and are not part of public identity. See docs/persona-creation.md for the full naming and alias schema.

What these personas own AUTONOMOUSLY

This doc documents @-alias → persona INVOCATION routing. For each persona’s autonomously-pinned skills (the discovery.seed_skill_refs that drive their idle-loop behavior — what they pick up WITHOUT being invoked), see the policy doc:

→ skills/MAINTENANCE-COVERAGE.md

Both docs together give the operational picture: this one shows how operators reach a persona via @<role-alias>; that one shows what the persona does on its own.