Local-first · Git-native · MIT
The execution graph for work that people and agents share.
Quest records what must happen, what depends on what, who is acting, which gates remain, and what evidence completed the work — in the same Git history as the code.
| Task | Work | State |
|---|---|---|
| T-101 | Freeze the record schema | ready |
| T-104 | Cut the release branch | blockedwaiting on T-101 |
| T-108 | Refresh the migration fixtures | claimedlease ends in 6m |
| T-112 | Publish the artifact | at a gatereview not signed |
Knowing the system is not the same as moving it.
A repository can hold every decision that shaped a system and still not answer the question that starts a working day: what can be picked up right now, and what is holding up the rest?
Trackers answer it for people, inside a service people log into. Quest answers it in files the repository already carries, so the same answer is available to a person reading a diff, to a script, and to an agent that has to show what it did.
The model
Five steps, in order, because each one depends on the one before it. This is what Quest is designed to record.
Authored
A task is a Git-tracked record. It is written, reviewed, and merged like anything else in the repository, so its history is already the audit trail.
Readiness
Every task declares what it depends on. Quest derives the ready set from those declarations: the tasks nothing is blocking right now.
Claim
An actor takes a ready task under a lease with a deadline. When a lease expires the task returns to the ready set, so abandoned work surfaces instead of stalling quietly.
Gate
A task can require a plan, a review, or a check before it may complete. A gate stays open until it is met, whoever or whatever is doing the work.
Evidence
Completion carries the artifact that proves it. Done is a record with something attached, not a status somebody set.
Where the authority sits
- Source of truth
- The Git-tracked records. The graph Quest builds over them is a projection: disposable, scoped to the repositories you enrol, and rebuildable from the records alone.
- No model inside
- There is no language model in the record layer. That is what makes it something a person and an agent can both read and write without either having to trust the other.
- Alongside Lore
- Quest works in a repository that has no Lore records at all. Where Lore is present the two exchange versioned public data; neither writes the other’s storage.
- Account
- None. Local use needs no Opum account, and this site has no sign-in, no analytics, and no third-party script.
What ships today
@opum-ai/quest 0.14.1 is published under the MIT licence, shipped in lockstep with @opum-ai/lore 0.14.1 under Opum’s constitution Article 3, which pairs the two at one version number going forward. Run in a scratch Git repository on 2026-10-20: a task is created and Git-tracked, a dependency declared when it is created keeps it out of the ready set until the blocker completes, so readiness is derived rather than asserted, and starting a task really moves it to claimed. Acceptance criteria and a definition of done can be recorded and checked off, the files a task touched can be recorded against it, and a completed task carries its final summary as evidence.
The command that produced this page’s own claims, and the only command this page shows:
npx @opum-ai/quest manifest --jsonNothing else here is a copyable control — this site ships no JavaScript, so the text above is the only affordance there is. The source is the honest place to judge progress beyond it, and release notes record what changed release by release.
Quest is one of three
Lore
Knows why. The organizational knowledge layer: decisions, constraints, and the reasoning behind them.
loregraph.devQuest
Does. Tasks, dependencies, readiness, claims, gates, and the evidence that closed them.
questgraph.devOpum
The platform planned above them, for teams that want the same records shared and governed. Nothing hosted exists today.
opum.aiThe project
- Report a problem
- Open an issue on the repository. There is no separate security contact yet; say so in the issue if a report is sensitive.
- Licence
- MIT
- Release
- quest-cli v0.14.1 tag on GitHub, the annotated tag the published pair was cut from — the changelog entry for it is distilled on the release notes page.
- Not linked here
- The project documentation is not public. This site links only to destinations that resolve for a visitor who is not signed in.