Eridian

Required checks for the code that moves money.

Index the tree. Review the diff. Generate tests. Ask the SHA. GPT, Gemini, or a URL you host. Findings post as CI. Completions stay in the editor.

Start Eridian Dev TrialRead the Dev Docs

dev features

Capability

Code review as a required check

Extract the diff, map affected modules, write path:line comments, and list test gaps. Publish is dual-control. The review object is the merge gate, not a chat transcript dumped on the PR.

Execution trace

Diff extracted180ms
Modules mapped94ms
Findings posted2.1s

Capability

Completions on the indexed SHA

Inline suggestions pull open files, recent commits, and retrieved chunks from the repository index. Completions are inference with a Dev schema. On ZDR they are not stored after the response returns.

Capability

Tests that have to pass

Generate unit and integration cases, score them against the suite, then revise the ones that fail. The job posts as eridian/tests. Coverage delta is a number, not a promise.

Capability

Codebase Q&A with citations

Ask how settle_batch retries, or which desk owns card-auth. Answers cite path, line range, and SHA. Stale SHAs mean the index lagged a push. Q&A does not merge. Review does.

Capability

PR summaries that stay in their lane

Descriptions, changelogs, and release notes from the diff. Do not ask the summarizer to find bugs. Findings belong on the review object. Mixing them is how a high-severity posting bug lands in a changelog.

Capability

Repositories pinned to the desk

Connect GitHub, GitLab, or Bitbucket. Set globs. Pin residency. Completions and Q&A fail if the index is not ready. Engineering source is Customer Data, same as the rest of the control plane.

Capability

CI that fails closed

GitHub Actions, GitLab CI, Jenkins. Require eridian/review and eridian/tests. A 503 from the model fails the check. GPT hops to Gemini only when the project routing policy says so. Skipping is not a path.

What a desk actually runs

Repositories, pull requests, required checks, and review comments. The same objects the CI job posts when a payments change tries to merge.

Indexed repositories

Residency pinned per desk

  • payments-core

    GitHub / eu-west-1 / 8f3a2b1c

    Ready

  • ledger-posting

    GitHub / eu-west-1 / c91e04aa

    Ready

  • card-auth

    GitLab / eu-west-1 / b7d11e90

    Stale

  • openapi-gateway

    GitHub / eu-central-1 / 11ab9c44

    Ready

payments-core #4821

Required checks, then comments

Require dual-control before settle_batch retries

  • eridian/review

    3 findings, 1 high

  • eridian/tests

    41 generated, 2 failing

  • eridian/index

    SHA 8f3a2b1c

src/ledger/posting.ts:214

Retry on settle_batch posts again without an Idempotency-Key. A 504 from the ledger will double-apply fees on the same instruction.

From push to a signed merge record

  1. Connect

    Attach the Git host, set globs, and pin residency to the desk that owns the tree.

  2. Index

    Chunk and embed the tree. Bind completions and Q&A to the SHA the push hook just sent.

  3. Check

    Review and tests run as required checks. A model 503 fails the job. Draft PRs do not publish comments.

  4. Record

    Comments publish under dual-control. The audit event keeps the SHA, route, region, and actor.

The merge gate, measured.

Review is a check. Tests are a check. Index freshness is a check. A 503 fails the job. Nothing skips.

  • 0

    INDEXED REPOSITORIES

  • 0.0s

    P95 REVIEW LATENCY

  • 0

    REQUIRED-CHECK POLICIES

  • 0

    GIT HOSTS CONNECTED

Put the merge gate on the same control plane as the rest of the bank.

Start Eridian Dev TrialRead the Dev Docs