ARIAgent Readiness Index
20 September 2026
Static repository assessment

native-go

native-go meets every static readiness gate with every counted check at ten. Execution, agent task success, and production delivery remain unverified.

100of 100
Static readiness
L4Strong foundation

All static readiness gates pass; execution, agent task success, and production delivery remain unverified.

0204050608090100
  1. L1DiscoverableStatic evidence identifies the repository's setup, test, and usage entry points; those commands were not executed.
  2. L2ControlledStatic evidence shows pull-request guardrails, secret hygiene, and usable agent guidance are present.
  3. L3PreparedThe repository has stronger static preconditions for supervised, bounded coding-agent changes.
  4. 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.
FOUNDATIONS100

Engineering foundations

Reproducibility, verification, structure, and repository knowledge.

4/4 dimensions scored
CHANGE_SAFETY100

Change safety

Controls that help a change remain reviewable, testable, and bounded.

4/4 dimensions scored
AGENT_OPERABILITY100

Agent operability

Static preconditions for supervised coding-agent work.

4/4 dimensions scored
100%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. service (operator supplied confidence). Portfolio manifest classification; verify with the repository owner.

Knowledge inventory (presence only). Agent guidance: AGENTS.md, CLAUDE.md. Planning: none found. Documentation: 2 files. Missing PLAN.md is not a failed control; file presence does not establish quality or freshness.

Structure diagnostic. Parsed 1 Go source files across 1 packages; 0 internal import edges and 0 cycles. Naming: not_assessed (0 rule violations). This is not part of the score.

Decision boundary. Use as a portfolio preflight and remediation baseline, not as proof of autonomous delivery.

Evidence dimensionsRisk-weighted static signals. Bar length is score; the small figure is weight.
Reproducibility
1010
Verification
1010
Delivery controls
107.5
Security boundaries
107.5
Changeability
107.5
Agent guidance
105
System knowledge
102.5
Work definition
102.5
Agent controls
102.5

pass partial fail experimental, not counted not applicable

DiagnosticsExperimental checks. Computed and shown; not counted.
CI-06Git hooks manager configured0No git hooks manager.
CI-07Lint or format enforced in CI10CI runs a linter or a formatter check.
DOCS-03Architecture decisions written down10ARCHITECTURE.md or ADRs exist.
DOCS-04CONTRIBUTING present0No CONTRIBUTING file.
ENV-05Runtime version pinned10A runtime version file or manifest constraint pins the toolchain.
GIT-02PR template asks for verification0No PR template.
GIT-03CODEOWNERS present0No CODEOWNERS.
INSTR-07No directory-tree dumps in instruction files10Instruction files are prose and commands, not tree dumps.
SAFE-04Destructive commands guarded10Deny/ask rules or a PreToolUse hook guard destructive shell commands.
SAFE-05Sandbox configured10Agent sandboxing is enabled in committed settings.
STRUCT-08No large binaries in the tree10No tracked files over 5 MiB outside asset directories.
TOOL-02Auto-format or lint hook10A PostToolUse (or afterFileEdit) hook formats or lints edited files.
TOOL-03Verification hook10A Stop hook runs tests or type checks before the agent yields.
Passed
21 checks at ten
CI-01CI runs tests on pull requestsCI runs a recognised test command on pull requests or pushes.
CI-02Linter configured for the primary languageA linter is configured for the primary language.
CI-03Formatter configuredA formatter is configured (or ships with the toolchain).
CI-04Type checking configuredStrict type checking (or a statically typed toolchain).
DOCS-01README covers setup, usage, and testingREADME has at least two of setup/usage/test sections and a fenced command.
ENV-01Every manifest has a tracked lockfile1 of 1
ENV-02One-command setupAn explicit setup entry point exists (make/just target, scripts/setup, devcontainer command, nix).
ENV-03Container or devcontainer definitionA devcontainer definition exists; cloud agents and CI share one environment.
ENV-04Agent cloud setup file present and validAt least one agent setup file is present and structurally valid.
GIT-01Issue templates require reproduction and expected behaviourIssue forms require reproduction and expected/actual fields.
INSTR-01Cross-tool instruction file presentAGENTS.md is present; read by 20+ agents.
INSTR-02Claude and AGENTS.md instructions do not divergeCLAUDE.md imports or links to AGENTS.md, so the two instruction surfaces cannot silently diverge.
INSTR-03Instruction files within vendor size bandsAlways-on instruction content is under 200 lines and 32 KiB.
INSTR-04Instruction files state build, test, and lint commands3 of 3
INSTR-05Referenced paths exist2 of 2
SAFE-01No committed secretsNo high-confidence secret patterns and no tracked .env with values.
SAFE-02Secrets excluded from agent readsClaude Code deny rules plus an ignore file keep .env out of agent reads.
STRUCT-02Repository size tiervalue 2 (median anchor 500, good anchor 100); anchors uncalibrated
TOOL-01Committed agent settings are valid1 of 1
VERIFY-01Test framework configured with test filesA test framework is configured and test files exist.
VERIFY-02One documented test commandA test command exists and is written down where an agent reads first.
Not applicable
10 checks did not apply or had no data
DOCS-02API contracts in the repositorynot applicable to this repository
GIT-04Historical change size is smalldata not available:
GIT-05Repository is maintaineddata not available: not a git repository
GIT-06Conventional commit messagesdata not available:
INSTR-10Local-only agent files are untrackeddata not available:
STRUCT-01Share of source files over 1,000 linesnot applicable to this repository
TOOL-04MCP configuration valid and scopednot applicable to this repository
TOOL-05Skills and subagents well-formednot applicable to this repository
TOOL-07Build artefacts ignorednot applicable to this repository
VERIFY-03Test-to-source file rationot 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:869de335e29bb514cfb0b89e223fa20830369926ca4921338ee20207ff9da4a7
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.