From acf4d37c86c7b768524b051002244ed7c396bbf7 Mon Sep 17 00:00:00 2001 From: Jose Daniel Date: Tue, 11 Aug 2026 20:29:31 -0500 Subject: [PATCH] docs: correct Manitos integration name --- docs/first-time-setup.md | 4 ++-- docs/jules-review-prompt.md | 4 ++-- docs/manitos-integration.md | 12 ++++++------ 3 files changed, 10 insertions(+), 10 deletions(-) diff --git a/docs/first-time-setup.md b/docs/first-time-setup.md index 1c29b54..f8e4ccc 100644 --- a/docs/first-time-setup.md +++ b/docs/first-time-setup.md @@ -9,7 +9,7 @@ Application -> POST /v1/traces/batch -> Observer API -> SQLite/PostgreSQL -> analytics/evaluations ``` -The ManitOS ingestion route is an optional compatibility integration. A general +The Manitos ingestion route is an optional compatibility integration. A general application does not need it. ## 1. Start Observer locally @@ -158,7 +158,7 @@ Before exposing Observer outside a development machine: The generic integration gate report `observer.integration.passive_gate.v2` is optional. It can validate a custom -runtime integration without adopting the ManitOS-specific ingestion contract. +runtime integration without adopting the Manitos-specific ingestion contract. ## Package publication ownership diff --git a/docs/jules-review-prompt.md b/docs/jules-review-prompt.md index 5dbe636..01b56a7 100644 --- a/docs/jules-review-prompt.md +++ b/docs/jules-review-prompt.md @@ -14,7 +14,7 @@ branch unless the task explicitly asks for a PR. Context: - Product name is "Observer" (a.k.a. "LLM Observatory", package - magic-lab-observer). "ManitOS" is an integration lane, not the product name. + magic-lab-observer). "Manitos" is an integration lane, not the product name. - Read AGENTS.md at the repository root and follow its review output contract exactly (Summary / Findings / Checklist / Verdict). - Baseline: for delta comparison. @@ -31,7 +31,7 @@ What to review: 5. Diff against the baseline commit: list changed files, new/removed public endpoints or SDK exports, and any migration changes. 6. Consistency: scan for wrong product names ("LLM Observatory service", - "ManitOS" as product), stale test counts in README/docs, and docs that + "Manitos" as product), stale test counts in README/docs, and docs that contradict code. 7. Do not report "none" as a finding. Every finding must carry evidence (path:line) and a concrete action. If nothing is actionable, state the diff --git a/docs/manitos-integration.md b/docs/manitos-integration.md index 2fe0637..574e6cf 100644 --- a/docs/manitos-integration.md +++ b/docs/manitos-integration.md @@ -1,6 +1,6 @@ -# ManitOS telemetry integration +# Manitos telemetry integration -ManitOS is one supported Observer integration. It uses an additive, versioned, +Manitos is one supported Observer integration. It uses an additive, versioned, retry-safe ingestion contract; existing `/v1/traces` clients remain supported. ## Public contract @@ -91,7 +91,7 @@ does not render `actor_id_hash`. The compatibility endpoint `GET /v1/analytics/manitos-quality` provides bounded, metadata-only aggregate fields for this integration. Existing field names are -retained to avoid breaking clients; they should not be interpreted as ManitOS +retained to avoid breaking clients; they should not be interpreted as Manitos production policy or release criteria. ## Optional integration gate @@ -100,7 +100,7 @@ Observer includes an optional metadata-only evaluation utility. New automation should use `observer-integration-passive-gate --generic-report`, which emits the additive `observer.integration.passive_gate.v2` report at `.observer-state/integration-gate-report.json` unless another path is supplied. -Its evaluation parameters are caller configuration, not Observer or ManitOS +Its evaluation parameters are caller configuration, not Observer or Manitos production policy. The v2 report excludes configured endpoint and output paths as well as legacy @@ -113,8 +113,8 @@ does not move, rewrite, or delete an existing v1 report. ## Runtime configuration -The ManitOS exporter is opt-in. Integration users may configure these published -environment variables in the ManitOS runtime: +The Manitos exporter is opt-in. Integration users may configure these published +environment variables in the Manitos runtime: ```bash MANITOS_OBSERVER_ENABLED=1