Design playbook / GitHub + Azure DevOps
Trace source revisions into assurance decisions.
How repository revision and change-request context could connect a declared AI configuration to a candidate, mapped assurance impact and a governance review.
Source → state → assurance → decision
A specific, explainable connection path.
This is a proposed integration contract illustrated with authored examples. Every state transition would require supported source access, provenance and product release qualification.
- 01
Bind source revision
Record allowed repositories, branch/revision and the source object representing an AI system.
- 02
Compare declared change
Map source-level modifications to semantic component changes while retaining the native diff.
- 03
Evaluate assurance impact
Identify which controls or evaluations depend on altered model, prompt, tool, data or permissions.
- 04
Link review and decision
Keep source provenance connected to the candidate and the explicit approval history.
Source inputs and provenance
Required for a bounded connector contract—not a promise that every native API exposes them.
- Permitted repository, PR and commit metadata
- Declared AI configuration or mapping
- Source revision and observation timestamps
Questions the control layer must answer
Consequences of change, measured against the governing baseline and evidence.
- What changed beyond raw file text?
- What did that change invalidate or preserve?
- Which candidate and approval decision correspond to the source revision?
Boundaries and unknowns
No source coverage, no certainty.
Steerlane does not treat unavailable fields as verified unchanged. Unsupported authority, missing telemetry and stale sources remain explicitly unresolved.
- A merged PR is not a production approval.
- Source declaration alone may not prove deployed or observed state.
- No GitHub or Azure DevOps account is connected to the public marketing site.
Evaluation focus: revision identity, declared configuration and deployed-state uncertainty.
Evaluate the actual scope before committing to a pilot.
Tell us your platform, tenant boundaries, evidence sources and review ownership. Pilot commitments remain limited to demonstrated capabilities.