Sericite

Sericite 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 Sericite source is compiled into Sericite's own instruction stream and executed by the Sericite 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.

中文文档与项目说明

Status

0.2.0 prototype. The engine is a Python reference implementation (codename Sericite-PY): zero runtime dependencies, Python ≥ 3.12, 198 regression tests. APIs and semantics may change before 1.0.

Security note. Sericite 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 for exactly what is and is not guaranteed.

Install

pip install sericite

The distribution is named sericite; the import package is sericite.

Quick start

As a CLI:

printf 'print("hello from sericite")\n' > hello.sericite
sericite hello.sericite        # hello from sericite

Embedded in Python:

from sericite import SericiteEngine

engine = SericiteEngine()
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):

def double(x):
    return x * 2

vm = engine.create_root("print(double(21))", functions={"double": double})
print(vm.run(), end="")    # 42

What a Sericite 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

Architecture notes, build journal, and behind-the-scenes are currently 中文-only; English versions are planned.

How this project was built

Sericite 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 (中文), 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: sericite survives an engine rewrite)

The name

Sericite (绢云母) is the finest-grained member of the mica family: thin silky scales that stack into sheets, and an insulator like every mica. The name keeps the three promises the project is named after — layering, insulation, lightness.

(The project was briefly named Mica/MicaLang; it was renamed after discovering the name was occupied multiple times over, including an actively developed commercial language publishing Docker images under the micalang namespace.)

License

Apache-2.0 — see NOTICE.