Domain coverage
The table classifies source at the reviewed commits. Archived legacy is not active v1 functionality; generic Entity primitives do not prove that a gameplay domain has been ported.
| v0 domain or v1 module | v1 state | Evidence and consequence |
|---|---|---|
| Entity, Action, Request, Requirement | Active v1 implementation | core supplies the modular foundation. |
| Character identity | Redesigned equivalent | Identity is an installed module, not v0’s Character layout. |
| Item and storage inventory | Active v1 implementation | Active inventory is request-routed. |
| Assemblies: gate, turret, storage unit | Archived legacy only | v0 modules remain under contracts/archive/world. |
| Network nodes, killmails, rifts | No active v1 equivalent / not yet ported | Present on v0/main, absent from the active v1 package set. |
| Fuel, energy, status, metadata | Archived legacy only | v0 primitives are retained in archive, not active modules. |
| Access, location, registry | Partially represented | Active core has services and registry concepts, with materially different interfaces and checks. |
| Extension examples | Archived legacy only | Examples were moved below archive. |
| v1 deployment | Deployment unknown or separately evidenced | dev/world.json names some artifacts, not every active package or a production environment. |
The coverage rows are intentionally conservative: a domain can be partially represented by generic platform features without possessing its v0 lifecycle, type, API, or authorization checks.