EDOS agent index¶

Audience: Agent

Use this file as a compact entrypoint when consuming hosted docs.

Read first¶

README.md
SCOPE.md
REPOS.md
HOSTNAMES.md — allocated *.howfe.org slugs; read before naming a new app
ARCHITECTURE.md
IPC.md
HOSTED_APP_CONTRACT.md — URL bootstrap, manifests, optional embed handshake (not MessageTypeEnum)
APP_DISCOVERY_REGISTRY.md — optional federated link-only indexes for composition hosts (read when building EDAC or operating a registry)
DESIGN_GUIDANCE.md — optional visual identity (first-party UIs)
TABLE_GUIDANCE.md — data-dense table behavior (views, filters, highlights)
AGENTS.md
DEPLOYMENT.md
AGENT_DEPLOYMENT_QUICKREF.md

apps/elite-dangerous-local-journal-reader.md — single Tauri host, injected HTTPS URL, build API → wired .exe (see project-local build-service.md).
apps/elite-dangerous-journal-event-viewer.md — EDJEV hosted UI (edjev) vs static-site env for download links.

journalFilesSamples/ (if present at workspace root): real journal lines and sidecar JSON for schema verification — not on the hosted docs site and often absent in partial clones.
When event or sidecar shape is unclear after elite-dangerous-event-types and the docs above, ask the operator for sample files or excerpts — do not guess. Details: AGENTS.md.

Treat EDOS as a multi-repo ecosystem, not a monorepo.
Route community API traffic through the cache/proxy pattern.
Keep IPC origin allowlists explicit; do not widen to * without documented reason.
For new deployable services, follow the compose + Traefik pattern in DEPLOYMENT.md.
Mark uncertainty as TODO: Verify with a concrete next step.
Native desktop shells and URL-wired Windows installer builds are owned by elite-dangerous-local-journal-reader (Tauri + build-service/). Other repos ship hosted web apps only and link to published installers or the documented build API — do not add a second Tauri / local-bridge app inside consumer repositories.