Skip to content

Integration Workspace

ETIS Project Workspace

Integration Workspace

Code review, AI implementation review, guardrail review, pull request review, integration verification.

ES-108 Project Repository Integration

Purpose

Show how separately built work is assembled, reviewed, verified, and made ready for formal testing.

This directory should contain the project’s actual working artifacts for this lifecycle area. The links below intentionally point to the Template Library and, where available, the completed LMU/COICP example. Create the real project files in this directory when the project is ready to populate them.

What belongs here

Artifact Project File Name Template Completed Example
Code Review Overview code_review_overview.md Template Completed example
Pull Request Review Record pull_request_review_record.md Template Completed example
Ai Implementation Review ai_implementation_review.md Template Completed example
Guardrail Review guardrail_review.md Template Completed example
Traceability Review traceability_review.md Template Completed example
Repository State Review repository_state_review.md Template Project-specific; no LMU example
Review Findings review_findings.md Template Completed example
Integration Plan integration_plan.md Template Completed example
Integration Decision Record integration_decision_record.md Template Completed example
Integration Verification Record integration_verification_record.md Template Completed example
Integration Readiness Summary integration_readiness_summary.md Template Completed example

Start from templates

Working pattern

  1. Open the relevant template.
  2. Create the same-named file in docs/project-workspace/integration/.
  3. Replace template guidance with project-specific evidence.
  4. Compare the result with the LMU/COICP example when available.
  5. Record open risks, assumptions, and unresolved questions.
  6. Finish with the review or readiness artifact for this stage.

Evidence quality bar

Quality What It Means
Specific Names actual project facts, stakeholders, systems, scenarios, risks, and decisions.
Traceable Connects back to earlier stages and forward to later stages.
Reviewable Gives another reviewer enough evidence to challenge or approve the work.
Current Reflects the project’s actual state rather than old intent.
Governable Makes AI use, exceptions, risks, release posture, and limitations visible.
Workspace Rule

Create project artifacts here. Learn the artifact structure from the Template Library. Learn the completed pattern from the LMU/COICP example.

Continue to Testing

Move forward when this stage has enough project evidence and a clear readiness decision.

Open Testing →