{ "model": { "rank": 2285, "code": "thing-q14116", "model_id": "vr.tr.macos", "name": "macOS", "purpose": "Enable an AI agent to recognise a macOS installation, assess its operational and security state, and determine which changes are compatible, authorised and recoverable.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q14116/", "tier": 2, "score": 110, "payload": { "layer": "wikidata", "aliases": [ "OSx86", "macOS Server", "Mac OS X 10.0" ], "aliasCount": 3, "merged": 3, "knownIn": 110, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q14116", "url": "https://www.wikidata.org/wiki/Q14116", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T11:20:02Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.00871012, "turns": 1, "seconds": 86.9, "error": null }, "codex": { "seconds": 81.5, "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: 01a07b97-6d6a-7ac1-b474-26d7395e74df\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: macOS\nRegistry id: vr.tr.macos\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Vercy model" } } }, "metaModel": { "id": "THING-Q14116", "registryId": "vr.tr.macos", "name": "macOS", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q14116/", "model": { "registry_id": "vr.tr.macos", "name": "macOS", "purpose": "Enable an AI agent to recognise a macOS installation, assess its operational and security state, and determine which changes are compatible, authorised and recoverable.", "definition": "macOS is Apple's Unix-based operating system for Macintosh personal computers, combining a Darwin kernel and POSIX userland with proprietary Aqua, Cocoa, and system frameworks that license, update, and bind hardware to a given major version.", "scope_statement": "This model owns macOS as an operating-system platform and the observable state of a particular installation, distinguishing platform identity, release properties and installation-specific conditions while relating them to the host Mac, users, applications and management authority.", "in_scope": [ "Platform identity, installed macOS version and build, and evidence distinguishing an installed system from an installer or recovery environment", "Compatibility between the installed release, host architecture, applications, extensions and required workflows", "Operating-system services, startup behaviour, system storage relationships and resource constraints", "macOS security controls, privacy permissions and effective administrative or device-management restrictions", "Installation, update, migration and recovery readiness, including evidence needed before consequential changes" ], "out_of_scope": [ "The Mac's physical components, ownership and hardware repair history", "Application-specific business data, functionality and licensing", "People, organisational roles and identity-provider account lifecycles", "Network infrastructure and services external to the installation", "The contents and retention policies of user documents and backups", "Apple's corporate operations and the development histories of other Apple operating systems" ], "distinguishing_features": [ "Confirm macOS identity using installed-system evidence such as product name, version and build; an Apple logo, desktop appearance or device name is insufficient.", "Distinguish macOS from its host Mac: hardware identity can persist while the installed operating system changes.", "Distinguish the installed operating system from macOS Recovery, an installer image or installation media before interpreting observations or attempting changes.", "Distinguish macOS from Darwin alone by verifying the macOS product identity and expected platform environment rather than treating a Darwin kernel identifier as sufficient.", "Distinguish separate macOS installations on the same host by their startup volume and installation context rather than merging their state under the hardware identifier." ], "characteristics": [ { "name": "Observation context", "kind": "category", "unit_or_values": "running installation | offline installation | recovery environment | installer | unknown", "why_it_matters": "Determines which installation an observation describes and which actions are meaningful." }, { "name": "Installed release identity", "kind": "category", "unit_or_values": "Recorded macOS product version and build identifier, with evidence and observation time", "why_it_matters": "Anchors compatibility, update and security assessments to an identifiable release." }, { "name": "Host and startup installation", "kind": "relation", "unit_or_values": "References to the host Mac or virtual machine and the startup volume or volume group", "why_it_matters": "Prevents state and changes from being attributed to the wrong installation." }, { "name": "Execution architecture context", "kind": "category", "unit_or_values": "Host architecture, operating-system architecture and native or translated process context, each recorded separately", "why_it_matters": "Supports accurate application, extension and tooling compatibility decisions." }, { "name": "Operational readiness", "kind": "state", "unit_or_values": "ready | degraded | startup blocked | login blocked | recovery only | unassessed, with supporting symptoms", "why_it_matters": "Connects observed failures to the workflows the installation must support." }, { "name": "Available installation storage", "kind": "measurement", "unit_or_values": "Bytes available on relevant volumes, distinguishing free and reported reclaimable capacity", "why_it_matters": "Constrains updates, installation operations and normal application activity." }, { "name": "Effective security posture", "kind": "state", "unit_or_values": "Observed states of applicable controls, including FileVault, System Integrity Protection, Gatekeeper and startup security, with unknown and not-applicable states allowed", "why_it_matters": "Exposes protections and restrictions that affect the safety and feasibility of proposed actions." }, { "name": "Effective management authority", "kind": "relation", "unit_or_values": "Relationships to local administrators, device management, enforced profiles and the authority approving the proposed action", "why_it_matters": "Distinguishes technical capability from permission to change the installation." }, { "name": "Update disposition", "kind": "state", "unit_or_values": "unassessed | eligible | deferred | blocked | staged | restart pending | failed, qualified by a specific target release", "why_it_matters": "Makes update readiness actionable without assuming that an offered update is suitable." }, { "name": "Recovery readiness", "kind": "state", "unit_or_values": "unassessed | prerequisites missing | prerequisites evidenced | recovery tested, qualified by a specific failure scenario", "why_it_matters": "Prevents an available backup or recovery interface from being mistaken for a verified restoration path." } ], "affordances": [ "Inspect and identify a macOS installation using observations whose source, time and execution context are recorded.", "Evaluate a proposed application, extension or operating-system update against the installation and host constraints.", "Diagnose startup, login, service and resource problems using macOS-specific evidence.", "Adjust supported system settings and permissions when the acting agent has the required authority.", "Plan and execute authorised installation or update operations after checking prerequisites and disruption.", "Select and verify a recovery or migration procedure appropriate to the host, installation and available recovery material." ] }, "sources": [ { "id": "apple-macos", "title": "macOS", "url": "https://www.apple.com/macos/", "what_it_supports": "Current product identity, supported Mac hardware, and the public name of the shipping desktop OS.", "url_status": "live" }, { "id": "wikipedia-macos", "title": "macOS", "url": "https://en.wikipedia.org/wiki/MacOS", "what_it_supports": "Lineage from Mac OS X through OS X to macOS, Darwin/Unix basis, version chronology, and distinction from Classic Mac OS.", "url_status": "live" }, { "id": "wikidata-q14116", "title": "macOS (Q14116)", "url": "https://www.wikidata.org/wiki/Q14116", "what_it_supports": "Stable identifier, official website, developer, and same-as links used as a registry key.", "url_status": "live" }, { "id": "apple-platform-security", "title": "Apple Platform Security", "url": "https://support.apple.com/guide/security/welcome/web", "what_it_supports": "Secure Boot, signed system volume, SIP, FileVault, and hardware-bound trust as the security model of current macOS.", "url_status": "live" } ], "structure": { "bundles": [ { "id": "platform-and-installation-identity", "name": "Platform and installation identity", "description": "Establishes what macOS environment is being modelled and which installation observations belong to.", "rationale": "Version information and system state are unsafe to interpret without separating the product, installed instance and current execution environment.", "layers": [ { "id": "release-identification", "name": "Release identification", "description": "Records evidenced macOS product and build identity.", "findings": [ { "id": "macos-product-and-build", "name": "macOS product and build", "description": "The model should distinguish a verified macOS release identity from names inferred from appearance, hardware or a kernel string.", "questions": [ { "text": "Which observed product version and build identify this macOS installation?", "kind": "definition", "id": "macos-product-and-build-q01" }, { "text": "Which command, system interface or offline installation record supplied that identity, and when?", "kind": "provenance", "id": "macos-product-and-build-q02" } ] } ] }, { "id": "installation-context", "name": "Installation context", "description": "Separates the target installation from its host and the environment used to inspect it.", "findings": [ { "id": "target-system-boundary", "name": "Target system boundary", "description": "The model should bind observations to a specific startup installation and identify whether inspection occurs from that installation, Recovery or another environment.", "questions": [ { "text": "Which host and startup volume or volume group identify the target installation?", "kind": "boundary", "id": "target-system-boundary-q01" }, { "text": "Does the current session describe the target macOS installation, macOS Recovery, an installer or a different booted system?", "kind": "boundary", "id": "target-system-boundary-q02" } ] } ] } ] }, { "id": "mac-and-software-compatibility", "name": "Mac and software compatibility", "description": "Relates macOS release requirements to the host and the software that must run.", "rationale": "An installation can be identifiable and operational while still being unsuitable for a required application, extension or target release.", "layers": [ { "id": "host-release-fit", "name": "Host and release fit", "description": "Evaluates a particular macOS release against the actual host environment.", "findings": [ { "id": "supported-host-context", "name": "Supported host context", "description": "The model should distinguish documented host compatibility from an installation that merely appears to run.", "questions": [ { "text": "What Mac model or virtual-machine configuration and processor architecture host this installation?", "kind": "measurement", "id": "supported-host-context-q01" }, { "text": "What authoritative compatibility evidence covers this host and the installed or proposed macOS release?", "kind": "provenance", "id": "supported-host-context-q02" } ] } ] }, { "id": "application-and-extension-fit", "name": "Application and extension fit", "description": "Assesses required software, architecture translation and system integration constraints.", "findings": [ { "id": "required-software-execution", "name": "Required software execution", "description": "The model should record whether required applications and extensions can execute and integrate under this macOS release and its effective policies.", "questions": [ { "text": "Which required applications or extensions depend on a particular architecture, Rosetta availability, macOS API or approval mechanism?", "kind": "boundary", "id": "required-software-execution-q01" }, { "text": "What vendor evidence or observed workflow test establishes compatibility with the installed or proposed build?", "kind": "provenance", "id": "required-software-execution-q02" }, { "text": "Which compatibility failures must be resolved before installing software or changing macOS?", "kind": "action", "id": "required-software-execution-q03" } ] } ] } ] }, { "id": "startup-and-operational-health", "name": "Startup and operational health", "description": "Captures whether macOS reaches a usable session and sustains required system functions.", "rationale": "A useful state judgement must connect macOS symptoms to startup stages, system services and storage conditions.", "layers": [ { "id": "startup-and-session", "name": "Startup and session", "description": "Locates failures between system startup, volume unlocking, login and usable sessions.", "findings": [ { "id": "usable-session-readiness", "name": "Usable session readiness", "description": "The model should distinguish inability to start macOS from inability to unlock storage, authenticate or sustain a user session.", "questions": [ { "text": "At which observed stage does progress stop: startup selection, volume unlock, macOS startup, login or session operation?", "kind": "measurement", "id": "usable-session-readiness-q01" }, { "text": "Which macOS diagnostic records or directly observed symptoms support that assessment?", "kind": "provenance", "id": "usable-session-readiness-q02" } ] } ] }, { "id": "services-and-system-storage", "name": "Services and system storage", "description": "Assesses macOS service behaviour and the storage conditions relevant to operation.", "findings": [ { "id": "system-function-constraints", "name": "System function constraints", "description": "The model should connect failed required functions to evidence about launchd-managed services, resource pressure and relevant system or data volumes.", "questions": [ { "text": "Which required macOS functions are failing, and what service status, crash reports or resource observations correspond to those failures?", "kind": "measurement", "id": "system-function-constraints-q01" }, { "text": "What capacity, mount, access or volume-health conditions constrain the installation's system and data storage?", "kind": "measurement", "id": "system-function-constraints-q02" }, { "text": "Which supported diagnostic or repair action fits the evidence and the agent's current execution context?", "kind": "action", "id": "system-function-constraints-q03" } ] } ] } ] }, { "id": "security-privacy-and-control", "name": "Security, privacy and control", "description": "Records applicable macOS protections and the effective authority governing changes.", "rationale": "Administrative access alone does not describe every security, privacy or management prerequisite for a macOS action.", "layers": [ { "id": "platform-protections", "name": "Platform protections", "description": "Assesses macOS protection mechanisms individually and in host context.", "findings": [ { "id": "effective-protection-states", "name": "Effective protection states", "description": "The model should retain separate evidence for applicable encryption, system-integrity, application-execution and startup protections.", "questions": [ { "text": "What are the evidenced states of FileVault, System Integrity Protection, Gatekeeper and the startup-security controls applicable to this host?", "kind": "measurement", "id": "effective-protection-states-q01" }, { "text": "Which protections constrain the proposed action, and what supported procedure satisfies those constraints?", "kind": "action", "id": "effective-protection-states-q02" } ] } ] }, { "id": "permissions-and-management", "name": "Permissions and management", "description": "Relates local privileges, privacy consent and device-management policy to a specific action.", "findings": [ { "id": "action-specific-authority", "name": "Action-specific authority", "description": "The model should distinguish user authorisation, process permissions and enforced management settings without recording secret credentials.", "questions": [ { "text": "Which local privileges, privacy permissions or interactive approvals does the acting process require for this action?", "kind": "action", "id": "action-specific-authority-q01" }, { "text": "Which configuration profiles or device-management restrictions govern the setting or operation being changed?", "kind": "boundary", "id": "action-specific-authority-q02" }, { "text": "What evidence establishes that the person or organisation authorising the change has authority over this installation?", "kind": "provenance", "id": "action-specific-authority-q03" } ] } ] } ] }, { "id": "updates-migration-and-recovery", "name": "Updates, migration and recovery", "description": "Evaluates transitions between macOS states and the means of recovering from unsuccessful changes.", "rationale": "Update availability, installation feasibility and recoverability are separate judgements requiring release-specific and installation-specific evidence.", "layers": [ { "id": "release-transition-readiness", "name": "Release transition readiness", "description": "Assesses a named target release and the conditions for reaching it.", "findings": [ { "id": "target-update-decision", "name": "Target update decision", "description": "The model should record the proposed target build, its provenance, compatibility gates and operational prerequisites.", "questions": [ { "text": "Which target macOS version and build are proposed, and what trusted release or update source establishes their identity?", "kind": "provenance", "id": "target-update-decision-q01" }, { "text": "What storage, power, connectivity, authorisation, management or restart conditions currently permit or block the transition?", "kind": "action", "id": "target-update-decision-q02" }, { "text": "Which post-update checks will demonstrate that macOS and the required workflows remain usable?", "kind": "action", "id": "target-update-decision-q03" } ] } ] }, { "id": "restoration-and-migration-paths", "name": "Restoration and migration paths", "description": "Qualifies recovery and migration options against the actual failure or replacement scenario.", "findings": [ { "id": "verified-recovery-path", "name": "Verified recovery path", "description": "The model should distinguish reinstalling macOS, restoring user state, migrating to another installation and returning to an earlier release.", "questions": [ { "text": "For the specified failure scenario, which Recovery, reinstall, backup-restoration or migration procedure is applicable to this host and release?", "kind": "action", "id": "verified-recovery-path-q01" }, { "text": "What evidence verifies access to the necessary backups, recovery material and authorisation without exposing secrets?", "kind": "provenance", "id": "verified-recovery-path-q02" }, { "text": "What system state or user data would the selected procedure preserve, replace or leave unrecoverable?", "kind": "boundary", "id": "verified-recovery-path-q03" } ] } ] } ] }, { "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": [ "Classic Mac OS (System 1 through Mac OS 9, pre-Unix lineage)", "Mac OS X / OS X desktop releases (10.0 Cheetah through 10.11 El Capitan)", "macOS desktop releases (10.12 Sierra onward, including 11 Big Sur and later major versions)", "macOS Server (server roles and tools, later folded into the desktop product)", "Developer and beta channels (Apple Beta Software Program, Seed, and Release Candidate builds)", "Apple silicon (arm64) versus Intel (x86_64) editions of the same named release", "Virtualized macOS guests (macOS Virtualization.framework / licensed VM installs on Apple hardware)", "Recovery, restore, and installer environments (macOS Recovery, Internet Recovery, IPSW/IPSW-like restore images)" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of macOS 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": "Q14116", "note": "Item for the macOS operating-system family (Apple, Darwin-based)." }, { "scheme": "CPE 2.3", "value_or_pattern": "cpe:2.3:o:apple:macos::*:*:*:*:*:*:*", "note": "NIST NVD product; older releases also appear as cpe:2.3:o:apple:mac_os_x and cpe:2.3:o:apple:os_x." }, { "scheme": "IANA/OS uname", "value_or_pattern": "Darwin; sysname Darwin, with marketing version in sw_vers ProductVersion", "note": "Kernel reports Darwin; the marketed product string is macOS / OS X / Mac OS X depending on era." }, { "scheme": "Apple software version", "value_or_pattern": "ProductVersion X.Y[.Z] plus BuildVersion e.g. 24A335", "note": "Read from sw_vers or SystemVersion.plist; build letter encodes major train." }, { "scheme": "User-Agent / HTTP", "value_or_pattern": "Macintosh; Intel Mac OS X _[_] or Macintosh; ARM Mac OS X ...", "note": "Safari and many apps still send 'Mac OS X' in the UA even on current macOS." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of macOS 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": [ "IEEE Std 1003.1 (POSIX) - IEEE / The Open Group: Darwin userland and many CLI utilities are POSIX-aligned; macOS has historically carried UNIX 03 certification on specific versions (e.g. OS X 10.5-10.8 era), later versions are Unix-like without a current Open Brand UNIX certificate.", "Open Brand UNIX 03 - The Open Group: certification applied to named Mac OS X / OS X releases, not to every later macOS train.", "IETF RFC 1034/1035 and related - hostname, mDNS/Bonjour (RFC 6762/6763) as shipped naming and discovery.", "Apple Platform Security / Apple Platform Security Guide - Apple Inc.: Secure Boot, signed system volume, System Integrity Protection, FileVault, TCC.", "EU Digital Markets Act (Regulation (EU) 2022/1925) - European Union: designated gatekeeper obligations affecting macOS app distribution, browser engines, and interoperability in the EU.", "IEC 62368-1 / regional electrical safety and EMC (FCC Part 15, CE RED/EMC) - apply to Mac hardware that runs macOS, not to the OS as a document, but they constrain what a Mac+macOS product may ship.", "NIST SP 800-179 / CIS Apple macOS Benchmarks - U.S. NIST and CIS: hardening baselines used in enterprise macOS fleets.", "App Store Review Guidelines and Notarization requirements - Apple Inc.: code signing, notarization (Gatekeeper), and distribution rules for software on macOS." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of macOS 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": [ "Primary OS on Apple Macintosh notebooks and desktops (MacBook Air/Pro, iMac, Mac mini, Mac Studio, Mac Pro) sold and supported for a sliding window of hardware generations.", "Creative-production workstation OS for video, audio, photography, and design shops using Final Cut, Logic, Adobe, and similar native apps.", "Developer workstation for iOS/iPadOS/watchOS/tvOS/visionOS toolchains; Xcode and the iOS Simulator officially run only on macOS.", "Enterprise-managed endpoint via MDM (Apple Business Manager, Jamf, Microsoft Intune, Kandji) with FileVault, configuration profiles, and software update deferrals.", "CI and build hosts, often as Mac minis or cloud Macs (AWS EC2 Mac, MacStadium, GitHub-hosted macOS runners) because Apple's license requires macOS to run on Apple-branded hardware.", "Consumer personal computer: Safari, Mail, iCloud, Continuity/Handoff, Sidecar, and iPhone/iPad companion features.", "Recovery and deployment: Internet Recovery, DFU restore, and MDM-enrolled zero-touch setup (ADE/ABM)." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of macOS 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": "Marketed major version (ProductVersion)", "typical_range": "10.0-10.15 historically; 11-16+ in the post-Big Sur numbering", "unit": "dotted version string" }, { "quantity": "Darwin kernel version (uname -r)", "typical_range": "roughly 1.x (early Mac OS X) through 24.x+ on current trains", "unit": "kernel release string" }, { "quantity": "Supported hardware window", "typical_range": "about 6-8 years of Mac models receive the current major macOS; security updates continue on N-1/N-2 for a shorter window", "unit": "calendar years / model years" }, { "quantity": "Installer / system volume size", "typical_range": "full installer ~12-15 GB; sealed system volume plus Data volume typically tens of GB on a working Mac", "unit": "gigabyte (GiB)" }, { "quantity": "Minimum RAM for current major releases", "typical_range": "8 GB officially on recent trains; 16 GB common for development/creative work", "unit": "gigabyte (GiB)" }, { "quantity": "Architecture", "typical_range": "x86_64 (Intel, including Rosetta 2 guests) or arm64 (Apple silicon); Universal 2 binaries contain both", "unit": "instruction-set architecture" }, { "quantity": "Update cadence", "typical_range": "one named major release per year (autumn); point releases and rapid security responses in between", "unit": "releases per year" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of macOS 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": [ "Unsigned or un-notarized code blocked by Gatekeeper; broken code signatures after disk clone or permission repair.", "Signed System Volume / Sealed System Volume seal break or failed update leaving the Mac unbootable until recovery reinstall.", "Firmware or T2/Apple silicon Secure Boot pairing failure; DFU restore required when the LocalPolicy or LLB chain is damaged.", "Kernel panic, third-party kext/system-extension incompatibility after a major upgrade (especially USB, VPN, and storage filters).", "FileVault recovery-key loss: ciphertext is unrecoverable without the password, recovery key, or institutional key.", "Malware and adware (typically user-level, not kernel) plus TCC/Full Disk Access social-engineering; historically Mac-specific families such as Shlayer, Bundlore, and Atomic Stealer.", "Rosetta 2 or architecture mismatch: Intel-only apps fail on Apple silicon without translation; old Carbon/32-bit apps already dropped after Catalina.", "MDM/profile lock and Activation Lock (Find My) making a device inoperable to a new owner.", "Privacy and data-exfiltration risk via Continuity, iCloud, screenshots, and always-on microphones/cameras on notebooks - mitigated by hardware indicators and TCC but still a deployment hazard.", "Licensing: running macOS on non-Apple hardware (Hackintosh) violates the software license and is operationally fragile across updates." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of macOS 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": [ "EU (DMA): alternative app marketplaces, browser-engine choice, and extra interoperability obligations on macOS that do not apply in the same form in the US or most other regions.", "China: iCloud operated by GCBD (云上贵州) for mainland Apple IDs; different notarization/network endpoints and App Store catalog.", "Language and locale packs: input methods (Pinyin, Kotoeri, Hangul, Arabic) and region-specific first-run legal text; some features (Apple Pay, some iCloud+ capabilities) are country-gated.", "Product naming: Japanese and some markets long used 'Mac OS X' branding later than others; the 2016 shift from 'OS X' to 'macOS' was global but documentation lag remains in UAs and enterprise catalogs.", "Keyboard hardware: ISO vs ANSI vs JIS physical layouts; the Option/Alt and Command glyphs and key positions differ, which affects how 'macOS shortcuts' are taught." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of macOS 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": "Classic Mac OS (System 1-Mac OS 9)", "difference": "Cooperative, non-Unix Mac OS; no Darwin kernel, no Aqua as later defined. Test: presence of Darwin/uname, Mach-O binaries, and a sealed APFS system volume - all indicate macOS/Mac OS X, not Classic." }, { "name": "Darwin (open-source kernel + userland)", "difference": "Darwin is the open kernel/userland subset. macOS is Darwin plus proprietary graphics, Aqua, Cocoa, Apple apps, and the license that binds it to Apple hardware. Test: whether Cocoa/AppKit, WindowServer, and Apple-signed system volume are present." }, { "name": "iOS / iPadOS", "difference": "Same Darwin/XNU family and many frameworks, but different UIKit-centric runtime, app sandbox, and device class. Test: UIDevice/idiom, presence of SpringBoard vs WindowServer/Dock, and whether the device is a Mac with a pointer-first AppKit desktop." }, { "name": "iPadOS with Stage Manager / 'PC-like' iPad", "difference": "Still iPadOS; cannot run Xcode as a full Mac IDE or arbitrary unsigned Mac apps. Test: uname/sysctl hardware model (iPad*) and lack of /System/Library/CoreServices/Finder.app as on a Mac." }, { "name": "visionOS, watchOS, tvOS", "difference": "Sibling Darwin-based Apple OSes for other device classes. Test: platform identifier in the SDK (macosx vs iphoneos vs xros vs watchos vs appletvos) and the hardware they boot on." }, { "name": "Linux or BSD on Apple silicon (Asahi Linux, OpenBSD)", "difference": "May boot on the same Mac hardware but is not macOS and cannot run most Mac apps or Apple's signed-system model. Test: kernel name (Linux/OpenBSD vs Darwin) and absence of Apple's signed system volume." }, { "name": "Windows (Boot Camp historically, or VMs / Parallels / VMware)", "difference": "Different kernel and ABI; Boot Camp was Intel-only. Test: NT vs Darwin; on Apple silicon, Windows is virtualized, not dual-booted as on Intel Boot Camp." }, { "name": "OS X / Mac OS X as a separate product", "difference": "Same lineage; 'Mac OS X' (10.0-10.7), 'OS X' (10.8-10.11), then 'macOS' from 10.12. Test: ProductName in sw_vers and the version number; treat as era names of one family unless a catalogue needs the 2012-2016 trademark split." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of macOS this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the existing Vercy catalogue already contain a macOS or operating-system model that this registry entry should reference rather than duplicate?", "How should the registry's PHY / PHY.OBJ placement distinguish macOS as a software platform from a concrete installation and its physical host?", "Which official sources establish host compatibility, update eligibility and security-maintenance status for each release without assuming a fixed support window?", "Which security, approval and recovery mechanisms vary by Mac hardware generation, macOS release and virtualised execution context?", "What minimum evidence and freshness requirements should establish operational readiness and tested recoverability for the intended agent workflows?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 33 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "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 macOS, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a macOS installation, assess its operational and security state, and determine which changes are compatible, authorised and recoverable.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: OSx86, macOS Server, Mac OS X 10.0.", "3 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 110 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 macOS, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "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": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Recognised by form, by the arrangement of its controls, and by markings - a plate, a model number, a certification mark. Form alone rarely separates two models that do very different things." ], "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": [ "OSx86", "macOS Server", "Mac OS X 10.0" ] } ], "standing": "Described in 110 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 macOS from another, and a macOS 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 macOS, 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 macOS, 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 macOS 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 macOS, 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 macOS, 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 macOS 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 macOS 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 macOS, 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 macOS, 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 macOS 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 macOS from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a macOS, 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 macOS, 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 macOS is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "form-and-composition", "name": "Form, composition and condition", "description": "What a macOS is made of, what shape and size it takes, and what state it is in.", "rationale": "A physical thing can be measured, and a model that cannot record its measurements cannot support any decision that depends on them.", "layers": [ { "id": "form-and-dimensions", "name": "Form and dimensions", "description": "Shape, size, mass and the ranges these take across examples.", "findings": [ { "id": "measurable-dimensions", "name": "Measurable dimensions and their units", "description": "The quantities worth recording and the units they are recorded in.", "questions": [ { "id": "measurable-dimensions-q01", "text": "What identifies and describes the dimensions of a macOS, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "measurable-dimensions-q02", "text": "Who or what asserted this about the dimensions of a macOS, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "measurable-dimensions-q03", "text": "What may an agent decide or do once the dimensions of a macOS is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "material-and-composition", "name": "Material and composition", "description": "Materials, parts and how they are put together.", "findings": [ { "id": "parts-and-materials", "name": "Parts and materials", "description": "What a macOS is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a macOS, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "parts-and-materials-q02", "text": "Who or what asserted this about the composition of a macOS, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "parts-and-materials-q03", "text": "What may an agent decide or do once the composition of a macOS is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "condition-and-integrity", "name": "Condition and integrity", "description": "Wear, damage, health and the difference between working and broken.", "findings": [ { "id": "condition-assessment", "name": "Condition, damage and health", "description": "How the condition of a macOS is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a macOS, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "condition-assessment-q02", "text": "Who or what asserted this about the condition of a macOS, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "condition-assessment-q03", "text": "What may an agent decide or do once the condition of a macOS is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "place-and-movement", "name": "Place and movement", "description": "Where a macOS is, how it got there and where it may go (varies).", "rationale": "A thing that can move needs its position recorded with a time, or every later claim about it is about a place it has left.", "layers": [ { "id": "location-and-placement", "name": "Location and placement", "description": "Position, containment and the reference frame the position is given in.", "findings": [ { "id": "position-and-frame", "name": "Position, container and reference frame", "description": "Where a macOS is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a macOS, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "position-and-frame-q02", "text": "Who or what asserted this about the location of a macOS, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "position-and-frame-q03", "text": "What may an agent decide or do once the location of a macOS is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "movement-and-transfer", "name": "Movement and transfer", "description": "How a macOS is carried, installed or relocated.", "findings": [ { "id": "movement-events", "name": "Movement events and constraints", "description": "What counts as a movement, what records it and what limits it.", "questions": [ { "id": "movement-events-q01", "text": "What identifies and describes the movement of a macOS, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "movement-events-q02", "text": "Who or what asserted this about the movement of a macOS, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "movement-events-q03", "text": "What may an agent decide or do once the movement of a macOS 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 macOS 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 macOS between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a macOS, 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 macOS, 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 macOS 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 macOS, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a macOS 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 macOS, 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 macOS, 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 macOS is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "function-and-principle", "name": "Function and operating principle", "description": "What macOS is for and how it achieves it.", "rationale": "Two devices with the same name can work on different principles, and the principle is what predicts failure and constrains use.", "layers": [ { "id": "intended-function", "name": "Intended function", "description": "The job it does, and the jobs it is used for anyway.", "findings": [ { "id": "function-record", "name": "Function, principle and variants", "description": "What it does, how, and which variants do it differently.", "questions": [ { "id": "function-record-q01", "text": "What function does macOS perform, on what operating principle, and which variants differ in that principle?", "kind": "definition" }, { "id": "function-record-q02", "text": "What use falls outside the intended function but happens in practice?", "kind": "boundary" } ] } ] }, { "id": "capacity-and-rating", "name": "Capacity and rating", "description": "The numbers that say what it can do and where it stops.", "findings": [ { "id": "ratings", "name": "Ratings and their conditions", "description": "Rated capacity, power, throughput and the conditions each assumes.", "questions": [ { "id": "ratings-q01", "text": "What ratings characterise macOS, in what units, and under what stated conditions?", "kind": "measurement" }, { "id": "ratings-q02", "text": "What happens beyond the rating - degradation, refusal, damage - and how is that detected?", "kind": "action" } ] } ] } ] }, { "id": "operation-and-state", "name": "Operation, controls and state", "description": "How macOS is operated and what state it is in right now.", "rationale": "An agent acting on a device needs its current state and the controls that change it, not just its specification.", "layers": [ { "id": "controls-and-modes", "name": "Controls and modes", "description": "What can be set, what that changes, and what is interlocked.", "findings": [ { "id": "control-surface", "name": "Control surface and interlocks", "description": "The settings available and the conditions that block them.", "questions": [ { "id": "control-surface-q01", "text": "What controls and modes does macOS have, and what does each change?", "kind": "definition" }, { "id": "control-surface-q02", "text": "Which actions are interlocked or forbidden in which state, and what must be true before acting?", "kind": "action" } ] } ] }, { "id": "condition-and-maintenance", "name": "Condition and maintenance", "description": "Wear, service intervals, consumables and the line between working and broken.", "findings": [ { "id": "service-record", "name": "Condition, service and consumables", "description": "What is consumed, what is serviced, and how condition is judged.", "questions": [ { "id": "service-record-q01", "text": "What consumables and service does macOS need, at what interval, and on whose authority?", "kind": "measurement" }, { "id": "service-record-q02", "text": "What evidence separates a unit that is working from one that is out of service?", "kind": "boundary" } ] } ] } ] }, { "id": "kind-model-unit", "name": "Kind, model and unit", "description": "Whether a claim about macOS is about the kind, a product line, or one physical unit.", "rationale": "This is the boundary most often got wrong for made things, and getting it wrong mixes a catalogue entry with the machine in the yard.", "layers": [ { "id": "level-of-reference", "name": "Level of reference", "description": "The three levels and what belongs at each.", "findings": [ { "id": "level-rules", "name": "What belongs to kind, model and unit", "description": "Which properties are shared by all of them and which are not.", "questions": [ { "id": "level-rules-q01", "text": "Which facts about macOS hold for every one of them, which for a model, and which only for one unit?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifies an individual unit, and what should an agent do when it has only the kind?", "kind": "action" } ] } ] }, { "id": "standards-and-conformity", "name": "Standards and conformity", "description": "The standards a working example must meet and who attests it.", "findings": [ { "id": "conformity", "name": "Standards, marks and attestation", "description": "Which standard applies, who certifies, and what the mark means.", "questions": [ { "id": "conformity-q01", "text": "Which standards govern macOS, issued by whom, and what does conformity actually assert?", "kind": "provenance" }, { "id": "conformity-q02", "text": "What may an agent conclude from a certification mark, and what may it not?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a macOS 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 macOS and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a macOS, 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 macOS, 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 macOS 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 macOS is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a macOS, 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 macOS, 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 macOS is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 8, "layers": 17, "findings": 19, "questions": 51 } } } }