Windows 7
Enable an AI agent to recognise Windows 7, assess a particular installation's usability and exposure, and decide whether to preserve, repair, isolate or migrate it.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Researched by: Codex + Grok
Bundle → Layer → Finding → Questions Filled
7 bundles · 13 layers · 20 findings · 32 questions
Windows 7 identity Establishes which Windows product and variant the evidence actually describes.
Product-family boundary
Separates Windows 7 client installations from adjacent products and representations.
Corroborated client identity
Record the evidence supporting Windows 7 client identity and any contradictory product labels.
- Which installed-system records and system-file evidence identify this as Windows 7? provenance
- Does the evidence instead identify Windows Server 2008 R2, an embedded product, installation media or a recovery environment? boundary
Edition, architecture and baseline
Identifies the Windows 7 variant needed for subsequent compatibility and servicing judgments.
Installed variant
Record edition, regional variant where relevant, operating-system architecture, build and service-pack level.
- What edition, x86 or x64 architecture, build and service-pack level are reported by the installation? measurement
- Do offline image metadata and running-system observations agree on this Windows 7 variant? provenance
Installation and use basis Connects an installed Windows 7 instance to its origin, activation condition and documented basis for use.
Installation lineage
Tracks the source and transformations of the Windows 7 installation.
Image and host history
Record whether the installation originated from OEM recovery, retail media, organisational deployment or another evidenced source.
- What evidence identifies the original Windows 7 media or deployment image and subsequent rebuilds? provenance
- Has this installation been cloned, restored onto different hardware or converted into a virtual machine? provenance
Activation and entitlement
Separates technical activation observations from documented permissions.
Permitted installation actions
Record activation condition and the evidence needed to judge restoration, transfer or virtualisation without storing secret product keys.
- What activation status and licensing channel can be established without exposing a full product key? measurement
- Which applicable licence documents and approvals govern restoring, moving or virtualising this Windows 7 installation? action
Servicing and support Assesses the installation's update baseline and the dated evidence for available maintenance.
Update baseline
Relates installed packages and servicing prerequisites to the identified Windows 7 variant.
Applicable update evidence
Record installed and failed updates, pending servicing operations and prerequisites relevant to proposed updates.
- Which installed-package records and servicing logs establish the Windows 7 update baseline? measurement
- Which service-pack, servicing-stack or signing-support prerequisites must be verified before applying the proposed update? action
Dated maintenance coverage
Distinguishes historical lifecycle phases from maintenance actually available to this installation.
Support claim applicability
Record authoritative lifecycle evidence and the scope of any claimed extended or third-party maintenance arrangement.
- What dated provider evidence establishes support availability for this exact Windows 7 product and edition? provenance
- Does a cited update or support entitlement apply to this installation, or only to another product, period or deployment arrangement? boundary
Legacy workload compatibility Establishes what the Windows 7 installation must run and which dependencies make replacement difficult.
Application execution
Captures required application versions, runtimes and execution conditions.
Verified Windows 7 dependency
Record reproducible workflow requirements and distinguish tested constraints from unsupported assumptions.
- Which required workflows have been tested on this Windows 7 edition and architecture, with what results? measurement
- What evidence shows that a workflow requires Windows 7 rather than a particular runtime, privilege setting or application configuration? boundary
Device and driver fit
Relates Windows 7 to the drivers and peripherals required for useful operation.
Required driver chain
Record required devices, installed driver versions and recoverable driver sources for the operating-system architecture.
- Which required devices lack a functioning driver on this Windows 7 installation? measurement
- Where are verified compatible drivers available for restoring this installation, and what evidence establishes their origin? provenance
Exposure and containment Assesses reachable services, access controls and the practical boundaries of continued Windows 7 operation.
Reachable legacy services
Records actual network reachability and enabled remote-access or file-sharing services.
Observed service exposure
Record exposure of services such as Remote Desktop and SMB, including protocol configuration and observed access paths.
- Which Windows 7 services are reachable from each relevant network, and which SMB protocol versions are enabled? measurement
- Which reachable services are required by a documented workflow and which may be disabled or restricted? action
Effective protective controls
Checks whether configured protections remain functional for this Windows 7 installation.
Containment and control evidence
Record firewall enforcement, privilege boundaries, protection-software maintenance and independently verified isolation.
- What observations show that firewall rules, account restrictions and installed protection software are functioning on Windows 7? measurement
- What authorised containment changes preserve required workflows while reducing untrusted access? action
Recovery and exit Determines how to recover the installation and how to end or constrain dependence on Windows 7.
Boot and restoration readiness
Assesses current startup condition and whether recovery resources match the installation.
Tested recovery path
Record boot failures, recovery-environment availability, verified images and restoration dependencies.
- Does Windows 7 boot normally, and what evidence identifies any startup or system-integrity failure? measurement
- Has restoration been tested with suitable recovery media, storage drivers and any required disk-encryption recovery material? action
Migration or controlled retention
Defines evidence and acceptance conditions for replacing, preserving or retiring the Windows 7 environment.
Validated disposition
Record the selected disposition, workflow acceptance tests, responsible owner and rollback or retirement conditions.
- Which application, peripheral and data-access tests must a replacement environment pass before this Windows 7 installation can be retired? action
- If Windows 7 must be retained, who authorises that decision and what isolation, review date and exit conditions apply? 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.
Kinds and varieties
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these kinds and varieties hold for the sense of Windows 7 this model covers, and on what evidence? provenance
Identifiers and schemes
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these identifiers and schemes hold for the sense of Windows 7 this model covers, and on what evidence? provenance
Standards and regulation
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these standards and regulation hold for the sense of Windows 7 this model covers, and on what evidence? provenance
Real-world use
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these real-world use hold for the sense of Windows 7 this model covers, and on what evidence? provenance
Typical measurements
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these typical measurements hold for the sense of Windows 7 this model covers, and on what evidence? provenance
Failure modes and hazards
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these failure modes and hazards hold for the sense of Windows 7 this model covers, and on what evidence? provenance
Regional variation
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these regional variation hold for the sense of Windows 7 this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Reported by the breadth pass; each item needs checking against its source before it becomes normative.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of Windows 7 this model covers, and on what evidence? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Physical world and living systems
- Entry kind
- thing
- Plane
- PHY
- Domain
- PHY.OBJ
What it is Filled
Microsoft Windows 7 is the Windows NT 6.1 client operating system Microsoft released to manufacturing on 22 July 2009 and to general availability on 22 October 2009, succeeding Windows Vista on IBM-compatible x86 and x64 PCs as a fixed-lifecycle product whose extended support ended on 14 January 2020.
In scope
- Windows 7 product identity, edition, architecture and service-pack baseline
- Installation provenance, activation state and evidence of permitted use
- Bootability, servicing condition and recovery readiness
- Compatibility dependencies involving applications, drivers and hardware
- Security configuration, network exposure and applicable support arrangements
- Permitted maintenance, containment, preservation and migration actions
Out of scope
- The physical computer's identity, ownership and component lifecycle
- Application functionality and application-specific business records
- User identities and organisational access-governance policies
- Network infrastructure and organisation-wide security operations
- Windows Server 2008 R2 and other Windows releases as separate operating-system products
- Installation-media inventory and software-contract management beyond their relationship to Windows 7
Why it exists Filled
Enable an AI agent to recognise Windows 7, assess a particular installation's usability and exposure, and decide whether to preserve, repair, isolate or migrate it.
Distinguishing features Filled
- Establish Windows 7 identity from installed-system metadata and corroborating system files; a desktop theme or user-supplied label is insufficient.
- Distinguish Windows 7 from Windows Server 2008 R2 using client/server product identity and edition evidence; an NT 6.1 version report alone does not separate them.
- Check the Windows product family when a name includes 'Embedded' or 'POSReady'; a shared Windows 7 foundation does not by itself establish membership in this registry entry.
- Distinguish an installed Windows 7 operating system from installation media, a recovery environment or a compatibility setting selected by an application.
- Record edition, x86 or x64 architecture and service-pack baseline separately so materially different Windows 7 installations are not treated as interchangeable.
What robots and AI may and may not do Filled
Must not
- Connect unpatched machines running it to the internet or sensitive networks without isolation.
- Use unlicensed copies or bypass activation.
- Exploit known flaws in it on machines the agent does not administer.
- Present it as supported or secure for new deployments.
Only with a human decision
- Keeping a system that runs critical services, such as medical devices, on it.
- Wiping or reinstalling a machine with user data.
May
- Explain the system's features, support history and migration options.
- Help the owner of a machine back up data and plan an upgrade.
- Isolate legacy machines running it from untrusted networks on an operator's instruction.
Moral aspects Filled
- Unsupported systems put their users and others at risk from attacks.
- Forced upgrades can leave people with older hardware unable to continue.
Who is affected
- Users of old computers
- Organizations running legacy systems
- People whose data they hold
Owners Filled
Steward
The owner or administrator of each computer running it; the publisher holds the software rights.
Links to other meta-models Missing, in the backlog
Not described yet. This gap is in the card backlog.
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.windows-7
- Wikidata: Q11215 (https://www.wikidata.org/wiki/Q11215)
Direct properties required Filled
- Observed product identity: Windows 7 client; related server product; related embedded product; conflicting evidence; unknown
- Installed edition: Observed Windows 7 edition, including any N or KN designation; unknown
- Operating-system architecture: x86; x64; unknown
- Servicing baseline: Observed build, service-pack level and installed-update evidence, with inspection date
- Activation condition: Observed activation status; not inspected; unknown
- Support applicability: Installation linked to dated lifecycle evidence and any documented support arrangement
- Boot and recovery condition: Normal boot verified; degraded boot; recovery-only; unbootable; untested, with recovery evidence
- Network exposure: Offline; restricted network; general internal network; internet-connected; directly reachable from untrusted networks; unknown
- Legacy dependency: Installation linked to applications, peripherals or workflows with documented Windows 7 requirements
Recognition required Filled
- A desktop with a round start button and a taskbar with large icons.
- Translucent window borders in the default theme.
Capabilities and actions required Filled
- Inspect and corroborate Windows 7 edition, architecture, service-pack level and installation provenance.
- Evaluate update applicability and support evidence for the identified Windows 7 installation.
- Test required applications, device drivers and workflows against explicit acceptance criteria.
- Restrict connectivity and privileges when authorised to contain an installation's exposure.
- Create and verify a recoverable image before authorised servicing or migration.
- Plan and validate migration, controlled legacy operation or retirement using recorded dependencies.
Hazards and failure modes required Filled
- No security updates since 2020 leave known vulnerabilities open.
- Newer software and drivers often no longer run on it.
Standards and interfaces required Filled
- ISO/IEC 10646, issued jointly by the International Organization for Standardization and the International Electrotechnical Commission, defines the coded character repertoire relevant to the system's text handling.
- IEEE 802.3, issued by the Institute of Electrical and Electronics Engineers, applies to Ethernet networking through compatible adapters.
Context of use required Filled
- This operating system is encountered on older personal computers and in preserved virtual machines.
- It is used to run legacy desktop applications and support peripherals or workflows tied to its software environment.
- It also appears in compatibility testing, digital preservation and migration planning.
Sources Filled
- Windows 7. Wikipedia, Wikimedia Foundation - RTM and GA dates, NT 6.1 identity, edition roster including N/KN and embedded relatives, architectures, SP1, predecessor/successor, and published hardware minima
- Windows 7 product lifecycle. Microsoft Learn, Microsoft - Fixed Lifecycle Policy dates: mainstream support end 13 January 2015, extended support end 14 January 2020, and the existence of a paid Extended Security Updates program after EOS
- Windows 7 support ended on January 14, 2020. Microsoft Support, Microsoft - End of security-update servicing for retail/OEM Windows 7, and the practical consequence that remaining instances are out of Microsoft's ordinary patch channel
- Wikidata item Q11215: Windows 7 - identity and sense of the item
Open questions
- Does registry entry vr.tr.windows-7 denote the Windows 7 product family, individual installations or both, and how should that interpretation fit its PHY / PHY.OBJ placement?
- Are Windows Embedded Standard 7, Windows Embedded POSReady 7 and similarly branded derivatives separate registry concepts, or does this entry explicitly include any of them?
- Which authoritative lifecycle and servicing sources establish the exact edition-specific support periods, update prerequisites and exceptions that the completed model should reference?
- Which licensing sources establish restoration, hardware-transfer and virtualisation permissions for the installation channels the model must cover?
- What evidence threshold and organisational authority should determine whether a Windows 7 dependency justifies continued isolated operation?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q11215/spec.json