Reactions and notifications when your knowledge graph changes. Chaski keeps notification delivery separate from the facts that triggered it.
- React to graph changes: evaluate rules when relevant facts change.
- Handle time-based conditions: schedule checks for deadlines and expiry.
- Preserve uncertainty: a timed-out query does not resolve a firing condition.
curl -fsSL https://raw.githubusercontent.com/scbrown/chaski/main/install.sh | shPython 3.11+ with venv/pip, curl, and a Linux or macOS shell. Downloads the latest checksummed wheel into its own virtual environment;
command links go in ~/.local/bin. Add that directory to PATH.
Set STACK_INSTALL_ROOT on the receiving shell for another prefix.
Pinned releases, alternatives, configuration and removal are in the
installation and usage reference.
The real reactor uses synthetic offline query outcomes; no graph or notification sink is connected. Read the transcript or reproduce the recording.
Inspect the installed receiver's options:
chaski --helpThen choose an explicit source and sink in the configuration guide. Installation alone starts no receiver or scheduled job.
Choose a rule, source and notification sink in the configuration guide. Rules select the nodes currently firing; a conclusive result can resolve them, while UNKNOWN retains the prior verdict. Use the offline demo to observe that lifecycle before configuring a receiver. Adapter setup and actual event coverage must be verified separately.
Run chaski prime (--brief, --json, --static, or --section core) before
receiver setup. See the primer and
skill. Prime reads only explicit sources and starts no
receiver, adapter or delivery. Give the agent the explicit source and sink
configuration rather than assuming installation activated them.
The installer needs Python 3.11+ with venv/pip, curl and Linux or macOS. A live receiver needs a configured source, rule inventory and sink. Review credentials and delivery behavior before starting it. The embedded demo uses synthetic offline query outcomes and sends no notifications.
- Documentation: receiver and adapter setup.
- Agent primer: bounded orientation.
- Offline demo: reproduce the lifecycle without a graph or sink.
A published book root has not been verified; these links use checked-in source.
- Tambo: guided stack installation and verification.
- Camayoc: governed memory and vocabulary.
- Detailed examples and agent setup.
Load this repository’s graph: public repository-pendant assets have not yet been verified. When a release supplies the archive, checksum and provenance, follow the verified import workflow: extract the share directory and use quipu import SHARE_DIR --db repository.db. Import stages knowledge; ROOT stays unchanged.
The Quipu stack is built around a governed, bitemporal knowledge store: shared facts, decisions and work history your agents can query. Quipu can check writes against your rules, records where each fact came from, and answers what was true when.
| tool | what it gives your agents |
|---|---|
| tambo | 🧰 Agent Platform Toolkit - installs and configures the quipu stack |
| quipu | stores shared facts with provenance and history; can check writes against your rules |
| camayoc | prepares knowledge and vocabulary for Quipu, with checks before it is admitted |
| quechua | shared vocabulary and shapes for interoperable knowledge |
| chaski | reacts to graph changes and delivers governed notifications |
| bobbin | indexes your codebase and injects context from that index and Quipu knowledge |
| yupana | shows code impact and can read policies from Quipu to govern agent actions |
| desire-path | turns agent mistakes into feature requests; works on its own without Quipu |
| seeds | a work item tracker backed by the Quipu knowledge base |
| shantytown | runs crews of AI agents on work items, triggered by hand, on a schedule or by events; can share work and memory through Quipu |
| rikuy | live brief: status, graphs, watches and signed decisions over Quipu |
| shuttle | runs signed agent workflows and keeps their records in Quipu |
See the repository tests and documentation checks before submitting a change.