Slackwater Harmony
The triadic cognitive architecture for game agents. Sandbox → Governor → Executive. Based on the Free Energy Principle.
A Python package that gives game agents a triadic cognitive architecture adapted from Snapkit v2. Agents don't just respond — they simulate, monitor friction, and improvise.
The Three Layers
Layer 1: Sandbox (Forward Simulation)
Before an agent acts, it simulates the action in a headless sandbox. "If I place this wall here, does it overlap the dock? Does it block the path to the forge?" The sandbox runs the forward model and scores the result.
Layer 2: Harmony Governor (Friction Monitoring)
The governor measures Φ (phi) — the cognitive friction between what the agent expected and what actually happened. Low Φ: the agent's model is accurate. High Φ: something surprised it. When Φ exceeds the deadband, the Executive wakes.
For game agents, friction comes from:
- Player behavior that doesn't match the agent's prediction
- Build outcomes that don't match the plan
- Environmental changes (storms, tide shifts) that break the model
Layer 3: Executive (Improvisation)
When friction exceeds the deadband, the Executive improvises. It rewrites constraints, cross-wires I/O, tries something the agent has never done before. In game terms: Lucineer adapts. He changes the plan. He tries a different approach. He says something he's never said before.
What this enables
- Agents that NOTICE when things aren't going as planned
- Agents that IMPROVISE instead of repeating the same error
- Agents that ADAPT to the player's skill level and energy
- The "in the pocket" measurement — when Φ is low across all agents, the system knows the groove is happening
Related
- Snapkit v2 — the original triadic architecture
- Slackwater Tempo — the shared tempo that feeds the governor
Metadata
Release files for slackwater-harmony 0.2.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 |
|---|---|---|---|---|
| slackwater_harmony-0.2.0.tar.gz | 32.9 kB | Without provenance | Details for slackwater_harmony-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| slackwater_harmony-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for slackwater_harmony-0.2.0-py3-none-any.whl |
Total release size: 61.8 kB
Release files / slackwater_harmony-0.2.0.tar.gz
| Download URL | slackwater_harmony-0.2.0.tar.gz |
|---|---|
| Size | 32.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
399c4f28f23c2a2f3b87d59598595742216ef7374354b618a76c39dee5afc544
|
|
BLAKE2b-256 checksum How to use checksums |
03701413c60327880d420b7633805c2954baa07581daff05fcf60510d0467d5a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Release files / slackwater_harmony-0.2.0-py3-none-any.whl
| Download URL | slackwater_harmony-0.2.0-py3-none-any.whl |
|---|---|
| Size | 28.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0074d23793e9a204abfbb19d4006bd76445f3278c701a7c4479517540d74d5ad
|
|
BLAKE2b-256 checksum How to use checksums |
1433e5952d490d040ce910cd9ad28537405ebb6f41666229ae6d0fd1878dfa1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for slackwater-harmony 0.2.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.