proserpina 0.3.0

Multi-agent critique and cross-examination pipeline for documents requiring intellectual rigor — provider-agnostic interaction-graph engine with pluggable LLM backends
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49

# Panels

A **panel** is a named set of critic personas. Pick one with `--panel <name>`.

## Built-in panels

| Panel | Critics | Use |
|---|---|---|
| `default` | Devil's Advocate | a quick single-critic pass (the default) |
| `duo` | Devil's Advocate + Methodologist | a second lens |
| `panel` | + Red Team, Domain Expert, Editor | full cross-examination |

## Custom panels

Define your own under `[panels.NAME]` in the credentials file:

```toml
[panels.red-team]
personas = [
  { name = "Skeptic", framing = "Doubt everything.", focus = "assumptions" },
  { name = "Nitpicker", framing = "Find the small flaws.", focus = "details" },
  { name = "Architect", framing = "Question the structure.", focus = "design" },
]
```

Each persona is `{ name, framing?, focus? }`. Then:

```bash
proserpina critique plan.md --panel red-team
```

A config-defined panel overrides a same-named built-in (so you can redefine
`default`). Names must be unique within a panel — agents are keyed by persona
name.

## How providers get assigned

Each critic in the panel is assigned a provider drawn (seeded, reproducibly)
from your authed providers. So a `--panel panel` run with DeepSeek + Z.ai
authed will fan the five critics across both. The seed (printed in every
report) makes the assignment reproducible.

## Discover panels

```bash
proserpina capabilities | jq '.panels'
```

Lists built-in + config-defined panel names.