google/gson

Can another program use it through a documented, machine-readable surface?

• next: L1 A programmatic surface exists (routes, a CLI or a library). (no service, CLI, library or frontend detected)

none ladder · level 0

• ✗ L1 A programmatic surface exists (routes, a CLI or a library). no service, CLI, library or frontend detected

Can integrators rely on it not changing under them?

Can others react to state changes without polling?

Can a machine act with its own revocable, least-privilege identity?

Can its data get in and out, in bulk, in open formats, with an explicit schema?

Can an automated caller use it without guessing, and recover from failure?

Can another system run and compose it without a human?

Can behaviour be added without modifying the code?

• next: L1 Internal seams: a registry, registration function or plugin manager. (no registry or registration function)

all ladder · level 0

• ✗ L1 Internal seams: a registry, registration function or plugin manager. no registry or registration function
• ✗ L2 The docs show how to add behaviour through those seams (even in-tree). no registration functions to document
• ✗ L3 Out-of-tree extensions are discovered (entry points, a plugin directory, configuration) without editing the package. extensions must be added inside the package
• ✗ L4 The extension API is versioned, has lifecycle hooks, and has example extensions. the extension API isn't versioned

Can an operator, or an orchestrating agent, tell whether it works and why not?

Can an agent change it safely with limited context?

• next: L2 CI runs the tests; applications pin dependencies (libraries and zero-dependency projects are exempt). (no lockfile (applications should pin dependencies))

all ladder · level 1

• ✓ L1 A README and some tests. README.mdextras/src/test/java/com/google/gson/interceptors/InterceptorTest.java 142 test files
• ✗ L2 CI runs the tests; applications pin dependencies (libraries and zero-dependency projects are exempt). no lockfile (applications should pin dependencies)
• ✗ L3 At least 90% of modules fit 32k tokens and no file exceeds 12k; test/source token ratio at least 0.3; at least 70% of the code is typed. 89% of modules fit 32k tokens; 3 files over 12k
• ✗ L4 No import cycles, and agent docs (AGENTS.md, CLAUDE.md, llms.txt). no agent docs (AGENTS.md, CLAUDE.md, llms.txt)