NYX · HPAD · COLLECTOR

Nothing has reported in yet

This is the collector. Every NYX pushes what she knows to it; it never reaches back into her. She is not controlled from here, and there is no endpoint that could — that is a property of the design, not a setting.

Waiting on three things

  1. A Google “Web application” OAuth client. The one NYX signs in with cannot be reused — it is of type “Desktop app”. A browser sign-in needs its own, with https://nyx-admin.hpad.co.in/api/auth/callback as an authorised redirect URI.
  2. Somewhere to put the data. Serverless functions keep nothing between requests. One small Postgres is plenty for 100 machines reporting a few times an hour.
  3. A DNS record pointing nyx-admin.hpad.co.in at this deployment.

The contract she posts to

POST /api/ingest is live and validating now, so the pipe can be proven from a real machine before storage exists. It takes only what she already knows, so nothing new has to be invented on her side.

{
  "machine":   "MEETING_ROOM1",
  "user":      "arjun",
  "person":    "arjun@hpad.co.in",   // verified by Google, or null
  "version":   "0.4.1",
  "at":        "2026-08-07T10:09:48Z",
  "tasks":     [ { "id": "..", "title": "..", "project": "..",
                   "status": "open|done", "createdAt": 0, "doneAt": null } ],
  "entries":   [ { "id": "..", "taskId": "..", "start": 0, "end": 0 } ],
  "active":    { "taskId": "..", "start": 0 } | null,
  "lastError": null
}

Her state file already carries a synced flag on every time entry, so she can mark what she has sent and never send it twice.

No HPAD staff data is on this host. The desktop panel’s seeded names and org chart were deliberately left behind rather than published to a URL.