Act in the real world
with intent.

agent has read access to the project's structured state stores: application database, infrastructure-as-code state (Terraform/Pulumi/Cloudflare config), and equivalent backends. Scores *capability and usability*; PII masking and IAM scoping are scored under `PL4-least-privilege` / `PL4-pii-masking`

code produces structured, correlated, breadcrumb-style signal. Silent handlers are a bug, not a feature. Correlation identifiers reference production entities via pseudonymous tokens (user-ID, session-ID, request-ID), not PII-derived values (email, phone, name) — logs are an engineering surface, and `PL4-pii-masking` applies

agent can investigate via MCP / API across logs, metrics, traces — not just humans via dashboards

agent has a unified memory tool (markdown + vector DB + structured DB + event log, MCP-exposed) covering decisions, postmortems, customer-context references (pseudonymous; raw PII does not enter the memory substrate), performance baselines

agent works the git platform end-to-end: branches, opens PRs, resolves merge conflicts, tags releases, *and* reads PR history, review comments, commit metadata

skills that let the agent complete real, end-to-end domain flows (e.g. virtual EV chargers and disposable payment cards for charging workflows; test tenants for multi-tenant SaaS; sandbox accounts for integrations). Examples are per-project; what matters is that critical domain flows don't require a human in the loop

agent triggers CI/deploys end-to-end (Fastlane, TestFlight, staging) *and* reads results: test outcomes, build logs, historical run data, coverage and mutation reports

agent can interact with web UIs: navigating dashboards, filling forms, verifying deployed staging visually. Browser actions are **deterministic** (reproducible across runs), **inspectable** (humans can read what the agent will do before it runs), and **version-controlled** (automation artefacts live with code)

agent can notify and present results via external channels: Slack messages, Linear comments, email summaries, docs-portal publishing. Outbound passes through a structural safety layer

beyond individual skills (3.1–3.9), the project's skill library *as a whole* is well-curated: inventoried, documented, tested, versioned, with coverage mapped against the domain surface. Distinct from 5.10 which scores portfolio-level reuse — this scores *this project's* skill infrastructure