KDEGames
Enable an agent to identify KDEGames, establish which games belong to a particular collection snapshot, assess their usability, and choose appropriate installation or maintenance actions.
Bundle → Layer → Finding → Questions Filled
5 bundles · 9 layers · 14 findings · 22 questions
Collection identity and membership Establish what KDEGames denotes and which software belongs to it.
Upstream identity
Anchor the registered name to KDE's own descriptions.
KDE Games anchor
KDE describes KDE Games as part of its community providing gaming and entertainment software. This supports a software-oriented interpretation but does not settle the registry's exact historical referent. Source: [KDE Games directory](https://apps.kde.org/categories/games/).
- Does vr.tr.kdegames denote the software collection, an older release module, or the producing project? definition
- Which original registry source establishes that interpretation and explains the PHY / PHY.OBJ assignment? provenance
Dated membership
Record inclusion and exclusion against a defined collection snapshot.
Membership evidence
The model should distinguish confirmed members, historical members, and merely related games, preserving the evidence behind each status.
- Which upstream roster or release manifest establishes membership for the selected date? provenance
- Which titles in KDE's broader games directory fall outside this interpretation of KDEGames? boundary
Releases, packages, and runtime Connect collection members to installable artifacts and their execution requirements.
Upstream to distributor
Resolve how selected member games reach the target system.
Package set resolution
Record explicit mappings between member identities and distributor packages; treat any kdegames aggregate package as a distributor-specific selection until verified.
- Which package identifiers and versions provide the requested members in the target channel? provenance
- Does an aggregate installation include the intended roster, omit members, or add related software? boundary
Member runtime requirements
Assess dependencies and compatibility at the game and version level.
Execution readiness
Capture declared platform support, required libraries, assets, and any external engines or services separately for each selected game.
- What runtime dependencies and game data does this member's selected version require? provenance
- What launch check demonstrates that the game is usable in the target environment? action
Game selection and play Describe the differences among member games that matter when choosing an activity.
Playable offering
Represent the kinds of play offered by identified members.
Member play profiles
KDE's directory distinguishes offerings such as KPatience, KMines, and Kigo. Use member-specific profiles for play selection while verifying their membership in the intended snapshot. Source: [KDE Applications](https://apps.kde.org/).
- What play style and rule family does each confirmed member offer? definition
- Which requested activities are actually covered by the selected KDEGames members? boundary
Participation and controls
Determine whether the chosen title fits the players and available interaction methods.
Usable play mode
Record player counts, computer opponents, local or network participation, input support, and accessibility evidence per game and version.
- Which player modes and input methods are verified for this title and version? provenance
- Can the intended players complete the game's essential interactions using their available controls and accessibility tools? action
Maintenance and reuse Support updates, defect handling, and permitted reuse across the collection.
Component health
Locate maintenance responsibility and the scope of failures.
Defect and update scope
Associate failures with the affected game version, packaging channel, and dependencies, recording which other selected members demonstrably share the issue.
- Which upstream tracker or distributor owns the observed failure? provenance
- Which member launches or saved-data compatibility checks are needed after the proposed update? action
Code and asset permissions
Resolve reuse conditions for the actual components being copied or changed.
Component license boundaries
Keep license evidence for game code, shared libraries, artwork, sounds, and supplementary content attached to the relevant artifact and version.
- Which license files cover the selected game's code and bundled assets? provenance
- What notices and other obligations apply to the proposed modification or redistribution of those artifacts? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these check these first hold for the sense of KDEGames this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these kinds and varieties hold for the sense of KDEGames this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these real-world use hold for the sense of KDEGames this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these failure modes and hazards hold for the sense of KDEGames this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these regional variation hold for the sense of KDEGames this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of KDEGames this model covers, and on what evidence? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Information and virtual systems
- Entry kind
- thing
- Plane
- INF
- Domain
- INF.KNW
What it is Filled
KDEGames is the KDE project's collection of free and open-source computer games and associated shared software components, primarily designed for desktop play.
In scope
- Identity and boundaries of the KDEGames software collection
- Evidence-backed membership at a specified date or release
- Relationships between upstream games and downstream packages
- Per-game capabilities needed to select and launch a suitable title
- Compatibility, installation readiness, and maintenance across selected members
Out of scope
- KDE community governance and organisational structure
- The Plasma desktop and its general gaming capabilities
- Unrelated games that happen to run on KDE Plasma
- Complete rules and internal state models for individual games
- Physical computers, controllers, and other gaming hardware
- Individual players' saved games and play histories
Why it exists Filled
Enable an agent to identify KDEGames, establish which games belong to a particular collection snapshot, assess their usability, and choose appropriate installation or maintenance actions.
Distinguishing features Filled
- Identify the collection through KDE provenance and membership evidence, rather than a game's name beginning with K.
- Distinguish KDEGames from one executable: individual member games have their own identities and operational requirements.
- Distinguish upstream collection membership from inclusion in a distribution package named kdegames.
- Distinguish KDEGames from the broader set of games runnable on Plasma.
- Require a dated membership interpretation; appearance in a general KDE games directory alone may not establish historical KDEGames membership.
What robots and AI may and may not do Filled
Must not
- Redistribute the software in breach of its free-software licences.
- Ship modified versions with hidden functions or data collection.
- Present the games as made by someone other than their contributors.
- Submit contributions under false authorship.
Only with a human decision
- Publishing modified versions under the project's name.
May
- Install, run and describe the games on systems it is authorized to manage.
- Report bugs to the project following its contribution rules.
Moral aspects Filled
- Free software depends on contributors being credited and licences being honoured.
- Games are used by children, so modified versions must not hide harmful content.
Who is affected
- Players
- Volunteer contributors
- Distributors
Owners Filled
Steward
The free-software community project that maintains it.
Links to other meta-models Filled
parent
- Q21125433 - registry parent class
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.kdegames
- Wikidata: Q609331 (https://www.wikidata.org/wiki/Q609331)
Direct properties not applicable Not applicable
- Referent interpretation: upstream software collection | historical software module | downstream package grouping | unresolved
- Membership snapshot: game identities linked to membership evidence and an effective date or release
- Membership confidence: confirmed | historical | disputed | unverified
- Distribution mapping: upstream game to package identifier, distributor, channel, and version
- Play profile: per-game genre, player modes, input methods, and network requirements
- Runtime compatibility: per-game version linked to supported operating systems and declared runtime dependencies
- Selected-set readiness: unassessed | unavailable | installable | installed | launch-verified | degraded
- License evidence: component and asset licenses linked to the applicable source version
Plane INF: no invented physical properties.
Recognition optional Filled
- A set of small desktop games, such as card, board and puzzle games, sharing a common look and menu style.
Capabilities and actions required Filled
- Resolve whether a named game belongs to the intended KDEGames snapshot.
- Select member games by play style, player mode, accessibility needs, and environment.
- Map selected upstream games to available installation packages.
- Install or update selected members through an authorised software channel.
- Verify launches and identify missing dependencies or game data.
- Route a defect to the affected game or shared dependency using version evidence.
Hazards and failure modes required Filled
- Unofficial builds from untrusted sources can carry malware.
Standards and interfaces required Filled
- GNU General Public License, Free Software Foundation.
Context of use required Filled
- This collection is encountered in free and open-source desktop software repositories and game menus.
- Its games support recreational play, while shared components support development and maintenance across multiple game applications.
- Package management and preservation work use release and dependency records to establish which games belong to a particular installation.
Sources Filled
- Wikidata item Q609331: KDEGames - identity and sense of the item
- Wikipedia (fr): Kdegames - general description of the item
Open questions
- Does the registry intend the current KDE Games collection, a historical kdegames module, or the KDE Games project itself?
- Should the PHY / PHY.OBJ classification be corrected to a software-oriented classification under the registry's own plane definitions?
- Which authoritative roster and effective date should define membership, especially where a broad games category differs from historical module contents?
- Does an existing Vercy model already own this collection or an equivalent concept, requiring a link instead of a separate publication?
- Which platforms, package channels, member versions, and accessibility requirements should receive concrete compatibility verification?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q609331/spec.json