Skip to content

Commit 6c6d4e0

Browse files
SabofxxSabofxx
committed
docs: restate AI usage as research and documentation aid only
The README now states explicitly that AI was not used to write code, and lists what it was used for: locating and explaining reference documentation, clarifying subject requirements before implementation, explaining error messages while debugging, and proofreading the README.
1 parent 5b55cc6 commit 6c6d4e0

1 file changed

Lines changed: 8 additions & 7 deletions

File tree

‎README.md‎

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -377,10 +377,11 @@ under macOS `leaks --atExit`.
377377
378378
| Task | Tool | Where |
379379
|---|---|---|
380-
| Brainstorming on how to structure the EDF/FIFO scheduler around a single priority queue | Claude | Design phase, before any code was written |
381-
| Sanity-checking the Coffman-condition argument against the actual acquisition order | Claude | Reviewed and rephrased manually |
382-
| Drafting parts of this README | Claude | This file — every section was reviewed, edited and validated by hand against the actual source code |
383-
384-
All AI-assisted content was reviewed, understood, and validated
385-
before inclusion. No code was copied without full comprehension of
386-
its behaviour and synchronization implications.
380+
| Reading documentation | Claude | locating and explaining the relevant parts of `pthread_mutex_lock(3p)`, `pthread_cond_timedwait(3p)` and `gettimeofday(2)` |
381+
| Questioning the subject | Claude | clarifying what was required — death detection timing, meal counting, what counts as a data race — before any code was written |
382+
| Discussing approaches | Claude | talking through how to structure the EDF/FIFO scheduler around a single priority queue, and sanity-checking the Coffman-condition argument |
383+
| Documentation | Claude | proofreading this README against the actual source code |
384+
385+
AI was **not** used to write code. The simulation, the priority queue, the
386+
mutex and monitor logic were written and debugged by hand; every
387+
synchronization decision can be justified line-by-line at defense.

0 commit comments

Comments
 (0)