What makes it different

Four things every projection carries.

Answers without evidence are a liability. Proteus objects ship with the signal you need to decide whether — and how — to act on them.

01 / PROVENANCE

Every field traces back to a source.

Each value is attached to the knowledge entries, retrieval hits, or Hermes observations that produced it. No floating claims. No "because the model said so."

knowledge retrieval hermes
02 / CONFIDENCE

Scores that tell you when to trust them.

Per-field confidence with named, documented bands — speculative, provisional, supported, corroborated, authoritative — and a calibration log so future labels can tune them.

5 bands per-field calibration log
03 / GAPS

Missing evidence is first-class data.

Schema-required fields without corroborating sources become tracked gaps, not silently defaulted values. You see what the projection doesn't know, with suggested next actions.

schema-aware enforced at persist
04 / POLICY

Action eligibility gated by evidence.

Every object carries a policy decision: is this safe to display, act on, or automate? Synthetic evidence downgrades actions. Human review is requested when it should be.

action_allowed requires_review freshness_ok
How projection works

From a question to a governed object.

Five stages, each leaving artifacts you can inspect. The viewer shows you every one.

01 / PLAN
Gather evidence
EvidencePlanner pulls from Knowledge, Retrieval, Hermes, and bootstrap packs.
02 / PROJECT
Shape the object
Typed projectors extract fields using pluggable extractors — regex today, judges tomorrow.
03 / SCORE
Confidence per field
Per-field signals — source count, trust, freshness, contradictions — combined into a band.
04 / VALIDATE
Gaps and policy
Schema requirements enforced at persist. Synthetic evidence marks human-review-required.
05 / PERSIST
Delta lineage
Every projection becomes a versioned state with field-level deltas. History is queryable.
Capabilities

Built for operators, not chat UX.

Proteus is infrastructure. Your agents, dashboards, and automations read from it — and every read has receipts.

⦿
Typed object registry
RunbookProcedure, SupportResolution, IncidentSummary out of the box. Register your own schemas and projectors via one callable — no framework rewrite.
Versioned lineage
Delta-backed persistence means every version knows what changed from the last. Lineage endpoints return field-level diffs, not just timestamps.
Lifecycle state machines
Draft → Reviewed → Published → Archived. Transitions are validated, audited, and gated by policy decisions on the underlying object.
Pluggable extractors
Extraction lives behind a Protocol seam. Ship with deterministic regex. Upgrade to a judge LLM without touching projector code.
Synthetic flagging
Evidence from bootstrap packs and synthetic adapters automatically downgrades the object's policy — no accidental automation on demo data.
Calibration log
Every emitted score is logged with its band. When labeled outcomes arrive, you replay the log to tune bands against reality.

See Proteus project a live object.

The viewer accepts a query, gathers evidence from your running Solstice stack, and returns a fully-annotated projection — data, confidence, provenance, gaps, policy, lineage — all in one screen.