Inputs
The systems and standard your team chooses
- Runbook, source material, and definition of done
- Records from Confluence, GitHub, Box
Documentation
Specs & datasheets in sync
What it does
- Keeps datasheets and design specs in sync with the latest silicon
- Flags every spec line that a design change invalidates
- Drafts the revised section with tracked changes
How it works
- 1Watches the spec repo and design database for diffs
- 2Maps changes to affected document sections
- 3Opens a redline for review
Works with
Deployment contract
What goes in, what comes out, and where people review.
Outputs
A finished artifact with its work attached
- Keeps datasheets and design specs in sync with the latest silicon
- Flags every spec line that a design change invalidates
Approvals
Human control at the steps that matter
Choose which steps run automatically and which stop for a named reviewer before deployment.
Evals
Quality measured against your rubric
Score completed runs against accepted examples and task-specific criteria. Review failures with the source trace before changing the runbook or model.
Example result
The result is reviewable, not a black box.
A completed run keeps the task, sources, actions, approvals, and eval result together. Open any step to inspect what happened or send it back with a correction.
RUN
Documentation
- Watches the spec repo and design database for diffsSource trace saved
- Maps changes to affected document sectionsSource trace saved
- Opens a redline for reviewOutput prepared
Rubric score, sources, and action log travel with the result
Related agents
Deploy in days, not months.
Request demo