Alamofire/Alamofire

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

• next: [desktop] L1 Launchable by other programs with input: command-line arguments, a URL scheme or file associations. (no arguments, URL scheme or file associations)

desktop ladder · level 0

• ✗ L1 Launchable by other programs with input: command-line arguments, a URL scheme or file associations. no arguments, URL scheme or file associations
• ✗ L2 An automation interface: AppleScript, App Intents/Shortcuts, D-Bus, COM, IPC commands, or a local API. no automation interface
• ✗ L3 Its functions run without the GUI (a headless/batch mode or a companion CLI). nothing runs without the GUI
• ✗ L4 The automation interface is specified machine-readably (an AppleScript sdef, D-Bus introspection XML, App Intents, an OpenAPI spec, MCP). no machine-readable automation contract

library ladder · level 4

• ✓ L1 An importable, packaged API exists. Package.swift Swift package library
• ✓ L2 The public API is delimited (__all__, an exports map, exported identifiers). Package.swift public access control
• ✓ L3 The public API is statically typed (py.typed, type declarations, a typed language). Package.swift statically typed language
• ✓ L4 An API reference is generated from the code (autodoc, mkdocstrings, typedoc, …). Gemfile 1 match

Can integrators rely on it not changing under them?

all ladder · level 4

• ✓ L1 Releases are versioned (semver tags or versioned changelog sections). 109 semver tags, latest 5.12.2
• ✓ L2 A changelog exists and marks breaking changes. CHANGELOG.md marks breaking changes
• ✓ L3 A deprecation mechanism is used in code (warnings, @deprecated, Deprecation/Sunset headers) or the API is versioned. Source/Features/ServerTrustEvaluation.swift 9 matchesSource/Features/NetworkReachabilityManager.swift 5 matches
• ✓ L4 Across tagged releases, no OpenAPI operation, CLI option or __all__ symbol was removed without first being deprecated. 20 tagged releases compared

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?

• next: [library] L2 Inputs are validated with messages naming the bad argument. (no input validation errors)
• next: [desktop] L1 In headless mode, failures end with a non-zero exit status instead of a dialog. (no headless mode for automated callers)

desktop ladder · level 0

• ✗ L1 In headless mode, failures end with a non-zero exit status instead of a dialog. no headless mode for automated callers
• ✗ L2 In headless mode, data goes to stdout and diagnostics to stderr. no headless mode for automated callers
• ✗ L3 Documented exit statuses distinguish error classes, and headless output is machine-readable (JSON). no headless mode for automated callers
• ✗ L4 Dry-run for side-effecting operations, and agent docs. no headless mode for automated callers

library ladder · level 1

• ✓ L1 Errors are specific exception types, and library code never calls sys.exit. Source/Core/AFError.swift 2 matchesSource/Core/ParameterEncoding.swift 1 match
• ✗ L2 Inputs are validated with messages naming the bad argument. no input validation errors
• ✓ L3 Timeouts and retries are configurable. Source/Features/OfflineRetrier.swift 2 matchesSource/Core/Session.swift 1 match
• ✗ L4 Agent docs, and examples that run as tests (doctests). no agent docs

Can another system run and compose it without a human?

• next: [library] L4 Optional features behind extras/features. (no optional extras)
• next: [desktop] L2 Packaged as an installer (dmg/pkg, MSI/MSIX, AppImage/Flatpak/Snap, electron-builder, Tauri bundle, PyInstaller). (no installer packaging)

desktop ladder · level 1

• ✓ L1 Buildable from source with documented steps (a README with commands). README.md
• ✗ L2 Packaged as an installer (dmg/pkg, MSI/MSIX, AppImage/Flatpak/Snap, electron-builder, Tauri bundle, PyInstaller). no installer packaging
• ✗ L3 Distributed for unattended installation: a package manager (Homebrew cask, winget, Chocolatey, Flathub, Snap) or release artifacts built in CI. no package-manager distribution or CI releases
• ✗ L4 Settings can be managed without the GUI: documented environment variables or config file, macOS defaults/MDM profiles, or Windows policies. settings only change through the GUI

library ladder · level 3

• ✓ L1 Importable from source. Package.swift Swift package library
• ✓ L2 Installable as a package (a package manifest). Package.swift package manifest
• ✓ L3 Published to a public registry, with at most 10 runtime dependencies. Package.swift Swift package released by semver tags 0 runtime dependencies
• ✗ L4 Optional features behind extras/features. no optional extras

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?

• next: [library] L1 Logs through a standard logger namespace and never prints from library code. (no standard logger)
• next: [desktop] L1 Writes logs through a standard logger (os_log/Logger, electron-log, logging, Qt categories). (no standard logging)

desktop ladder · level 0

• ✗ L1 Writes logs through a standard logger (os_log/Logger, electron-log, logging, Qt categories). no standard logging
• ✗ L2 Log verbosity can be raised for diagnosis (--verbose/--debug, a log-level setting). no verbosity control
• ✗ L3 Crashes are reported (Sentry, Crashpad/Breakpad, Crashlytics, MetricKit). no crash reporting
• ✗ L4 Tracing or metrics (OpenTelemetry). no tracing

library ladder · level 0

• ✗ L1 Logs through a standard logger namespace and never prints from library code. no standard logger
• ✗ L2 Log levels are used meaningfully (at least two levels). fewer than two log levels used
• ✗ L3 Optional metrics or tracing hooks. no metrics or tracing hooks
• ✗ L4 OpenTelemetry instrumentation available. no OpenTelemetry instrumentation

Can an agent change it safely with limited context?

• next: 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. (71% of modules fit 32k tokens; 4 files over 12k)

all ladder · level 2

• ✓ L1 A README and some tests. README.mdTests/AFError+AlamofireTests.swift 45 test files
• ✓ L2 CI runs the tests; applications pin dependencies (libraries and zero-dependency projects are exempt). .github/workflows/ci.yml library or zero-dependency project: lockfile not required
• ✗ 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. 71% of modules fit 32k tokens; 4 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)