Shared Workspace¶
Purpose¶
Use shared for repository-wide project assets that cut across lifecycle stages. The Template Library calls this cross-cutting; the Project Workspace calls it shared because these are project-wide assets.
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 |
|---|---|---|---|
| Repository Conventions | repository_conventions.md |
Template | LMU example |
| Decision Record | decision_record.md |
Template | LMU decision log |
| Evidence Record | evidence_record.md |
Template | LMU artifact index |
| Assumption Log | assumption_log.md |
Template | LMU risk register |
| Issue Log | issue_log.md |
Template | LMU risk register |
| Action Item Register | action_item_register.md |
Template | LMU risk register |
| Review Checklist | review_checklist.md |
Template | LMU artifact index |
| Meeting Notes | meeting_notes.md |
Template | LMU stakeholder directory |
| Engineering Journal | engineering_journal.md |
Template | LMU decision log |
| Change Log | change_log.md |
Template | LMU decision log |
Completed LMU shared assets¶
The LMU/COICP example now includes a shared/ directory that demonstrates repository-wide project evidence. These files are not lifecycle-stage artifacts; they connect lifecycle artifacts.
| LMU Shared Asset | Purpose |
|---|---|
| Repository Conventions | Naming, navigation, baseline, and evidence conventions. |
| Glossary | Common terminology, roles, scenarios, and evidence language. |
| Decision Log | Cross-stage decisions and downstream effects. |
| Risk Register | Cross-stage risks that persist across lifecycle gates. |
| AI Usage Log | Material engineering AI assistance and human review expectations. |
| Artifact Index | Map of major artifacts and evidence families. |
| Stakeholder Directory | Project-wide stakeholder roles and evidence interests. |
Start from templates¶
Repository Conventions
Open the reusable template for repository_conventions.md.
Decision Record
Open the reusable template for decision_record.md.
Evidence Record
Open the reusable template for evidence_record.md.
Assumption Log
Open the reusable template for assumption_log.md.
Issue Log
Open the reusable template for issue_log.md.
Action Item Register
Open the reusable template for action_item_register.md.
Review Checklist
Open the reusable template for review_checklist.md.
Meeting Notes
Open the reusable template for meeting_notes.md.
Engineering Journal
Open the reusable template for engineering_journal.md.
Change Log
Open the reusable template for change_log.md.
Working pattern¶
- Open the relevant template.
- Create the same-named file in
docs/project-workspace/shared/. - Replace template guidance with project-specific evidence.
- Compare the result with the LMU/COICP example when available.
- Record open risks, assumptions, and unresolved questions.
- 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. |
Create project artifacts here. Learn the artifact structure from the Template Library. Learn the completed pattern from the LMU/COICP example.