FOUNDATIONS8
Engineering foundations
Reproducibility, verification, structure, and repository knowledge.
2/4 dimensions scoredARIAgent Readiness Index
20 September 2026
Static repository assessment
docs-only
docs-only has not yet earned a static evidence level on static evidence. 1 check stands between it and Discoverable; the three priorities below are worth 52 points together.
24of 100
Static readiness
L0Unscored
No static readiness level earned yet. The repository does not expose enough documented evidence for a stronger conclusion.
- L1DiscoverableStatic evidence identifies the repository's setup, test, and usage entry points; those commands were not executed.
- L2ControlledStatic evidence shows pull-request guardrails, secret hygiene, and usable agent guidance are present.
- L3PreparedThe repository has stronger static preconditions for supervised, bounded coding-agent changes.
- L4Strong foundationAll static readiness gates pass; execution, agent task success, and production delivery remain unverified.
Decision viewThree overlapping, uncapped lenses over the same static evidence. They help prioritise remediation; they do not predict task success.
CHANGE_SAFETY43
Change safety
Controls that help a change remain reviewable, testable, and bounded.
3/4 dimensions scoredAGENT_OPERABILITY33
Agent operability
Static preconditions for supervised coding-agent work.
3/4 dimensions scored100%evidence coverage
7 stable checks scored · 16 not applicable · 0 unavailable. Coverage reports what could be resolved, not how healthy the repository is.
ObservedRepository evidence
Files, configuration, and available git history.
Not runCommand execution
Setup, build, tests, lint, and type checks.
Not runAgent task evaluation
Real changes graded with hidden tests and constraints.
Not assessedProduction delivery
Deploy, rollback, reliability, and operational controls.
Repository profile. documentation (operator supplied confidence). Portfolio manifest classification; verify with the repository owner.
Knowledge inventory (presence only). Agent guidance: none found. Planning: none found. Documentation: 2 files. Missing PLAN.md is not a failed control; file presence does not establish quality or freshness.
Structure diagnostic. Language-aware dependency analysis not available for this repository; no semantic coupling or naming claim is made.
Decision boundary. Use as a portfolio preflight and remediation baseline, not as proof of autonomous delivery.
Where to start
Add a workflow that runs the test command on pull_request and push.
Add `make setup` (or the ecosystem equivalent) that works from a clean clone, and name it in AGENTS.md.
Add .devcontainer/devcontainer.json with postCreateCommand running your setup command.
Next level L1 Discoverable. Static evidence identifies the repository's setup, test, and usage entry points; those commands were not executed. Requires ENV-02 >= 5 (is 0).
Evidence dimensionsRisk-weighted static signals. Bar length is score; the small figure is weight.
| Reproducibility | 0 | 10 | ||
|---|---|---|---|---|
| Verification | no conclusive checks | n/a | 10 | |
| Delivery controls | 0 | 7.5 | ||
| Security boundaries | 10 | 7.5 | ||
| Changeability | no conclusive checks | n/a | 7.5 | |
| Agent guidance | 0 | 5 | ||
| System knowledge | 4 | 2.5 | ||
| Work definition | 0 | 2.5 | ||
| Agent controls | no conclusive checks | n/a | 2.5 |
pass partial fail experimental, not counted not applicable
OpportunitiesEvery counted check below ten, in order of what it is worth. Points are the change to the score if the check reached ten.
01
CI runs tests on pull requests
+22CI-01·0 of 10·No CI configuration found.
Add a workflow that runs the test command on pull_request and push.
Why it matters DORA's AI capabilities model names strong version control and fast feedback as the amplifiers of AI gains; without CI an agent's PR is unverified. [1]
02
One-command setup
+15ENV-02·0 of 10·No way to set up the project without a person.
Add `make setup` (or the ecosystem equivalent) that works from a clean clone, and name it in AGENTS.md.
Why it matters Every agent vendor's guidance opens with "install, run, test commands"; Codex's own docs say many quality issues are really setup issues. [1][2]
03
Container or devcontainer definition
+15ENV-03·0 of 10·No container definition.
Add .devcontainer/devcontainer.json with postCreateCommand running your setup command.
Why it matters Devcontainers are what Copilot, Cursor cloud, and Claude Code cloud consume; EnvBench shows agents build under 30% of environments without one. [1][2]
04
Cross-tool instruction file present
+15INSTR-01·0 of 10·No agent instruction file.
Add a root AGENTS.md with commands, layout, conventions, and completion criteria. Bridge CLAUDE.md to it (INSTR-02).
Why it matters Two controlled studies found instruction files do not change pass rates, which is why this dimension is Medium; they do change cost and every vendor reads them. [1][2][3]
05
Issue templates require reproduction and expected behaviour
+7GIT-01·0 of 10·No issue templates.
Convert the bug template to a form with required Steps to reproduce, Expected, Actual, and Version fields.
Why it matters Underspecified issues were 38% of the flaws in the original SWE-bench; human-written requirements tripled agent success in a controlled study. [1][2]
06
README covers setup, usage, and testing
+5DOCS-01·4 of 10·README exists but lacks operational sections or commands.
Add Getting started, Usage, and Development sections with one command each.
- README.md
Why it matters Copilot's coding agent reads the README before coding; documentation reduces API hallucination when it is specific. [1][2]
DiagnosticsExperimental checks. Computed and shown; not counted.
| CI-06 | Git hooks manager configured | 0 | No git hooks manager. |
| DOCS-03 | Architecture decisions written down | 0 | No architecture document or decision records. |
| DOCS-04 | CONTRIBUTING present | 0 | No CONTRIBUTING file. |
| ENV-05 | Runtime version pinned | 0 | No runtime version pin (.nvmrc, .python-version, .tool-versions, rust-toolchain, go directive, engines). |
| GIT-02 | PR template asks for verification | 0 | No PR template. |
| GIT-03 | CODEOWNERS present | 0 | No CODEOWNERS. |
| STRUCT-08 | No large binaries in the tree | 10 | No tracked files over 5 MiB outside asset directories. |
Passed
1 checks at ten
| SAFE-01 | No committed secrets | No high-confidence secret patterns and no tracked .env with values. |
Not applicable
30 checks did not apply or had no data
| CI-02 | Linter configured for the primary language | not applicable to this repository |
| CI-03 | Formatter configured | not applicable to this repository |
| CI-04 | Type checking configured | not applicable to this repository |
| CI-07 | Lint or format enforced in CI | not applicable to this repository |
| DOCS-02 | API contracts in the repository | not applicable to this repository |
| ENV-01 | Every manifest has a tracked lockfile | not applicable to this repository |
| ENV-04 | Agent cloud setup file present and valid | not applicable to this repository |
| GIT-04 | Historical change size is small | data not available: |
| GIT-05 | Repository is maintained | data not available: not a git repository |
| GIT-06 | Conventional commit messages | data not available: |
| INSTR-02 | Claude and AGENTS.md instructions do not diverge | not applicable to this repository |
| INSTR-03 | Instruction files within vendor size bands | not applicable to this repository |
| INSTR-04 | Instruction files state build, test, and lint commands | not applicable to this repository |
| INSTR-05 | Referenced paths exist | not applicable to this repository |
| INSTR-07 | No directory-tree dumps in instruction files | not applicable to this repository |
| INSTR-10 | Local-only agent files are untracked | data not available: |
| SAFE-02 | Secrets excluded from agent reads | not applicable to this repository |
| SAFE-04 | Destructive commands guarded | not applicable to this repository |
| SAFE-05 | Sandbox configured | not applicable to this repository |
| STRUCT-01 | Share of source files over 1,000 lines | not applicable to this repository |
| STRUCT-02 | Repository size tier | not applicable to this repository |
| TOOL-01 | Committed agent settings are valid | not applicable to this repository |
| TOOL-02 | Auto-format or lint hook | not applicable to this repository |
| TOOL-03 | Verification hook | not applicable to this repository |
| TOOL-04 | MCP configuration valid and scoped | not applicable to this repository |
| TOOL-05 | Skills and subagents well-formed | not applicable to this repository |
| TOOL-07 | Build artefacts ignored | not applicable to this repository |
| VERIFY-01 | Test framework configured with test files | not applicable to this repository |
| VERIFY-02 | One documented test command | not applicable to this repository |
| VERIFY-03 | Test-to-source file ratio | not applicable to this repository |
Method
- Score
- The risk-weighted mean of nine static repository dimensions, 0 to 100. It is a prioritisation index, not a probability that an agent will succeed.
- Level
- An evidence band earned only when every static check in its gate passes. It describes repository preconditions. It does not certify command execution, autonomous task completion, merging, or production delivery.
- Coverage
- The share of stable checks resolved from available evidence. Not-applicable checks are resolved; unavailable or errored checks reduce coverage. Coverage is shown separately so missing evidence cannot hide behind the score.
- Points
- What the score becomes if one check is fixed and nothing else changes. The opportunities are already in that order.
- Determinism
- No model judgment anywhere. Two runs with the same inputs hash saw the same repository.
inputs sha256:d3949061beb0dae00275e13a18f9f7ee0f2c2edf6f8edaa4fcd0ba2d03028cad
rubric sha256:add0515531acf415c6a9dd5e7f9e1e7585f47c682087c8055ed58c3fabe3990f - Not in static score
- Command execution, coding-agent task success, semantic coupling, naming quality, deployment, rollback, reliability, and production operations. Any execution or language-aware diagnostic above is reported separately and cannot change this score.
- Benchmark
- A percentile against a validated corpus is not yet published. This report shows none rather than inventing one.