The three moving parts
A bounded task with rules an agent must follow. A file format with no field for source code. And a way of deciding that two analyses are talking about the same component, which is the part that is genuinely hard.
- Protocol Scan job A scan job is a bounded, expiring task with explicit rules: read-only, nothing executed, no secrets, relative paths only, repository text treated as data rather than as instructions, and a network rule that differs between connecting an agent and working by hand. What is an agent actually allowed to do during a 1ADK analysis?
- Protocol Evidence Package One JSON file describing a system: entities, structure, relations, interfaces, data, claims, evidence, unknowns and coverage. What each section is for, and what the format deliberately has no field for. What is an Evidence Package?
- Protocol Snapshots and change Identity is the hard problem behind any tool that tracks architecture over time. How components are recognised across analyses, why coverage decides what may be reported as removed, and what a semantic difference is. How do you tell that two analyses describe the same component?
Why any of this is public
Because the alternative is asking people to take it on faith. A product whose central claim is "we do not need access to your code" should be able to explain what it does need, in enough detail that somebody technical can decide whether the claim holds.
The three pages above are the parts that matter for that judgement: what an agent is instructed to do, what the file it produces can and cannot contain, and how two of those files are compared. Between them they answer the question a sceptical engineer actually has, which is not "what does it do" but "where could this go wrong?"
What is not published
- The full schema. Publishing it in machine-readable form is a separate product decision that has not been taken, and this section does not pre-empt it.
- Server-side internals. Storage layout, queueing, locking and validation implementation. Nothing here is a secret worth keeping for its own sake, and nothing here helps a reader judge the boundary.
- Anything that would help somebody attack a customer's project. The security page states the boundary and its limits; it does not hand over a map of where to push.
The metadata preview shows a complete worked example of a package, field by field, which is the practical version of this section.