{ "model": { "rank": 6540, "code": "thing-q203005", "model_id": "vr.tr.suite", "name": "suite", "purpose": "Enable an AI agent to recognise a suite as a named musical whole, assess the integrity of its constituent movements or pieces, and determine which arrangements, performances or presentations preserve its identity.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.MED", "industry": "", "version": "", "url": "/models/thing/q203005/", "tier": 2, "score": 60, "payload": { "layer": "wikidata", "aliases": [ "Baroque suite", "orchestral suite", "organ suite" ], "aliasCount": 3, "merged": 3, "knownIn": 60, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.suite-group", "source": { "dataset": "wikidata", "item": "Q203005", "url": "https://www.wikidata.org/wiki/Q203005", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T15:11:44Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.00467942, "turns": 1, "seconds": 75.7, "error": null }, "codex": { "seconds": 82.8, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\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: 01a07c6b-134a-7af3-92c7-5188453e0dbd\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: suite\nRegistry id: vr.tr.suite\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Vercy model" } } }, "metaModel": { "id": "THING-Q203005", "registryId": "vr.tr.suite", "name": "suite", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q203005/", "model": { "registry_id": "vr.tr.suite", "name": "suite", "purpose": "Enable an AI agent to recognise a suite as a named musical whole, assess the integrity of its constituent movements or pieces, and determine which arrangements, performances or presentations preserve its identity.", "definition": "A software or content product grouping sold, licensed, or deployed as one named offering, in which separately identifiable applications, modules, or titles share branding, a common commercial envelope, and usually a joint install or entitlement path.", "scope_statement": "Provisionally interpret suite in INF.MED as a musical work comprising distinct movements or pieces intended to form a larger whole; own its collective identity, membership, ordering constraints and relationship to source works, while leaving the registry's intended sense open for confirmation.", "in_scope": [ "The evidence that establishes the suite as a whole rather than an incidental grouping", "Constituent movements or pieces and their roles within the suite", "Required, optional and version-dependent membership and sequence", "Musical or programmatic relationships connecting the constituents", "Boundaries between the suite, its source works, variants and partial presentations" ], "out_of_scope": [ "Software product suites and their application integrations", "Hotel suites and other spatial groupings", "Detailed internal analysis of each constituent movement", "Individual performance events and performer biographies", "Recording releases, audio files and their technical properties", "Independent rights records for compositions, arrangements and recordings" ], "distinguishing_features": [ "A title, score, attribution or other identifiable evidence establishes the constituents as one suite; their co-occurrence in a playlist is insufficient.", "The constituents retain distinguishable identities or boundaries within the larger whole; multiple passages alone do not establish a suite.", "An album or concert programme may contain a suite, but its track list or running order does not by itself define the suite's membership.", "A suite assembled from another work has an identifiable selection or arrangement relationship to that source; it is not automatically the complete source work.", "Movement count, dance titles or stylistic resemblance alone cannot settle classification against neighbouring forms such as a sonata, symphony or song cycle." ], "characteristics": [ { "name": "Suite designation evidence", "kind": "category", "unit_or_values": "creator designation | editorial designation | catalogue designation | inferred | unresolved", "why_it_matters": "Distinguishes an evidenced work identity from an agent's proposed grouping." }, { "name": "Constituent membership", "kind": "relation", "unit_or_values": "Links to constituent pieces or movements, qualified by suite version and membership evidence", "why_it_matters": "Makes it possible to recognise the whole and detect omissions or substitutions." }, { "name": "Constituent count", "kind": "measurement", "unit_or_values": "Number of constituents in a specified version, with uncertainty recorded", "why_it_matters": "Supports completeness checks without treating recording track count as movement count." }, { "name": "Sequence constraint", "kind": "category", "unit_or_values": "fixed | partially constrained | flexible | version-dependent | unresolved", "why_it_matters": "Determines whether reordering preserves an established presentation of the suite." }, { "name": "Formation relationship", "kind": "category", "unit_or_values": "composed as a suite | extracted from a larger work | assembled from existing pieces | mixed | unresolved", "why_it_matters": "Identifies which source relationships and selection decisions the agent must inspect." }, { "name": "Suite-level cohesion", "kind": "category", "unit_or_values": "One or more evidenced links: dance sequence, thematic material, tonal plan, narrative, programme, stylistic design, other stated rationale, unresolved", "why_it_matters": "Records why these constituents belong together without imposing one universal musical pattern." }, { "name": "Presentation completeness", "kind": "state", "unit_or_values": "complete for identified version | selected movements | altered membership | unresolved", "why_it_matters": "Prevents excerpts and modified programmes from being represented as an unqualified complete suite." }, { "name": "Scoring relationship", "kind": "relation", "unit_or_values": "Links between the suite's identified scoring and alternative arrangements or orchestrations", "why_it_matters": "Helps distinguish another realisation of the suite from a separately constituted work." } ], "affordances": [ "Determine whether a candidate grouping has sufficient evidence to be represented as a suite.", "Reconstruct and compare membership and order across identified suite versions.", "Classify a programme or recording as a complete suite, an excerpt or an altered selection.", "Trace extracted movements to their source works and identify suite-specific changes.", "Evaluate proposed omissions, substitutions or reordering against documented constraints.", "Select a suitable score or arrangement for a requested presentation while exposing unresolved identity and permission questions." ] }, "sources": [ { "id": "iso-19770-5", "title": "ISO/IEC 19770-5:2015 Information technology - IT asset management - Overview and vocabulary", "url": "https://www.iso.org/standard/68291.html", "what_it_supports": "Defines software identification and grouping vocabulary used when a suite is treated as a licensed software product rather than a single executable.", "url_status": "blocked" }, { "id": "spdx-3", "title": "SPDX 3.0 Specification - Software Package Data Exchange", "url": "https://spdx.github.io/spdx-spec/v3.0.1/", "what_it_supports": "Package and relationship model (CONTAINS, PACKAGE_OF) against which a suite-as-bundle of packages is recorded.", "url_status": "live" }, { "id": "cim-sw", "title": "DMTF CIM Schema - CIM_SoftwareElement / CIM_Product", "url": "https://www.dmtf.org/standards/cim", "what_it_supports": "Product vs. software-element distinction used in inventory: a suite is typically a Product that groups SoftwareElements.", "url_status": "live" }, { "id": "gs1-gtin", "title": "GS1 General Specifications - GTIN and trade item hierarchy", "url": "https://www.gs1.org/standards/barcodes-epcrfid-id-keys/gs1-general-specifications", "what_it_supports": "Trade-item hierarchy (each, inner pack, case) analogous to SKU-level identification of a suite as a sellable bundle.", "url_status": "blocked" } ], "structure": { "bundles": [ { "id": "suite-identity", "name": "Suite identity", "description": "Establish the named musical whole and the evidence for calling it a suite.", "rationale": "A collection of pieces must not acquire suite identity merely because an agent encounters them together.", "layers": [ { "id": "designation-and-attribution", "name": "Designation and attribution", "description": "Record who designated the whole as a suite and what that designation covers.", "findings": [ { "id": "evidenced-suite-designation", "name": "Evidenced suite designation", "description": "Capture the title, responsible party and supporting material that establish the collective work.", "questions": [ { "text": "Which title and attribution identify this particular suite rather than another suite with a similar name?", "kind": "definition", "id": "evidenced-suite-designation-q01" }, { "text": "What score, creator statement, edition or catalogue supports the suite designation, and who supplied it?", "kind": "provenance", "id": "evidenced-suite-designation-q02" } ] } ] }, { "id": "work-and-container-boundaries", "name": "Work and container boundaries", "description": "Separate the suite from programmes, releases and neighbouring musical forms.", "findings": [ { "id": "whole-versus-incidental-grouping", "name": "Whole versus incidental grouping", "description": "Record the evidence that the pieces constitute a work-level whole independently of a particular presentation.", "questions": [ { "text": "What establishes these pieces as constituents of one suite rather than items on a playlist, album or concert programme?", "kind": "boundary", "id": "whole-versus-incidental-grouping-q01" }, { "text": "If another form designation also applies, what evidence supports retaining suite as this work's classification?", "kind": "definition", "id": "whole-versus-incidental-grouping-q02" } ] } ] } ] }, { "id": "movement-constitution", "name": "Movement constitution", "description": "Describe which pieces constitute the suite and how they may be sequenced.", "rationale": "Recognising a suite and judging its completeness require version-specific membership and ordering evidence.", "layers": [ { "id": "constituent-membership", "name": "Constituent membership", "description": "Identify movements or pieces without confusing musical divisions with file or track divisions.", "findings": [ { "id": "movement-roster", "name": "Movement roster", "description": "Record constituent identities, alternate titles and required or optional status for an identified version.", "questions": [ { "text": "Which movements or pieces belong to this version, and which are optional, alternative or disputed?", "kind": "definition", "id": "movement-roster-q01" }, { "text": "How many musical constituents are established, and where do recording tracks split or combine them?", "kind": "measurement", "id": "movement-roster-q02" } ] } ] }, { "id": "sequence-and-continuity", "name": "Sequence and continuity", "description": "Record ordering requirements and connections between adjacent movements.", "findings": [ { "id": "permitted-movement-order", "name": "Permitted movement order", "description": "Distinguish documented sequence constraints from customary or presentation-specific choices.", "questions": [ { "text": "Which movement positions, transitions or uninterrupted connections are prescribed by the relevant score or edition?", "kind": "provenance", "id": "permitted-movement-order-q01" }, { "text": "Can an agent reorder movements or insert an interval while still describing the result as this version of the suite?", "kind": "action", "id": "permitted-movement-order-q02" } ] } ] } ] }, { "id": "suite-cohesion", "name": "Suite cohesion", "description": "Represent the evidenced musical or programmatic relationships that give the sequence collective significance.", "rationale": "Membership alone cannot explain whether a proposed alteration disrupts the suite's organising design.", "layers": [ { "id": "musical-relationships", "name": "Musical relationships", "description": "Capture relationships across movements when supported by analysis or explicit documentation.", "findings": [ { "id": "cross-movement-design", "name": "Cross-movement design", "description": "Record shared material, tonal relationships, rhythmic patterns or deliberate contrasts without assuming that every suite uses them.", "questions": [ { "text": "Which recurring materials or musical contrasts connect particular movements, and which remain unestablished?", "kind": "definition", "id": "cross-movement-design-q01" }, { "text": "What score passages or identified analyses support each proposed cross-movement relationship?", "kind": "provenance", "id": "cross-movement-design-q02" } ] } ] }, { "id": "programmatic-and-functional-design", "name": "Programmatic and functional design", "description": "Record any dance, narrative, descriptive or other stated organising rationale.", "findings": [ { "id": "constituent-roles", "name": "Constituent roles", "description": "Explain evidenced roles such as opening, contrast, narrative episode or closure within this suite.", "questions": [ { "text": "Does the suite have a documented dance sequence, programme or narrative, and what role does each relevant movement serve?", "kind": "definition", "id": "constituent-roles-q01" }, { "text": "Which omissions or substitutions would interrupt that documented design, and on what evidence?", "kind": "action", "id": "constituent-roles-q02" } ] } ] } ] }, { "id": "formation-and-versions", "name": "Formation and versions", "description": "Trace the constitution of the suite and distinguish its versions from related works.", "rationale": "An extracted or revised suite can differ materially from both its source work and other suites drawn from that source.", "layers": [ { "id": "source-work-derivation", "name": "Source work derivation", "description": "Identify pre-existing material and the acts of selection or adaptation that formed the suite.", "findings": [ { "id": "extraction-and-assembly", "name": "Extraction and assembly", "description": "Link constituents to source material and record who selected, reordered or adapted it.", "questions": [ { "text": "Was this suite composed as a whole or constituted from existing material, and what evidence establishes that history?", "kind": "provenance", "id": "extraction-and-assembly-q01" }, { "text": "Where do extracted movements differ from their source passages through cuts, new endings, transitions or other changes?", "kind": "boundary", "id": "extraction-and-assembly-q02" } ] } ] }, { "id": "version-and-arrangement-boundaries", "name": "Version and arrangement boundaries", "description": "Distinguish revisions, alternative scorings and independently constituted suites.", "findings": [ { "id": "variant-identity", "name": "Variant identity", "description": "Record how a candidate variant relates to the suite, including unresolved work-identity decisions.", "questions": [ { "text": "Which membership, sequence or scoring differences distinguish this version from other documented versions?", "kind": "boundary", "id": "variant-identity-q01" }, { "text": "What attribution or editorial evidence supports treating the candidate as an arrangement, a revision or a separate suite?", "kind": "provenance", "id": "variant-identity-q02" } ] } ] } ] }, { "id": "presentation-and-intervention", "name": "Presentation and intervention", "description": "Assess proposed or observed presentations against an identified suite and its constraints.", "rationale": "Agents need to label partial presentations accurately and determine what evidence is needed before altering the suite.", "layers": [ { "id": "presentation-integrity", "name": "Presentation integrity", "description": "Compare an actual programme, score or recording with the intended suite version.", "findings": [ { "id": "complete-or-selected-presentation", "name": "Complete or selected presentation", "description": "Identify missing, repeated, substituted or reordered movements and qualify completeness accordingly.", "questions": [ { "text": "Against which suite version is this presentation being checked, and which constituents are present or absent?", "kind": "measurement", "id": "complete-or-selected-presentation-q01" }, { "text": "Should the agent label the presentation as the complete suite, selected movements or an altered selection?", "kind": "action", "id": "complete-or-selected-presentation-q02" } ] } ] }, { "id": "adaptation-decisions", "name": "Adaptation decisions", "description": "Connect proposed changes to musical constraints, attribution and external permission evidence.", "findings": [ { "id": "change-conditions", "name": "Change conditions", "description": "Record what supports a proposed cut, reordering or rescoring and which dependencies remain unresolved.", "questions": [ { "text": "What documented constraints and suite-level relationships must an agent check before cutting, reordering or rescoring this suite?", "kind": "action", "id": "change-conditions-q01" }, { "text": "Which external rights or permission records govern the proposed adaptation or use of the chosen score, and are those records available?", "kind": "action", "id": "change-conditions-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-kinds", "name": "Kinds and varieties", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "office/productivity suite", "creative/media production suite", "security/endpoint suite", "developer/test suite", "enterprise application suite (ERP/CRM/HCM)", "media/content catalogue suite (film, TV, or recording)", "operating-environment suite (OEM/OEM-bundled)", "compliance/governance documentation suite" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of suite this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "scheme": "Wikidata", "value_or_pattern": "Q1312270 (software suite); also Q813366 (application suite) where catalogues collapse the two", "note": "Wikidata splits 'software suite' from looser 'application suite'; media suites may instead sit under Q11424 (film) franchise items or Q7366 (song) collections and should not reuse Q1312270." }, { "scheme": "CPE 2.3", "value_or_pattern": "cpe:2.3:a::::*:*:*:*:*:*:*", "note": "NIST NVD binds many suites at product level (e.g. microsoft:365, adobe:creative_cloud) rather than at each constituent app." }, { "scheme": "SWID / ISO/IEC 19770-2 tag", "value_or_pattern": " with or parent/child tags", "note": "Suite SKU is the parent SoftwareIdentity; constituent apps are component or patch links." }, { "scheme": "SPDX / purl", "value_or_pattern": "pkg:generic//@ or pkg:nuget/pkg:npm for constituents; suite recorded as a package with CONTAINS relationships", "note": "There is no dedicated 'suite' purl type; practice is a parent package plus relationships." }, { "scheme": "GS1 GTIN / ISBN-13", "value_or_pattern": "14-digit GTIN for boxed or downloadable suite SKUs; ISBN-13 for published media box-sets sold as one title", "note": "A GTIN identifies the sellable suite SKU, not the running software inside it." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of suite this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "ISO/IEC 19770-2 and 19770-3 (ISO/IEC JTC 1/SC 7) - SWID tags and software entitlement schema, the usual way a licensed suite is identified and counted", "ISO/IEC 19770-5:2015 vocabulary (ISO) - product vs. element vs. entitlement", "SPDX 2.x/3.x (Linux Foundation / ISO/IEC 5962) - bill of materials when a suite is redistributed or embedded", "NIST IR 7695 / CPE 2.3 Naming (NIST) - vulnerability and inventory naming of suite products", "EU Digital Markets Act (Regulation (EU) 2022/1925) and bundling case law (European Commission / CJEU) - constraints on tying and pre-installation of software suites on gatekeeper platforms", "US DOJ/FTC tying and bundling doctrine (Sherman Act §1/§2; Clayton Act §3) - historic Microsoft, Adobe, and office-suite bundling cases", "Software licence / EULA of the suite vendor (vendor-issued, not a public standard) - defines whether constituents may be installed, transferred, or used separately" ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of suite this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Procurement and SAM tools (Flexera, ServiceNow SAM, Snow) count a suite SKU as one entitled product that covers several installable titles, then reconcile installs against that entitlement.", "Enterprise app stores and MDM/EMM catalogues advertise a suite (Microsoft 365 Apps, Adobe Creative Cloud, Google Workspace) as the unit of assignment, while endpoints receive individual packages.", "Media distributors sell a 'suite' of titles or a box-set (Criterion, a record-label anthology, a broadcaster's 'complete series') as one catalogue entry with one price and one rights window.", "Developer CI systems treat a test suite as the runnable collection of cases for a component; that usage is neighbouring, not the commercial software-suite sense.", "OEM and ISP bundles ship a security or utility suite pre-installed, licensed for a device lifetime or a subscription term." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of suite this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "quantity": "constituent title count", "typical_range": "2-20 named apps or modules in a commercial software suite; media box-sets 3-50 titles", "unit": "count" }, { "quantity": "list or subscription price of the suite SKU", "typical_range": "USD 5-100 per user-month for cloud productivity/creative suites; USD 50-2500 perpetual for on-prem suites", "unit": "currency / seat / year" }, { "quantity": "licence metric (seats, devices, cores, or named users)", "typical_range": "1-unlimited; enterprise agreements commonly 100-100000 seats", "unit": "seat | device | core" }, { "quantity": "install footprint of the full suite", "typical_range": "0.5-20 GiB on disk for office/security suites; 10-100+ GiB for creative suites with shared media caches", "unit": "GiB" }, { "quantity": "entitlement coverage ratio (licensed titles vs. installed titles)", "typical_range": "0.2-1.0 in SAM audits; under-deployment is common when users install only 1-2 apps of a large suite", "unit": "dimensionless ratio" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of suite this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Licence under- or over-counting: installing one constituent can legally consume a whole-suite entitlement, or conversely a suite licence may not cover a standalone SKU of the same app.", "Bundle lock-in and tying: a required constituent (e.g. a browser or media player) is unremovable or updates independently, creating supply-chain and competition risk.", "Shared-component version skew: suite runtime libraries (VC++ redistributables, Creative Cloud desktop, .NET) break other products on the same machine.", "Orphaned constituents after suite retirement or SKU rename (Office 365 → Microsoft 365; Creative Suite → Creative Cloud) leave inventory and CPE mappings stale.", "Security surface: a vulnerability in one suite component is often scored against the parent product CPE, causing false-positive or false-negative patch status.", "Rights-window mismatch in media suites: one title in a box-set or channel bundle expires or is geo-blocked while the suite listing remains on sale." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of suite this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "North American SAM practice usually inventories the suite SKU (Microsoft 365 E3, Adobe All Apps); much of continental Europe still records each constituent application for audit against OEM and volume-licence contracts.", "Japanese and Korean ISVs historically sold 'office packs' as a single localised SKU with different constituent lists than the US suite of the same brand.", "EU DMA and national consumer-bundling rules restrict pre-installation and uninstallation of suite constituents on gatekeeper OSes; US practice is largely contractual/EULA.", "In broadcasting and home video, UK/Commonwealth 'box set' is the common commercial name; US catalogues say 'collection' or 'complete series'; 'suite' is rarer except in software and hotel senses.", "French and Spanish IT catalogues often use 'suite logicielle' / 'suite ofimática' as the headword where English procurement says 'office suite' or just the vendor product name." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of suite this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "name": "application (single product)", "difference": "A single application is licensed, installed, and versioned on its own; a suite is the commercial parent that may include that application plus others under one SKU." }, { "name": "software package / installer", "difference": "A package is a distribution artefact (MSI, deb, magento module). A suite may comprise many packages and is identified at product/entitlement level, not by one file." }, { "name": "platform or operating system", "difference": "A platform provides runtime and APIs that third parties target; a suite is a vendor-curated set of applications that happens to share branding and licence, and need not expose a platform." }, { "name": "test suite", "difference": "A test suite is a runnable collection of cases or fixtures (xUnit, CTS). It is not a licensed product grouping; count tests, not seats." }, { "name": "bundle / BOM / distro", "difference": "A Linux distro or an SPDX BOM is a technical composition. A commercial suite is defined by the sellable SKU and EULA even if the technical BOM is larger or smaller than the marketed list." }, { "name": "collection / box-set / anthology (media)", "difference": "A media collection groups finished titles for sale or exhibition. Call it a suite only when the publisher markets that grouping as one named product with shared rights and catalogue identity; otherwise it is a collection." }, { "name": "hotel/apartment suite", "difference": "A lodging suite is a unit of real property (rooms + facilities). INF.MED 'suite' is an information product; do not reuse lodging identifiers (UN/LOCODE + property codes)." }, { "name": "musical suite", "difference": "A musical suite is an ordered set of movements (BWV, opus). Identity is a work/expression (ISWC, music-catalogue number), not a software SKU." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of suite this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.suite in INF.MED specifically mean a musical suite, or does the registry intend another media grouping?", "Which existing Vercy models already own musical works, movements, collections and arrangements, and could one already cover this concept?", "What evidence threshold should establish suite identity when the designation comes from a later editor, publisher or catalogue?", "How should catalogue identity be maintained when versions differ in movement membership as well as scoring?", "How broadly should the model cover suites outside the traditions represented by its initial research sources?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "work, medium or creative form", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a suite, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a suite as a named musical whole, assess the integrity of its constituent movements or pieces, and determine which arrangements, performances or presentations preserve its identity.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted", "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Baroque suite, orchestral suite, organ suite.", "3 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 60 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a suite, and on what evidence are they told apart?" ], "whatItIsMadeOf": "content that has to be carried by something else", "physicalCharacter": [ "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "read it and act on what it says", "observe it, measure it, record its state" ], "howItIsRecognised": [ "What is seen is a copy or a performance, not the work. Recognising the work means recognising the content through whatever is carrying it." ], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "Baroque suite", "orchestral suite", "organ suite" ] } ], "standing": "Described in 60 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 3 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one suite from another, and a suite from things that resemble it.", "rationale": "Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.", "layers": [ { "id": "naming-and-identifiers", "name": "Names and identifiers", "description": "The names this thing goes by and the identifiers that survive translation and time.", "findings": [ { "id": "preferred-name-and-aliases", "name": "Preferred name, aliases and local names", "description": "Which name to use, which names mean the same thing, and which merely sound similar.", "questions": [ { "id": "preferred-name-and-aliases-q01", "text": "What identifies and describes the name of a suite, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "preferred-name-and-aliases-q02", "text": "Who or what asserted this about the name of a suite, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "preferred-name-and-aliases-q03", "text": "What may an agent decide or do once the name of a suite is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "stable-identifiers", "name": "Stable identifiers and external keys", "description": "Identifiers that keep pointing at this kind of thing across systems and languages.", "questions": [ { "id": "stable-identifiers-q01", "text": "What identifies and describes an identifier for a suite, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stable-identifiers-q02", "text": "Who or what asserted this about an identifier for a suite, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stable-identifiers-q03", "text": "What may an agent decide or do once an identifier for a suite is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "classification-and-granularity", "name": "Classification and granularity", "description": "Where a suite sits among kinds, and how finely a task needs to cut it.", "findings": [ { "id": "kind-and-parents", "name": "Kind, parents and neighbouring kinds", "description": "The classes this thing belongs to and the ones it is next to.", "questions": [ { "id": "kind-and-parents-q01", "text": "What identifies and describes the kind of a suite, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "kind-and-parents-q02", "text": "Who or what asserted this about the kind of a suite, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "kind-and-parents-q03", "text": "What may an agent decide or do once the kind of a suite is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "distinguishing-features", "name": "Distinguishing features", "description": "What separates a suite from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a suite, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "distinguishing-features-q02", "text": "Who or what asserted this about what distinguishes a suite, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "distinguishing-features-q03", "text": "What may an agent decide or do once what distinguishes a suite is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "state-and-lifecycle", "name": "State and lifecycle", "description": "The states a suite passes through and the events that move it between them.", "rationale": "Most decisions about a thing depend on what state it is in now, which is a claim with a time on it, not a property.", "layers": [ { "id": "lifecycle-stages", "name": "Lifecycle stages", "description": "From coming into existence to ceasing to be one of these.", "findings": [ { "id": "stages-and-transitions", "name": "Stages and transitions", "description": "The stages worth naming and what moves a suite between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a suite, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stages-and-transitions-q02", "text": "Who or what asserted this about the lifecycle of a suite, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stages-and-transitions-q03", "text": "What may an agent decide or do once the lifecycle of a suite is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "observations-and-status", "name": "Observations and current status", "description": "What is observed about a suite, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a suite is recorded so that it can be superseded rather than overwritten.", "questions": [ { "id": "observation-record-q01", "text": "What identifies and describes an observation of a suite, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "observation-record-q02", "text": "Who or what asserted this about an observation of a suite, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "observation-record-q03", "text": "What may an agent decide or do once an observation of a suite is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "content-and-access", "name": "Content, encoding and access", "description": "What a suite says, how it is encoded and who may read it.", "rationale": "An informational thing carries content that can be copied, versioned and withheld, none of which its physical carrier explains.", "layers": [ { "id": "content-and-encoding", "name": "Content and encoding", "description": "The content itself, its format and its language.", "findings": [ { "id": "content-and-format", "name": "Content, format and language", "description": "What a suite contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a suite, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "content-and-format-q02", "text": "Who or what asserted this about the content of a suite, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "content-and-format-q03", "text": "What may an agent decide or do once the content of a suite is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "access-and-rights", "name": "Access, rights and retention", "description": "Who may read, copy or change it, and for how long it is kept.", "findings": [ { "id": "access-rules", "name": "Access rules and retention", "description": "The permissions attached to a suite and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a suite, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "access-rules-q02", "text": "Who or what asserted this about access to a suite, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "access-rules-q03", "text": "What may an agent decide or do once access to a suite is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "work-and-manifestation", "name": "Work, version and copy", "description": "Which level of suite a statement is about.", "rationale": "The work, the edition, the file and the copy in hand are four things; rights and content attach to different ones.", "layers": [ { "id": "levels", "name": "Levels of the thing", "description": "Work, expression, manifestation and item, in plain terms.", "findings": [ { "id": "level-rules", "name": "What belongs at each level", "description": "Which facts hold for the work and which only for one copy.", "questions": [ { "id": "level-rules-q01", "text": "For suite, which facts belong to the work itself, which to a version, and which to a single copy?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifier exists at each level, and which one is being cited?", "kind": "definition" } ] } ] }, { "id": "versions", "name": "Versions, editions and variants", "description": "How versions differ and which is canonical to whom.", "findings": [ { "id": "version-record", "name": "Versions and canonicity", "description": "Differences that matter and who calls one authoritative.", "questions": [ { "id": "version-record-q01", "text": "Which versions or editions of suite exist, and how do they differ substantively?", "kind": "definition" }, { "id": "version-record-q02", "text": "Who treats which version as authoritative, and for what purpose?", "kind": "provenance" } ] } ] } ] }, { "id": "authorship-and-rights", "name": "Authorship, rights and permitted use", "description": "Who made suite and what may be done with it.", "rationale": "Rights are jurisdictional, time-limited and attached to a level, and an agent that ignores that will copy what it may not.", "layers": [ { "id": "authorship", "name": "Authorship and contribution", "description": "Who contributed what, and in what capacity.", "findings": [ { "id": "contribution-record", "name": "Contributors and roles", "description": "The people and bodies behind it, with their roles.", "questions": [ { "id": "contribution-record-q01", "text": "Who authored or contributed to suite, in what roles, and how is that attested?", "kind": "provenance" }, { "id": "contribution-record-q02", "text": "Where authorship is disputed or anonymous, what is recorded instead?", "kind": "boundary" } ] } ] }, { "id": "rights", "name": "Rights and permissions", "description": "Which rights subsist, where, until when, and what they permit.", "findings": [ { "id": "rights-record", "name": "Rights, term and permitted acts", "description": "The regime in force and what it allows.", "questions": [ { "id": "rights-record-q01", "text": "What rights subsist in suite, in which jurisdictions, and until when?", "kind": "definition" }, { "id": "rights-record-q02", "text": "Which acts are permitted without further permission, and which must an agent refuse?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a suite came from and when it held.", "rationale": "A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.", "layers": [ { "id": "source-and-authority", "name": "Source and authority", "description": "Who said it, on what evidence, and how strongly.", "findings": [ { "id": "claim-provenance", "name": "Claim provenance and confidence", "description": "The authority behind each claim about a suite and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a suite, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "claim-provenance-q02", "text": "Who or what asserted this about a claim about a suite, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "claim-provenance-q03", "text": "What may an agent decide or do once a claim about a suite is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "time-and-versions", "name": "Time, versions and supersession", "description": "When a claim was true, when it was learnt, and what replaced it.", "findings": [ { "id": "validity-and-supersession", "name": "Validity period and supersession", "description": "How an old claim about a suite is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a suite, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "validity-and-supersession-q02", "text": "Who or what asserted this about the validity of a claim about a suite, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "validity-and-supersession-q03", "text": "What may an agent decide or do once the validity of a claim about a suite is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 12, "findings": 14, "questions": 38 } } } }