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

    For the private pilot, your operator helps connect one GitHub or GitLab repository and checks repository access and runner readiness with you. You approve the provider connection 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.

    GitLab CI example · Node.js required · set AEGIS_TOKEN as a protected CI secret
    set -eu
    payload=$(node <<'NODE'
    const { readFileSync } = require('node:fs');
    function required(name) {
      const value = process.env[name];
      if (!value) throw new Error('Set ' + name + ' before uploading coverage');
      return value;
    }
    process.stdout.write(JSON.stringify({
      repository: required('CI_PROJECT_PATH'),
      token: required('AEGIS_TOKEN'),
      commit: required('CI_COMMIT_SHA'),
      branch: required('CI_COMMIT_REF_NAME'),
      buildId: required('CI_JOB_ID'),
      coverage: readFileSync('coverage/lcov.info').toString('base64'),
    }));
    NODE
    )
    printf '%s' "$payload" | curl --fail-with-body --silent --show-error \
      -X POST 'https://aegis.tokdio.com/api/coverage/upload' \
      -H 'Content-Type: application/json' --data-binary @-
  3. 03

    Dispatch a targeted fix

    Start with one actionable finding on a recorded commit. Your operator confirms that the selected repository and executor are ready before the first fix run.

  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

    Review the proposed changes and their evidence before approving write-back. Self-attested evidence is a runner's claim; runner-verified evidence records checks against the patch. The private pilot requires a passing verification receipt for the exact fix attempt.

  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