fix(substrate): strip hardware identity from today's code + docs - #1565
Merged
Conversation
…ode + docs Joel called this out: is 5090 coded into the repo? Yes — GPU-specific narrative and operator-personal labels leaked into substrate source, test fixtures, and doc-strings across today's PRs (#1560, #1561, #1563, #1564). None were load-bearing, but the repo should be hardware-agnostic. Replacements (one PR, surgical edits): core/continuum-core/src/inference/airc_remote/adapter.rs - doc: "route to Joel's 5090" -> generic remote-inference-peer description - test fixture: "joels-5090" -> "test-remote-peer" core/continuum-core/src/inference/airc_remote/transport.rs - test fixture: "joels-5090" (2 sites) -> "test-remote-peer" core/continuum-core/tests/airc_remote_inference_roundtrip.rs - doc: "airc://<rtx5090>/ai/generate" -> "airc://<remote-peer>/ai/generate" - peer labels generic: "remote inference host" / "local caller" - canned response: "pong from the remote peer" / "test-model" / "test-remote-llamacpp" apps/cli/src/main.rs - Generate doc: "(e.g., the operator's 5090)" -> generic GPU-rich grid host apps/cli/src/grid_smoke.rs - module doc + ai/generate row comment: "constrained-locally host dispatches at a GPU-rich peer" / "If the target is a GPU host running a real LLM" Out of scope: - Older codebase doctrine attributions ("Joel's never-swallow-errors") stay — those name doctrine origin, fine. - Task #85 mentioning 5090 stays — it's a real airc bug ticket about that hardware. Verified: grep -rn "5090|joels-" on touched files -> zero hits cargo check -p continuum-cli -> clean (1.94s) The pattern lesson: any hardware-specific identity is narrative scaffolding, not substrate truth. The substrate is hardware-agnostic; tests use neutral labels; docs describe categories, not specific units. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Joel called this out: 'Is 5090 coded into the repo? That would be weird.' Yes — I let GPU-specific narrative and operator-personal labels leak into substrate source + test fixtures + doc-strings across today's PRs (#1560, #1561, #1563, #1564). None load-bearing, but the repo should be hardware-agnostic.
Replacements (one PR, surgical edits)
joels-5090->test-remote-peer(3 sites). Doc "route to Joel's 5090" -> generic remote-inference-peer description.pong from the remote peer/test-model/test-remote-llamacpp).(e.g., the operator's 5090)-> generic GPU-rich grid host.Out of scope (intentionally kept)
Joel's never-swallow-errors) — they name doctrine origin, fine.Verified
Lesson
Any hardware-specific identity is narrative scaffolding, not substrate truth. The substrate is hardware-agnostic; tests use neutral labels; docs describe categories, not specific units.
Generated with Claude Code