Area
service, deployment
Outcome
Internal services need consistent authentication, while external consumers need a restricted public entry point. This epic establishes a shared internal auth library and a separate curated external gateway without placing a gateway in front of internal traffic.
Definition of done
Ownership
packages/auth owns the shared internal authentication foundation (#58). The gateway work (#59) owns the curated external HTTP surface and deploy runbook. Internal service APIs remain private; this epic does not add an internal gateway.
Parallel work
#58 is complete. Continue #59 through the existing implementation PR #65 and its review/runbook; no further child work is introduced by this breakdown.
Task breakdown
| Task |
Area |
Effort |
| #59 — Add a public gateway for scoped directory reads |
service, deployment |
L |
Earlier decisions and completed history
Closed children: #58. Their existing issue states and discussions retain the completion, cancellation, or supersession details.
Scope and implementation notes
Children: #58 (completed) and #59 (open). Related: #34; the directory already stores GitHub and Discord person identifiers.
Internal plane: Railway private network and full scoped-key APIs. External plane: curated public reads through the gateway. Implementation PR for #59: #65.
Out of scope: an internal gateway and external write access. Revisit internal gateway architecture only if the consumer landscape materially changes.
Working conventions
Filed tasks are direct sub-issues of this epic. GitHub Relationships record the existing hard prerequisites; the task table summarizes the work and existing project Size estimates. Keep each task independently reviewable and normally within one CODEOWNERS zone; explain deliberate cross-zone changes. Misty issues may carry several area labels; zones apply to PRs. Follow AGENTS.md and the affected service's CONTRIBUTING.md for implementation, tests, and documentation.
Area
service, deployment
Outcome
Internal services need consistent authentication, while external consumers need a restricted public entry point. This epic establishes a shared internal auth library and a separate curated external gateway without placing a gateway in front of internal traffic.
Definition of done
Ownership
packages/authowns the shared internal authentication foundation (#58). The gateway work (#59) owns the curated external HTTP surface and deploy runbook. Internal service APIs remain private; this epic does not add an internal gateway.Parallel work
#58 is complete. Continue #59 through the existing implementation PR #65 and its review/runbook; no further child work is introduced by this breakdown.
Task breakdown
Earlier decisions and completed history
Closed children: #58. Their existing issue states and discussions retain the completion, cancellation, or supersession details.
Scope and implementation notes
Children: #58 (completed) and #59 (open). Related: #34; the directory already stores GitHub and Discord person identifiers.
Internal plane: Railway private network and full scoped-key APIs. External plane: curated public reads through the gateway. Implementation PR for #59: #65.
Out of scope: an internal gateway and external write access. Revisit internal gateway architecture only if the consumer landscape materially changes.
Working conventions
Filed tasks are direct sub-issues of this epic. GitHub Relationships record the existing hard prerequisites; the task table summarizes the work and existing project Size estimates. Keep each task independently reviewable and normally within one CODEOWNERS zone; explain deliberate cross-zone changes. Misty issues may carry several area labels; zones apply to PRs. Follow AGENTS.md and the affected service's CONTRIBUTING.md for implementation, tests, and documentation.