micalang 0.1.0__tar.gz

micalang-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,23 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.12", "3.13", "3.14"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: uv sync
+      - run: uv run python -m unittest discover -s tests
+      - run: uv build
+      - run: uvx twine check dist/*

micalang-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,33 @@
+name: release
+
+on:
+  push:
+    tags: ["v*"]
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+      - run: uv build
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

micalang-0.1.0/.gitignore

@@ -0,0 +1,14 @@
+.venv/
+.idea/
+uv.lock
+__pycache__/
+*.py[cod]
+.env
+.env.*
+!.env.example
+dist/
+build/
+*.egg-info/
+.pytest_cache/
+.ruff_cache/
+.DS_Store

micalang-0.1.0/CHANGELOG.md

@@ -0,0 +1,23 @@
+# Changelog
+
+本项目的所有重要变更都会记录在此文件中。
+
+格式基于 [Keep a Changelog](https://keepachangelog.com/zh-CN/1.1.0/)，
+版本号遵循 [语义化版本](https://semver.org/lang/zh-CN/)。
+
+## [Unreleased]
+
+## [0.1.0] - 未发布
+
+首次公开发布。构建过程见构建手记 `docs/stages/`（tag `stage-0`…`stage-6`）。
+
+### Added
+
+- Mica-PY 参考实现：源码经白名单校验编译为内部指令流，由统一调度循环执行，不经 `exec`/`eval`。
+- 语言：int/float/str/bool/None/list/dict；`if/while/for`、`break/continue`、`try/except/else/finally`、`raise`、三元表达式；函数、递归、默认参数与关键字实参。
+- 嵌套 VM：任意层可创建子 VM，子 VM 不感知层深；父 VM 可预置文件、喂输入、单步调试、快照、终止。
+- 能力授予（FFI）：宿主向 root VM 注入函数，任意层 VM 向下一层授予函数；跨宿主边界双向深拷贝 + 纯数据类型白名单。
+- 资源治理：指令数、输出字节、调用深度、子 VM 数量、嵌套深度、容器大小、字符串字节、整数位宽、近似内存总量、VM 总数、文件数与单文件字节配额；子 VM 消耗计入所有祖先。
+- 每个 VM 自带私有虚拟文件系统（纯内存、纯文本）。
+- 回归测试：198 个用例。
+- demo：HTTP 能力授予 + 多层虚拟化的 LLM 代码执行示例（`demo` extra，含离线桩服务器）。

micalang-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,33 @@
+# 贡献指南
+
+English readers: this project's development workflow is currently documented in Chinese. An English version is planned.
+
+## 开发环境
+
+- Python ≥ 3.12，包管理用 [uv](https://docs.astral.sh/uv/)。
+- 引擎本体零第三方依赖；`demo` 的依赖在 `pyproject.toml` 的 `demo` extra 里。
+
+## 验证
+
+修改引擎、编译器或脚本接口后，必须先运行回归套件：
+
+```bash
+uv sync
+uv run python -m unittest discover -s tests
+```
+
+仓库采用 `src/` 布局，直接运行 `python -m unittest` 前需要先安装本项目（`uv sync` 会自动处理）。
+
+## 设计纪律
+
+- 理念问题以 [`docs/design.zh-CN.md`](docs/design.zh-CN.md) 为准。改理念先改它，不要在别处另造表述。
+- 架构不变量见 [`docs/architecture.zh-CN.md`](docs/architecture.zh-CN.md)。新语法必须先过编译器白名单，禁止引入 `exec`/`eval`。
+- 不给引擎加网络/设备等内建能力；能力的正确形态是 FFI 授予。安全边界见 [`docs/security.zh-CN.md`](docs/security.zh-CN.md)。
+
+## 文档流程
+
+本项目的说明性文档遵循一条规则：**AI 可以起草，入库前必须经作者人工打磨**。如果你提交的 PR 改动文档，请确保文本由人通读并修改过，而不是直接提交模型输出。
+
+## 提交信息
+
+使用中文，一句话说明这次提交做了什么，格式参考已有历史（如 `docs: 文档初始化——设计理念、语言参考与构建手记框架`）。

micalang-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

micalang-0.1.0/NOTICE

@@ -0,0 +1,4 @@
+MicaLang
+Copyright 2026 LeoLoudWarden
+
+Licensed under the Apache License, Version 2.0.

micalang-0.1.0/PKG-INFO

@@ -0,0 +1,123 @@
+Metadata-Version: 2.5
+Name: micalang
+Version: 0.1.0
+Summary: Mica: a scripting language with cheap, arbitrarily nested VM isolation
+Project-URL: Homepage, https://github.com/LeoLoudWarden/micalang
+Project-URL: Repository, https://github.com/LeoLoudWarden/micalang
+Project-URL: Issues, https://github.com/LeoLoudWarden/micalang/issues
+Project-URL: Changelog, https://github.com/LeoLoudWarden/micalang/blob/main/CHANGELOG.md
+Author: LeoLoudWarden
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: interpreter,isolation,language,sandbox,scripting-language,virtual-machine
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Interpreters
+Requires-Python: >=3.12
+Provides-Extra: demo
+Requires-Dist: python-dotenv; extra == 'demo'
+Requires-Dist: requests; extra == 'demo'
+Description-Content-Type: text/markdown
+
+# MicaLang
+
+**Mica** is a scripting language and its execution engine, built around a single idea: creating a fully isolated, arbitrarily nestable runtime environment should be a cheap, first-class operation in the language itself.
+
+Syntax borrows a subset of Python, but Mica source is compiled into Mica's own instruction stream and executed by the Mica engine — never through `exec`/`eval`. Every VM starts with zero capabilities: its own virtual IO, its own in-memory filesystem, and the ability to create child VMs. Everything else (network, host data, whatever you choose) is granted explicitly, layer by layer, through FFI.
+
+[中文文档与项目说明](README.zh-CN.md)
+
+## Status
+
+0.1.0 prototype. The engine is a Python reference implementation (codename **Mica-PY**): zero runtime dependencies, Python ≥ 3.12, 198 regression tests. APIs and semantics may change before 1.0.
+
+> **Security note.** Mica is designed for isolation, but the current prototype runs in the host process and has not been formally audited. Do not rely on it as the *only* boundary when executing adversarial code. See the [security model](docs/security.zh-CN.md) (中文) for exactly what is and is not guaranteed.
+
+## Install
+
+```bash
+pip install micalang
+```
+
+The distribution is named `micalang`; the import package is `mica`.
+
+## Quick start
+
+As a CLI:
+
+```bash
+printf 'print("hello from mica")\n' > hello.mica
+micalang hello.mica        # hello from mica
+```
+
+Embedded in Python:
+
+```python
+from mica import MicaEngine
+
+engine = MicaEngine()
+vm = engine.create_root("""
+sub = VM("print('hello from a child VM')")
+print(sub.run())
+""")
+print(vm.run(), end="")
+```
+
+Grant a capability to a VM (FFI):
+
+```python
+def double(x):
+    return x * 2
+
+vm = engine.create_root("print(double(21))", functions={"double": double})
+print(vm.run(), end="")    # 42
+```
+
+## What a Mica VM is
+
+A VM is a cheap, self-contained workspace:
+
+- it cannot see its parent's variables, files, or handles, and cannot tell how deep it is nested;
+- it has its own empty in-memory filesystem (text only — structurally unable to touch the real disk);
+- resource quotas (instructions, memory, output, child VMs, nesting depth, …) can only be tightened, never loosened, and a child's consumption is charged to all its ancestors;
+- its parent can preset files, feed input, single-step it statement by statement or instruction by instruction, snapshot its state, or terminate it;
+- it can create its own child VMs — isolation is recursive, because untrusted code is.
+
+## Documentation
+
+| Document | Language | Contents |
+|---|---|---|
+| [Design notes](docs/design.zh-CN.md) | 中文 | What Mica is, why it exists, where the boundaries are |
+| [Language reference](docs/language-reference.zh-CN.md) | 中文 | The language subset and semantics, self-contained |
+| [Architecture](docs/architecture.zh-CN.md) | 中文 | Engine structure, invariants, resource quotas |
+| [Security model](docs/security.zh-CN.md) | 中文 | Threat model; what the engine does and does not guarantee |
+| [Build journal](docs/stages/README.md) | 中文 | How Mica 0.1.0 was built, stage by stage, with runnable checkpoints (`git checkout stage-1` … `stage-6`) |
+| [Behind the scenes](docs/behind-the-scenes/README.md) | 中文 | Origin story and how AI-assisted development was used |
+
+An English documentation set is planned after 0.1.0.
+
+## How this project was built
+
+Mica was developed with AI assistance throughout — design discussion, implementation, testing, adversarial review, and documentation drafting. What the AI did, what the author did, and how outputs were verified are documented in [AI-assisted development](docs/behind-the-scenes/ai-assisted-development.zh-CN.md) (中文), with selected conversation records alongside.
+
+## Roadmap
+
+- List/dict/string methods and more ergonomic syntax
+- Performance benchmarks (child-VM creation cost, per-instruction overhead)
+- A normative language spec and a conformance test suite, so a future non-Python engine can be validated against them
+- Evaluation of a native engine (the package name is language-level on purpose: `micalang` survives an engine rewrite)
+
+## The name
+
+Mica (云母) is a layered mineral: it cleaves into thin sheets, each sheet complete in itself, and it is an insulator — layers do not conduct into each other. That is the shape of a Mica VM tree.
+
+Not related to the Windows "Mica" UI material, the PyPI bioinformatics package MICA, or the (inactive) Rust scripting language named Mica.
+
+## License
+
+[Apache-2.0](LICENSE) — see [NOTICE](NOTICE).

micalang-0.1.0/README.md

@@ -0,0 +1,97 @@
+# MicaLang
+
+**Mica** is a scripting language and its execution engine, built around a single idea: creating a fully isolated, arbitrarily nestable runtime environment should be a cheap, first-class operation in the language itself.
+
+Syntax borrows a subset of Python, but Mica source is compiled into Mica's own instruction stream and executed by the Mica engine — never through `exec`/`eval`. Every VM starts with zero capabilities: its own virtual IO, its own in-memory filesystem, and the ability to create child VMs. Everything else (network, host data, whatever you choose) is granted explicitly, layer by layer, through FFI.
+
+[中文文档与项目说明](README.zh-CN.md)
+
+## Status
+
+0.1.0 prototype. The engine is a Python reference implementation (codename **Mica-PY**): zero runtime dependencies, Python ≥ 3.12, 198 regression tests. APIs and semantics may change before 1.0.
+
+> **Security note.** Mica is designed for isolation, but the current prototype runs in the host process and has not been formally audited. Do not rely on it as the *only* boundary when executing adversarial code. See the [security model](docs/security.zh-CN.md) (中文) for exactly what is and is not guaranteed.
+
+## Install
+
+```bash
+pip install micalang
+```
+
+The distribution is named `micalang`; the import package is `mica`.
+
+## Quick start
+
+As a CLI:
+
+```bash
+printf 'print("hello from mica")\n' > hello.mica
+micalang hello.mica        # hello from mica
+```
+
+Embedded in Python:
+
+```python
+from mica import MicaEngine
+
+engine = MicaEngine()
+vm = engine.create_root("""
+sub = VM("print('hello from a child VM')")
+print(sub.run())
+""")
+print(vm.run(), end="")
+```
+
+Grant a capability to a VM (FFI):
+
+```python
+def double(x):
+    return x * 2
+
+vm = engine.create_root("print(double(21))", functions={"double": double})
+print(vm.run(), end="")    # 42
+```
+
+## What a Mica VM is
+
+A VM is a cheap, self-contained workspace:
+
+- it cannot see its parent's variables, files, or handles, and cannot tell how deep it is nested;
+- it has its own empty in-memory filesystem (text only — structurally unable to touch the real disk);
+- resource quotas (instructions, memory, output, child VMs, nesting depth, …) can only be tightened, never loosened, and a child's consumption is charged to all its ancestors;
+- its parent can preset files, feed input, single-step it statement by statement or instruction by instruction, snapshot its state, or terminate it;
+- it can create its own child VMs — isolation is recursive, because untrusted code is.
+
+## Documentation
+
+| Document | Language | Contents |
+|---|---|---|
+| [Design notes](docs/design.zh-CN.md) | 中文 | What Mica is, why it exists, where the boundaries are |
+| [Language reference](docs/language-reference.zh-CN.md) | 中文 | The language subset and semantics, self-contained |
+| [Architecture](docs/architecture.zh-CN.md) | 中文 | Engine structure, invariants, resource quotas |
+| [Security model](docs/security.zh-CN.md) | 中文 | Threat model; what the engine does and does not guarantee |
+| [Build journal](docs/stages/README.md) | 中文 | How Mica 0.1.0 was built, stage by stage, with runnable checkpoints (`git checkout stage-1` … `stage-6`) |
+| [Behind the scenes](docs/behind-the-scenes/README.md) | 中文 | Origin story and how AI-assisted development was used |
+
+An English documentation set is planned after 0.1.0.
+
+## How this project was built
+
+Mica was developed with AI assistance throughout — design discussion, implementation, testing, adversarial review, and documentation drafting. What the AI did, what the author did, and how outputs were verified are documented in [AI-assisted development](docs/behind-the-scenes/ai-assisted-development.zh-CN.md) (中文), with selected conversation records alongside.
+
+## Roadmap
+
+- List/dict/string methods and more ergonomic syntax
+- Performance benchmarks (child-VM creation cost, per-instruction overhead)
+- A normative language spec and a conformance test suite, so a future non-Python engine can be validated against them
+- Evaluation of a native engine (the package name is language-level on purpose: `micalang` survives an engine rewrite)
+
+## The name
+
+Mica (云母) is a layered mineral: it cleaves into thin sheets, each sheet complete in itself, and it is an insulator — layers do not conduct into each other. That is the shape of a Mica VM tree.
+
+Not related to the Windows "Mica" UI material, the PyPI bioinformatics package MICA, or the (inactive) Rust scripting language named Mica.
+
+## License
+
+[Apache-2.0](LICENSE) — see [NOTICE](NOTICE).

micalang-0.1.0/README.zh-CN.md

@@ -0,0 +1,93 @@
+# MicaLang
+
+**Mica** 是一门脚本语言及其执行引擎，围绕一个想法构建：**创建一个完全隔离、可以任意嵌套的运行环境，应当是语言自身的一种廉价的第一类操作。**
+
+语法借用 Python 的一个子集，但 Mica 源码会被编译为 Mica 自己的指令流，由 Mica 引擎逐条执行——不经过 `exec`/`eval`。每台 VM 初始能力为零：独立的虚拟 IO、独立的内存文件系统、创建子 VM。其余一切能力（网络、宿主数据、任何你选择授予的东西）都通过 FFI 逐层显式授予。
+
+## 状态
+
+0.1.0 原型。引擎是 Python 参考实现（代号 **Mica-PY**）：零运行时依赖，Python ≥ 3.12，198 个回归测试用例。1.0 之前 API 与语义可能变化。
+
+> **安全提示。** Mica 为隔离而设计，但当前原型与宿主同进程运行，未经正式安全审计。执行对抗性代码时，不要把 Mica 当作**唯一**的隔离边界。引擎保证什么、不保证什么，见[安全模型](docs/security.zh-CN.md)。
+
+## 安装
+
+```bash
+pip install micalang
+```
+
+发行包名为 `micalang`，导入包名为 `mica`。
+
+## 快速上手
+
+命令行：
+
+```bash
+printf 'print("hello from mica")\n' > hello.mica
+micalang hello.mica        # hello from mica
+```
+
+嵌入 Python：
+
+```python
+from mica import MicaEngine
+
+engine = MicaEngine()
+vm = engine.create_root("""
+sub = VM("print('hello from a child VM')")
+print(sub.run())
+""")
+print(vm.run(), end="")
+```
+
+向 VM 授予能力（FFI）：
+
+```python
+def double(x):
+    return x * 2
+
+vm = engine.create_root("print(double(21))", functions={"double": double})
+print(vm.run(), end="")    # 42
+```
+
+## 一台 Mica VM 是什么
+
+一台廉价、自包含的工作空间：
+
+- 看不到父级的变量、文件和句柄，也不知道自己嵌套在第几层；
+- 有独立的空白内存文件系统（纯文本——结构上碰不到真实磁盘）；
+- 资源配额（指令、内存、输出、子 VM 数、嵌套深度……）只能收紧不能放宽，子 VM 的消耗计入所有祖先；
+- 父级可以预置文件、喂输入、逐语句或逐指令单步、查看快照、随时终止；
+- 它可以创建自己的子 VM——隔离是递归的，因为不可信的代码是递归的。
+
+## 文档
+
+| 文档 | 内容 |
+|---|---|
+| [设计说明](docs/design.zh-CN.md) | Mica 是什么、为什么存在、边界划在哪里 |
+| [语言参考](docs/language-reference.zh-CN.md) | 自完备的语言子集与语义 |
+| [架构说明](docs/architecture.zh-CN.md) | 引擎结构、设计不变量、资源配额 |
+| [安全模型](docs/security.zh-CN.md) | 威胁模型；引擎保证什么、不保证什么 |
+| [构建手记](docs/stages/README.md) | Mica 0.1.0 逐阶段构建过程，含可运行检查点（`git checkout stage-1` … `stage-6`） |
+| [幕后](docs/behind-the-scenes/README.md) | 项目由来与 AI 辅助开发过程 |
+
+## 这个项目是怎么写出来的
+
+Mica 全程使用 AI 辅助开发——设计讨论、实现、测试、对抗性审查、文档起草。AI 做了什么、作者做了什么、产出如何被验证，记录在 [AI 辅助开发说明](docs/behind-the-scenes/ai-assisted-development.zh-CN.md)，附开发对话选编。
+
+## 路线图
+
+- 列表/字典/字符串方法与更多易用性语法
+- 性能基准（子 VM 创建成本、每指令开销）
+- 规范化的语言规范与一致性测试套件，供未来非 Python 引擎对照验证
+- 原生引擎评估（包名刻意取语言级：`micalang` 在引擎重写后依然成立）
+
+## 名字
+
+Mica（云母）是一种层状矿物：可以沿解理面剥成薄片，每一片都是完整的一层，且层间绝缘。这正是 Mica VM 树的形状。
+
+本项目与 Windows 的 Mica 界面材质、PyPI 上的生物信息学包 MICA、以及已停更的同名 Rust 脚本语言均无关。
+
+## 许可证
+
+[Apache-2.0](LICENSE)——见 [NOTICE](NOTICE)。