Back to corpus
architecturetechnical paper candidatescore 22

Mac3 Worker Config

- `sea-worker.plist` — launchd plist for the main SEA scorer/worker process - `install.sh` — Deploy script to install the plist on mac3

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

- `sea-worker.plist` — launchd plist for the main SEA scorer/worker process - `install.sh` — Deploy script to install the plist on mac3 | Key | Default | Description | |-----|---------|-------------| | `SEA_NODE_ID` | `mac3` | Node identifier in SEA cluster | | `SEA_ROLE` | `scorer` | Worker role (scorer, router, health) | | `SEA_PORT` | `18080` | HTTP port for worker API | - Python 3.8.2 (system) — adequate for scoring/routing workers - 8 GB RAM — keep ML models on Mac4 (16 GB) instead - launchd auto-restarts on crash (`KeepAlive.SuccessfulExit = false`) - Logs at `[home-path]`

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.