podium

Comparison rubric

Rubric 0.3. Every comparison and product page uses these 51 criteria. A finding answers the criterion's judgment rule; its atomic answers address the listed questions.

Access and agent choice

ACC-01

Client access

Judgment rule. List desktop OS and minimum versions, iOS, Android, browser, mobile browser, CLI and editor extensions separately. For each client, record start, steer, approve, review and resume actions, notifications and plan restrictions. Distinguish an installable mobile app from a mobile website and from status-only monitoring.

  • desktop_os Desktop os
  • mobile_apps Mobile apps
  • browser Browser
  • mobile_browser Mobile browser
  • cli Cli
  • editor_extensions Editor extensions
  • task_actions Task actions
  • notifications Notifications
  • cross_device_continuity Cross device continuity
ACC-02

Agent and model choice

Judgment rule. List supported harnesses and model providers separately, including custom adapters. Record whether the product embeds a harness, controls its sessions through an API, or only launches its terminal command. Describe mixed-harness operation only when sources establish at least two different harnesses.

  • harnesses Harnesses
  • model_providers Model providers
  • custom_adapters Custom adapters
  • session_integration Session integration
  • mixed_harness_operation Mixed harness operation
ACC-03

Subscriptions, API keys and vendor credits

Judgment rule. Record bring-your-own agent subscription, bring-your-own API account, vendor credits and local models as separate routes. List supported plans, models/modes, multiple-account switching and what works without a vendor account or token purchase. Existing subscription support cannot be inferred from API-key support. Record required extra payments and documented provider restrictions.

  • agent_subscriptions Agent subscriptions
  • api_accounts Api accounts
  • vendor_credits Vendor credits
  • local_models Local models
  • account_switching Account switching
  • vendor_account_requirement Vendor account requirement
  • provider_restrictions Provider restrictions
ACC-04

Onboarding and project prerequisites

Judgment rule. Record the documented path from fresh install to a first task, with its manual steps. Record support for a local directory without Git, a local Git repo without a remote, and a GitHub-backed repo separately. Record the documented account, project, host, credential and permission prerequisites. Record managed-cloud setup and first-class BYO VPS installer/onboarding independently of hidden settings or a DIY shell recipe.

  • first_task_setup First task setup
  • no_git No git
  • local_git_without_remote Local git without remote
  • hosted_git Hosted git
  • prerequisite_guidance Prerequisite guidance
  • managed_cloud_setup Managed cloud setup
  • byo_vps_onboarding Byo vps onboarding
ACC-05

Programmable access

Judgment rule. Inventory actual CLI, API, SDK, MCP and webhook operations for create, inspect, steer, stop and review. Record authentication and API stability. Having an MCP client that uses external tools is different from exposing the product to other agents over MCP.

  • cli Cli
  • api Api
  • sdk Sdk
  • mcp_server Mcp server
  • webhooks Webhooks
  • operations Operations
  • authentication Authentication
  • stability Stability
ACC-06

External tools and extensions

Judgment rule. Record MCP client support, plugins, custom tools, skill/instruction import, integration authentication and permission scope. Name which component provides each connection and whether setup is product-managed or inherited from the underlying harness.

  • mcp_client Mcp client
  • plugins Plugins
  • custom_tools Custom tools
  • instructions_import Instructions import
  • authentication Authentication
  • permission_scope Permission scope
  • integration_owner Integration owner
ACC-07

Client implementation

Judgment rule. For each desktop/mobile client, record native platform UI, Electron, Tauri, React Native, web/PWA or unknown, plus hybrids. Require official technical docs or pinned source/build evidence. Tauri is not synonymous with fully native UI. Implementation choice says nothing about responsiveness or usability.

  • desktop_implementation Desktop implementation
  • mobile_implementation Mobile implementation
  • hybrids Hybrids
  • implementation_evidence Implementation evidence

Planning and context

PLAN-01

Intake and external tracker relationship

Judgment rule. Record local creation, prompt intake, issue import and chat/Git triggers. Identify the authoritative tracker, stable issue IDs, one-way or two-way sync, supported edits and operations requiring a trip back to Linear/GitHub/Jira. Importing or attaching a ticket is not native issue management. Answer PLAN-06 and PLAN-07 separately.

  • local_creation Local creation
  • prompt_intake Prompt intake
  • external_import External import
  • chat_git_triggers Chat git triggers
  • authoritative_tracker Authoritative tracker
  • stable_ids Stable ids
  • sync Sync
  • supported_edits Supported edits
  • external_roundtrips External roundtrips
PLAN-02

Durable task plans

Judgment rule. Record task plans and acceptance criteria, editors, revision history and links to implementation. Record whether a plan can be amended while work is running and revisited later. A task-specific starting brief, reusable memory and a persistent product specification are different objects; product specs are judged in PLAN-08.

  • plans Plans
  • acceptance_criteria Acceptance criteria
  • editors Editors
  • revisions Revisions
  • implementation_links Implementation links
  • amendment Amendment
  • restart_persistence Restart persistence
PLAN-03

Hierarchy, dependencies and evolving scope

Judgment rule. Record epics, arbitrary parent/child depth, blockers, readiness, dependency enforcement and state propagation. Record whether a simple task can grow into an epic while keeping its identity, discussion, history and outputs, and whether blockers prevent dispatch or are only displayed. Record whether a rigid preselected workflow is required, and whether changing scope requires recreating work.

  • epics Epics
  • hierarchy Hierarchy
  • blockers Blockers
  • readiness Readiness
  • enforcement Enforcement
  • state_propagation State propagation
  • task_to_epic Task to epic
  • identity_retention Identity retention
  • workflow_constraints Workflow constraints
PLAN-04

Shared context and memory

Judgment rule. List repository instructions, skills, project docs and cross-session/cross-harness memory. Record scope, provenance, citation, correction/deletion and stale-context controls. Record what survives a new session or colleague takeover. A notes page or shared file is not automatically a maintained spec or managed memory.

  • instructions Instructions
  • skills Skills
  • project_docs Project docs
  • memory Memory
  • scope Scope
  • provenance Provenance
  • correction Correction
  • deletion Deletion
  • freshness Freshness
  • takeover_continuity Takeover continuity
PLAN-05

Architecture and API awareness

Judgment rule. Record code search, repository indexing, external knowledge and multimodal inputs, with source freshness and access scope. Record retrieval, citation, conflict detection and review-time enforcement separately. A large context window or an instruction file alone does not prove architectural consistency.

  • code_search Code search
  • indexing Indexing
  • external_knowledge External knowledge
  • multimodal_inputs Multimodal inputs
  • freshness Freshness
  • access_scope Access scope
  • api_retrieval Api retrieval
  • citations Citations
  • conflict_detection Conflict detection
  • review_enforcement Review enforcement
PLAN-06

Native issue management and idea backlog

Judgment rule. Enumerate create, edit, discuss, prioritize, label, assign, search, filter, archive, reopen and project/epic views within the product. Record whether an idea can be saved without starting an agent, refined with another person, and marked ready or dispatched later. Record separate task/session entities, metadata depth, multiple sessions per task, durable state transitions and whether an external tracker remains necessary.

  • create Create
  • edit Edit
  • discuss Discuss
  • prioritize Prioritize
  • label Label
  • assign Assign
  • search Search
  • filter Filter
  • archive Archive
  • reopen Reopen
  • project_epic_views Project epic views
  • idea_parking Idea parking
  • explicit_dispatch Explicit dispatch
  • task_session_separation Task session separation
  • metadata Metadata
  • durable_states Durable states
  • external_tracker_requirement External tracker requirement
PLAN-07

Agent-native issue operations

Judgment rule. Record whether an agent can read/create/update the same durable issue IDs and fields humans use, claim/assign work, change state, create dependencies/children and report blockers/results through documented CLI/API/MCP. Record whether human views reflect agent writes with attribution, permissions and conflict handling. Distinguish shared authoritative records, synchronized external records, agent-private metadata and prompt-only conventions.

  • shared_ids Shared ids
  • read Read
  • create Create
  • update Update
  • claim Claim
  • assign Assign
  • state_changes State changes
  • dependencies Dependencies
  • children Children
  • results Results
  • human_visibility Human visibility
  • attribution Attribution
  • permissions Permissions
  • conflicts Conflicts
PLAN-08

Living product specifications

Judgment rule. Record persistent requirements across tasks/releases, editable by humans and agents with attributable revisions and approval rules. Record requirement-to-task/implementation links, retrieval during later tasks, drift detection and consideration during review/quality control. A one-time spec-to-plan workflow, per-task brief, memory store or unreferenced document does not establish a living product spec.

  • persistent_requirements Persistent requirements
  • human_edits Human edits
  • agent_edits Agent edits
  • revisions Revisions
  • approvals Approvals
  • implementation_links Implementation links
  • later_retrieval Later retrieval
  • drift_detection Drift detection
  • review_integration Review integration

Coordination and automation

COORD-01

Parallel work

Judgment rule. Record independently running sessions and tasks, documented quotas and concurrency limits. Describe how a user sees running, waiting, failed and finished work. Several chat tabs are not proof that runs execute concurrently.

  • concurrent_sessions Concurrent sessions
  • concurrent_tasks Concurrent tasks
  • quotas Quotas
  • observed_concurrency Observed concurrency
  • status_visibility Status visibility
COORD-02

Ownership and dispatch

Judgment rule. Record assignment to humans or agents, claims, queues, routing and duplicate-work prevention. Distinguish a display label, an advisory lock and enforced exclusive ownership.

  • human_assignment Human assignment
  • agent_assignment Agent assignment
  • claims Claims
  • queues Queues
  • routing Routing
  • duplicate_prevention Duplicate prevention
  • ownership_enforcement Ownership enforcement
COORD-03

Inspectable delegation and communication

Judgment rule. Record parent/child roles, model/harness/effort choice, messages, result return and cross-harness teams. Distinguish product orchestration, provider-native subagents, installed orchestration skills and scripts. Record activation, auth and experimental flags. Record child identity, live progress, retained results and ability to reopen or follow up after completion.

  • roles Roles
  • model_harness_effort Model harness effort
  • messages Messages
  • results_return Results return
  • cross_harness Cross harness
  • orchestration_owner Orchestration owner
  • activation Activation
  • authentication Authentication
  • live_progress Live progress
  • retained_results Retained results
  • followup Followup
  • invocation Invocation
COORD-04

Unattended triggers

Judgment rule. Record schedules, event triggers, recurring tasks and completion conditions. Name where the scheduler runs, overlap handling, retries and whether closing the client stops it. A desktop cron recipe is a manual integration unless the product owns it.

  • schedules Schedules
  • events Events
  • recurring_tasks Recurring tasks
  • completion_conditions Completion conditions
  • scheduler_location Scheduler location
  • overlaps Overlaps
  • retries Retries
  • client_independence Client independence
COORD-05

Intervention and attention

Judgment rule. Record pause, stop, resume, steering, notifications, pending decisions and escalation. Record documented behavior for silent waits, CLI-only questions and whether stop terminates execution while preserving history.

  • pause Pause
  • stop Stop
  • resume Resume
  • steer Steer
  • notifications Notifications
  • pending_decisions Pending decisions
  • escalation Escalation
  • visible_errors Visible errors
  • chat_terminal_parity Chat terminal parity
  • retained_history Retained history
COORD-06

Fleet and epic management UI

Judgment rule. Record how the interface shows work across several epics, including blocked, failed, awaiting-input, reviewing and completed states. Record whether parent/child relationships, dependencies, attention needs, history and workload are visible without reading every transcript. Boards, graphs, waterfalls, timelines or another interface can qualify; no required visual form.

  • fleet_fixture Fleet fixture
  • parent_child Parent child
  • dependencies Dependencies
  • attention Attention
  • history History
  • workload Workload
  • navigation_errors Navigation errors
  • fixture_mode Fixture mode
COORD-07

Workflow flexibility and orchestration visibility

Judgment rule. Record mandatory workflow/preset selection, natural-language configuration, per-agent model/effort control, changes during execution and whether the UI exposes what actually ran, including coordinator and child roles, relationships and results during work and after completion. Record discoverability and auth requirements.

  • quick_task Quick task
  • growing_epic Growing epic
  • presets Presets
  • natural_language Natural language
  • agent_configuration Agent configuration
  • in_run_changes In run changes
  • live_roles Live roles
  • retained_relationships Retained relationships
  • discoverability Discoverability
  • auth_friction Auth friction

Execution and reliability

RUN-01

Laptop-independent execution

Judgment rule. List local, user-owned VPS/remote host, self-hosted service, vendor cloud and hybrid modes. Record provisioning, payer, compute resources, region, idle/max lifetime and disconnection rules. Record whether work continues after the originating client disconnects and can be continued from another device. A hosted UI or keep-awake setting is not evidence of remote execution. Record managed-cloud convenience separately from BYO setup effort in ACC-04.

  • local Local
  • byo_remote Byo remote
  • self_hosted Self hosted
  • managed_cloud Managed cloud
  • hybrid Hybrid
  • provisioning Provisioning
  • payer Payer
  • resources Resources
  • region Region
  • expiry Expiry
  • client_disconnect Client disconnect
  • other_device_continuation Other device continuation
RUN-02

Workspace and process isolation

Judgment rule. Record shared checkout, branch, worktree, container, VM and OS sandbox separately. Name filesystem, process, network and secret boundaries. Do not claim hostile-code containment without separate security evidence.

  • checkout Checkout
  • branch Branch
  • worktree Worktree
  • container Container
  • vm Vm
  • os_sandbox Os sandbox
  • filesystem Filesystem
  • process Process
  • network Network
  • secrets Secrets
  • code_separation Code separation
  • security_boundary Security boundary
RUN-03

Recovery, expiry and continuity

Judgment rule. Record behavior on client disconnect, worker crash, service restart and documented sandbox expiry. Separate transcript reload, process reconnection, task resumption and state reconstruction. Record lost context, duplicated actions, manual repair and ability to continue a multi-day epic after compute replacement. Short sandbox lifetimes are reported with their continuity behavior, not automatically treated as failure.

  • client_disconnect Client disconnect
  • worker_crash Worker crash
  • service_restart Service restart
  • expiry Expiry
  • transcript_reload Transcript reload
  • process_reconnect Process reconnect
  • task_resume Task resume
  • state_reconstruction State reconstruction
  • context_loss Context loss
  • duplicate_actions Duplicate actions
  • manual_repair Manual repair
  • multi_day_continuity Multi day continuity
RUN-04

Development environment reliability

Judgment rule. Record dependency setup, node_modules/cache handling, snapshots, services, port allocation and secret injection. Record how two workspaces with the same service requirements avoid installation duplication and port collisions. Record which problems the product handles automatically and which the user must diagnose.

  • dependencies Dependencies
  • caches Caches
  • snapshots Snapshots
  • services Services
  • ports Ports
  • secrets Secrets
  • duplicate_installs Duplicate installs
  • collisions Collisions
  • remote_setup Remote setup
  • automatic_repair Automatic repair
RUN-05

Limits and failure handling

Judgment rule. Record time, turn, token and spend limits; timeout, retry and provider-failure behavior. Record whether limits are warnings, enforced stops, or external billing controls.

  • time_limits Time limits
  • turn_limits Turn limits
  • token_limits Token limits
  • spend_limits Spend limits
  • timeouts Timeouts
  • retries Retries
  • provider_failures Provider failures
  • enforcement Enforcement
RUN-06

Truthful status and operational statistics

Judgment rule. Record logs, traces, failure reasons, usage exports and statistics by task, agent, project and time. Record how agent, task and board state are kept consistent, including after reconnect. Distinguish working, blocked, failed, idle, ready for review and delivered. Attribute speed and success-rate figures to their source; this catalog measures none.

  • logs Logs
  • traces Traces
  • failure_reasons Failure reasons
  • usage_export Usage export
  • task_stats Task stats
  • agent_stats Agent stats
  • project_stats Project stats
  • time_stats Time stats
  • failure_status Failure status
  • approval_status Approval status
  • reconnect_consistency Reconnect consistency
  • performance_method Performance method
  • responsiveness Responsiveness
RUN-07

Per-task API and compute cost

Judgment rule. Record visible model/API spend per task, session, child and epic, including aggregation across harness changes. Distinguish billed charges, estimates, tokens, subscription allowance and unavailable amounts; never render unknown subscription marginal cost as zero. Record compute fees separately, refresh delay, budget alerts, export and drill-down from summary statistics.

  • task_cost Task cost
  • session_cost Session cost
  • child_cost Child cost
  • epic_cost Epic cost
  • harness_aggregation Harness aggregation
  • billed_vs_estimated Billed vs estimated
  • tokens Tokens
  • subscription_allowance Subscription allowance
  • provider_reconciliation Provider reconciliation
  • compute_cost Compute cost
  • refresh_delay Refresh delay
  • alerts Alerts
  • export Export
  • drilldown Drilldown
RUN-08

Compute-aware scheduling and verification

Judgment rule. Record concurrency limits, queues, CPU/RAM limits, backpressure, per-host resource awareness and reuse/deduplication of checks. Record whether excess work queues or throttles, plus cancellation, fairness, recovery and whether overlapping epics share limits.

  • concurrency Concurrency
  • queues Queues
  • cpu_ram Cpu ram
  • backpressure Backpressure
  • host_awareness Host awareness
  • check_reuse Check reuse
  • check_deduplication Check deduplication
  • bounded_tests Bounded tests
  • cancellation Cancellation
  • fairness Fairness
  • recovery Recovery
  • shared_limits Shared limits

Human collaboration and control

TEAM-01

Live human collaboration

Judgment rule. Record shared visibility, issue discussion, comments, presence and simultaneous co-prompting as independent capabilities. For co-prompting, record input ordering/conflict handling, attribution and permission controls. Read-only links and shared issues do not establish co-steering. Record team/free-tier restrictions and whether the original owner must stay online.

  • visibility Visibility
  • discussion Discussion
  • comments Comments
  • presence Presence
  • coprompting Coprompting
  • ordering Ordering
  • conflicts Conflicts
  • attribution Attribution
  • permissions Permissions
  • plan_restrictions Plan restrictions
  • owner_online Owner online
TEAM-02

Roles and access boundaries

Judgment rule. Record organization/project/task roles, membership lifecycle, SSO and provisioning where offered. Record which plan provides each control and whether enforcement is documented or visible in source.

  • organization_roles Organization roles
  • project_roles Project roles
  • task_roles Task roles
  • membership Membership
  • sso Sso
  • provisioning Provisioning
  • unauthorized_access Unauthorized access
  • revocation Revocation
  • plan_scope Plan scope
TEAM-03

Approvals and temporary access

Judgment rule. Record command, tool, network, secret and delivery approvals, approver identity and scope lifetime. Record allow, deny and revocation, including what happens to temporary tunnels or shared access after their thread/session ends. Separate default full access, available safer modes and product-enforced policy from instructions the model is expected to follow.

  • command Command
  • tool Tool
  • network Network
  • secret Secret
  • delivery Delivery
  • approver_identity Approver identity
  • lifetime Lifetime
  • allow Allow
  • deny Deny
  • revoke Revoke
  • tunnels Tunnels
  • defaults Defaults
  • safer_modes Safer modes
  • enforcement Enforcement
TEAM-04

Decision and activity history

Judgment rule. Record attributed actions, approvals, edits, discussion and decision links. Record whether history persists across users and sessions, can be exported, and can be altered. Use the word audit only with a defined retention and integrity model.

  • actions Actions
  • approvals Approvals
  • edits Edits
  • discussion Discussion
  • decisions Decisions
  • cross_user_persistence Cross user persistence
  • cross_session_persistence Cross session persistence
  • export Export
  • mutability Mutability
  • retention Retention
  • integrity Integrity
TEAM-05

Review experience and guidance

Judgment rule. Record how a reviewer locates pending reviews, understands a change, navigates evidence, comments, requests changes and finds the next shipping action. Record documented keyboard and narrow-screen support, clarity of agent roles and preservation of review context. Generic diff/PR access and a guided review workflow are different capabilities. Link high-volume review findings to SHIP-06.

  • pending_reviews Pending reviews
  • change_understanding Change understanding
  • evidence_navigation Evidence navigation
  • comments Comments
  • request_changes Request changes
  • shipping_guidance Shipping guidance
  • effort Effort
  • missed_evidence Missed evidence
  • keyboard Keyboard
  • narrow_screen Narrow screen
  • context_switching Context switching
  • roles Roles
  • retained_context Retained context
TEAM-06

Colleague takeover and continuity

Judgment rule. Record whether a second authorized person can take over ongoing work with the same task, session history, decisions, artifacts, permissions and runtime context, including after the first person disconnects. Record ownership transfer, attribution and lost context. Separately record transferring to another model/harness; a forked transcript or shared link alone is not full human takeover.

  • ongoing_takeover Ongoing takeover
  • same_task Same task
  • session_history Session history
  • decisions Decisions
  • artifacts Artifacts
  • permissions Permissions
  • runtime_context Runtime context
  • owner_disconnect Owner disconnect
  • ownership Ownership
  • attribution Attribution
  • context_loss Context loss
  • harness_transfer Harness transfer

Verification and delivery

SHIP-01

Retained artifacts and outputs

Judgment rule. Record diffs, documents, screenshots, recordings, previews and test/reviewer outputs. Record a searchable/browsable artifact gallery or equivalent retrieval, linked to task and exact revision, usable after sessions end, including a completed child reviewer's full findings. In-chat attachments, persistent review evidence and a cross-task gallery get distinct answers.

  • diffs Diffs
  • documents Documents
  • screenshots Screenshots
  • recordings Recordings
  • previews Previews
  • test_outputs Test outputs
  • reviewer_outputs Reviewer outputs
  • gallery Gallery
  • task_links Task links
  • revision_links Revision links
  • persistence Persistence
  • child_findings Child findings
  • prompt_leakage Prompt leakage
SHIP-02

Verification and spec gates

Judgment rule. Record tests, lint, types, CI, independent review and persistent-spec conformance checks as required versus optional. Record whether a failed check or a conflict with an existing product requirement blocks delivery. An agent saying checks passed is not a passing gate; record configured and enforced policy separately.

  • tests Tests
  • lint Lint
  • types Types
  • ci Ci
  • independent_review Independent review
  • spec_checks Spec checks
  • required_checks Required checks
  • failure_blocking Failure blocking
  • requirement_conflicts Requirement conflicts
  • configured_policy Configured policy
  • enforced_policy Enforced policy
SHIP-03

Git and pull request workflow

Judgment rule. Record branches/worktrees, commits, PR creation, review comments, CI response, rebase and conflict handling. Distinguish an integrated workflow from the agent running Git commands without product state.

  • branches Branches
  • worktrees Worktrees
  • commits Commits
  • pull_requests Pull requests
  • comments Comments
  • ci_response Ci response
  • rebase Rebase
  • conflicts Conflicts
  • product_state Product state
SHIP-04

Merge and deployment authority

Judgment rule. Record who can approve, merge, release and deploy, plus checks against the exact revision. PR creation, merge and production deployment are separate capabilities.

  • approve Approve
  • merge Merge
  • release Release
  • deploy Deploy
  • exact_revision Exact revision
  • authority_enforcement Authority enforcement
SHIP-05

Completion evidence and rollback

Judgment rule. Record task-to-commit/PR/build/deployment links, delivery status, retained evidence and rollback or revert support. Record whether approval and evidence are invalidated when the candidate revision changes after review. Agent exit alone does not prove delivery.

  • commit_links Commit links
  • pr_links Pr links
  • build_links Build links
  • deployment_links Deployment links
  • delivery_status Delivery status
  • retained_evidence Retained evidence
  • rollback Rollback
  • revert Revert
  • stale_approval_invalidation Stale approval invalidation
SHIP-06

Batch review and high-volume shipping

Judgment rule. For a queue of completed tasks, record summaries, grouping, risk/size filters, retained reviewer findings, artifact navigation, request-changes flow, approval of exact revisions, dependency-aware merge/release queues and clear next actions. Record whether stale approvals invalidate after edits and whether duplicate checks respect RUN-08. Distinguish basic diff/PR actions from a coordinated review-and-delivery queue; do not require any product's terminology.

  • review_queue Review queue
  • summaries Summaries
  • grouping Grouping
  • risk_size_filters Risk size filters
  • findings Findings
  • artifacts Artifacts
  • request_changes Request changes
  • exact_revision_approval Exact revision approval
  • dependency_queues Dependency queues
  • next_actions Next actions
  • stale_approval_invalidation Stale approval invalidation
  • check_deduplication Check deduplication

Ownership, privacy and economics

OWN-01

Source and license

Judgment rule. Record license and revision per component, including client, server and hosted extensions. Distinguish open source, source-available and closed components. Repository visibility is not a license classification or proof of hosted parity.

  • client_license Client license
  • server_license Server license
  • hosted_extensions Hosted extensions
  • source_visibility Source visibility
  • source_revision Source revision
  • hosted_parity Hosted parity
OWN-02

Hosting and exit

Judgment rule. Record self-hosting scope, required vendor services, data export/import, standard formats and account cancellation behavior. Record what remains usable without the vendor account. Exported code alone does not mean tasks, context and history are portable.

  • self_hosting Self hosting
  • vendor_dependencies Vendor dependencies
  • export Export
  • import Import
  • formats Formats
  • cancellation Cancellation
  • account_independence Account independence
  • history_portability History portability
OWN-03

Data handling and telemetry

Judgment rule. Record where code, prompts, credentials, logs and artifacts go, retention/deletion, training use, residency and subprocessors. Separately record telemetry disclosure, collection defaults, opt-in/opt-out controls and documented first-run prompts. The absence of a documented consent dialog is not proof of no telemetry, secret telemetry or unlawful processing. Separate orchestration-vendor and model-provider policies.

  • code_data Code data
  • prompts Prompts
  • credentials Credentials
  • logs Logs
  • artifacts Artifacts
  • retention Retention
  • deletion Deletion
  • training Training
  • residency Residency
  • subprocessors Subprocessors
  • telemetry_disclosure Telemetry disclosure
  • telemetry_defaults Telemetry defaults
  • telemetry_controls Telemetry controls
  • consent_prompt Consent prompt
  • provider_separation Provider separation
OWN-04

Price and included usage

Judgment rule. Record currency, billing interval, seats/seat minimums, workspace charges, included usage, credits, trial conditions, overages, taxes treatment and separate model/compute costs. Map billing routes to ACC-03. Cite public prices or dated quotes. Per-seat versus pooled billing is a fact, not a universal quality judgment.

  • currency Currency
  • interval Interval
  • seats Seats
  • seat_minimum Seat minimum
  • workspace_fees Workspace fees
  • included_usage Included usage
  • credits Credits
  • trial Trial
  • overages Overages
  • taxes Taxes
  • model_cost Model cost
  • compute_cost Compute cost
OWN-05

Scenario cost and controls

Judgment rule. Price stated workloads for one, two and five developers, with fixed tasks, concurrency, tokens and compute-hours. The two-person scenario models two developers collaborating. Include subscription, platform, model and compute charges; separate fixed, variable, included and unknown costs. No invented average task cost. Link cost visibility and reconciliation to RUN-07.

  • one_person One person
  • two_people Two people
  • five_people Five people
  • task_assumptions Task assumptions
  • concurrency Concurrency
  • tokens Tokens
  • compute_hours Compute hours
  • fixed_cost Fixed cost
  • variable_cost Variable cost
  • included_cost Included cost
  • unknown_cost Unknown cost
OWN-06

Availability and support

Judgment rule. Record GA/beta/access restrictions, support channels, documented response commitments, release activity, status history and deprecation/export options. Funding, stars and popularity can be context but are not reliability scores. An archived repository does not prove the hosted service is discontinued.

  • release_stage Release stage
  • access_restrictions Access restrictions
  • support Support
  • response_commitments Response commitments
  • release_activity Release activity
  • status_history Status history
  • deprecation Deprecation
  • export_options Export options
OWN-07

Enterprise assurance

Judgment rule. Record each claimed assurance separately: ISO standard/certificate scope, issuer and validity; SOC 2 report type, covered service and audit period; report/certificate access and verification date. Distinguish public documentation, vendor assertion, independently accessible evidence and unavailable evidence. A logo, enterprise pricing tier, SSO or a provider certification does not prove this product is certified or audited. Report controls in TEAM-02 separately; no legal-compliance verdict.

  • iso_scope Iso scope
  • iso_issuer Iso issuer
  • iso_validity Iso validity
  • soc2_type Soc2 type
  • soc2_scope Soc2 scope
  • soc2_period Soc2 period
  • report_access Report access
  • verification_date Verification date
  • evidence_status Evidence status
OWN-08

Useful free tier and evaluation access

Judgment rule. Distinguish an ongoing free tier, time-limited trial, credits-only trial, open-source self-hosting costs, paid-only access and gated early access. Map which shared scenarios work for free, especially two-person collaboration, BYO subscriptions, remote compute, mobile, issue management and review. Record card requirement, usage caps and whether meaningful evaluation needs payment or sales approval.

  • ongoing_free Ongoing free
  • trial Trial
  • credits_trial Credits trial
  • self_host_cost Self host cost
  • paid_only Paid only
  • early_access Early access
  • free_scenarios Free scenarios
  • card_required Card required
  • usage_caps Usage caps
  • paid_evaluation Paid evaluation
OWN-09

Pricing transparency

Judgment rule. Record publicly stated units, included limits, overage rates, compute/model pass-through or markup, minimum commitment, cancellation and sales-only unknowns. Use transparent, partially specified, quote-only or unknown, with named missing fields. A quote-only enterprise price is a disclosed procurement constraint, not proof of dishonesty.

  • units Units
  • included_limits Included limits
  • overages Overages
  • compute_markup Compute markup
  • model_markup Model markup
  • minimum_commitment Minimum commitment
  • cancellation Cancellation
  • sales_only_unknowns Sales only unknowns
  • transparency_classification Transparency classification