uro-core
The Uro Engine core library — the embeddable, headless world-state engine.
Uro is a world-state engine: the persistent, versioned, forkable canonical record of a living fictional world. A model narrates; a fenced extractor distills that narration into a queryable world model — actors, places, factions, beliefs, open threads — that stays authoritative while the story plays over it. It tracks not only what is true but who knows it, and world state is versioned and forkable: a finished campaign's ending becomes a point in history any new campaign can continue from, branch off, or explore as a what-if.
uro-core contains all engine logic and is embeddable in any consumer — the engine only ever
sees ports (hexagonal architecture), never concrete adapters.
Install
pip install "uro-core[postgres,llm]"
The base install is the pure engine (it imports only ports). The shipped adapters live behind extras:
postgres— the bundled event store + semantic memory over PostgreSQL + pgvector.llm— the bundled LLM provider adapters (OpenAI-compatible + Anthropic).all— both.
An embedder can install the base package and supply their own adapters behind the same ports.
Runtime
The bundled store requires PostgreSQL 17 + pgvector. The reference setup runs it via Docker on host port 5433; see the project repository.
Links
- Source, docs, and the reference CLI/server: https://github.com/cupskeee/uro
- License: MIT
1 maintainer
Metadata
1 maintainer
Release files for uro-core 0.11.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| uro_core-0.11.0.tar.gz | 340.3 kB | Without provenance | Details for uro_core-0.11.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| uro_core-0.11.0-py3-none-any.whl | Python 3 | none | any | Details for uro_core-0.11.0-py3-none-any.whl |
Total release size: 590.5 kB
Release files / uro_core-0.11.0.tar.gz
| Download URL | uro_core-0.11.0.tar.gz |
|---|---|
| Size | 340.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7619e0809c485166828eefd4b1569dd4e607137169c3230b128247db724690c6
|
|
BLAKE2b-256 checksum How to use checksums |
cc4cb3166d067755f6a83998483f1316e3345d4c85a0549db83b74e7575cb6ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / uro_core-0.11.0-py3-none-any.whl
| Download URL | uro_core-0.11.0-py3-none-any.whl |
|---|---|
| Size | 250.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d14514efa72ea3d15bdf474b23a4e345c12861ca2d78a298092470beb431974c
|
|
BLAKE2b-256 checksum How to use checksums |
d6d33c23b18cf080ecc5e1a9ce3c547f0748cdb9bc91a700ecc3e59e5bcea654
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for uro-core 0.11.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
