Framework

Distribution	archetype-ecs
Import package	archetype
Primary entry point	ArchetypeRuntime
Depends on a world library	No

The framework owns the generic ECS and process host: Components, Processors, worlds, append-only ticks, storage, commands, Activities, artifacts, evaluation, runtime lifetime, REST hosting, and the CLI.

Missions, Physical AI, and Research are separately installed libraries. Their domain values and workflows do not belong to the framework root API.

For a deliberately bounded synchronous teaching loop without production runtime or storage semantics, see Smol.

Learn the engine

• Quickstart
• Components
• Processors
• Working with worlds
• History and forks
• Core architecture

Build and extend

• Building simulations
• Resources
• Lifecycle hooks
• Prefab libraries
• Custom commands

Run and operate

• Runtime contract
• Activities
• Storage
• Artifacts
• Access control and audit
• Running a server

Reference

• Python API
• Framework evaluation
• REST API
• CLI

For framework internals, cross-package architecture, and executable contract evidence, continue to Maintainers.