@pellux/goodvibes-agent 1.1.7 → 1.3.0

package/src/agent/competitive-feature-inventory.ts

@@ -0,0 +1,294 @@
+export type CompetitorId = 'openclaw' | 'hermes' | 'odysseus';
+
+export type GoodVibesCompetitiveStatus = 'leading' | 'parity' | 'partial' | 'gap';
+
+export type GoodVibesOwner = 'agent' | 'connected-host' | 'companion' | 'release';
+
+export interface CompetitorFeatureSignal {
+  readonly competitor: CompetitorId;
+  readonly evidence: string;
+}
+
+export interface CompetitiveFeatureInventoryItem {
+  readonly id: string;
+  readonly userOutcome: string;
+  readonly targetStandard: 'parity' | 'better';
+  readonly bestInClassRequirement: string;
+  readonly goodVibesStatus: GoodVibesCompetitiveStatus;
+  readonly owners: readonly GoodVibesOwner[];
+  readonly goodVibesNow: string;
+  readonly nextMoves: readonly string[];
+  readonly competitorSignals: readonly CompetitorFeatureSignal[];
+}
+
+export const COMPETITIVE_FEATURE_INVENTORY: readonly CompetitiveFeatureInventoryItem[] = [
+  {
+    id: 'one-assistant-mental-model',
+    userOutcome: 'The user asks one assistant for help and does not need to understand package, host, daemon, or execution-boundary ownership.',
+    targetStandard: 'better',
+    bestInClassRequirement: 'Every setup, chat, automation, channel, and execution route is presented as one assistant with visible safety and recovery state.',
+    goodVibesStatus: 'leading',
+    owners: ['agent', 'connected-host', 'companion'],
+    goodVibesNow: 'Agent has a strong operator workspace, visible TUI Home cockpit, first-class `route action:"plan|status"`, `setup action:"repair"`, and `agent_harness mode:"summary|route_decision|setup_repair"` that all start from the same assistant-first lanes: setup, chat/model, project work, Personal Ops, research/docs, background work, and safety/recovery with user-facing next actions. The route planner accepts a plain user task, returns the preferred visible route, alternatives, missing fields, confirmation boundary, workspace matches, and harness mode matches, so the model can choose Agent-owned setup, settings, Personal Ops, research, autonomy, execution, delegation, computer/browser, workspace, host, device, channel, security, Local Context, or Knowledge paths without asking the user to understand package ownership. Host/daemon health, doctor, readiness, service, and compatibility wording goes directly to `host action:"status"` before repair or lifecycle effects. Normal settings/configuration wording goes directly to `settings action:"list"` before set/reset/import effects. Model provider, local-cookbook, local server smoke, and route-fit wording goes directly to `models action:"provider|local|smoke|route"` before credential, smoke, benchmark, or route-change effects. Personal Ops briefing, saved queue, fresh inbox/calendar read, and connector setup wording goes directly to `personal_ops action:"briefing|queue|intake|lane"` before live provider reads or effects. Direct reminder, schedule, cron, and schedule lifecycle wording goes directly to `schedule action:"list"` before confirmed schedule effects. Command-shaped background work goes directly to `execution action:"processes"` plus first-class `terminal`/`process` controls, interactive PTY/stdin/sudo wording goes directly to `execution action:"process_capabilities"` before hidden process starts or credential effects, while broader ongoing or watcher-like background work stays on autonomy intake. External memory-provider, backend, cross-session sync, import/export, and named-provider wording goes directly to `memory action:"provider"` or the external provider checklist before any provider write, sync, credential, or import/export effect. Browser-backed research runner wording goes directly to `research action:"runner"` readiness, and visual research report rendering wording goes directly to `research action:"plan"` plus report artifacts before browser/PWA rendering is claimed. Voice workflow, TTS-provider, browser cockpit, and PWA wording goes directly to `device action:"voice|provider"` or `computer action:"browser"` before capture, playback, picker, or browser-open effects. Channel setup, triage, delivery-receipt, and send wording goes directly to `channels action:"setup|triage|deliveries|channel"` before confirmed external delivery. Permission posture, security finding, and blocked-action wording goes directly to `security action:"status|finding|explain"` before policy changes or risky work. Support-bundle, saved-session/bookmark/continuity, and release/audit evidence wording goes directly to `support action:"status|bundle"`, `sessions action:"list|get"`, and `audit action:"readiness|evidence|item|artifact"` before bundle export/import/share, session lifecycle, or audit drill-in effects. File undo/redo/recovery wording goes directly to `execution action:"recovery"` before any confirmed snapshot mutation. Media generation wording goes to media provider readiness plus confirmed `agent_media_generate` saved artifacts, with no inline bytes or silent Knowledge promotion. Screenshot, browser-navigation/control, screen-observation, and desktop-control wording goes directly to `computer action:"plan"` before any live UI tool is considered. Setup repair accepts the current setup blocker or a plain target such as host/auth/service, then returns the safest next route: token repair, connected-host status, services.status receipt, user-run bootstrap commands, or no lifecycle action when the host is already reachable. Technical host, daemon, provider, MCP, and delegation details remain available as diagnostics and confirmation boundaries instead of first-screen ownership questions.',
+    nextMoves: [
+      'Keep adding plain-language route fixtures for any user task that still falls through to technical ownership language.',
+      'Promote new daemon and SDK contracts into first-class Agent routes only after they have visible status, confirmation, and recovery semantics.',
+    ],
+    competitorSignals: [
+      { competitor: 'openclaw', evidence: 'Gateway is described as the control plane while the assistant is the product.' },
+      { competitor: 'hermes', evidence: 'CLI, gateway, and messaging all expose one Hermes assistant conversation model.' },
+      { competitor: 'odysseus', evidence: 'Web workspace combines chat, agents, memory, docs, email, calendar, and tasks in one app.' },
+    ],
+  },
+  {
+    id: 'first-run-and-always-on-setup',
+    userOutcome: 'A fresh user can install, configure models, start the always-on runtime, and reach the assistant without manual topology work.',
+    targetStandard: 'better',
+    bestInClassRequirement: 'One guided flow verifies dependencies, installs or starts the host, configures auth, pairs channels, and leaves a working assistant.',
+    goodVibesStatus: 'leading',
+    owners: ['agent', 'connected-host', 'release'],
+    goodVibesNow: 'Agent has onboarding, diagnostics, a first-class `setup action:"status|item|repair|checkpoint|save_checkpoint|clear_checkpoint|token|smoke|finish|import_settings"` adapter, first-class `settings action:"list|get|set|reset|import"` UX for Agent settings plus redacted GoodVibes settings import preview/apply, first-class `host action:"status|capabilities|capability|services|service|methods|method"` UX for connected-host diagnostics, and a visible Start checklist that keeps connected-host auth, install smoke, and Browser/PWA readiness beside runtime/model setup. First-run onboarding now renders visible `Option` / `Change` controls, compact redacted current -> proposed setting previews, command-free Local Context setup cards, plain prompt-receipt controls, and onboarding result panes that suppress internal `Command:` lines. The shared first-run setup wizard orders connected-host readiness, connected-host auth, provider/model access, install smoke, local model readiness, Agent Knowledge, local behavior, channels, Browser/PWA readiness, automation review, browser/desktop control, delegation, and finish state with progress, current-step route hints, backtracking routes, setup-smoke rerun/save routes, saved-smoke repeated-blocker focus, and Agent-owned saved setup checkpoints that resume across restarts without storing user prompt text while reporting stale-checkpoint auto-advance evidence when a saved step is already ready. Setup wizard history now records stable timestamped entries for Agent-owned setup checkpoints, saved setup-smoke artifact receipts, durable connected-host setup receipt artifacts, and live connected-host setup receipt read-model snapshots when the SDK/daemon publishes them; ready service/auth/install-smoke/browser-PWA receipts from either source auto-advance matching setup rows and remove release receipt gaps, while blocked or failed durable receipts remain visible in history without satisfying closeout. The Start pane shows remaining durable receipt gaps for connected-host service/auth/install-smoke/browser-PWA evidence instead of pretending the daemon has published them, and setup closeout accepts a satisfying durable install-smoke receipt instead of contradicting a ready setup row. Connected-host setup includes a read-only setup repair decision route, live service probe evidence, token-safe auth posture with exact pairing route ids, confirmed SDK-backed local operator-token create/repair with no raw-token output, recommended diagnostic/status cards, confirmed service install/start/restart routes that stay inspect-first unless service status proves need, setup `serviceLifecycleDecision` gates, service repair-card success criteria, `agent_operator_method` certified receipt outcomes plus exact install/start/restart/no-action lifecycle decisions from services.status receipts, offline bootstrap commands for missing-host setup, a confirmed token-safe setup smoke route with optional durable redacted evidence artifacts from package binary to first assistant turn, Home/setup summary surfacing for the latest smoke result plus smoke history/trend/frequent blockers, `setupWizard.closeout` and top-level `setupCloseout` decisions that reduce critical blockers, smoke evidence, durable receipt evidence, and the user completion marker into blocked/run-smoke/finish/complete states, confirmed setup finish marker writes, setup checkpoint direct model routes, visible Start actions to show/save/clear the checkpoint, and fixtures for missing host, unreachable host, missing token, model-unconfigured, durable-receipt auto-advance, live setup-read-model auto-advance, and ready-closeout paths.',
+    nextMoves: [
+      'Keep per-step setup receipt schemas aligned with any new SDK/daemon first-run receipt versions before release evidence accepts them.',
+      'Add real connected-host CI fixtures for ordered setup receipt event streams once the daemon publishes stable stream snapshots outside unit tests.',
+    ],
+    competitorSignals: [
+      { competitor: 'openclaw', evidence: 'Onboarding can install the Gateway daemon so it stays running.' },
+      { competitor: 'hermes', evidence: 'Installers handle runtime dependencies and the setup wizard configures the gateway.' },
+      { competitor: 'odysseus', evidence: 'Docker and native setup generate an admin account and open a local web UI.' },
+    ],
+  },
+  {
+    id: 'models-and-local-model-cookbook',
+    userOutcome: 'The user can choose cloud, subscription, or local models without knowing provider-specific setup details.',
+    targetStandard: 'better',
+    bestInClassRequirement: 'Model setup recommends the best available route, detects local servers, benchmarks fit, and can help download or serve local models.',
+    goodVibesStatus: 'leading',
+    owners: ['agent', 'connected-host'],
+    goodVibesNow: 'First-class `models action:"status|route|local|providers|provider|smoke"` UX now fronts provider routing, subscription posture, local compatible provider discovery, model pickers, visible route-readiness inspection, and a hardware-scored local model cookbook for Ollama, llama.cpp, vLLM, and local OpenAI-compatible servers; lower-level harness modes remain available for detailed inspection. The route planner now prefers `models action:"local"` for Ollama/local cookbook/hardware-fit wording, `action:"smoke"` for local server health checks, `action:"provider"` for provider account/subscription setup, and `action:"route"` for context/tool/latency/cost/privacy route-fit requests before credential, smoke, benchmark, or route-change effects. Model routes and local recipes expose one readiness score across latency, context window, tool support, vision, cost, and privacy. Exact model-route readiness now includes providerHealth posture that separates SDK provider-health type availability, daemon publication status, Agent consumption status, missing signals, provider-level fallback, exact route-level daemon read models, live latency, rate-limit posture, and redacted error posture when a daemon-published read model is reachable; saved local benchmark artifacts now expose stable per-candidate route latency evidence and exact model-route readiness consumes the newest measured benchmark latency for matching local candidates and cloud baselines while keeping benchmark task-fit and winner evidence separate from live provider-health posture. The cookbook scans local CPU/RAM/platform, applies safe accelerator hints, ranks fit, returns setup plans with download/start guidance, local endpoint candidates with exact endpoint inspect routes, model-list smoke commands, smoke success criteria, failure triage, confirmed local smoke checks, provider-add and refresh route hints, benchmark action routes, a visible Check local servers action, a visible model-lane local benchmark action backed by agent_model_compare, saved benchmark-evidence review, saved local-route benchmark artifacts with per-route latency summaries, and revealed winner judgments that raise matching recipe confidence before any separate default-model apply action. When the SDK/daemon publishes local serving diagnostics read models, the cookbook and exact endpoint routes now consume server version, loaded-model detail, context/tool support, resource pressure, start/repair receipt ids, receipt status, source path, certified schema/version/provenance/publication/publisher metadata, exact confirmed start/repair routes when the host publishes them, and redacted summary metadata without probing local servers or running provider changes.',
+    nextMoves: [
+      'Keep daemon provider-health schema fixtures current for any new route-health fields before accepting release evidence.',
+      'Add connected-host CI coverage for certified local serving diagnostics across newly supported local stacks as host operator methods expand.',
+    ],
+    competitorSignals: [
+      { competitor: 'openclaw', evidence: 'Supports multiple model providers plus subscription auth and model failover.' },
+      { competitor: 'hermes', evidence: 'Supports many providers, OpenRouter, local endpoints, and a managed tool gateway subscription.' },
+      { competitor: 'odysseus', evidence: 'Cookbook scans hardware and recommends or serves models through Ollama, llama.cpp, and vLLM.' },
+    ],
+  },
+  {
+    id: 'omnichannel-inbox-and-delivery',
+    userOutcome: 'The assistant is reachable where the user already communicates and can reply safely on those channels.',
+    targetStandard: 'better',
+    bestInClassRequirement: 'Channel setup is guided, inbound trust is default-safe, delivery is reliable, and the user can inspect every route from one place.',
+    goodVibesStatus: 'parity',
+    owners: ['agent', 'connected-host', 'companion'],
+    goodVibesNow: 'GoodVibes has broad channel adapters, readiness, policy, account inspection, pairing, notification, confirmed send routes, route-planner preference for channel setup/triage/delivery-receipt/send wording, and first-class `channels action:"status|channel|setup|triage|deliveries"` inspection for readiness, one channel, setup guide, triage, and redacted confirmed-send receipt history before any external delivery; `agent_channel_send` remains the confirmed send route. The guide ranks the next channel, walks the user through choosing a surface, enabling it intentionally, inspecting setup schema, configuring secret-backed settings, choosing delivery targets, reviewing allowlist policy, checking live status/doctor output, and sending only one explicitly confirmed test. Channel triage unifies setup blockers, daemon `/api/deliveries` attempts, visible control-plane surface messages, route bindings, and redacted Agent receipts without claiming provider-specific inbox polling.',
+    nextMoves: [
+      'Promote provider-specific unread channel inbox polling only when the connected-host contract publishes a general safe message feed.',
+      'Certify real delivery outcomes per channel before claiming release readiness.',
+      'Attach structured connected-host setup-schema, account, policy, status, and doctor receipts to the channel setup guide when the host publishes stable success/failure evidence.',
+    ],
+    competitorSignals: [
+      { competitor: 'openclaw', evidence: 'Lists broad messaging support across WhatsApp, Telegram, Slack, Discord, iMessage, Matrix, Teams, and more.' },
+      { competitor: 'hermes', evidence: 'Gateway supports Telegram, Discord, Slack, WhatsApp, Signal, CLI, and email.' },
+      { competitor: 'odysseus', evidence: 'Uses browser, email, ntfy, and mobile/PWA surfaces for user reach.' },
+    ],
+  },
+  {
+    id: 'email-calendar-notes-and-tasks',
+    userOutcome: 'The assistant can triage email, draft replies, track calendar context, and act on notes or tasks with reminders.',
+    targetStandard: 'better',
+    bestInClassRequirement: 'Email, calendar, notes, tasks, reminders, and schedules share one reviewed personal operations surface.',
+    goodVibesStatus: 'leading',
+    owners: ['agent', 'connected-host'],
+    goodVibesNow: 'Agent now has a unified Personal Ops workspace and first-class `personal_ops action:"briefing|status|queue|intake|lane|read"` model tool, backed by the existing harness modes. The route planner prefers `personal_ops action:"briefing"` for daily/calendar briefings, `action:"queue"` for saved review queues, `action:"intake"` for fresh provider-read planning, and `action:"lane"` for connector setup posture before live provider reads or effects. The direct tool exposes a read-only daily plan across inbox, agenda, tasks, reminders, routines, delivery, notes, and the autonomy queue, a read-only queue view across saved inbox thread/calendar event review items plus fresh provider-read routes, and model-visible request intake that turns inbox, agenda, task, reminder, note, routine, and delivery asks into the safest lane, route, required fields, next steps, and confirmation boundary. Model-visible lanes for inbox, agenda, notes, work plans, tasks, reminders, routines, schedules, and delivery surface Agent-owned notes, routines, schedule receipts, and delivery channels as live records with safe routes. Email/calendar-capable MCP connectors surface as inspectable setup routes, expanded Personal Ops lanes classify connector tool names into read-only and write-like inbox/calendar capabilities, MCP schemas expand into inbox/calendar operation records with required fields, sample inputs, schema routes, confirmation flags, and fresh-read routes, inbox triage/draft plus calendar agenda/conflict workflow cards expose prerequisites, inspect routes, send/edit confirmation boundaries, and ordered execution plans that separate connector reads, local composition, and confirmed provider effects. Confirmed `personal_ops action:"read"` preserves the existing `run_personal_ops_read` boundary: one read-only inbox/calendar MCP operation with required-field checks, bounded redacted output, normalized review cards for common messages/events/results shapes, optional saved redacted review-card artifacts, and saved review artifacts resurfaced as redacted inbox thread and calendar event queue records with artifact inspect routes, freshness status, confirmed refresh routes when a matching read connector is ready, local draft/reminder follow-up routes, and explicit confirmed provider-effect boundaries. Saved provider-effect receipt artifacts for inbox, calendar, task, and reminder lanes now resurface as read-only effect evidence for send, label, archive, edit, RSVP, update, complete, defer, snooze, delete, and similar confirmed provider outcomes, including provider, operation, normalized status, subject id, redaction posture, failure reason, source tool, artifact inspect route, certified schema/version/publication/publisher/provenance/receipt evidence, and a lane continuation route without claiming fresh provider queue state. When the SDK or daemon publishes durable Personal Ops read models, Agent now consumes fresh provider-backed inbox thread, calendar event, task, and reminder records from `context.platform.readModels.personalOps.*`, related email/calendar/task/reminder read-model paths, and operator SDK mirrors; those records surface current provider ids, labels, snippets, agenda windows, conflict signals, due times, priority, cadence, delivery targets, redacted summaries, source paths, freshness status, certified schema/version/publication/publisher/provenance/receipt ids, queue or lane cards, briefing counts, read-only inspect routes, and confirmed follow-up routes only for published reply/send/label/archive/edit/RSVP/delete/update/complete/defer/snooze routes. Task/reminder lanes also expose visible work-plan, connected-host task, confirmed reminder, autonomous schedule, and connected schedule operation records.',
+    nextMoves: [
+      'Keep Personal Ops provider-read-model schema fixtures current as providers add message state, recurrence, attachment, or delegation fields.',
+      'Add connected-host CI coverage for certified inbox/calendar/task/reminder provider-effect receipt streams as SDK routes expand.',
+    ],
+    competitorSignals: [
+      { competitor: 'openclaw', evidence: 'Showcases mail, calendar, reminders, issues, and personal operating-system workflows.' },
+      { competitor: 'hermes', evidence: 'Messaging gateway includes email and skills include Google Workspace dependencies.' },
+      { competitor: 'odysseus', evidence: 'Ships IMAP/SMTP email triage and local-first CalDAV calendar support.' },
+    ],
+  },
+  {
+    id: 'closed-learning-loop',
+    userOutcome: 'The assistant gets better over time by saving useful memories, skills, and routines only when they are useful and reviewable.',
+    targetStandard: 'better',
+    bestInClassRequirement: 'Learning is automatic enough to be useful, but every durable behavior has provenance, review, rollback, and quality scoring.',
+    goodVibesStatus: 'leading',
+    owners: ['agent'],
+    goodVibesNow: 'Agent has local memory, notes, personas, skills, routines, learned-behavior capture, safe VIBE.md personality discovery from project/global files, safe project context discovery for .hermes.md/HERMES.md/AGENTS.md/CLAUDE.md/HERMES_HOME/SOUL.md/.cursorrules/.cursor/rules/*.mdc files, prompt injection for VIBE.md and project context after secret-looking content scans, direct `vibe action:"status|show|init|import_persona"` routes, /vibe status/init/show/import-persona routes, init/import preview confirmationRoutes, setup posture, Local Context and Personas workspace health counts for applied/loaded/blocked/truncated VIBE.md and project context files, learning-curator personality health cards for blocked/truncated personality files, and opt-in profile starter export/import/application for VIBE.md so users can start with a friendly personality file without persona-registry ceremony, hidden prompt surprises, or profile portability gaps. `context action:"files|file"` exposes target-aware context inspection, loaded/truncated/blocked status, bounded bodies, and direct workspace action route hints from Inspect project context / Inspect one context file. Formal behavior prompt injection still uses only reviewed memory at or above the durable confidence threshold plus reviewed setup-ready skills, routines, bundles, and personas while listing suppressed unreviewed/setup-blocked behavior for curator review; runtime prompt builds now write durable prompt-context receipt ids with turn/source/model/provider, selected and suppressed record refs, segment counts, prompt hash, size, timestamp, and sanitized terminal outcome for completed/error/cancelled turns without storing raw prompt or response text, `context action:"prompt|receipts|receipt"` exposes the applied prompt composition order, recent receipt ids, exact receiptId/turnId/outcomeStatus filters, turn outcomes, selected VIBE.md/project context/memory/routine/skill/persona records, suppressed records, prompt previews on request, and approximate token budget without mutating local context, and Agent Workspace -> Local Context renders a compact prompt receipt timeline with total/completed/error/cancelled/pending counts, latest turn outcome, applied/suppressed counts, bounded outcome detail, exact latest-receipt drill-in, and outcome filter routes. The direct `memory action:"curator|candidate"` route now returns a score-driven prompt plan that shows prompt-active records, suppressed review/setup/low-confidence/personality/consolidation counts, proposal queues, consolidation queues, ordering rules, and exact review routes before durable context expands; it also ranks review, stale, missing-setup, low-confidence, VIBE.md health, duplicate-consolidation candidates with visible diffs/rollback/recreate routes, an ordered duplicate-consolidation batch review plan, confirmed duplicate-consolidation phase helpers for preview/merge/stale/delete/rollback/recreate with durable receipts, delete refusal until duplicates are staged stale, and exact-id post-delete recreate guidance that refuses unsafe id collisions, reviewed-note, completed-work, completed-research, and saved-session memory/behavior proposals, and promotion candidates with existing safe routes. The direct `memory action:"status|provider|list|search|get"` route now exposes local memory counts, direct memory record lookup/search, prompt-active recall, vector stats, embedding-provider doctor warnings, provider inspection, route-planner preference for external provider/backend/sync/import/export setup posture, and external-memory setup contract maps for Honcho, OpenViking, Mem0, Hindsight, Holographic, RetainDB, ByteRover, Supermemory, and daemon-published similar backends with provider-specific next-route packets, certified schema/version/publication/publisher/provenance provider contract checks, setup/status/read/write/sync/forget checklist items, required sync/write receipt fields, certified durable external-memory provider receipt artifact consumption for status/read/write/upsert/import/export/sync/forget evidence, and sanitized live read-model consumption when the connected host or SDK publishes provider records. The direct `memory action:"refinement"` route exposes the SDK-backed Agent Knowledge semantic self-improvement task ledger, task counts, trace tails, job availability, latest job run, task/gap/source ids, and follow-up routes without running searches or changing prompt memory; the confirmed `memory action:"run_refinement"` route runs bounded `KnowledgeService.runRefinement` with optional knowledge-space, source-id, gap-id, limit, maxRunMs, and force scope, then returns closed/blocked/queued task counts, accepted/ingested source ids, task inspect routes, and policy evidence without exposing raw source text or silently promoting local memory. When host or SDK read models publish live external provider records, provider posture consumes sanitized setup/status/read/write/sync readiness, explicit forget/delete or not-supported contract state, secret-safe credential state, prompt-eligibility policy, receipt ids, and read/write/sync/forget route hints plus certified schema/version/publication/publisher/provenance/receipt-stream evidence; when only receipt artifacts exist, posture shows certified receipt id, schema version, publication guarantee, publisher, provenance, operation, status, source count, redaction policy, correlation id, and artifact inspect route without claiming live readiness.',
+    nextMoves: [
+      'Keep Honcho, Mem0, Supermemory, and similar provider schema fixtures current as SDK/daemon contracts add provider-owned receipt fields.',
+      'Add connected-host CI coverage for certified external-memory provider streams once stable daemon fixtures publish real Honcho/Mem0/Supermemory receipts.',
+    ],
+    competitorSignals: [
+      { competitor: 'openclaw', evidence: 'Skills and memory are core extension points.' },
+      { competitor: 'hermes', evidence: 'Markets a closed learning loop with autonomous skill creation, skill improvement, session search, and user modeling.' },
+      { competitor: 'odysseus', evidence: 'Ships persistent memory and skills backed by vector and keyword retrieval.' },
+    ],
+  },
+  {
+    id: 'autonomous-schedules-and-background-work',
+    userOutcome: 'The user can ask for ongoing work in natural language and then supervise, pause, resume, or cancel it from a clear queue.',
+    targetStandard: 'better',
+    bestInClassRequirement: 'Schedules, cron jobs, recurring routines, and long-running tasks are autonomous but never hidden.',
+    goodVibesStatus: 'leading',
+    owners: ['agent', 'connected-host'],
+    goodVibesNow: 'Agent has a first-class `schedule` adapter for schedule action:list/create/remind/edit/run/pause/resume/delete that routes to confirmed natural-language autonomous schedule creation when task, cadence, success criteria, and user request provenance are explicit; reminder scheduling; routine promotion; confirmed connected schedule editing with read-only current-state before/after diffs from schedules.list before confirmation; and allowlisted schedule lifecycle controls. Unconfirmed schedule and routine-promotion previews now return explicit confirmationRoutes instead of vague rerun guidance, and confirmed actions return next routes for schedule list, autonomy queue inspection, run, edit, pause, resume, and delete when applicable. It also has connected schedule posture; a read-only ongoing-work intake selector with trigger workflow posture, watcher receipt success criteria, and a read-only watcher evidence contract for durable run-history receipts, provider source records, redacted event payload descriptors, and queue correlation records across time-based wakeups/schedules, published watchers.create/list/run/start/stop incoming webhook or event watchers, Gmail/email connector-gated triggers, and control-plane event streams; `agent_operator_method` certified watcher receipt outcomes for watchers.create/patch/run/start/stop/delete; and a read-only autonomy queue that maps visible owners, status, inspect routes, cancel/recovery routes, live research runs, live connected-host task records, live approval records, live automation run records, live SDK/daemon watcher run-history/source records, durable watcher/run receipt artifacts, live schedule records, delegated subagent orchestration routes, log tails, diagnostics for task retry/output/correlation, automation telemetry/delivery/route posture, watcher receipt purpose/redaction/source ids, bounded redacted host task and watcher output route/preview descriptors, source ids, normalized available/unavailable controls with reasons, and exact confirmed checkpoint/pause/resume/cancel/edit/control routes where supported, including first-class schedule pause/resume aliases over the daemon enable/disable lifecycle. Durable watcher, watcher-run, automation-run-history, and provider-source receipt artifacts appear in the automation-runs lane with metadata-only redaction posture, provider/source/trigger/run correlation, read-only `agent_artifacts show` inspect controls, and no live run control unless a daemon read model publishes one. Live watcher run/source records from SDK or daemon read models now appear in the same automation-runs lane with bounded redacted host output chunk previews, provider-specific Gmail/email source records, source/checkpoint/correlation diagnostics, read-only provider-source inspect/refresh controls, and exact confirmed watcher cancel/retry/checkpoint/pause/resume controls only when those routes are published by the owning SDK or daemon surface. Agent also exposes visible local Agent orchestration through `agent_orchestration` and `agent_orchestration_agent`, plus tracked local background processes through `background_processes`, `background_process`, and confirmed `run_background_process` start/wait/stop routes with process-style poll/log/kill/write and session-id aliases that feed the same background-work cockpit lane.',
+    nextMoves: [
+      'Add live connected-host verification artifacts from real daemon watcher source streams as soon as CI can publish a stable GoodVibes daemon fixture.',
+      'Broaden provider-specific watcher source fixtures beyond Gmail/email as the SDK and daemon publish additional source-owned watcher families.',
+    ],
+    competitorSignals: [
+      { competitor: 'openclaw', evidence: 'Supports cron, wakeups, webhooks, Gmail triggers, and always-on gateway workflows.' },
+      { competitor: 'hermes', evidence: 'Built-in cron scheduler delivers daily reports, backups, audits, and unattended work.' },
+      { competitor: 'odysseus', evidence: 'Notes, tasks, reminders, and cron-style scheduled tasks can be acted on by the agent.' },
+    ],
+  },
+  {
+    id: 'computer-use-browser-and-shell',
+    userOutcome: 'The assistant can browse, use the computer, run shell commands, edit files, and recover from mistakes with understandable approvals.',
+    targetStandard: 'better',
+    bestInClassRequirement: 'Computer use includes browser control, shell, files, code edits, desktop/device actions, sandboxing, undo, and live tool cards.',
+    goodVibesStatus: 'leading',
+    owners: ['agent', 'connected-host', 'companion'],
+    goodVibesNow: 'Agent exposes local-first execution posture for read/search/analyze, file edit/write, bounded foreground shell commands, web/fetch evidence, Work workspace process supervision with tracked/running/completed counts plus stdin/PTY/sudo parity and direct process actions, visible process monitor/live tail/tool inspector supervision routes, first-class `execution action:"capabilities|process_capabilities"`, `computer action:"plan"`, `terminal`, and `process` adapters for direct process parity reports, browser navigation/screenshot/desktop-control workflow planning, terminal(command, background:true), and process(action:list/poll/wait/log/kill/write/capabilities) UX over confirmed tracked local background process start/list/status/log/wait/stop routes, session-id aliases, bounded redacted process log tails with byte/count/truncation metadata, a read-only process parity matrix for terminal background start plus process list/poll/wait/log/kill/write/PTY/sudo semantics, route-planner preference for `execution action:"process_capabilities"` when the user asks about interactive CLI, PTY, stdin, sudo, or privilege prompts, dynamic SDK/daemon substrate probes for ProcessManager stdin/PTY methods, terminal/PTY operator routes, session-input steering routes, and credential routes, confirmed stdin write execution when a safe ProcessManager stdin method is discovered, setup-linked sudo execution posture with foreground-supervised escalation guidance, SUDO_PASSWORD presence-only reporting, blocked background sudo/stdin password routes, and missing contract evidence, execution-history activity cards that group redacted records by turn with status/outcome, verification evidence, bounded process-output summaries, live-output routes, exact inspect routes, and file-recovery handoffs, confirmed file recovery, strict browser/desktop ready-attention-setup posture with workflow cards/checklists/fallback routes, and delegation for isolation, parallelism, remote execution, separate worktrees, or requested review. Agent now also consumes certified SDK/daemon interactive runtime read models for live process output chunks, typed PTY session input/output routes, sudo credential mediation routes, and browser/desktop command receipts from `context.platform.readModels.execution.*`, `context.platform.readModels.computer.*`, SDK mirrors, and daemon runtime mirrors. Those records surface durable process/session/receipt ids, bounded redacted output chunks, exact confirmed write/input/resize/close/credential/execute routes, receipt inspect routes, status, source path, schema/version/publication/publisher/provenance evidence, and missing certification signals without returning raw tokens, command secrets, sudo values, screenshot payloads, or private UI bodies. Certified browser/desktop command receipts now make `computer action:"plan|control"` ready through the published daemon route, while artifact-free or uncertified setups continue to show honest setup/review posture.',
+    nextMoves: [
+      'Keep certified interactive runtime schema fixtures current as SDK/daemon process, PTY, sudo, and browser-control contracts add fields.',
+      'Add connected-host CI coverage for real daemon interactive runtime streams and browser/desktop command receipts when stable fixtures are available.',
+      'Keep delegation for isolation, parallelism, or remote execution, not as the default user-facing answer to coding work.',
+    ],
+    competitorSignals: [
+      { competitor: 'openclaw', evidence: 'Provides browser control, canvas, nodes, system.run, camera, screen recording, and session tools.' },
+      { competitor: 'hermes', evidence: 'Includes terminal backends, browser tools, code execution, computer-use tooling, and isolated subagents.' },
+      { competitor: 'odysseus', evidence: 'Agent uses web, files, shell, MCP, skills, and memory through opencode.' },
+    ],
+  },
+  {
+    id: 'multi-agent-and-remote-execution',
+    userOutcome: 'Large tasks can be split safely across isolated agents or remote runners while the user sees progress and can intervene.',
+    targetStandard: 'better',
+    bestInClassRequirement: 'Parallelism is available when it improves time-to-result, with per-task workspaces, logs, artifacts, and review gates.',
+    goodVibesStatus: 'leading',
+    owners: ['agent', 'connected-host'],
+    goodVibesNow: 'GoodVibes has shared-session, remote runner, artifact, task, worktree, orchestration, subagent, and delegation foundations; Agent exposes `agent_orchestration` and `agent_orchestration_agent` for live visible subagent records, serial-by-default policy, managed multi-agent plan milestones, per-agent plan cards with cancel/message/wait routes, work-plan links, dispatch receipt counts, closeout cards, remote-runner contract/artifact evidence, durable remote closeout receipt evidence from the artifact store, auto-attached remote artifact or receipt review routes matched by runner id, spawn/batch-spawn decision cards, templates, and exact first-class `agent` list/inspect/message/wait/cancel routes, plus local-first, TUI handoff, delegated-review, remote-inspection, and hidden-fanout-blocked decision cards with structured confirmed handoff briefs. Approved visible work-plan items can now be dispatched through `agent_work_plan action:"dispatch_agents"` into first-class `agent` spawn or batch-spawn calls with saved linked-agent receipts, post-dispatch next routes for orchestration, work-plan detail, agent inspect/wait/message/cancel, and closeout, and managed orchestration closeout visibility. Remote artifact-store receipts for remote-runner artifact, closeout, and export outcomes attach to overview and single-agent closeout cards with receipt counts, metadata-only redaction posture, source artifact ids, read-only `agent_artifacts show` inspect routes, and status priority that keeps active/running agents in pending-work instead of treating receipt evidence as completion. When the SDK/daemon publishes remote-runtime read models, Agent now also consumes certified live capture/export/closeout outcome records and per-runner workspace/worktree isolation evidence from `context.platform.readModels.remoteRuntime.*`, related remote runner read-model paths, runtime SDK mirrors, and operator SDK mirrors; those records surface runner ids, capture/export/artifact ids, status, bounded redacted summaries, source paths, workspace ids, path-bounded worktree refs, branches, model inspect routes, source counts, closeout counts, review-gate requirements, schema/version/publication/publisher/provenance/freshness-cursor/receipt evidence, and missing certification signals without creating pools, spawning agents, importing artifacts, accepting workspace evidence, exposing path or token secrets, or mutating remote state. It intentionally blocks invisible local fanout and raw remote mutation from Agent.',
+    nextMoves: [
+      'Keep remote-runtime outcome and workspace certification fixtures current as SDK/daemon read models add fields.',
+      'Add connected-host CI coverage for real remote capture/export/closeout streams, workspace lifecycle controls, and failure states when stable daemon fixtures publish them.',
+      'Keep default chat serial, but route complex execution to supervised parallel work when it clearly helps the user.',
+    ],
+    competitorSignals: [
+      { competitor: 'openclaw', evidence: 'Supports multi-agent routing and sessions tools for agent-to-agent coordination.' },
+      { competitor: 'hermes', evidence: 'Spawns isolated subagents and has kanban-style orchestration with per-task worktrees.' },
+      { competitor: 'odysseus', evidence: 'Lets users hand tools to an agent and have it run whole tasks itself.' },
+    ],
+  },
+  {
+    id: 'deep-research-and-knowledge-reports',
+    userOutcome: 'The user can ask for deep research and receive a sourced, inspectable report that can be saved to knowledge.',
+    targetStandard: 'better',
+    bestInClassRequirement: 'Research plans, source quality, citations, synthesis, visual report output, and knowledge ingest are one coherent workflow.',
+    goodVibesStatus: 'leading',
+    owners: ['agent', 'connected-host'],
+    goodVibesNow: 'Agent has web research, URL inspection, Agent Knowledge, ingest routes, route-planner preference for browser-backed runner readiness and visual report rendering posture, a Research workspace that shows browser-runner and visual-report readiness plus exact run/source/report routes, a Research briefing action, Plan workflow action, Public source search action, Browser runner readiness action, and Report artifacts action, a project-local visible research run ledger with phase/progress/checkpoints/log tails/pause/resume/cancel/complete routes, a read-only next-action briefing across visible runs, source review, saved reports, browser readiness, and exact follow-up routes, read-only research workflow planning across run/source/report/browser/Knowledge routes, bounded public source-candidate search that returns capture-ready source summaries and exact confirmed add_source routes without writing the queue, confirmed `research action:"runner"` source collection that creates or resumes a visible run, runs bounded public `web_search`, saves candidate source queue records, checkpoints the run with source ids/log tail/next review routes, and keeps report saving, Knowledge ingest, external messaging, and browser/PWA control separate, browser-backed runner readiness with setup/fallback/source-review/report/Knowledge-promotion routes plus an explicit browser-runner contract for visible controls/source receipts/bounded logs/report handoff, certified SDK/daemon live browser-runner read models with schema/version/publication/publisher/provenance/freshness-cursor/receipt metadata, redacted current URLs/logs, visible checkpoint/pause/resume/cancel routes, source/page receipt ids, and missing-signal surfacing, a research source queue with credibility, score, review/reject/use state, report-ready source lines, reviewed-source bundle handoff, direct saved report artifact inspection, confirmed sourced report artifact saving with citation/source maps plus citation coverage metadata, repair guidance, optional strict enforcement, visual report packets that add at-a-glance summary, evidence matrix, findings board, dated source/comparison view, open questions, next actions, and handoff checklist over the same reviewed source artifact, and certified SDK/daemon browser/PWA visual report render read models with render routes, source-map counts, citation coverage, visual sections, publication/receipt evidence, and redacted render URLs before connected-host rendering is counted as ready.',
+    nextMoves: [
+      'Keep live research runner and visual report renderer certification fixtures current as SDK/daemon read models add fields.',
+      'Add connected-host CI coverage for real browser-backed research runs, page/source receipts, rendered report routes, and failure states when stable daemon fixtures publish them.',
+    ],
+    competitorSignals: [
+      { competitor: 'openclaw', evidence: 'Showcases web research, bookmarks, project research, and personal knowledge workflows.' },
+      { competitor: 'hermes', evidence: 'Has web tools, session search, trajectory tooling, and research-ready batch workflows.' },
+      { competitor: 'odysseus', evidence: 'Ships Deep Research that gathers, reads, and synthesizes sources into a visual report.' },
+    ],
+  },
+  {
+    id: 'documents-files-and-model-comparison',
+    userOutcome: 'The user can write documents, compare models, handle uploads, and inspect generated artifacts without leaving the assistant.',
+    targetStandard: 'parity',
+    bestInClassRequirement: 'Documents, uploads, AI edit suggestions, blind model comparison, and artifact reuse are first-class app workflows.',
+    goodVibesStatus: 'parity',
+    owners: ['agent', 'connected-host'],
+    goodVibesNow: 'Document Ops now has project-scoped versioned markdown drafts with browse/show/create/revise/review/comment/suggest/accept-suggestion/reject-suggestion/artifact-attach/artifact-insert/export, uploads, exports, sources, media artifacts, reviewer-ready document export appendices with comment and AI suggestion summaries plus review metadata counts, a visible chronological review packet timeline across documents, comments, AI suggestions, attachments, document exports, comparisons, judgments, route-decision receipts, saved packet presets, handoffs, handoff archives, and route-decision next actions, a visible read-only reviewer-readiness preflight that flags missing source artifacts, unresolved comments, proposed suggestions, unrevealed comparisons, hidden judgments, route-change decisions, and incomplete reviewer handoff evidence before export/archive/apply, inline readiness badges at document export, reviewer handoff/archive, and route-apply forms, review packet defaults that pick the latest document/export/comparison/judgment/route-decision/handoff evidence and use saved preset evidence only as fallback to prefill document export, compare handoff/archive, winner-apply, leave-unchanged route-decision, save-preset, and share forms with field-local hints, a guided read-only review packet wizard with progress, current-step routing, backtracking routes, persisted apply/leave-unchanged route-decision evidence, final archive review, and refreshed-preset lineage verification before external sharing, a confirmed `agent_review_packet_presets` tool plus workspace forms that save/list/show reusable document/comparison/judgment/route-decision/handoff/archive/related artifact packet presets without changing documents, model routing, handoffs, or archives, run list/show freshness checks for missing or superseded artifact ids, recommend reuse routes that point at newer matching evidence when metadata is sufficient, and refresh stale presets into new local preset artifacts with source-preset lineage after explicit confirmation, a unified artifact browser with read-only browse/show, filters, redacted metadata, bounded text previews, confirmed artifact export-to-file, confirmed multi-artifact package directory and ZIP archive export with exact bytes, README, and redacted manifest, confirmed artifact-to-Knowledge promotion, confirmed artifact-to-document attachment, and confirmed artifact-to-compare reuse for saved text artifacts, plus a confirmed blind comparison runner with delayed reveal, durable JSON comparison artifacts, saved review boards, side-by-side reviewer views that combine related document/artifact excerpts with comparison evidence, split-pane reviewer handoff diffs with section jump focus plus recent-handoff defaults and visible recent choices from artifact metadata, saved judgment artifacts, task/document/benchmark-filtered preference analytics and cross-session synthesis, markdown report export, confirmed apply-winner route-decision receipts, confirmed leave-unchanged route-decision receipts, reviewer handoff artifacts that combine comparison evidence with related document/artifact exports, one-click reviewer handoff ZIP archives with source comparison/judgment, related evidence bytes, matching route-decision receipt bytes, README, and manifest ids, confirmed `agent_review_packet_share` delivery of plain-text archive references through configured channel targets after explicit confirmation, and confirmed winner route updates.',
+    nextMoves: [
+      'Certify real reviewer packet delivery outcomes across configured channel targets before claiming release-depth external delivery.',
+      'Carry the same packet wizard, lineage, and archive-share workflow into future browser/PWA surfaces without weakening confirmation or ZIP-byte boundaries.',
+    ],
+    competitorSignals: [
+      { competitor: 'openclaw', evidence: 'Canvas and browser/web surfaces provide visual interaction primitives.' },
+      { competitor: 'hermes', evidence: 'TUI and dashboard surfaces support conversation history, tools, and sessions.' },
+      { competitor: 'odysseus', evidence: 'Ships Documents and Compare workflows in the web workspace.' },
+    ],
+  },
+  {
+    id: 'mobile-voice-and-device-nodes',
+    userOutcome: 'The user can talk to the assistant and use phone or desktop device capabilities without returning to the terminal.',
+    targetStandard: 'better',
+    bestInClassRequirement: 'Voice, mobile, notifications, camera, screen, location, and device commands are paired, permission-aware, and reliable.',
+    goodVibesStatus: 'leading',
+    owners: ['agent', 'connected-host', 'companion'],
+    goodVibesNow: 'Agent now has first-class `computer action:"status|plan|control|browser|setup|mcp|open_browser"` UX over browser/PWA readiness, browser/screenshot/desktop-control route planning, repair/setup, trusted tool discovery, and visible browser cockpit handoffs, plus `device action:"status|capability|voice|provider|open_tts_provider|open_tts_voice"` UX over companion pairing, mobile/PWA compatibility, voice/TTS, notifications, provider posture, and visible TTS picker handoffs while preserving the existing harness detail routes. The route planner now prefers `device action:"voice"` for push-to-talk, voice memo transcription, spoken-response, and wake-word posture, `device action:"provider"` for TTS provider/voice setup, and `computer action:"browser"` for browser cockpit/PWA readiness before visible handoffs. The read-only device capability map reports ready/attention/setup-needed/not-published states, computer browser/PWA readiness reports URL/category/mobile/receipt gaps, browser/desktop control reports trusted-tool/MCP setup posture and safe workflow plans, and voice workflow posture maps push-to-talk, voice memo transcription, spoken responses, and wake-word capture. Agent also consumes certified SDK/daemon companion device capability records for camera, screen, location, local device commands, and wake-word routes with schema/version/publication/publisher/provenance/freshness-cursor/receipt metadata, permission scopes, exact inspect/control routes, redacted summaries, and missing-signal surfacing before those capabilities are counted as ready. The Voice & Media workspace now gives users Voice workflows, Device capability map, and Browser/PWA readiness actions with direct `device` and `computer` route hints while preserving confirmation gates for capture, playback, picker, browser-open, permission repair, and device-command effects.',
+    nextMoves: [
+      'Keep companion device capability certification fixtures current as SDK/daemon records add camera, screen, location, notification, wake, and device-command fields.',
+      'Add connected-host/companion CI coverage for real permission prompts, capture receipts, route failures, and mobile foreground/background transitions when stable fixtures publish them.',
+      'Keep all device capture, permission repair, notification send, and local command effects behind exact confirmed routes.',
+    ],
+    competitorSignals: [
+      { competitor: 'openclaw', evidence: 'macOS, iOS, and Android nodes expose voice, canvas, camera, screen, location, notifications, and system commands.' },
+      { competitor: 'hermes', evidence: 'Runs in Termux and supports voice memo transcription and messaging continuity.' },
+      { competitor: 'odysseus', evidence: 'Responsive PWA works on mobile and includes browser notifications.' },
+    ],
+  },
+  {
+    id: 'web-dashboard-and-pwa',
+    userOutcome: 'The assistant is usable from a browser with clear status, settings, sessions, tools, and mobile-friendly controls.',
+    targetStandard: 'better',
+    bestInClassRequirement: 'The browser surface is not a secondary admin panel; it is a full user-grade assistant cockpit.',
+    goodVibesStatus: 'leading',
+    owners: ['connected-host', 'agent'],
+    goodVibesNow: 'GoodVibes host has web/control-plane foundations, and Agent now exposes the configured connected-host browser cockpit/PWA through first-class `computer action:"browser|open_browser"` routes plus Home and Voice & Media workspace actions, with route-planner preference for browser cockpit, web dashboard, and PWA wording before any visible browser-open handoff. The route resolves `web.publicBaseUrl` or the web endpoint binding, requires explicit user confirmation before opening an external browser, returns service/web setup routes when disabled, and reports workspace-category coverage, mobile/PWA controls, Agent onboarding marker status, and browser/PWA first-run receipts without pretending Agent hosts a separate web app. Agent now consumes certified SDK/daemon browser/PWA category-route read models for the full Agent workspace category map, requiring schema/version/publication/publisher/provenance/freshness-cursor/receipt metadata, exact inspect/open routes, and mobile/touch evidence before the browser cockpit is counted as browser-native ready. It also consumes certified browser/PWA first-run runtime receipts with manifest/service-worker/install/offline evidence and redacted URLs/summaries, while the Start checklist still promotes Browser/PWA from durable setup receipt artifacts, live setup receipt read models, or ordered setup receipt event streams. With certified route coverage and certified first-run evidence, `computer action:"browser"` and the connected UI surface report `browser-native-ready`; without that evidence, the same UX keeps setup/receipt gaps visible and falls back to the TUI workspace.',
+    nextMoves: [
+      'Keep certified browser/PWA category-route and first-run receipt schemas in lockstep with SDK/daemon contract versions.',
+      'Add live connected-host browser/PWA acceptance artifacts to every stable-release verification run.',
+      'Keep mobile browser cockpit controls mapped to the same Agent workspace categories as new workspace lanes are added.',
+    ],
+    competitorSignals: [
+      { competitor: 'openclaw', evidence: 'Gateway serves Control UI and WebChat, plus companion apps.' },
+      { competitor: 'hermes', evidence: 'Provides local web dashboard and TUI gateway surfaces.' },
+      { competitor: 'odysseus', evidence: 'Primary experience is a self-hosted responsive web workspace/PWA.' },
+    ],
+  },
+  {
+    id: 'security-permissions-and-recovery',
+    userOutcome: 'Powerful automation is safe by default, explainable, recoverable, and adjustable without killing capability.',
+    targetStandard: 'better',
+    bestInClassRequirement: 'Every risky action has clear scope, trust, provenance, approval UX, logs, rollback, and doctor repair.',
+    goodVibesStatus: 'leading',
+    owners: ['agent', 'connected-host', 'release'],
+    goodVibesNow: 'GoodVibes has strong permission policy, secrets, MCP trust, pairing, redaction, readiness, doctor, release evidence, operator audit surfaces, first-class security posture and finding inspection, and route-planner preference for `security action:"status|finding|explain"` so users can ask what permissions are active, inspect exact findings, or see whether one model action is allowed, denied, blocked, or waiting on confirmation.',
+    nextMoves: [
+      'Keep strong defaults while reducing unnecessary confirmations for already-approved low-risk workflows.',
+      'Attach every autonomous task to audit logs, artifacts, and rollback or cancel affordances.',
+    ],
+    competitorSignals: [
+      { competitor: 'openclaw', evidence: 'Emphasizes secure defaults, DM pairing, allowlists, sandboxing, and doctor checks.' },
+      { competitor: 'hermes', evidence: 'Documents command approval, DM pairing, container isolation, network egress isolation, and observability hooks.' },
+      { competitor: 'odysseus', evidence: 'Gates admin-only tools, local services, shell, file access, webhooks, and tokens with security guidance.' },
+    ],
+  },
+];
+
+export function competitiveInventoryStatusCounts(): Record<GoodVibesCompetitiveStatus, number> {
+  return COMPETITIVE_FEATURE_INVENTORY.reduce<Record<GoodVibesCompetitiveStatus, number>>((counts, item) => {
+    counts[item.goodVibesStatus] += 1;
+    return counts;
+  }, {
+    leading: 0,
+    parity: 0,
+    partial: 0,
+    gap: 0,
+  });
+}

package/src/agent/document-registry-types.ts

@@ -0,0 +1,106 @@
+export type AgentDocumentStatus = 'draft' | 'reviewed' | 'archived';
+export type AgentDocumentCommentStatus = 'open' | 'resolved';
+export type AgentDocumentSuggestionStatus = 'proposed' | 'accepted' | 'rejected';
+
+export interface AgentDocumentVersion {
+  readonly id: string;
+  readonly title: string;
+  readonly body: string;
+  readonly summary: string;
+  readonly createdAt: string;
+}
+
+export interface AgentDocumentComment {
+  readonly id: string;
+  readonly body: string;
+  readonly status: AgentDocumentCommentStatus;
+  readonly createdAt: string;
+  readonly updatedAt: string;
+  readonly resolvedAt?: string;
+}
+
+export interface AgentDocumentSuggestion {
+  readonly id: string;
+  readonly title: string;
+  readonly body: string;
+  readonly tags: readonly string[];
+  readonly documentStatus?: AgentDocumentStatus;
+  readonly summary: string;
+  readonly rationale: string;
+  readonly status: AgentDocumentSuggestionStatus;
+  readonly createdAt: string;
+  readonly updatedAt: string;
+  readonly resolvedAt?: string;
+}
+
+export interface AgentDocumentAttachment {
+  readonly id: string;
+  readonly artifactId: string;
+  readonly label: string;
+  readonly note?: string;
+  readonly filename?: string;
+  readonly mimeType?: string;
+  readonly kind?: string;
+  readonly sizeBytes?: number;
+  readonly createdAt: string;
+  readonly updatedAt: string;
+}
+
+export interface AgentDocumentRecord {
+  readonly id: string;
+  readonly title: string;
+  readonly body: string;
+  readonly tags: readonly string[];
+  readonly status: AgentDocumentStatus;
+  readonly createdAt: string;
+  readonly updatedAt: string;
+  readonly versions: readonly AgentDocumentVersion[];
+  readonly comments: readonly AgentDocumentComment[];
+  readonly suggestions: readonly AgentDocumentSuggestion[];
+  readonly attachments: readonly AgentDocumentAttachment[];
+  readonly lastArtifactId?: string;
+}
+
+export interface AgentDocumentCreateInput {
+  readonly title: string;
+  readonly body: string;
+  readonly tags?: readonly string[];
+  readonly summary?: string;
+}
+
+export interface AgentDocumentUpdateInput {
+  readonly title?: string;
+  readonly body?: string;
+  readonly tags?: readonly string[];
+  readonly summary?: string;
+  readonly status?: AgentDocumentStatus;
+  readonly lastArtifactId?: string;
+}
+
+export interface AgentDocumentCommentInput {
+  readonly body: string;
+}
+
+export interface AgentDocumentSuggestionInput {
+  readonly title?: string;
+  readonly body: string;
+  readonly tags?: readonly string[];
+  readonly status?: AgentDocumentStatus;
+  readonly summary?: string;
+  readonly rationale?: string;
+}
+
+export interface AgentDocumentAttachmentInput {
+  readonly artifactId: string;
+  readonly label?: string;
+  readonly note?: string;
+  readonly filename?: string;
+  readonly mimeType?: string;
+  readonly kind?: string;
+  readonly sizeBytes?: number;
+}
+
+export interface AgentDocumentSnapshot {
+  readonly path: string;
+  readonly documents: readonly AgentDocumentRecord[];
+}