FOUNDATIONS83
Engineering foundations
Reproducibility, verification, structure, and repository knowledge.
4/4 dimensions scoredARIAgent Readiness Index
20 September 2026
Static repository assessment
ready-ts
ready-ts is Controlled on static evidence. 2 checks stand between it and Prepared; the three priorities below are worth 12 points together.
84of 100
Static readiness
L2Controlled
Static evidence shows pull-request guardrails, secret hygiene, and usable agent guidance are present.
- 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_SAFETY87
Change safety
Controls that help a change remain reviewable, testable, and bounded.
4/4 dimensions scoredAGENT_OPERABILITY73
Agent operability
Static preconditions for supervised coding-agent work.
3/4 dimensions scored100%evidence coverage
21 stable checks scored · 2 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. unknown (low confidence). Source is present, but no reliable service/library distinction was found. Supply a profile in a portfolio manifest.
Knowledge inventory (presence only). Agent guidance: AGENTS.md, CLAUDE.md. Planning: none found. Documentation: 1 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 .devcontainer/devcontainer.json with postCreateCommand running your setup command.
Add the setup file for the agent you use; the evidence names the exact structural issue when one exists.
Convert the bug template to a form with required Steps to reproduce, Expected, Actual, and Version fields.
Next level L3 Prepared. The repository has stronger static preconditions for supervised, bounded coding-agent changes. Requires ENV-03 >= 5 (is 0); GIT-01 >= 5 (is 0).
Evidence dimensionsRisk-weighted static signals. Bar length is score; the small figure is weight.
| Reproducibility | 5 | 10 | ||
|---|---|---|---|---|
| Verification | 10 | 10 | ||
| Delivery controls | 10 | 7.5 | ||
| Security boundaries | 8.5 | 7.5 | ||
| Changeability | 10 | 7.5 | ||
| Agent guidance | 10 | 5 | ||
| System knowledge | 10 | 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
Container or devcontainer definition
+4ENV-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]
02
Agent cloud setup file present and valid
+4ENV-04·0 of 10·The repository configures an agent but provides no environment setup for it.
Add the setup file for the agent you use; the evidence names the exact structural issue when one exists.
Why it matters Vendor requirement. Copilot silently ignores a mis-named job; Cursor cloud agents need an idempotent install. [1][2]
03
Issue templates require reproduction and expected behaviour
+4GIT-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]
04
Secrets excluded from agent reads
+2SAFE-02·7 of 10·An agent ignore file (or Cursor's default list) excludes .env.
Add to .claude/settings.json: permissions.deny ["Read(./.env)", "Read(./.env.*)"] and a .cursorignore with .env*.
- .gitignore .env ignored
- .cursorignore .env excluded from agent
Why it matters Vendor-documented boundary. Reading a secret into context is one tool call away from writing it somewhere. [1][2]
DiagnosticsExperimental checks. Computed and shown; not counted.
| CI-06 | Git hooks manager configured | 0 | No git hooks manager. |
| CI-07 | Lint or format enforced in CI | 10 | CI runs a linter or a formatter check. |
| 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. |
| INSTR-07 | No directory-tree dumps in instruction files | 10 | Instruction files are prose and commands, not tree dumps. |
| STRUCT-08 | No large binaries in the tree | 10 | No tracked files over 5 MiB outside asset directories. |
| TOOL-07 | Build artefacts ignored | 10 | .gitignore covers the ecosystem's build and dependency directories. |
Passed
17 checks at ten
| CI-01 | CI runs tests on pull requests | CI runs a recognised test command on pull requests or pushes. |
| CI-02 | Linter configured for the primary language | A linter is configured for the primary language. |
| CI-03 | Formatter configured | A formatter is configured (or ships with the toolchain). |
| CI-04 | Type checking configured | Strict type checking (or a statically typed toolchain). |
| DOCS-01 | README covers setup, usage, and testing | README has at least two of setup/usage/test sections and a fenced command. |
| ENV-01 | Every manifest has a tracked lockfile | 1 of 1 |
| ENV-02 | One-command setup | An explicit setup entry point exists (make/just target, scripts/setup, devcontainer command, nix). |
| INSTR-01 | Cross-tool instruction file present | AGENTS.md is present; read by 20+ agents. |
| INSTR-02 | Claude and AGENTS.md instructions do not diverge | CLAUDE.md imports or links to AGENTS.md, so the two instruction surfaces cannot silently diverge. |
| INSTR-03 | Instruction files within vendor size bands | Always-on instruction content is under 200 lines and 32 KiB. |
| INSTR-04 | Instruction files state build, test, and lint commands | 3 of 3 |
| INSTR-05 | Referenced paths exist | 2 of 2 |
| SAFE-01 | No committed secrets | No high-confidence secret patterns and no tracked .env with values. |
| STRUCT-01 | Share of source files over 1,000 lines | value 0 (median anchor 0.02, good anchor 0.002); anchors uncalibrated |
| STRUCT-02 | Repository size tier | value 14 (median anchor 500, good anchor 100); anchors uncalibrated |
| VERIFY-01 | Test framework configured with test files | A test framework is configured and test files exist. |
| VERIFY-02 | One documented test command | A test command exists and is written down where an agent reads first. |
Not applicable
13 checks did not apply or had no data
| DOCS-02 | API contracts in the repository | 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-10 | Local-only agent files are untracked | data not available: |
| SAFE-04 | Destructive commands guarded | not applicable to this repository |
| SAFE-05 | Sandbox configured | 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 |
| 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:abc628618dab45cedbc66f13f2c6725db5fa810b1927daf12df8697b9545360e
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.