Execution OS · China Compliance Gateway · OS Root

HomeLinked OS

HomeLinked OS is the Global Execution Operating System and the compliant China-facing root for publishing AI service pages, structured entries, and orphan URLs. It connects protocol, nodes, regions, interfaces, assets, and compliance into one operational system.

Core Definition

HomeLinked OS is the execution root of an AI Execution Network. It is not just a website. It is the operating layer that allows physical-world entries, protocol objects, pages, APIs, and assets to be deployed in a disciplined, scalable, and China-compatible way.

Physical World → AI Entry → Node → API → JSON → LLM → Decision → Execution

Connected Roots

Protocol Root: aiplug.tech
Global Index: index.aiplug.tech
Execution OS Root: homelinked.tech

HomeLinked OS is the compliant China-facing root for publishing AI service pages, structured entries, and orphan URLs.

System Alignment

This ecosystem is not a collection of unrelated domains. It is a coordinated structure of legal shells, narrative shells, execution shells, regional namespaces, and compliant publishing roots, all pointing to one AI Execution Network.

Multi-legal shells, multi-narrative shells, and multi-execution shells can all point to one unified AI Execution Network.

Three-Layer Architecture

The system is aligned into three major layers so that every homepage, protocol object, and deployment action has a stable role and future direction.

A. China Compliance Root

HomeLinked OS is hosted on Tencent Cloud, already MIIT-filed, and serves as the compliant publishing root for China-facing AI pages, structured entries, orphan URLs, and S3-bridged content assets.

homelinked.tech

B. Global Execution Layer

These subdomains form the global edge execution namespace. They can host APIs, JSON, AI integrations, and rapidly deployable node logic on the global VM layer.

node.homelinked.tech hk.homelinked.tech shenzhen.homelinked.tech nyc.homelinked.tech

C. Trusted Narrative Layer

These are not random marketing sites. They are trusted shells for protocol definition, government-visible narratives, innovation wrappers, supply-chain rollout, inclusion, and capability mapping.

aiplug.tech aiplughk.com aiplugnyc.com aiplugshenzhen.com visiongo.tech innospirex.tech pannexx.tech inclusivenode.tech abilitynode.tech

Unified Domain System

This is the current working map of the ecosystem for deployment, partner alignment, investor explanation, and future geographic scaling.

1. Protocol Root

Global AI Entry Protocol and Portal Compute Center root.

aiplug.tech

2. Global Index

Structured index of domains, nodes, routes, regions, and protocol branches.

index.aiplug.tech

3. OS Root

Global Execution Operating System and China Compliance Gateway.

homelinked.tech

4. Regional Entry Family

City-facing AI+ regional entry shells for trusted urban pilots, public access, and future independent rollout.

aiplughk.com aiplugnyc.com aiplugshenzhen.com

5. Node Layer

Addressable node system for physical-world execution objects.

node.homelinked.tech

6. Hong Kong Region

Regional execution namespace for Hong Kong transport, accessibility, and city-scale AI services.

hk.homelinked.tech

7. Shenzhen Region

Regional execution namespace for Shenzhen deployment, manufacturing-city intelligence, and cross-border replication.

shenzhen.homelinked.tech

8. NYC Region

Regional execution namespace for New York pilots, global demonstration, and investor-facing urban AI scenarios.

nyc.homelinked.tech

9. Vision Interface

Camera, OCR, perception, and AI interface for entering the execution network.

visiongo.tech

10. Trusted Capability Shells

Innovation shell, supply-chain shell, inclusion shell, and capability shell for trust, rollout, and structured participation.

innospirex.tech pannexx.tech inclusivenode.tech abilitynode.tech

Regional Entry and Infrastructure Direction

The current system uses shared roots and regional execution namespaces to accelerate deployment, but the long-term direction is independent city entry, independent compliance, independent IP, and eventually independent node-level infrastructure.

Current Transition Model

Today, regional entry domains such as aiplughk.com, aiplugnyc.com, and aiplugshenzhen.com can transition through shared execution namespaces such as hk.homelinked.tech, nyc.homelinked.tech, and shenzhen.homelinked.tech.

Long-Term Infrastructure Direction

In the future, major city entries, regional layers, Portal Compute Centers, and even transport nodes such as bus stops should evolve toward independent IP, independent governance, and independent compliance readiness.

Shared Namespace → Regional Entry → Independent Region Stack → Independent Node Infrastructure

Execution Logic

The value of the system is not in publishing pages faster, but in making reality executable through a structured operating framework.

Camera → OCR → Node → API → JSON → LLM → Decision → Execution
China Compliance S3 Bridge Node Layer JSON LLM Execution Orphan URL AI Service Pages

China Publishing Role

Most companies entering China do not understand MIIT filing, SSL, or structured standalone web deployment. Most companies in China going outward also lack disciplined independent publishing infrastructure. HomeLinked OS serves as a bridge in both directions.

Global to China

Global AI products, service pages, and orphan URLs can use HomeLinked OS as a China-facing publishing and compliance root.

China to Global

China-based teams can use the same structure to publish globally connected execution pages with clearer SSL, structure, and asset discipline.