Split execution
The core idea behind ajq — keep jq deterministic, call a model only for fuzzy operators.
Explanation
How ajq works and why it’s designed this way.
Design notes for ajq’s execution model, reproducibility guarantees, and architecture.
- Split execution — the core idea: keep jq deterministic, call a model only for the fuzzy operators.
- The determinism contract — what “byte-reproducible” guarantees, and what it deliberately doesn’t.
- The three-phase executor — harvest, resolve, execute, and why deduplication is free.
- Architecture — the components and how data flows between them.
- Project status — the shipped capabilities and how the pieces fit together.
The determinism contract
What ajq’s byte-reproducibility guarantees, and what it deliberately doesn’t.
The three-phase executor
Harvest, resolve, execute — and why deduplication comes for free.
Architecture
The components of ajq and how data flows between them.
Project status
The capabilities that ship today, and how they fit together.
Iterative-harvest prototype evaluation
Reproducible evidence and the no-go decision for the non-default iterative-harvest prototype.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.