CorvinOS

least_privilege=2: The console defaults to 127.0.0.1, third-party entry points are not imported without opt-in, and CI permissions are scoped; however, full runtime privileges, bridge permissions, and outbound-network scope are not shown. user_confirmation=2: Uninstall prompts once, extensions require opt-in, and the README asserts fail-closed consent gates; per-action confirmation for autonomous routing, learning, and outbound messaging is not evidenced in code. data_flow_transparency=2: DataHub ingestion, model routing, feedback, auditing, and some online voice flows are described; destinations, processors, retention, and handling for Discord, Telegram, WhatsApp, Slack, email, and telemetry remain incomplete. sensitive_data_handling=2: Secret redaction, PII flagging, metadata-only auditing, deletion proofs, mode-600 backups, and test audit isolation are described; most controls are assertions, with no supplied implementation for secret storage, encryption, or erasure. dependency_security=1: Dependencies are extensively justified and packaging exclusions reduce accidental disclosure, but most versions have only lower bounds, Actions are not commit-pinned, installers execute mutable main through shell pipelines, and no lockfile, vulnerability scan, or artifact verification is shown. external_effects=2: Installation, startup, update, deletion, maintainer push effects, and several exit codes are explicit; approval and scoping for connector, browser, and uploader actions are not shown. rollback=3: Failed updates automatically restore prior code/build, preserve old HEAD and local changes, while uninstall backs up non-downloadable state with restoration instructions and distinguishes rollback failure; the evidence is unusually concrete. source_attribution=2: License, author, repository, and ADR reference paths are identified, and data-source attribution is claimed; the external ADR contents are absent, publisher identity remains unknown, and third-party attribution is incomplete.

self_consistency=1: Installation, update, and audit narratives are detailed, but the README says production-ready, guaranteed convergence, and 99.9% SLA while package metadata says Beta; numerous proven/measured/guaranteed statements lack accompanying results. dependency_availability=2: Supported Python versions, platforms, required versus optional dependencies, online/offline fallbacks, and previously missing dependencies are documented concretely; broad ranges, the external ffprobe requirement, external ADRs, and online services still permit drift. failure_messages=3: Install, update, uninstall, unconfigured YouTube, and CI paths describe diagnostics, exit codes, or explicit errors, and workflows provide actionable PR failure guidance; no material gap is evident in the supplied files.

audience_and_scenarios=3: The developer/self-hosted-builder audience is explicit, with console, headless, messaging, voice, browser, workflow, compliance-report, and maintainer scenarios plus layered reading paths. capability_boundaries=2: Base versus optional capabilities, end-user versus maintainer updates, online versus offline voice, and credential-dependent YouTube support are distinguished; boundaries around autonomous learning, model decisions, and connector actions remain vague. trigger_precision=2: Extension entry points are enumerated but not imported absent explicit per-name or global opt-in, and CI path triggers are precise; end-user agent triggers, channel authorization, and false-trigger prevention are not evidenced. environment_fit=3: macOS, Linux, Windows/WSL, Python 3.10–3.13, loopback defaults, LAN mode, OS trust stores, platform dependencies, and installation presets are handled in substantial detail.

information_architecture=3: The README clearly separates quick start, lifecycle operations, architecture, scenarios, technology, and document navigation; packaging, entry points, and CI responsibilities are also well organized. install_notes=3: Remote and checkout installs, Windows usage, options, verification, updates, uninstall, backup, restoration, managed source trees, and PyPI/main differences are covered. naming_stability=2: corvin/corvinos compatibility aliases, explicit entry points, and version 2.0.0 aid stability; CorvinOS, CorvinVS, Forge 2.0, and multiple legacy directory names indicate migration debt. examples_and_faq=2: Commands, architecture flows, cost examples, and a question index are present, but complete agent conversations, bridge setup examples, and representative end-to-end outputs are absent. known_limitations=1: PyPI lag, online voice, ffprobe, OAuth, and optional-dependency constraints appear piecemeal; there is no consolidated limitations section, and strong production/compliance claims obscure Beta status and unverified assumptions. license=3: The full Apache-2.0 text and copyright statement are present and agree with package metadata and the sample package manifest. versioning_changelog=2: Version 2.0.0, a CHANGELOG link, dependency bounds, and update procedures exist; the changelog content was not supplied, and default installation from mutable main weakens revision stability. maintenance_responsibility=2: An author email, security contact, issue repository, and maintainer release workflow are provided; publisher identity is unverified, and team structure, support commitments, and response targets are unspecified.

output_usability=2: Console, CLI, headless operation, reports, audit artifacts, and multiple delivery bridges provide concrete output channels, but no real agent output or implementation evidence establishes everyday result quality. marginal_value=2: The combination of self-hosting, multichannel access, routing, auditability, offline voice, and rollback offers plausible added value; differentiation from existing orchestrators is supported mainly by the project's own narrative. cost_benefit=1: Pricing assumptions, routing proportions, and ROI examples are supplied, but the claimed 60–80% savings, 2–5% quality gains, two-to-three-week convergence, and instant payback lack datasets, methods, or result artifacts and omit operational costs.

claim_traceability=1: Named verification scripts, ADR identifiers, test paths, and technical-document paths offer leads for some claims; decisive compliance, SLA, cost, quality, and convergence claims lack underlying measurements or complete implementation evidence. cross_source_corroboration=2: pyproject, LICENSE, SECURITY, CI workflows, and the test fixture partly corroborate cross-platform, dependency, entry-point, audit, and licensing statements; learning effectiveness and regulatory compliance receive no substantive independent corroboration. fact_inference_separation=0: Architecture intentions, mathematical extrapolations, and marketing scenarios are repeatedly labeled proven, measured, guaranteed, or compliant without the corresponding evidence, so facts, forecasts, and inferences are not reliably separated.