Informational Fresh jira_story: GOV-301

Lesson 1 of 6 — Connector framework and interface

Automated Discovery Connectors · Source: Jira Story GOV-301 (8 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Define a common connector interface for discovery.

Why it matters

A shared contract lets many connectors plug in without bespoke glue.

Where this lives

Runs in the Customer AI Governance platform (components: intelligence). A connector framework defines a common interface returning candidate systems. Learn teaches this read-only.

Workflow

Given a connector
When it runs
Then it returns candidate systems via a common interface

Worked example

Two teams write M365 and SAP connectors independently. What keeps them interoperable?

The common connector interface — every connector returns candidates the same way.

Acceptance criteria (authoritative — GOV-301)

Given a connector, when it runs, then it returns candidate systems via a common interface.

Common pitfalls

One-off connectors with no shared contract, unmaintainable at scale.

Knowledge check

Scenario: Two teams write M365 and SAP connectors independently. What keeps them interoperable?
Look for: The common connector interface — every connector returns candidates the same way.

Key concepts

connector framework
common interface
candidate systems

For the AI Tutor

Summary: Define a common connector interface for discovery.
When to use: teaching or answering questions about "connector framework and interface".
When NOT to use: manual discovery methods (that is GOV-112).
Key concepts: connector framework, common interface, candidate systems.

Completion criteria

Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-301's acceptance criterion.

Module: LEARN-MOD-009 (Automated Discovery Connectors)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-046