Field-tested mechanics

The proposed @machinapractica/* packages will contain reusable implementation mechanics: evidence capture, build identity, deterministic replay, and other boundaries justified by working consumer code.

A shared package should remove duplication and maintenance while preserving product-specific rules, privacy boundaries, and presentation. Three real adopters and historical compatibility evidence are required before 1.0.

Status: experimental implementations, not yet published to npm. Evidence tooling and build identity are available in the package repository with source inventory, tests and local alpha tarballs. There are no consumer adopters yet.

Read the package extraction proposal in the package repository. The @machinapractica npm scope is reserved; release tooling and remaining evidence gates are documented in the repository.