Docs

Appearance

Engineer & Integrations Path ​

Connect the systems that matter so governance work is grounded in real artifacts: repositories, docs, tickets, and operational signals.

Outcome ​

You leave this path with:

  • Scout connectors connected for user-scoped research
  • project sources configured for stable, project-level access and testing
  • API tokens and Modulos Client set up when you need push-style integration

Time to first value: 30–90 minutes
Prerequisites: you have access to the project and permission to configure integrations

Path at a glance ​

1

Connect Scout

Add user-scoped connectors for docs, code, and tickets

2

Add project sources

Configure service accounts for stable project access

3

Set up API access

Create API tokens and validate authentication

4

Validate signals

Confirm Scout and Testing can retrieve the right context

Step 1: Connect Scout connectors ​

Goal: let Scout retrieve external context within a user permission boundary.

Where in Modulos

  • Settings → Connectors

Do this

  • Connect the systems you expect Scout to reference, such as GitHub, Bitbucket, Atlassian, or Google Drive.
  • Confirm the connector shows as connected.

You’re done when

  • Scout can reference external context you have access to

Step 2: Add project sources ​

Goal: configure stable, project-level service accounts for automation and signals.

Where in Modulos

  • Project → Settings → Sources

Do this

  • Add metrics-capable sources for Testing (for example Prometheus, Datadog, or Modulos Client).
  • Add context sources used by Scout research (for example GitHub or Azure) when relevant.

You’re done when

  • sources are configured and visible in Project Settings

Step 3: Set up API tokens and Modulos Client ​

Goal: enable push-style integrations and automation.

Where in Modulos

  • User Settings → API Tokens to create tokens
  • Resources → Modulos Client for client usage and examples

Do this

  • Create a token for your integration use case and store it securely.
  • Use Modulos Client when you want your code to push metrics or artifacts into Modulos.

You’re done when

  • you can authenticate to the API and perform the intended integration workflow

Step 4: Validate end-to-end behavior ​

Goal: confirm connected systems produce usable governance context.

Where in Modulos

  • Project → Testing to validate metrics, tests, and results
  • Project → Scout to validate retrieval and grounded answers

Do this

  • Create or update a test condition and run it.
  • Ask Scout a question that requires external context and confirm it returns grounded references.
  • If you see access issues, confirm connector permissions and source configuration.

You’re done when

  • testing signals are visible and Scout can retrieve the expected context

Next handoff ​

Compliance Lead

Use connected context to drive evidence-backed control execution

AI Product Owner

Keep system scope and lifecycle stage current for governance decisions

Monitor stage

Turn metrics into continuous governance signals and remediation loops