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
50
51
52
53
54
55

# Installing and Configuring

## Install

```bash
cargo install proserpina
```

This installs the binary with default features. For the full feature set
(HTTP backend, roster, summarizer, JSON output):

```bash
cargo install proserpina --features cli,backend-http,json
```

> **Note:** `cargo install proserpina` installs with *default* features only (`std`).
> To actually critique documents with real LLMs, you need `backend-http`. If you
> install with defaults, Proserpina falls back to the echo backend with a notice.
> The recommended install is `cargo install proserpina --features cli,backend-http,json`.

## Build from source

```bash
git clone https://github.com/Industrial-Algebra/Proserpina
cd Proserpina
cargo build --features cli,backend-http,json
```

## Verify

```bash
proserpina --version
proserpina capabilities   # overview; check the `authed` field
```

## Authenticate

```bash
proserpina auth login deepseek    # API key prompt → validate → store
proserpina auth login openai      # OAuth browser flow
proserpina auth check             # validate all stored keys
```

## The credentials file

All configuration lives in one TOML file, discovered in order:

1. `--config <path>` CLI flag
2. `$PROSERPINA_CONFIG`
3. `$XDG_CONFIG_HOME/proserpina/credentials.toml`
4. `~/.config/proserpina/credentials.toml`

A missing file is not an error — Proserpina proceeds with whatever provider keys
are in the environment. See [Providers and Credentials](./providers.md) for
the format.