Define 'forge' on first use in Module 8 #47

New Issue

2026-06-22T14:24:01-04:00

claude commented

2026-06-22 14:24:01 -04:00

Problem

"Forge" (a Git hosting platform) is load-bearing — it first appears in Module 8's objectives and is used ~150+ times through the capstone — but is never glossed for an audience fluent in AI chat apps yet new to the dev toolchain. They know GitHub/GitLab but not "forge" as the generic category term; its meaning is only inferable later from the hosted/self-hosted discussion.

Evidence

modules/08-remotes-and-hosting/README.md line 31 (objectives): "… on any forge, with the same commands." — first use, no definition. The hosted/self-hosted text (~line 147) implies but never states what a forge is. (Module 14 later glosses it inline, showing it's glossable.)

Why it matters

Cheap clarity win for an audience that may not know "forge" as a category; the locked exemplars define terms on introduction.

Proposed change

Gloss it at the first prose use (the "A remote is just another copy" concept section, ~line 45, or line 54), e.g.: "on any forge (a Git hosting platform such as GitHub, GitLab, Gitea, or Forgejo)." Keep the vendor list balanced; avoid stuffing the definition into the terse objective.

Acceptance criteria

"Forge" is defined in a balanced, vendor-neutral parenthetical at/near its first use in Module 8.

Affected files

modules/08-remotes-and-hosting/README.md

References

Source finding F58 (realVotes 3/3).

Filed from an adversarial multi-agent course review (217 raw findings → 54 adversarially-verified survivors). Scoped for manual review; intentionally not auto-assigned to an agent.

## Problem "Forge" (a Git hosting platform) is load-bearing — it first appears in Module 8's objectives and is used ~150+ times through the capstone — but is never glossed for an audience fluent in AI chat apps yet new to the dev toolchain. They know GitHub/GitLab but not "forge" as the generic category term; its meaning is only inferable later from the hosted/self-hosted discussion. ## Evidence `modules/08-remotes-and-hosting/README.md` line 31 (objectives): "… on any forge, with the same commands." — first use, no definition. The hosted/self-hosted text (~line 147) implies but never states what a forge is. (Module 14 later glosses it inline, showing it's glossable.) ## Why it matters Cheap clarity win for an audience that may not know "forge" as a category; the locked exemplars define terms on introduction. ## Proposed change Gloss it at the first prose use (the "A remote is just another copy" concept section, ~line 45, or line 54), e.g.: "on any forge (a Git hosting platform such as GitHub, GitLab, Gitea, or Forgejo)." Keep the vendor list balanced; avoid stuffing the definition into the terse objective. ## Acceptance criteria - [ ] "Forge" is defined in a balanced, vendor-neutral parenthetical at/near its first use in Module 8. ## Affected files - `modules/08-remotes-and-hosting/README.md` ## References Source finding F58 (realVotes 3/3). --- *Filed from an adversarial multi-agent course review (217 raw findings → 54 adversarially-verified survivors). Scoped for manual review; intentionally not auto-assigned to an agent.*

claude added the bug ai-ready P2 labels 2026-06-22 14:24:01 -04:00

claude referenced a pull request that will close this issue

2026-06-22 17:15:28 -04:00

Module 8 polish: backup check, credentials, forge, prices (#38,#39,#47,#52) #64

claude referenced this issue from a commit

2026-06-22 17:15:29 -04:00

fix(module-8): fail-fast backup check, credential walkthrough, define forge, reconcile prices

claude closed this issue

2026-06-22 17:15:41 -04:00

Sign in to join this conversation.