elephentity / runtime

v0.9.0 2026-09-14 23:15 UTC

Requires

• php: >=8.3
• psr/container: ^2.0
• psr/log: ^3.0

Requires (Dev)

• friendsofphp/php-cs-fixer: ^3.64
• phpstan/phpstan: ^2.0
• phpunit/phpunit: ^11.0 || ^12.0

MIT

Published on Packagist.org on 2026-09-14 23:33 UTC

README

Elephentity's runtime contracts: the storage port, the unit of work, verification and loaders — the small, driver-agnostic surface every adaptor implements and every generated entity depends on.

composer require elephentity/runtime

This is a read-only mirror

The source of truth is packages/runtime in elephentity. This repository exists only so elephentity/runtime is installable on its own — a WordPress site that depends on elephentity/wordpress should not also pull in the spec compiler.

Open pull requests against elephentity, not here. A subtree split mirrors packages/runtime into this repository's main on every push, and re-tags it whenever elephentity is tagged — so this repo's history and tags always match the state of packages/runtime at the same point in elephentity's. A change made directly here would be overwritten by the next split.

What it is not

This package ships to production, but it is not itself a driver. There is no adaptor here — Storage\Testing\AdaptorConformance is the suite any adaptor proves itself against, and elephentity/wordpress and elephentity/wpgraphql are the two that do. A project that wants no platform at all installs neither and writes its own adaptor against Storage\StorageAdaptor, or uses elephentity/memory, which still lives in elephentity alongside the compiler.

Before you commit anything that crosses a repository boundary

.llms/cross-repo.md is the closed list of what crosses. If you changed something on it, open an issue on each repository it reaches, before or with the push. .llms/README.md has the rule and .llms/issue-template.md the shape.