Short answer
#Small units of work
The server keeps a plan for each analysis and hands out one unit of work at a time. A unit is a structured question with a fixed shape for its answer: first the outline of the system, then its components, interfaces, data stores and the operations that matter, then the questions an earlier analysis left open. The coding agent never receives free-form instructions from the server, only units of a kind the published contract describes.
Small units are what make the analysis survivable. A coding agent session can end at any moment, for reasons that have nothing to do with 1ADK. When the work is a sequence of small answered questions, an ended session loses at most the unit it was holding.
#Checked twice, before and after the network
-
On the machine, before anything is sent
1adk-agent checks each answer against the same contract the server uses, and runs a privacy guard over it. An answer that fails is returned to the coding agent with the reason, so it can be corrected. An answer that fails the privacy guard is never sent, in any form.
The contract is published in the open, with a version and a hash, and both sides execute it.
-
On the server, before anything is kept
The server checks the answer again, independently, because a check on somebody else machine is not a check the server can rely on. Accepted answers are kept as a draft that the project does not see yet.
Nothing changes in the project while the analysis is still running.
-
When every unit is answered
The draft is assembled into one result and validated as a whole. A connected analysis then goes into the project by itself. A result that cannot be assembled is not written in, and the analysis page says what to do next.
An absence is only recorded where the analysis actually looked, and two answers that contradict each other are kept as a contradiction rather than resolved by guessing.
#What is sent
What reaches 1ADK is a structured description: names of components and interfaces, what they connect to, where data is kept, the operations that matter, references to where each fact was found, and what could not be established. It is not the source files.
The boundary
1ADK does not require repository access and does not require uploading source code to us. The coding agent itself reads the repository under the terms of whoever provides it, which is a separate relationship that 1ADK is not part of.
#Stopping and resuming
Close the coding agent, lose the network, shut the laptop: the unit that was being worked on is handed out again when the machine comes back, and the units already answered stay answered. To carry on, open the coding agent in the same folder and say the phrase again.
The cabinet shows whether the machine is connected and what it is doing, so an analysis that has gone quiet is visible as quiet, with the step that would start it again.
#A commit in the middle
An analysis describes one revision of the code. If the repository moves while an analysis is running, half the answers would describe one revision and half another, so the analysis stops and waits for you rather than mixing them. The analysis page says so and offers to continue against the revision the repository is on now.
#Finishing, early or on time
An analysis finishes when every unit is answered. It can also be finished early from the analysis page: the units already answered are kept and the rest are skipped, and the result says how much it covered.
The next pass starts from the project page with «Carry on learning». It asks the same connected machine for new work, starting from what the project already knows and from the questions that are still open. The person at the machine opens the coding agent and says the phrase, because 1ADK cannot start a coding agent remotely.
#When something is not working
| What you see | What to do |
|---|---|
| The coding agent does not know the 1ADK tools. | Restart the coding agent in the connected folder. It loads tool servers when it starts, so one registered while it was open is not visible to it yet. |
| The connect line says the code is not valid. | A pairing code works once and expires within minutes. Open the connection page again for a new one. |
| The cabinet says the machine is behind. | Run the install line again. It replaces the program with the current release after checking its checksum. |
| The analysis is waiting for you. | Usually the repository moved while it ran. Open the analysis page and continue from the card at the top. |
| The result has not gone into the project. | On the free plan, two accepted analyses is the limit. The result waits, and the project stays readable. The plan page says what is open to you. |