glm-5.1
2b63cda1c7
Copy architecture docs, ADRs, storage domain specs, research, reviews, and 56 storage architecture tasks from the alkhub_ts monorepo. Adapt for standalone @alkdev/hub repo structure (src/ not packages/hub/). Sanitize all sensitive information: - Replace private IPs (10.0.0.1) with localhost defaults - Remove internal server hostnames (dev1, ns528096) - Replace /workspace/ private paths with npm package references - Remove hardcoded credentials from examples - Rewrite infrastructure.md without private network details Add Deno project scaffolding: deno.json (pinned deps), .gitignore, AGENTS.md, entry point. Migrate existing code stubs (crypto, config types, logger) with updated import paths.
19 lines
931 B
Markdown
19 lines
931 B
Markdown
# ADR-005: Spoke naming, not runner
|
|
|
|
- **Status**: Accepted
|
|
- **Date**: 2026-04-19
|
|
- **Deciders**: alkdev
|
|
|
|
## Context
|
|
|
|
The concept of a process connecting to the hub via websocket is a "spoke." Previous drafts used "runner" (influenced by GitHub Actions runner naming), but spokes are more general — dev environments, client applications, or compute instances.
|
|
|
|
## Decision
|
|
|
|
Use "spoke" consistently in table names, column names, and throughout the codebase. Table is `spokes` (not `runners`). FK columns are `spoke_id` (not `runner_id`). Registered spoke record is a "spoke registration."
|
|
|
|
Rationale: Hub-spoke metaphor is consistent throughout architecture docs. "Runner" is a specific kind of spoke, not the general concept.
|
|
|
|
## Consequences
|
|
|
|
Positive: naming consistency with hub-spoke architecture metaphor, more general and accurate terminology. Negative: none — purely a naming convention decision that improves clarity. |