From c0ef8bdd81144d5a740d4f84fe68d6f6e97768c5 Mon Sep 17 00:00:00 2001 From: Perseus Computing <51974392+tcconnally@users.noreply.github.com> Date: Wed, 1 Jul 2026 22:35:24 +0000 Subject: [PATCH] docs: rename Mneme -> Perseus Vault Product renamed Mneme -> Perseus Vault (perseus-vault repo, v2.9.0). Updates brand prose, ASCII/HTML diagram labels, and broken repo links. mimir_*/mneme_* tool-name aliases and machine-readable IDs left unchanged where they are stable API surfaces. --- CHANGELOG.md | 4 ++-- ROADMAP-1.0.md | 4 ++-- ROADMAP.md | 4 ++-- openapi.yaml | 2 +- prompts/plutus-roadmap-2026-2027.md | 2 +- 5 files changed, 8 insertions(+), 8 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4eb3f81..b92552a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,7 +11,7 @@ ledger is now an auditable mirror of Stripe (refunds, disputes, and failed payments reverse it idempotently); every money- and quota-bearing input is guarded; ingest and auth are hardened; self-serve export and a token-scoped admin API are in; and the `/v1` OpenAPI spec plus the DB forward-compatibility policy -are published as the frozen contract Perseus and Mneme build against. An internal +are published as the frozen contract Perseus and Perseus Vault build against. An internal security review (documented in `docs/security-review-2026-06-27.md`) cleared the money/auth/tenant surfaces; an external review remains the gate before any public launch. @@ -27,7 +27,7 @@ launch. ### Added - **OpenAPI 3.1 spec for `/v1/*` + the forward-compatibility contract (#67).** [`openapi.yaml`](openapi.yaml) documents the frozen `/v1` surface (usage ingest, - spend export, admin) that Perseus/Mneme build against. [`docs/schema.md`](docs/schema.md) + spend export, admin) that Perseus/Perseus Vault build against. [`docs/schema.md`](docs/schema.md) states the database forward-compat policy (additive-only within 1.x; breaking changes need a new major), and [`docs/postgres.md`](docs/postgres.md) records the ADR keeping the single-file SQLite backend for 1.0 while documenting the diff --git a/ROADMAP-1.0.md b/ROADMAP-1.0.md index d63bfbc..413dd12 100644 --- a/ROADMAP-1.0.md +++ b/ROADMAP-1.0.md @@ -51,7 +51,7 @@ The deep-review findings that can corrupt billing data. Root cause for most: rea - *Exit:* an external security-review pass on the public surface. ### v0.7.1 — Foundation hardening *(carryover + hygiene; precondition to v0.8)* -A 2026-06-26 foundation review verified v0.6/v0.7 against `main`. Most fixes landed; the items below were closed but only partially resolved, plus new hygiene gaps. Close these before the v0.8 feature work — 1.0 is the convergence gate for Perseus/Mneme, so the contract must be honest and stable first. +A 2026-06-26 foundation review verified v0.6/v0.7 against `main`. Most fixes landed; the items below were closed but only partially resolved, plus new hygiene gaps. Close these before the v0.8 feature work — 1.0 is the convergence gate for Perseus/Perseus Vault, so the contract must be honest and stable first. - **#28** prepaid hard-stop: default-on for prepaid orgs + enforce *inside* the debit transaction (currently off-by-default and racy). - **#30** atomic `balance_after` + free-tier quota race: wrap the ledger read-modify-write in `BEGIN IMMEDIATE` (or one conditional `INSERT…SELECT`). - **#32** CSRF: fail closed in `_same_origin` when `base_url` is unset, and/or add a per-session token. @@ -110,4 +110,4 @@ Already done: README reframed, `pip install plutus-agent`, GHCR image, hosted da | Docs | README + 3 docs | full reference + guides | ## Sequencing note -v0.6 and v0.7 **shipped** (0.6.0 / 0.7.0), but the 2026-06-26 review surfaced partial fixes + hygiene gaps now collected in **v0.7.1 — Foundation hardening**. Close v0.7.1 before any public push and before wiring Plutus into Perseus/Mneme (the convergence-gated-on-1.0 decision). v0.8 (Team tier + integrations) is the revenue/distribution lever and can proceed in parallel, but the 1.0 tag waits on v0.7.1 + an external security-review pass + a frozen API/schema. +v0.6 and v0.7 **shipped** (0.6.0 / 0.7.0), but the 2026-06-26 review surfaced partial fixes + hygiene gaps now collected in **v0.7.1 — Foundation hardening**. Close v0.7.1 before any public push and before wiring Plutus into Perseus/Perseus Vault (the convergence-gated-on-1.0 decision). v0.8 (Team tier + integrations) is the revenue/distribution lever and can proceed in parallel, but the 1.0 tag waits on v0.7.1 + an external security-review pass + a frozen API/schema. diff --git a/ROADMAP.md b/ROADMAP.md index 0db1082..1986c20 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -9,7 +9,7 @@ Plutus (Greek god of wealth) is a credit & spend monitor and runway-based model router for Hermes Agent. It tracks money draining from LLM providers and automatically rebalances -routing toward the provider with the most projected days-left. Part of the Perseus / Mneme / +routing toward the provider with the most projected days-left. Part of the Perseus / Perseus Vault / Minions toolset. Tracks three providers today: **deepseek, anthropic, google**. @@ -132,7 +132,7 @@ Tracks three providers today: **deepseek, anthropic, google**. - Enterprise SSO (SAML/OIDC) for the Plutus dashboard. ### v3.3 — Usage-Based Billing for Managed Services (Q2 2030) -- Metered billing for Mneme Cloud + Perseus Cloud: per-entity, per-render, per-synthesis-call. +- Metered billing for Perseus Vault Cloud + Perseus Cloud: per-entity, per-render, per-synthesis-call. - Free tier: 10K entities, 100 renders/day, 10 syntheses/day. - Pro tier: unlimited entities, 1K renders/day, 100 syntheses/day. - Enterprise: custom limits, SLA, dedicated infrastructure. diff --git a/openapi.yaml b/openapi.yaml index 535cf94..2fe9fdc 100644 --- a/openapi.yaml +++ b/openapi.yaml @@ -6,7 +6,7 @@ info: The Plutus `/v1` HTTP API — usage ingest, spend export, and operator admin for the self-hostable LLM-spend billing engine. - **This document is the frozen 1.0 contract.** Perseus and Mneme build against + **This document is the frozen 1.0 contract.** Perseus and Perseus Vault build against it; within the 1.0 major line it changes only additively (new optional fields, new endpoints). Breaking changes require a `/v2`. See `docs/SCHEMA.md` for the paired database forward-compatibility policy. diff --git a/prompts/plutus-roadmap-2026-2027.md b/prompts/plutus-roadmap-2026-2027.md index 20689bc..db8dc45 100644 --- a/prompts/plutus-roadmap-2026-2027.md +++ b/prompts/plutus-roadmap-2026-2027.md @@ -111,7 +111,7 @@ Priority tests, in order: ### Standalone OSS "LLM FinOps" positioning - Launch post, comparison page, "awesome-llm-ops" listing -- Decouple from Perseus/Mneme/Minions toolset branding +- Decouple from Perseus/Perseus Vault/Minions toolset branding ## Design principles (non-negotiable) 1. **Never lose a key.** Config writes back up first and refuse to drop any provider block or API key.