zlh-grind/UPSTREAMS.md

46 lines
1.3 KiB
Markdown

# Upstreams — zlh-grind
This repository tracks GPT execution work across upstream projects.
## Rules
- This file is a registry of upstream repos used during execution.
- Do not duplicate canonical documentation here; link to it.
---
## ZeroLagHub Knowledge Base (Canonical)
- Repo: `https://git.zerolaghub.com/jester/knowledge-base`
- Role: Canonical architecture, decisions, procedures, handovers
## zlh-grind (Execution Ledger)
- Repo: `https://git.zerolaghub.com/jester/zlh-grind`
- Role: GPT execution notes, session logs, drift prevention
## zlh-api (API / Control Plane)
- Repo: `https://git.zerolaghub.com/jester/zlh-api`
- Role: Control-plane orchestration (instance lifecycle, DB writes, agent coordination)
## zlh-agent (Go Agent)
- Repo: `https://git.zerolaghub.com/jester/zlh-agent`
- Role: Agent runtime for provisioning/install/verify/start workflows
- Notes: Tagged `v0.1.0-dev` as the first dev snapshot.
---
## Authentication Ownership
### Portal
- Owns identity UX (login, logout, session handling)
- Stores JWT token
- Attaches Authorization header to API calls
### APIv2
- Validates credentials
- Issues JWT tokens
- Verifies tokens for protected routes
- Persists user records
### Explicit Non-Responsibilities
- API does not manage frontend sessions
- Portal does not validate credentials directly