# AI Logs

This folder documents representative AI-assisted prompts used during the development of the HoldLight web prototype and process portfolio.

AI tools were used to support coding, layout refinement, accessibility checks, debugging, design organization, and portfolio writing refinement. The project motivation, user research findings, design logic, requirement analysis, evaluation interpretation, and final design decisions remained the group’s own work.

## Log Index

| Log File | Main Area | AI Tools Used | Project Use | Status |
|---|---|---|---|---|
| `01-route-preview-ui-prompt.md` | Layered route preview UI | Figma AI / Figma Make; OpenAI ChatGPT | Supports route preview structure, user-requirement explanation, iteration evidence, and AI reflection. | Completed |
| `02-accessibility-controls-prompt.md` | Accessibility controls and voice guidance | Figma AI / Figma Make; OpenAI ChatGPT | Documents repeat, pause, more detail, help, text size, contrast, and low-overload voice guidance decisions. | Completed |
| `03-evaluation-layout-prompt.md` | Evaluation layout and reflection structure | Google Gemini; OpenAI ChatGPT | Documents how testing overview, alpha usability testing, task cards, results, refinements, and AI disclosure were structured. | Completed |
| `04-responsive-debugging-prompt.md` | Responsive debugging and layout fixes | OpenAI Codex; OpenAI ChatGPT | Documents responsive table, gallery, hero, contribution table, and mobile layout debugging support. | Completed |
| `05-portfolio-content-refinement-prompt.md` | Portfolio writing refinement | Google Gemini; OpenAI ChatGPT | Documents writing, grammar, evidence alignment, contribution clarity, and responsible AI-use disclosure support. | Completed |

## Related Project Files

- Main portfolio pages: `index.html`, `why-gap.html`, `user-requirements.html`, `iteration-alternatives.html`, `implementation.html`, `evaluation-reflection.html`
- Redirect / support pages: `brief.html`, `testing-iteration.html`, `final-reflection.html`
- Shared styling and interaction files: `portfolio.css`, `portfolio.js`
- Project summary source: `content-summary.md`
- Prototype and evidence assets: `assets/images/prototype/`, `assets/images/testing-evidence/`, `assets/images/beforeafter/`, `assets/videos/`

## Documentation Notes

- Prompts in these logs are summarized representative prompts. Where the exact original prompt was not preserved, a concise reconstructed prompt was written to match the actual task, project stage, and resulting portfolio changes.
- Different AI tools were used for different types of support: Figma AI / Figma Make for design and prototype layout exploration, Google Gemini for writing, organization, and design-summary support, and OpenAI ChatGPT / Codex for implementation-oriented prompts, debugging, and code-structure support.
- “Used in files/pages” entries refer to real paths in this repository.
- AI outputs were treated as drafts. Final design, writing, accessibility judgement, evaluation interpretation, and ethical framing were manually reviewed by the team.
- No AI log should be read as evidence that AI created user research findings, participant data, evaluation results, or final safety claims.
- Model / version information is recorded only when known. If the exact model or version was not visible or not preserved, the log marks this field for team confirmation before final submission.

## What Each Log Records

Each log follows a consistent structure:

1. **Date / Project Stage** — when the AI-assisted task happened in the project timeline.
2. **AI Tool Used** — which AI tool was used and, where available, its model or version.
3. **Intended Task** — what the team wanted AI to support.
4. **Prompt** — the actual or summarized prompt used for the task.
5. **AI Outcome** — what the AI provided, including what worked and what did not work.
6. **Team Action After AI Output** — how the team modified, refined, kept, or discarded the AI output.
7. **Verification Against User Requirements** — how the result was checked against HoldLight’s requirements and project evidence.
8. **Ethical / Accessibility / Reliability Considerations** — possible risks and how the team reduced them.
9. **Final Use in Project** — where the AI-assisted output was used in the final system or portfolio.

## Academic Integrity Boundary

These logs are included for coursework transparency. They show how AI-assisted work was reviewed, adapted, and verified by the team.

AI was used to accelerate design exploration, code support, debugging, and writing refinement. It was not used to define the project motivation, create user research data, invent participant feedback, produce evaluation findings, or make final design decisions.

All final claims in the portfolio should be supported by the group’s own research, prototype development, testing evidence, and iterative reflection.