Or start from a section
- Guides Twenty-three guides that help you finish a task rather than read about one: handing a system over, reducing supplier dependency, understanding a legacy or AI-built codebase, and knowing what to ask.
- Solutions Eight situations in which an owner suddenly needs to know what their software actually contains: a developer leaving, a handover, changing agency, vendor dependency, a legacy system, a new CTO, AI-built software, and running a product you cannot read.
- Tools Nine free diagnostics for software owners: handover readiness, developer and agency dependency, a new CTO plan, a founder knowledge check, a handover checklist, a delay calculator, a metadata preview and an honest solution selector. No account, no email.
- Articles Long-form pieces on what it costs to not understand your own system, and on the AI agents now acting inside it: permissions, the radius of one mistake, chains of automated steps, and where a model actually runs.
- Product The seven things a 1ADK project contains, each explained on its own page with an example: the system map, the component registry, the integrations map, evidence, unknowns, change history and technical memory.
- Protocol The three moving parts published in public: the scan job and its safety rules, the Evidence Package format, and how two snapshots are compared. Enough to judge whether this is engineering or a prompt with a logo.
- Compare See how 1ADK helps owners understand their software, check technical findings, and review changes. Compare it with IcePanel, Miro and other architecture tools.