Name the project IODD Tool #25

New issue

Closed

opened 2026-10-13 08:43:17 +00:00 by phg · 1 comment

phg commented

2026-10-13 08:43:17 +00:00

Owner

Question

What canonical display name and repository identity should replace fat-defrag-native across the project, specification, documentation, and tracker?

Parent: #7
Type: grilling
Mode: HITL

The user proposed the display name “IODD Tool” and confirmed the full rename, including the Forgejo repository URL. The answer will be recorded as a resolution comment.

## Question What canonical display name and repository identity should replace fat-defrag-native across the project, specification, documentation, and tracker? Parent: https://git.s1q.dev/phg/iodd-tool/issues/7 Type: grilling Mode: HITL The user proposed the display name “IODD Tool” and confirmed the full rename, including the Forgejo repository URL. The answer will be recorded as a resolution comment.

phg self-assigned this

2026-10-13 08:43:23 +00:00

phg added the

wayfinder:grilling

label

2026-10-13 08:43:24 +00:00

phg commented

2026-10-13 08:50:52 +00:00

Author

Owner

Resolution — IODD Tool

On 13 October 2026, the user selected IODD Tool as the project's display name and confirmed “Full rename, including Forgejo URL.” This live feedback resolves the naming and repository-scope decision.

Canonical project and future application display name: IODD Tool.
Repository: phg/iodd-tool.
Git origin: ssh://forgejo@git.s1q.dev/phg/iodd-tool.git.
Hosted map and specification title: IODD Tool specification.

Applied the Forgejo repository rename and description, the T3 project title, Git origin, current documentation and glossary naming, and current hosted issue/comment links. The packaging handoff explicitly requires IODD Tool naming. Local documentation changes remain in the working tree alongside the pre-existing work; no commit or push was performed.

The original FAT Defrag application keeps its source-product name. The original specification/publication snapshots, recorded research checkout paths, and accepted prototype commits retain their historical identity. Their current context pointers use the new repository URL. The existing local checkout path is retained so the active session and linked worktrees remain usable. The accepted prototype's historical branding is superseded by this naming decision for the eventual application; its behavior contracts stand.

Verification: authenticated Forgejo reads resolve the renamed repository and old repository alias; Git can read the new origin and the retained prototype branch; all 25 hosted issue bodies and 11 changed comments were read back; current documentation has no old hosted repository links; original publication snapshots and reference baseline are byte-for-byte preserved. The production app remains a later implementation effort.

## Resolution — IODD Tool On 13 October 2026, the user selected **IODD Tool** as the project's display name and confirmed **“Full rename, including Forgejo URL.”** This live feedback resolves the naming and repository-scope decision. - Canonical project and future application display name: **IODD Tool**. - Repository: [phg/iodd-tool](https://git.s1q.dev/phg/iodd-tool). - Git origin: `ssh://forgejo@git.s1q.dev/phg/iodd-tool.git`. - Hosted map and specification title: [IODD Tool specification](https://git.s1q.dev/phg/iodd-tool/issues/7). Applied the Forgejo repository rename and description, the T3 project title, Git origin, current documentation and glossary naming, and current hosted issue/comment links. The packaging handoff explicitly requires IODD Tool naming. Local documentation changes remain in the working tree alongside the pre-existing work; no commit or push was performed. The original FAT Defrag application keeps its source-product name. The original specification/publication snapshots, recorded research checkout paths, and accepted prototype commits retain their historical identity. Their current context pointers use the new repository URL. The existing local checkout path is retained so the active session and linked worktrees remain usable. The accepted prototype's historical branding is superseded by this naming decision for the eventual application; its behavior contracts stand. Verification: authenticated Forgejo reads resolve the renamed repository and old repository alias; Git can read the new origin and the retained prototype branch; all 25 hosted issue bodies and 11 changed comments were read back; current documentation has no old hosted repository links; original publication snapshots and reference baseline are byte-for-byte preserved. The production app remains a later implementation effort.

phg closed this issue

2026-10-13 08:50:52 +00:00

phg referenced this issue

2026-10-13 08:50:54 +00:00

IODD Tool specification #7