Example

Review Session

A read-only review contract that produces findings without becoming the implementer.

Persona	behavior-reviewer
Directive	behavior-preserving-review
Kits	review-guardrails
Authorized Skills	read-only-review
Forbidden Skills	code-editing, deployment-runner

Adopt This Root

Copy the closest example root into your project.
Rename the copied folder to .personakit.
Revise the session, persona, directive, kits, and skills for your lane.
Run personakit validate before relying on the root.
Inspect the resolved contract before exporting handoff context.

Inspect The Contract Pieces

Start with the session file; it shows which persona, directive, kits, and skills compose this lane.

Session Sessions/behavior-review.session.json Persona Packs/personas/behavior-reviewer.persona.json Directive Packs/directives/behavior-preserving-review.directive.json Kit Packs/kits/review-guardrails.kit.json Authorized Skill Packs/skills/read-only-review.skill.json Forbidden Skill Packs/skills/code-editing.skill.json

This example is intentionally non-executing. It shows how PersonaKit can define a review identity without authorizing code editing, deployment, or tool-driven follow-up work.

Use this when the important boundary is separation of authority: the reviewer can identify defects, but cannot quietly become the fixer.

Authority Split

The reviewer reports confirmed defects, risks, and missing validation. If a fix is needed, implementation waits for explicit approval and a separate work mode.

Key Contract Signal

forbiddenSkillIds: code-editing, deployment-runner

Runnable Commands

cd Site/public/examples/review-session
personakit validate --root personakit-root
personakit contract --root personakit-root --session behavior-review
personakit export --root personakit-root --session behavior-review

Expected Validation Shape

Validation summary: personas=1 kits=1 directives=1 intents=0 references=0 skills=3 essentials=1 errors=0

What To Inspect

The session resolves to behavior-reviewer and behavior-preserving-review.
read-only-review is authorized.
code-editing and deployment-runner are forbidden.
The directive requires stopping if implementation is needed.
The export path produces human-readable grounding without launching an agent.

Why This Matters

Without a separate review session, an assistant may blend reviewer and implementer behavior. PersonaKit makes review identity explicit and keeps execution authority separate.