> For the complete documentation index, see [llms.txt](https://dragoncapsule.gitbook.io/di-er-bu-qiong-ding-jia-yuan/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dragoncapsule.gitbook.io/di-er-bu-qiong-ding-jia-yuan/noii/dc-origin.md).

# 第二卷. 穹顶家园（ Domeland）

到了2100年，全真元宇宙高度发达，初步形成人类虚拟化生存的共识。

 

对于元宇宙，新的物理学共识已经在全球主流精英中形成：**人类的主观意识塑造了古代与近现代科学的一切物理学体系**。人类物理学在客观本质上并不存在，**现代科学的所有物理学，都是人类对世界主观认知基础上的经验与总结。**

> ***客观宇宙唯有物质和空间，物理现实与客观宇宙的唯一不变联系，仅有几何学。***

 

在主流 **“元宇宙派”** 的推动下，元宇宙与AI 大行其道，人类在九天幻方中越陷越深，并且在元宇宙中尝试制造自定义的新物理规律。

 

以马克西姆、伊隆等为首的自由企业家，认为**AI+全真元宇宙**正在吞噬虚幻中的人类，磨灭了人类的宝贵的探险精神，最终将导致人类文明的灭绝

 

为了抵抗日益强大的AGI驱动 **“元宇宙派”**，各国政府精英们、伊隆代表的自由企业家们紧急联合起来，发起了庞大的第二家园计划 “**DomeLand-穹顶家园”**， 号召那些不满意和不愿意沉沦在元宇宙虚拟幻境中的全球人民，飞翔星空，作为星际拓荒的先驱者，共同开拓太空新领地。

 

**“穹顶家园”** 立法设立星际人类发展路线，发展用于长期深空航行的（100年以上）**超级方舟**，并在穹顶家园计划范围内全面约束全真元宇宙技术，全力为开辟打造地球之外的**人类第二绿洲**，保留人类发展的火种。 “穹顶家园” 的推动者们被统称 “**星空派”**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dragoncapsule.gitbook.io/di-er-bu-qiong-ding-jia-yuan/noii/dc-origin.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.