Blame · Line-by-line history

`PLATFORM_STATUS.md`

Each line is annotated with the commit that last touched it. Click any SHA to jump to that commit and see the surrounding change.

PLATFORM_STATUS.mdBlame57 lines · 1 contributor

Normal view Raw

3bd8e2fDictation App	1	# Platform Status — cross-repo contract
	2
	3	The three products (Crontech, Gluecron, GateTest) each expose a small public endpoint:
	4
	5	```
	6	GET /api/platform-status
	7	```
	8
	9	Returns JSON:
	10
	11	```json
	12	{
	13	"product": "crontech" \| "gluecron" \| "gatetest",
	14	"version": "1.0.0",
	15	"commit": "4c512ce",
	16	"healthy": true,
	17	"timestamp": "2026-04-20T12:34:56Z",
	18	"siblings": {
	19	"crontech": "https://crontech.ai/api/platform-status",
	20	"gluecron": "https://gluecron.com/api/platform-status",
	21	"gatetest": "https://gatetest.io/api/platform-status"
	22	}
	23	}
	24	```
	25
	26	## Why
	27
	28	Each admin console fetches the other two siblings so the operator can see all three platforms' state from one page. Each customer dashboard fetches its own endpoint (+ any siblings the user has entitlements for) so end users see a unified "your platform" card.
	29
	30	This is the first step of the three-repo platform wiring. It is intentionally small: no auth, no shared packages, no cross-repo SSO. The endpoints only publish non-sensitive product state that is safe to read from any browser session.
	31
	32	## Wire-up status
	33
	34	- Crontech (`apps/web/src/routes/api/platform-status.ts`) — auto-picked by SolidStart file router, zero wiring.
	35	- Gluecron (`src/routes/platform-status.ts`) — exported Hono handler. Needs one line in `src/app.tsx`:
	36	```ts
	37	import { platformStatus } from "./routes/platform-status";
	38	app.route("/api/platform-status", platformStatus);
	39	```
	40	- GateTest (`website/app/api/platform-status/route.ts`) — auto-picked by Next.js App Router, zero wiring.
	41
	42	## Environment variables
	43
	44	Each deploy should set:
	45
	46	- `APP_VERSION` — semver tag (default `"dev"`)
	47	- `GIT_COMMIT` — short SHA (default `"unknown"`)
	48
	49	## CORS
	50
	51	The endpoint sends `Access-Control-Allow-Origin: *` because product status is public — no secrets, no user data, no PII. Safe to poll from any admin browser session or status page.
	52
	53	## Next steps (follow-up PRs)
	54
	55	1. Admin UI widget — add a 3-card grid to each product's existing `/admin` page that fetches all three siblings and renders health + commit + last-seen.
	56	2. Customer onboarding card — show on each product's customer dashboard: "Your status on each product" (bootstrapped from the sibling endpoints, gated by entitlements once SSO lands).
	57	3. Shared identity (SSO) — dedicated follow-up session. Will add an `entitlements` table and require CLAUDE.md PIN per doctrine.