agent readinessPerformance evidence · portfolio assessment
Executive portfolio · task evidence and codebase friction

Illustrative engineering portfolio

See where agent performance has been reported, where it remains unknown, and which codebase constraints need attention. Open a repository for task-level evidence and the supporting engineering baseline.

Decision boundaryStatic readiness is a prioritisation index. Portfolio zones identify candidates for separately evaluated tasks, not autonomous delivery. Task trials are separate; locally run trials are not sandboxed and verifier strength must be reviewed.
4repositories assessed
1critical systems
1capped by a critical finding
0repositories with qualifying reported performance
01 · Agent performance

Proof before rollout

No estate-wide success average: repositories have different tasks and configurations. Illustrative, stale and local-command data do not count as verified performance.

RepositoryEvidence statusTasks / runsVerified completion
payments-corenot measured0 / 0Not established
customer-platformnot measured0 / 0Not established
policy-apinot measured0 / 0Not established
docs-sitenot measured0 / 0Not established
02 · Supporting static evidence

Where attention goes first

Priority combines criticality, static-score gap, production status, and critical caps. This index helps order remediation priorities; it does not predict outages or rank team performance.

Repository / systemBusiness contextStatic scoreEvidence / executionNext decisionPriority index
payments-corePayments platform · Payments teamcritical · production
service · high
30/100 · L130100%
stable-check coverage · execution not run
foundation first
cap: SAFE-01
400
customer-platformCustomer experience · Experience teamhigh · production
service
84/100 · L284100%
stable-check coverage · execution not run
task-trial candidate68
policy-apiPolicy services · Core platformhigh · production
service
100/100 · L4100100%
stable-check coverage · execution not run
task-trial candidate20
docs-siteDeveloper documentation · Developer experiencelow
documentation
24/100 · L024100%
stable-check coverage · execution not run
profile reviewNot ranked

Not ranked under the current code-centric rubric: docs-site (low, documentation). Review applicability before using their scores for decisions.

02 · Repeated constraints

Systemic fixes

  • ENV-03 appears in 2 repositories: customer-platform, payments-core
  • ENV-04 appears in 2 repositories: customer-platform, payments-core
  • GIT-01 appears in 2 repositories: customer-platform, payments-core
  • SAFE-02 appears in 2 repositories: customer-platform, payments-core
03 · Agent-task evidence

Trials stay separate

No empirical agent-task trials were supplied. Candidate zones do not establish task success.

04 · Critical risk register

What needs an owner

  • critical · payments-core: Static score capped by SAFE-01. Review the cited finding and remediate before a task trial.
  • high · payments-core: Production system with weak static controls. Validate release and rollback controls, then address top repository findings.
05 · Suggested sequence

90-day improvement plan

Days 0–30 · Close critical risks and evidence gaps

  • payments-core: Review the cited finding and remediate before a task trial.
  • payments-core: Validate release and rollback controls, then address top repository findings.

Days 31–60 · Remove recurring constraints

  • Address ENV-03 across 2 repositories, then rerun the same standard.
  • Address ENV-04 across 2 repositories, then rerun the same standard.
  • Address GIT-01 across 2 repositories, then rerun the same standard.
  • Address SAFE-02 across 2 repositories, then rerun the same standard.

Days 61–90 · Prove movement and bound agent use

  • Reassess with the same rubric and separate rubric effects from repository effects.
  • Run named, bounded agent-task trials only for agreed candidates.
  • Review deployment and operational evidence before any production-readiness claim.

A system owner should validate effort, dependencies, and sequencing before committing dates.

Method and limits

Priority index: criticality weight (critical 4, high 3, medium 2, low 1) × (100 − static score), plus 20 for production and 100 for a cap. Documentation, archived, monorepo, and unknown profiles are not ranked until their rubric applicability is reviewed. No cross-repository average is reported. Repository profiles may be manually corrected in the manifest. Static structural diagnostics do not change the score. Execution, when separately requested, is not a security sandbox.