Review system integration
Assess one repository, a repository group, or an existing fleet evidence bundle. Treat declared, observed, and inferred relationships as distinct evidence classes.
Run the lens
- Read the standalone lens protocol completely and prepare the supplied scope with lens ID
system-integration.
- Read the system integration checks completely. Apply every check family relevant to contracts, clients, data, messages, artifacts, and graph edges in scope.
- Reconcile authoritative declarations with observed evidence and bounded inferences. Classify supported outcomes as strengths or findings; record missing peers, contracts, deployment data, and edge evidence as unknowns.
- Link findings to relevant interaction edges, then follow the protocol to account for every contract-registered check family, validate the result, ingest it, and hand back the canonical artifact path.
When a declared system map is supplied, read its semantics in configuration. For raw collection or contract-tool execution, read and follow the safety model.
Boundary
Own cross-repository contracts, topology, coupling, and coordinated change. Route internal module structure to codebase design and repository-local failure implementations to software reliability.
Completion
Complete when: every in-scope repository has an exact commit or explicit unavailable state, every applicable check family is accounted for, every reported edge has evidence, source type, and confidence, gaps remain visible in unknowns and coverage, and the shared result validator succeeds.
1---2name: review-system-integration3description: System integration review for cross-repository contracts, versioning, shared data, service boundaries, dependency direction, synchronous and messaging chains, failure propagation, cycles, and coordinated-release risk. Use for system maps, integration, or fleet-architecture questions.4---56# Review system integration78Assess one repository, a repository group, or an existing fleet evidence bundle. Treat declared, observed, and inferred relationships as distinct evidence classes.910## Run the lens11121. Read the [standalone lens protocol](../audit-software-fleet/references/standalone-lens.md) completely and prepare the supplied scope with lens ID `system-integration`.132. Read [the system integration checks](references/checks.md) completely. Apply every check family relevant to contracts, clients, data, messages, artifacts, and graph edges in scope.143. Reconcile authoritative declarations with observed evidence and bounded inferences. Classify supported outcomes as strengths or findings; record missing peers, contracts, deployment data, and edge evidence as unknowns.154. Link findings to relevant interaction edges, then follow the protocol to account for every contract-registered check family, validate the result, ingest it, and hand back the canonical artifact path.1617When a declared system map is supplied, read its semantics in [configuration](../audit-software-fleet/references/configuration.md). For raw collection or contract-tool execution, read and follow the [safety model](../audit-software-fleet/references/safety-model.md).1819## Boundary2021Own cross-repository contracts, topology, coupling, and coordinated change. Route internal module structure to codebase design and repository-local failure implementations to software reliability.2223## Completion2425**Complete when:** every in-scope repository has an exact commit or explicit unavailable state, every applicable check family is accounted for, every reported edge has evidence, source type, and confidence, gaps remain visible in unknowns and coverage, and the shared result validator succeeds.
kenlck