What AI can do
Select dependencies, read logs, minimally patch recipes, choose resource profiles and queue the next test.
AI workflow
AI should operate the build, not guess the system state.
First check queue control and log tails. Then build one package at a time, run smoke tests and update recipe status only after evidence exists.
Loop
Minimal AI work cycle for a package.
- 1Check PC server status, queue state and active build.
- 2Start one job through the network queue with a selected resource profile.
- 3Read tail/watch output instead of opening huge logs in the terminal.
- 4After success, import the artifact, run a smoke test and save the result.
- 5After failure, patch only the local test recipe and do not publish it as confirmed.
What AI should not do
Publish broken recipes, invent checksums, overwrite USB drives without confirmation or mix experiments into the public index.