{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T08:23:26Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 16.5, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a094b5-e7b7-7bf3-908f-6ccb9eacb398\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: careware\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 043: 1001 regist", "usd": 0.0, "recall": true }, "codex": { "seconds": 63.1, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a094b5-e7c0-7ba1-acb9-3f2cd6a8fa83\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: careware\nRegistry id: vr.tr.careware\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContex" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:54:37+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:25+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q1035935", "registryId": "vr.tr.careware", "name": "careware", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1035935/", "model": { "registry_id": "vr.tr.careware", "name": "careware", "purpose": "Enable an agent to recognise careware and determine how its charitable contribution arrangement relates to acquiring, using and redistributing the software.", "definition": "Careware is software distributed under an arrangement that asks users to support a charitable cause or perform a beneficial act, often instead of paying the software author.", "scope_statement": "This model owns the charitable distribution arrangement attached to software identified as careware under vr.tr.careware, provisionally interpreting the term as charityware; the supplied PHY / PHY.OBJ classification remains unresolved because the documented meaning concerns software rather than a physical object.", "in_scope": [ "Evidence that a software release is offered as careware", "Requested or required charitable contributions associated with distribution or use", "Beneficiary selection and contribution routing", "Distinction between charitable appeals and software permission conditions", "Changes to the careware arrangement across releases and distributors" ], "out_of_scope": [ "Software functionality, architecture and runtime performance", "Physical storage media and computing hardware", "Charity governance and general programme operations", "Generic payment processing and personal donation records", "Healthcare software identified only by a similar product name" ], "distinguishing_features": [ "The charitable connection is evidenced in the software's distribution materials or provider statements, rather than inferred from a socially useful function.", "An appeal for money solely to support the developer does not establish careware status without evidence of a charitable arrangement.", "Free distribution alone does not establish careware status; Vim demonstrates free distribution accompanied by a charitable appeal. [Vim: About](https://www.vim.org/about.php)", "A charitable arrangement may involve a suggested donation or a charity-directed distribution levy; the careware label alone does not identify which applies. [Jargon File: careware](https://www.catb.org/jargon/html/C/careware.html)", "The entry describes a software distribution category, provisionally distinguished from physical care equipment and similarly named software products." ], "characteristics": [ { "name": "Careware designation evidence", "kind": "relation", "unit_or_values": "Software release linked to an attributable careware statement", "why_it_matters": "Supports classification without relying on the name or application purpose." }, { "name": "Contribution mechanism", "kind": "category", "unit_or_values": "Suggested direct donation; stated donation condition; included charitable levy; other documented mechanism; unresolved", "why_it_matters": "Determines which contribution workflow the agent should describe." }, { "name": "Contribution force", "kind": "category", "unit_or_values": "Voluntary appeal; stated contractual condition; ambiguous; unspecified", "why_it_matters": "Prevents an appeal from being treated as an established restriction on use." }, { "name": "Beneficiary selection", "kind": "category", "unit_or_values": "Provider-nominated; user-selected within stated criteria; unspecified", "why_it_matters": "Determines whether a proposed recipient matches the arrangement." }, { "name": "Contribution recipient", "kind": "relation", "unit_or_values": "Named beneficiary or intermediary linked to its stated role", "why_it_matters": "Separates the intended beneficiary from whoever collects the money." }, { "name": "Contribution amount rule", "kind": "measurement", "unit_or_values": "Currency amount, percentage with calculation base, user-selected amount, or unspecified", "why_it_matters": "Allows an agent to explain the charitable component without inventing a price." }, { "name": "Contribution trigger", "kind": "category", "unit_or_values": "Acquisition; use; continued use; redistribution; sale; other documented trigger; unspecified", "why_it_matters": "Identifies when the appeal or stated condition applies." }, { "name": "Arrangement verification state", "kind": "state", "unit_or_values": "Verified for identified release; historical evidence only; conflicting evidence; unresolved", "why_it_matters": "Prevents old donation instructions from being presented as current." } ], "affordances": [ "Classify a software offering as careware when attributable evidence supports the designation.", "Explain the charitable appeal separately from the release's software permissions.", "Identify the nominated beneficiary or evaluate a user-selected recipient against stated criteria.", "Calculate a documented charitable levy from its amount rule and calculation base.", "Prepare contribution instructions for user review using verified recipient information.", "Compare releases or distribution channels for changes in their charitable arrangements." ], "agent_conduct": { "may": [ "Describe careware and how its charitable requests work, citing the author's terms.", "Report the licence terms and the cause an author names for a careware program." ], "must_not": [ "Claim that a program is careware or that a charity endorses it without the author's terms.", "Redirect donations meant for a named cause to anyone else.", "Pressure users with guilt or false urgency to donate.", "Distribute modified copies against the author's licence." ], "requires_human": [ "Making a donation or commitment on a user's behalf." ] }, "ethics": { "considerations": [ "Careware relies on trust; misusing the charity link deceives users and harms causes.", "Users who cannot pay should not be shamed." ], "affected_parties": [ "Users", "Software authors", "Charities named" ] }, "owners": { "steward": "The software author who sets the terms.", "master_systems": [] }, "failure_modes_and_hazards": [ "Fake charity requests can be used to scam users.", "Vague terms leave users unsure what is asked of them." ], "what_it_is_for": [ "Careware is encountered in software distribution arrangements that connect use of a program with support for a charitable cause or beneficial activity.", "Users and redistributors consult the actual license to distinguish enforceable conditions from voluntary requests for contributions." ], "standards_and_regulation": [ "The WIPO Copyright Treaty, adopted by the World Intellectual Property Organization, requires computer programs to receive copyright protection as literary works and provides a legal framework relevant to careware licensing." ], "facets_not_applicable": { "recognition": "Careware is a distribution arrangement established through its terms rather than through the software's visual appearance." } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q1035935: careware", "url": "https://www.wikidata.org/wiki/Q1035935", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Careware", "url": "https://en.wikipedia.org/wiki/Careware", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "careware-identity", "name": "Careware identity", "description": "Establish what makes the offering careware and which software it covers.", "rationale": "The registry has no definition and assigns a physical-object domain that conflicts with the documented software meaning.", "layers": [ { "id": "term-and-boundary", "name": "Term and boundary", "description": "Resolve the intended sense without silently changing registry identity.", "findings": [ { "id": "charitable-software-sense", "name": "Charitable software sense", "description": "The working interpretation is software associated with a charitable contribution arrangement. A primary example is Vim's own charityware designation. [Vim: About](https://www.vim.org/about.php)", "questions": [ { "text": "Does the registry's originating record identify careware as the software distribution concept?", "kind": "provenance", "id": "charitable-software-sense-q01" }, { "text": "Should this entry's PHY / PHY.OBJ assignment be corrected while retaining vr.tr.careware?", "kind": "boundary", "id": "charitable-software-sense-q02" } ] } ] }, { "id": "designation-coverage", "name": "Designation coverage", "description": "Bind the charitable designation to the offering that actually carries it.", "findings": [ { "id": "release-specific-evidence", "name": "Release-specific evidence", "description": "Record the provider statement and its coverage rather than automatically extending a careware designation to every edition, fork or distributor.", "questions": [ { "text": "Which release, edition or distribution carries the careware statement?", "kind": "boundary", "id": "release-specific-evidence-q01" }, { "text": "Who issued that statement, and where can its original wording be read?", "kind": "provenance", "id": "release-specific-evidence-q02" } ] } ] } ] }, { "id": "appeals-and-permissions", "name": "Appeals and permissions", "description": "Determine how charitable language relates to permission to use and distribute the software.", "rationale": "An agent must not infer restrictions from a charitable label or erase explicitly stated conditions.", "layers": [ { "id": "contribution-language", "name": "Contribution language", "description": "Identify the force and trigger of the charitable statement.", "findings": [ { "id": "appeal-or-condition", "name": "Appeal or condition", "description": "Preserve the distinction between encouragement, a stated condition and ambiguous wording without asserting legal enforceability.", "questions": [ { "text": "What exact language presents the contribution as optional, expected or required?", "kind": "definition", "id": "appeal-or-condition-q01" }, { "text": "What event activates the appeal or stated condition?", "kind": "action", "id": "appeal-or-condition-q02" } ] } ] }, { "id": "license-relationship", "name": "License relationship", "description": "Link the charitable arrangement to the applicable software terms.", "findings": [ { "id": "independent-permission-evidence", "name": "Independent permission evidence", "description": "Determine software permissions from the relevant terms. Careware status alone does not establish source availability, modification rights or redistribution rights.", "questions": [ { "text": "Which license applies to the identified release, and does it incorporate the charitable statement?", "kind": "provenance", "id": "independent-permission-evidence-q01" }, { "text": "Which requested software action requires checking terms beyond the careware designation?", "kind": "action", "id": "independent-permission-evidence-q02" } ] } ] } ] }, { "id": "charitable-benefit", "name": "Charitable benefit", "description": "Describe the intended beneficiary and what contribution the arrangement requests.", "rationale": "A donation request is not actionable until its recipient rules and contribution basis are understood.", "layers": [ { "id": "beneficiary-choice", "name": "Beneficiary choice", "description": "Identify who receives the intended charitable benefit and who selects them.", "findings": [ { "id": "recipient-selection-rule", "name": "Recipient selection rule", "description": "Record named beneficiaries or documented criteria for user selection, keeping the beneficiary distinct from the software author.", "questions": [ { "text": "Does the provider nominate a beneficiary or allow the user to choose one?", "kind": "definition", "id": "recipient-selection-rule-q01" }, { "text": "What evidence identifies the named recipient or establishes the selection criteria?", "kind": "provenance", "id": "recipient-selection-rule-q02" } ] } ] }, { "id": "contribution-basis", "name": "Contribution basis", "description": "Capture the requested contribution without supplying missing amounts.", "findings": [ { "id": "amount-and-frequency", "name": "Amount and frequency", "description": "Distinguish discretionary donations from fixed amounts or percentage levies, and capture any documented frequency.", "questions": [ { "text": "What amount, currency or percentage base is specified, if any?", "kind": "measurement", "id": "amount-and-frequency-q01" }, { "text": "Is the contribution requested once, per acquisition, periodically or on another stated basis?", "kind": "definition", "id": "amount-and-frequency-q02" } ] } ] } ] }, { "id": "contribution-routing", "name": "Contribution routing", "description": "Connect the charitable arrangement to a verifiable contribution route.", "rationale": "A direct donation and a distributor-collected levy require different instructions and different evidence of delivery.", "layers": [ { "id": "collection-path", "name": "Collection path", "description": "Identify how the contribution reaches its intended beneficiary.", "findings": [ { "id": "direct-or-intermediated", "name": "Direct or intermediated contribution", "description": "Record whether users contribute directly or a distributor collects and forwards a charitable component.", "questions": [ { "text": "Who receives the user's payment, and who is supposed to transfer any charitable share?", "kind": "definition", "id": "direct-or-intermediated-q01" }, { "text": "Which provider or beneficiary source verifies the contribution route?", "kind": "provenance", "id": "direct-or-intermediated-q02" } ] } ] }, { "id": "benefit-evidence", "name": "Benefit evidence", "description": "Separate promised charitable benefit from evidenced transfer.", "findings": [ { "id": "claim-and-delivery", "name": "Claim and delivery", "description": "A careware designation describes an arrangement; it does not itself demonstrate that funds were transferred or outcomes achieved.", "questions": [ { "text": "What evidence supports any claim that the charitable share was delivered?", "kind": "provenance", "id": "claim-and-delivery-q01" }, { "text": "Should the agent describe the benefit as promised, transfer-evidenced or unresolved?", "kind": "action", "id": "claim-and-delivery-q02" } ] } ] } ] }, { "id": "arrangement-continuity", "name": "Arrangement continuity", "description": "Track whether the careware arrangement remains applicable as software and beneficiaries change.", "rationale": "Historical labels, changed recipients and repackaged releases can otherwise produce incorrect contribution instructions.", "layers": [ { "id": "release-and-channel-changes", "name": "Release and channel changes", "description": "Compare charitable terms across versions and distribution channels.", "findings": [ { "id": "arrangement-inheritance", "name": "Arrangement inheritance", "description": "Require evidence before carrying a predecessor's charitable arrangement into a fork, commercial edition or repackaged distribution.", "questions": [ { "text": "Does this release or distributor retain, replace or omit the earlier charitable arrangement?", "kind": "boundary", "id": "arrangement-inheritance-q01" }, { "text": "Which dated statement supports the change or continuity?", "kind": "provenance", "id": "arrangement-inheritance-q02" } ] } ] }, { "id": "recipient-and-link-changes", "name": "Recipient and link changes", "description": "Manage obsolete or conflicting contribution instructions.", "findings": [ { "id": "current-instruction-confidence", "name": "Current instruction confidence", "description": "Record when instructions were verified and preserve uncertainty when a recipient changes or authoritative sources disagree.", "questions": [ { "text": "When were the recipient identity and contribution route last verified?", "kind": "measurement", "id": "current-instruction-confidence-q01" }, { "text": "What authoritative update is needed before the agent can present replacement contribution instructions?", "kind": "action", "id": "current-instruction-confidence-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "The recalled meaning concerns software distribution, which does not fit the supplied PHY.OBJ domain or device classification; verify the registry's intended referent.", "Careware is an informal label rather than a single standardized license; requests and obligations vary by program.", "The boundary between careware and charityware is not consistently maintained." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of careware this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Distributing software while encouraging donations to charity.", "Using software distribution to encourage goodwill or community service." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of careware this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Mistaking the careware label for permission to modify or redistribute software; those rights depend on the actual license.", "Confusing a voluntary charitable request with a binding condition of use." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of careware this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "charityware", "difference": "Often used synonymously; charityware more specifically emphasizes charitable support, whereas careware can request other beneficial acts." }, { "name": "donationware", "difference": "Requests donations that may support the developer; careware emphasizes a charitable cause or beneficial action." }, { "name": "freeware", "difference": "Describes software available without a monetary charge, without necessarily requesting charitable action." }, { "name": "free software", "difference": "Defines freedoms to use, study, modify and share software; the careware label alone does not establish those freedoms." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of careware this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the originating registry record confirm the software meaning of careware, and what plane and domain should replace PHY / PHY.OBJ if so?", "Does an existing Vercy software or licensing model already own this concept, requiring a link instead of a separate publication?", "Should nonmonetary good-deed requests qualify as careware in this registry, and which primary examples establish that boundary?", "Where should this registry draw the boundary between careware, developer-support donationware and commercial software with incidental charitable promotions?", "Which primary examples establish mandatory contribution arrangements, and how should their stated conditions be represented without assuming enforceability?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 14, "questions": 24 } }