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 osmobile_apps Mobile appsbrowser Browsermobile_browser Mobile browsercli Clieditor_extensions Editor extensionstask_actions Task actionsnotifications Notificationscross_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 Harnessesmodel_providers Model providerscustom_adapters Custom adapterssession_integration Session integrationmixed_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 subscriptionsapi_accounts Api accountsvendor_credits Vendor creditslocal_models Local modelsaccount_switching Account switchingvendor_account_requirement Vendor account requirementprovider_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 setupno_git No gitlocal_git_without_remote Local git without remotehosted_git Hosted gitprerequisite_guidance Prerequisite guidancemanaged_cloud_setup Managed cloud setupbyo_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 Cliapi Apisdk Sdkmcp_server Mcp serverwebhooks Webhooksoperations Operationsauthentication Authenticationstability 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 clientplugins Pluginscustom_tools Custom toolsinstructions_import Instructions importauthentication Authenticationpermission_scope Permission scopeintegration_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 implementationmobile_implementation Mobile implementationhybrids Hybridsimplementation_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 creationprompt_intake Prompt intakeexternal_import External importchat_git_triggers Chat git triggersauthoritative_tracker Authoritative trackerstable_ids Stable idssync Syncsupported_edits Supported editsexternal_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 Plansacceptance_criteria Acceptance criteriaeditors Editorsrevisions Revisionsimplementation_links Implementation linksamendment Amendmentrestart_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 Epicshierarchy Hierarchyblockers Blockersreadiness Readinessenforcement Enforcementstate_propagation State propagationtask_to_epic Task to epicidentity_retention Identity retentionworkflow_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 Instructionsskills Skillsproject_docs Project docsmemory Memoryscope Scopeprovenance Provenancecorrection Correctiondeletion Deletionfreshness Freshnesstakeover_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 searchindexing Indexingexternal_knowledge External knowledgemultimodal_inputs Multimodal inputsfreshness Freshnessaccess_scope Access scopeapi_retrieval Api retrievalcitations Citationsconflict_detection Conflict detectionreview_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 Createedit Editdiscuss Discussprioritize Prioritizelabel Labelassign Assignsearch Searchfilter Filterarchive Archivereopen Reopenproject_epic_views Project epic viewsidea_parking Idea parkingexplicit_dispatch Explicit dispatchtask_session_separation Task session separationmetadata Metadatadurable_states Durable statesexternal_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 idsread Readcreate Createupdate Updateclaim Claimassign Assignstate_changes State changesdependencies Dependencieschildren Childrenresults Resultshuman_visibility Human visibilityattribution Attributionpermissions Permissionsconflicts 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 requirementshuman_edits Human editsagent_edits Agent editsrevisions Revisionsapprovals Approvalsimplementation_links Implementation linkslater_retrieval Later retrievaldrift_detection Drift detectionreview_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 sessionsconcurrent_tasks Concurrent tasksquotas Quotasobserved_concurrency Observed concurrencystatus_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 assignmentagent_assignment Agent assignmentclaims Claimsqueues Queuesrouting Routingduplicate_prevention Duplicate preventionownership_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 Rolesmodel_harness_effort Model harness effortmessages Messagesresults_return Results returncross_harness Cross harnessorchestration_owner Orchestration owneractivation Activationauthentication Authenticationlive_progress Live progressretained_results Retained resultsfollowup Followupinvocation 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 Schedulesevents Eventsrecurring_tasks Recurring taskscompletion_conditions Completion conditionsscheduler_location Scheduler locationoverlaps Overlapsretries Retriesclient_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 Pausestop Stopresume Resumesteer Steernotifications Notificationspending_decisions Pending decisionsescalation Escalationvisible_errors Visible errorschat_terminal_parity Chat terminal parityretained_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 fixtureparent_child Parent childdependencies Dependenciesattention Attentionhistory Historyworkload Workloadnavigation_errors Navigation errorsfixture_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 taskgrowing_epic Growing epicpresets Presetsnatural_language Natural languageagent_configuration Agent configurationin_run_changes In run changeslive_roles Live rolesretained_relationships Retained relationshipsdiscoverability Discoverabilityauth_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 Localbyo_remote Byo remoteself_hosted Self hostedmanaged_cloud Managed cloudhybrid Hybridprovisioning Provisioningpayer Payerresources Resourcesregion Regionexpiry Expiryclient_disconnect Client disconnectother_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 Checkoutbranch Branchworktree Worktreecontainer Containervm Vmos_sandbox Os sandboxfilesystem Filesystemprocess Processnetwork Networksecrets Secretscode_separation Code separationsecurity_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 disconnectworker_crash Worker crashservice_restart Service restartexpiry Expirytranscript_reload Transcript reloadprocess_reconnect Process reconnecttask_resume Task resumestate_reconstruction State reconstructioncontext_loss Context lossduplicate_actions Duplicate actionsmanual_repair Manual repairmulti_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 Dependenciescaches Cachessnapshots Snapshotsservices Servicesports Portssecrets Secretsduplicate_installs Duplicate installscollisions Collisionsremote_setup Remote setupautomatic_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 limitsturn_limits Turn limitstoken_limits Token limitsspend_limits Spend limitstimeouts Timeoutsretries Retriesprovider_failures Provider failuresenforcement 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 Logstraces Tracesfailure_reasons Failure reasonsusage_export Usage exporttask_stats Task statsagent_stats Agent statsproject_stats Project statstime_stats Time statsfailure_status Failure statusapproval_status Approval statusreconnect_consistency Reconnect consistencyperformance_method Performance methodresponsiveness 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 costsession_cost Session costchild_cost Child costepic_cost Epic costharness_aggregation Harness aggregationbilled_vs_estimated Billed vs estimatedtokens Tokenssubscription_allowance Subscription allowanceprovider_reconciliation Provider reconciliationcompute_cost Compute costrefresh_delay Refresh delayalerts Alertsexport Exportdrilldown 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 Concurrencyqueues Queuescpu_ram Cpu rambackpressure Backpressurehost_awareness Host awarenesscheck_reuse Check reusecheck_deduplication Check deduplicationbounded_tests Bounded testscancellation Cancellationfairness Fairnessrecovery Recoveryshared_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 Visibilitydiscussion Discussioncomments Commentspresence Presencecoprompting Copromptingordering Orderingconflicts Conflictsattribution Attributionpermissions Permissionsplan_restrictions Plan restrictionsowner_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 rolesproject_roles Project rolestask_roles Task rolesmembership Membershipsso Ssoprovisioning Provisioningunauthorized_access Unauthorized accessrevocation Revocationplan_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 Commandtool Toolnetwork Networksecret Secretdelivery Deliveryapprover_identity Approver identitylifetime Lifetimeallow Allowdeny Denyrevoke Revoketunnels Tunnelsdefaults Defaultssafer_modes Safer modesenforcement 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 Actionsapprovals Approvalsedits Editsdiscussion Discussiondecisions Decisionscross_user_persistence Cross user persistencecross_session_persistence Cross session persistenceexport Exportmutability Mutabilityretention Retentionintegrity 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 reviewschange_understanding Change understandingevidence_navigation Evidence navigationcomments Commentsrequest_changes Request changesshipping_guidance Shipping guidanceeffort Effortmissed_evidence Missed evidencekeyboard Keyboardnarrow_screen Narrow screencontext_switching Context switchingroles Rolesretained_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 takeoversame_task Same tasksession_history Session historydecisions Decisionsartifacts Artifactspermissions Permissionsruntime_context Runtime contextowner_disconnect Owner disconnectownership Ownershipattribution Attributioncontext_loss Context lossharness_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 Diffsdocuments Documentsscreenshots Screenshotsrecordings Recordingspreviews Previewstest_outputs Test outputsreviewer_outputs Reviewer outputsgallery Gallerytask_links Task linksrevision_links Revision linkspersistence Persistencechild_findings Child findingsprompt_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 Testslint Linttypes Typesci Ciindependent_review Independent reviewspec_checks Spec checksrequired_checks Required checksfailure_blocking Failure blockingrequirement_conflicts Requirement conflictsconfigured_policy Configured policyenforced_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 Branchesworktrees Worktreescommits Commitspull_requests Pull requestscomments Commentsci_response Ci responserebase Rebaseconflicts Conflictsproduct_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 Approvemerge Mergerelease Releasedeploy Deployexact_revision Exact revisionauthority_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 linkspr_links Pr linksbuild_links Build linksdeployment_links Deployment linksdelivery_status Delivery statusretained_evidence Retained evidencerollback Rollbackrevert Revertstale_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 queuesummaries Summariesgrouping Groupingrisk_size_filters Risk size filtersfindings Findingsartifacts Artifactsrequest_changes Request changesexact_revision_approval Exact revision approvaldependency_queues Dependency queuesnext_actions Next actionsstale_approval_invalidation Stale approval invalidationcheck_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 licenseserver_license Server licensehosted_extensions Hosted extensionssource_visibility Source visibilitysource_revision Source revisionhosted_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 hostingvendor_dependencies Vendor dependenciesexport Exportimport Importformats Formatscancellation Cancellationaccount_independence Account independencehistory_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 dataprompts Promptscredentials Credentialslogs Logsartifacts Artifactsretention Retentiondeletion Deletiontraining Trainingresidency Residencysubprocessors Subprocessorstelemetry_disclosure Telemetry disclosuretelemetry_defaults Telemetry defaultstelemetry_controls Telemetry controlsconsent_prompt Consent promptprovider_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 Currencyinterval Intervalseats Seatsseat_minimum Seat minimumworkspace_fees Workspace feesincluded_usage Included usagecredits Creditstrial Trialoverages Overagestaxes Taxesmodel_cost Model costcompute_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 persontwo_people Two peoplefive_people Five peopletask_assumptions Task assumptionsconcurrency Concurrencytokens Tokenscompute_hours Compute hoursfixed_cost Fixed costvariable_cost Variable costincluded_cost Included costunknown_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 stageaccess_restrictions Access restrictionssupport Supportresponse_commitments Response commitmentsrelease_activity Release activitystatus_history Status historydeprecation Deprecationexport_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 scopeiso_issuer Iso issueriso_validity Iso validitysoc2_type Soc2 typesoc2_scope Soc2 scopesoc2_period Soc2 periodreport_access Report accessverification_date Verification dateevidence_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 freetrial Trialcredits_trial Credits trialself_host_cost Self host costpaid_only Paid onlyearly_access Early accessfree_scenarios Free scenarioscard_required Card requiredusage_caps Usage capspaid_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 Unitsincluded_limits Included limitsoverages Overagescompute_markup Compute markupmodel_markup Model markupminimum_commitment Minimum commitmentcancellation Cancellationsales_only_unknowns Sales only unknownstransparency_classification Transparency classification