PERSONA-1: persona pipeline plugin specification

[JarbasAl]

Companion issue: #50

Summary

Defines the persona pipeline plugin — a complete conversational agent that, when active for a session, claims every utterance that reaches its pipeline stage and generates natural-language responses.

What the spec covers

• §3 — persona_id session field: absent = no-persona mode (deterministic pipeline); present = named persona active
• §4 — No-persona mode: persona stages MUST decline except for embedded commands
• §5–§6 — Summon (self-summon via Match.updated_session, or external via session field) and dismiss
• §7 — Match contract: two routes — embedded persona command detection (always active) and utterance claim when persona is active
• §8 — Handler contract: standard PIPELINE-1 dispatch; multi-turn via CONVERSE-1; session.fallback_pipeline_id for per-persona fallback chains; conversation history via SESSION-2 MAY-internal pathway
• §8.5 — Out-of-band query: ovos.persona.query / ovos.persona.answer — direct text-in/text-out bypassing the pipeline; session for history from context.session.session_id
• §9 — Multiple persona coexistence: each plugin declares supported persona_ids; at most one active per session
• §10 — Pipeline positioning: after deterministic intents and converse, before fallback
• §11 — Bus surface
• §12 — Conformance

Bus surface

Topic	Purpose
ovos.persona.query	Out-of-band query to a persona
ovos.persona.answer	Persona's generated response
ovos.persona.list	Enumerate supported persona identities
ovos.persona.list.response	Supported-identity listing
ovos.persona.register	Runtime persona registration
ovos.persona.deregister	Runtime persona deregistration

[coderabbitai]

Warning

Review limit reached

@JarbasAl, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 36 minutes and 3 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 014080cd-9e2e-4f33-8a3c-b6fe68e02478

📥 Commits

Reviewing files that changed from the base of the PR and between 03e8fcf and 9bde58d.

📒 Files selected for processing (4)

• APPENDIX.md
• CHANGELOG.md
• appendix/persona-flow.md
• persona.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch spec/persona

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[JarbasAl]

Merge-ready (MERGEABLE, dev merged in). Template conformance: header present (OVOS-PERSONA-1 v1 Draft), RFC-2119 boilerplate present, 12 numbered sections plus See also. Fixed: OVOS-PERSONA-1 was absent from README spec table and CHANGELOG — both added. Spec filename persona.md is already using clean naming (consistent with #55). Note: after #55 merges, GLOSSARY.md in this branch will need ovos-intent-*.md links updated.