Paqad
What is Paqad?
The open-source framework Eliyce builds with and installs in Programme teams. The AI thinks and types; something else has to judge. Here is who does what, what you receive with every change, and what Paqad refuses to claim about itself.
Want to see a change travel it? How it works
Paqad in short
Paqad is an open-source framework, MIT licensed and published on npm since March 2026, that wraps an AI coding assistant in an enforced delivery method. Rules your team agreed load before the AI edits, checkpoints run before every file save on the coding tools with live hooks, the project’s own checks decide, and a separate program reads the record and gives one of three verdicts. Scripts write the record.
Who does what
The AI thinks and types. Scripts record and judge. People decide.
You decide
You type the request, answer when the AI hits a real decision, confirm the specification, decide whether to open the pull request and read the receipt.
The AI thinks and types
It is the worker, never the judge. It never writes its own evidence and never grades its own work.
Paqad records and judges
Checkpoints the AI cannot skip, commands that write the official files, and a separate program that reads the record and speaks the verdict.
Three roles, one road. The same six moments as everywhere on this site.
One change, six moments
The same six moments as everywhere on this site. Paqad is what enforces them.
01
Requested
Your request, in your words, at the top of the record.
02
Agreed
Acceptance criteria with a proof method each, signed off before any code.
03
Built
Inside your rules, loaded on record. Every save checked.
04
Reviewed
By someone who did not write it, with a rollback plan.
05
Checked
Your own build and test commands decide. Gaps are named, not rounded up.
06
Live
After your approval, with the record attached.
At the end of the road, one folder per change.
What you receive with every change
One folder per change, written while the work happened.
What was agreed
The frozen specification: acceptance criteria with a proof method each, invariants a person confirmed, non-goals, who signed and when.
What changed
The plan with its reuse declaration, the rules loaded on record, the witnessed edits, the commits and the merge.
What was tested
Each command with its exit code and duration, the rule-script sweeps, the recorded review with findings and a rollback plan.
What is still open
The verdict and its gate rows: what passed, what failed, and what could not be measured this run.
Six words carry that folder.
Six words carry the record
Three verdicts and three strengths of evidence, the same in the chat, the pull request, the report and Spine.
Safe to merge
Every gate the framework ran passed. It attests the gates, not that the change is beyond all error.
Needs your attention
A gate is blocking. The receipt names it. Resolve before merging.
Inconclusive
A gate could not reach a confident result. “Could not verify” never rounds up to “verified”.
Machine
A script proved it: a file exists with this fingerprint, a command exited 0, these rules matched these files.
Judged
A model assessed it, and the row says so. It never borrows the credibility of a machine result.
Not measured
The measure could not be taken this run, and the record says why.
And three things Paqad will not say about itself.
What Paqad does not prove
Honest about its limits, in its own words
A passing gate attests the gate, not that the code is correct or secure. Loaded rules were loaded and acknowledged, not necessarily understood. A judged row is a model’s assessment and is labelled as one. A measure that could not be taken reads not measured, never passed. The receipt is hash-chained and tamper-evident; it is not a cryptographic signature, and we do not call it one.
Open foundations
Paqad is free and public. Read how it works before you talk to us, and use it without us. The AI Delivery Programme adds guided adoption, team alignment and engineering support.
Key facts
Paqad in four numbers
2026
on npm since March, MIT licensed, built with itself since
npm registry, package created 18 March 2026
9
real change records in Paqad’s own ledger, each with the same fixed set of files
paqad-ai ledger, read 17 September 2026
54
decisions the AI could not take alone, each recorded with the options, the choice and the reason
paqad-ai repository, counted 17 September 2026
17
files in the evidence bundle of one change, written by scripts rather than by the AI
Change #557, 12 September 2026
Our services
Three ways we make AI work you can check.
Questions
What people ask about Paqad
An open-source framework that wraps an AI coding assistant in an enforced delivery method: rules loaded before the AI edits, checkpoints before every save, the project’s own checks deciding, and a separate program reading the record to give a verdict. Eliyce maintains it and builds with it.
Yes. The framework is MIT licensed and published on npm as paqad-ai since March 2026. You can read it and use it without Eliyce; the AI Delivery Programme adds guided adoption inside your team, on your real backlog.
Full enforcement runs on Claude Code and Codex CLI, where the checkpoints can block an edit. Gemini CLI records the evidence at the end of a turn without blocking. Other supported coding tools use an advisory instruction contract without executed host hooks: the record depends on the agent following the workflow, and no host hook blocks an edit. Current as of paqad-ai 1.90.0.
Paqad itself does not send your code anywhere. The record is written on the developer’s machine and stays there until your team chooses to share it, for example into Paqad Spine, which you host. Two optional features contact outside services only when you turn them on: the dependency vulnerability check sends package names and versions to the OSV database, and the optional retrieval reranker sends text to a provider you configure with your own key. Your AI coding tool’s own data handling is separate from Paqad.
Paqad is the framework on each developer’s machine that enforces the method and writes the record. Spine is the team view that collects those records so a lead can see the week; it runs in your environment and comes with the AI Delivery Programme.
Last reviewed 13 October 2026 by Eliyce.
See Paqad on your own backlog.
The framework is free. The programme installs it in your team, on your real work, in five weeks.
We reply within one working day. Or write to hello@eliyce.com.