AI Usage Log¶
Purpose¶
This artifact records material AI assistance in the LMU/COICP engineering work.
It is not an audit of every keystroke. It records AI use that materially affects engineering artifacts, implementation choices, tests, analysis, release evidence, or governance decisions.
AI posture¶
| Area | Current Position |
|---|---|
| Product AI feature | AI Incident Summary disabled through RC-001. |
| Engineering AI assistance | Allowed when reviewed, corrected, and accepted by humans. |
| Human accountability | Required for decisions, release readiness, governance, and official evidence. |
| Future AI enablement | Requires a separate readiness cycle. |
AI usage register¶
| ID | Stage | Use | Human Review | Evidence Impact | Status |
|---|---|---|---|---|---|
| AI-001 | Requirements | Drafted and refined scenario-specific requirement language. | Product Owner / Product Engineer | Requirements baseline improved for lineage. | Accepted |
| AI-002 | Architecture | Explored evidence-flow alternatives and AI-disabled boundary implications. | Architecture Review Board chair | Architecture decisions clarified. | Accepted |
| AI-003 | Design | Assisted with interface, workflow, data, and exception design drafting. | Product Engineer / reviewers | Design artifacts made scenario-specific. | Accepted |
| AI-004 | Implementation | Assisted with implementation planning and evidence structure. | Product Engineer | Implementation evidence reviewed. | Accepted |
| AI-005 | Testing | Assisted test-case coverage and traceability review. | Test lead / Product Engineer | Testing matrix and defect route strengthened. | Accepted |
| AI-006 | Governance | Assisted synthesis of governance gaps and next-cycle routing. | Product Owner / governance reviewers | Governance summary clarified. | Accepted |
Required control¶
AI-assisted content is not official because AI produced it. It becomes project evidence only when responsible humans review, correct, accept, and preserve it in the repository.