00 · How it works
Aideps is the layer around your agents.
Aideps doesn’t write code. Your agents do — Claude Code, Cursor, Codex, Devin, custom harnesses. Aideps gives every one of them the same company-shaped context, memory, and execution controls so they can do real work without humans re-explaining everything.
01 · Capture
Slack · GitHub · docs · tickets — wherever the work lives.
Right-click any Slack thread → Create Aideps Packet. The compiler reads the thread, follows references to Linear tickets and GitHub PRs, and pulls related Notion pages and prior packets. The raw company context becomes the packet’s source field.
02 · Compile
One Work Packet. Ten fields. Same shape across every agent.
A Work Packet carries the task, source context, constraints (cited from prior packets), decisions, acceptance criteria, relevant memory, approval gates, run logs, linked PRs, and the final outcome — in a stable shape every supported agent knows how to read.
03 · Run
One CLI. Every agent.
npm install -g @aideps/cli aideps init <your-token> # one shot; non-interactive aideps packet pull PKT-3F2A1 # drop the packet into the repo
Your agent reads the packet file before anything else. No per-agent prompt engineering, no context window juggling. Same packet works in Claude Code, Cursor, Codex, Devin, or whatever your team is running.
04 · Check
The PR is linked. Acceptance criteria become a check.
When the agent opens a PR, our GitHub App posts a Packet Validation check that tracks acceptance criteria coverage line-by-line. The PR, the branch, the diff, and the run log are all back-linked to the originating packet.
05 · Gate
Risky paths require human approval.
Default-on gates on packets touching billing/, auth/, schema migrations, or infra config. Reviewers approve in-app or via Slack interactive button. Agents never auto-merge.
06 · Compound
Merged work becomes company memory.
When a packet ships, the harvester extracts durable rules — “auth changes need an audit_log entry,” “rate limits live in middleware/rateLimit.ts” — with citations back to the packet that produced them. Every future packet sees those rules in its constraints section. No human updates the rules.
07 · Replay
Hash-chained execution trace.
Every packet, run, gate, approval, and harvested rule is hash-chained together. Pull up any shipped feature six months later and replay the decisions that produced it — what was rejected, what constraints applied, who approved.