docs · setup

From first signalto first governed fix

Aegis sits between the CI you already run and the repository changes a human is willing to authorize. Connect a repo, upload your signals, and close the loop on a selected finding.

  1. 01

    Connect GitHub or GitLab

    Sign in with the account that owns the repositories you want Aegis to observe. You approve the OAuth connection on your provider's own screen and can revoke it there.

  2. 02

    Upload the signals you already produce

    Aegis reads coverage, duplication, dependency, and static-analysis reports from your existing CI. Use the repository-scoped upload token so report ingestion never needs account credentials.

    example — coverage upload from CI
    curl -X POST https://app.aegis.dev/api/coverage/upload \
      -H "Content-Type: application/json" \
      -d '{
        "repository": "your-org/your-repo",
        "token": "$AEGIS_TOKEN",
        "commit": "$CI_COMMIT_SHA",
        "branch": "$CI_COMMIT_BRANCH",
        "buildId": "$CI_JOB_ID",
        "coverage": "'"$(base64 -w0 coverage/lcov.info)"'"
      }'
  3. 03

    Dispatch a targeted fix

    Choose a failing build, low-coverage file, duplicate block, static finding, or AI-triage suggestion. Aegis queues only the action and writable scope needed for that target.

  4. 04

    Let the isolated runner propose

    A Truemark-operated per-client runner claims the work, uses its local source checkout and client-provided credentials, then submits proposed files, a summary, and any evidence. It cannot write to the repository.

  5. 05

    Review the whole decision

    See the proposed diff, evidence origin and completeness, and run cost together. Reject the result or explicitly approve write-back. Current evidence is labeled self-attested, not Aegis-verified.

  6. 06

    Follow the outcome

    After approval, Aegis writes the approved files to the intended branch or opens a PR/MR. Normal provider review still decides the merge; Aegis records the merge and any later revert.

the authority handoff

Runner submits

proposal only

Human approves

authority granted

Aegis writes back

branch or PR/MR

Wiring up more than coverage?

Quality and security analyzers emit runs into one SARIF 2.1.0 document and upload it once through the canonical analysis endpoint. Aegis retains each producer's signal and provenance.

Read the API reference