consensus-persona-respawn

Ledger-informed persona lifecycle management. Replaces low-performing personas with successor personas derived from mistake patterns in board decision histor...

Security Scan

The skill's code, install spec, and runtime instructions are consistent with its stated purpose (local, ledger-backed persona respawn) and it only requires local state-path configuration and Node/tsx to run.

Purpose & Capability

Name/description (persona respawn from ledger history) align with required binaries (node, tsx), the npm package install, and the code which reads/writes board artifacts under a configured consensus state path. Required env vars (CONSENSUS_STATE_FILE, CONSENSUS_STATE_ROOT) are coherent with a filesystem-backed state store.

Instruction Scope

SKILL.md and run.js/index.mjs limit runtime actions to reading the configured consensus state and writing persona_respawn/persona_set artifacts. There are no unexpected network calls, credential reads, or instructions to access unrelated system files.

Install Mechanism

Install uses a published npm package (consensus-persona-respawn) and depends on consensus-guard-core and tsx; this is an expected and traceable mechanism. No downloads from arbitrary URLs or extract-from-URL steps are present.

Credentials

The skill declares only state-path environment variables (CONSENSUS_STATE_FILE, CONSENSUS_STATE_ROOT) and no secret tokens. The code itself calls resolveStatePath(opts) rather than reading process.env directly, but requiring state-path env vars is proportionate to a filesystem-backed ledger.

Persistence & Privilege

The skill is not always-on (always:false), does not request system-wide privileges, and only writes artifacts under the configured consensus state path. It does not modify other skills' configs.

Assessment

This skill appears internally consistent for local, ledger-backed persona maintenance. Before installing: (1) confirm CONSENSUS_STATE_FILE / CONSENSUS_STATE_ROOT point to the intended state JSON (or supply statePath in opts) so artifact writes go to the right place; (2) review the behavior of consensus-guard-core/writeArtifact in your environment to ensure artifact writes are acceptable; (3) run the included tests in a disposable environment to verify expected behavior; (4) note that the package has no external credential or network requirements in shipped logic, but you should still pin dependencies and review upstream packages if you plan to run this in production.

consensus-persona-respawn is the adaptive maintenance loop for persona governance.

What this skill does

• identifies dead/weak personas by trigger or reputation threshold
• mines historical decision artifacts for mistake patterns
• generates successor persona profiles informed by those failures
• writes persona_respawn and updated persona_set artifacts
• keeps governance panel quality from stagnating

Why this matters

A static evaluator panel drifts over time. This skill provides lifecycle renewal so consensus quality improves instead of degrading.

Ecosystem role

Consumes persona-engine outputs for long-term adaptation and ties directly into board-ledger evidence.

Best use cases

• long-running agent teams
• recurring decision domains with repeated failure classes
• autonomous systems requiring evaluator maintenance

Runtime and network behavior

• runtime binaries: node, tsx
• network calls: none in shipped respawn logic
• environment config read by this package: CONSENSUS_STATE_FILE, CONSENSUS_STATE_ROOT
• filesystem writes: board/state artifacts under the configured consensus state path

Dependency trust model

• consensus-guard-core is the first-party consensus package used in runtime execution
• versions are semver-pinned in package.json for reproducible installs
• this skill does not request host-wide privileges and does not mutate other skills

Install

npm i consensus-persona-respawn

Quick start

node --import tsx run.js --input ./examples/input.json

Tool-call integration

This skill is wired to the consensus-interact contract boundary (via shared consensus-guard-core wrappers where applicable):

• readBoardPolicy
• getLatestPersonaSet / getPersonaSet
• writeArtifact / writeDecision
• idempotent decision lookup

This keeps board orchestration standardized across skills.

Invoke Contract

This skill exposes a canonical entrypoint:

• invoke(input, opts?) -> Promise<OutputJson | ErrorJson>

invoke() executes persona replacement based on lineage and failure patterns. Reputation deltas are expected from consensus-persona-engine outputs.