Use case · Reference org
ElMundi — operating a public monorepo like an enterprise program
Linear as the SDLC spine, GitHub Actions as the nervous system, Cursor Cloud Agent for execution, Playwright for proof — all documented in-repo so procurement can read the same story engineers diff.
Executive summary
ElMundi is the reference wiring for Ship: not a separate product, but a living receipt of how the methodology kit is applied to a real org surface. The outcome is predictable delivery with audit trails (labels, states, Actions logs) instead of heroics in chat threads.
01 · Challenge
Scale agent execution without losing governance
Teams want autonomous agents, but enterprise risk asks for who approved what, which branch ran, and how QA was evidenced. ElMundi encodes those answers as infrastructure: Linear projects mirror SDLC lanes, GitHub Actions own scheduling and secrets, and the manual names the exact files so security can grep instead of guessing.
02 · Solution
Treat the monorepo as the control plane
The fix is not another dashboard — it is instruction-first documentation plus automation that matches the words. Ship ships the patterns; ElMundi shows one complete install: intake → build → QA → release, with receipts in .github/workflows, documentation/examples/elmundi, and the Linear taxonomy described in the manual.
03 · Implementation
What was actually wired
- Linear — SDLC projects, states, labels, and audit issues that agents must satisfy before merge.
- GitHub Actions — scheduled and on-demand workflows for agent launch, docs sync, and release hygiene; secrets stay in GitHub, not in prompts.
- Cursor Cloud Agent — branch-per-ticket execution with PRs as the review surface.
- Playwright — hosted browser runs that attach traces/screenshots to the ticket narrative.
- MkDocs-style reader — the same content is readable on the marketing site under
/docs/examples/elmundifor buyers who will not clone first.
04 · Outcomes
What leadership can point to
- Repeatable agent launches — operators follow named workflows instead of improvising slash commands.
- Audit-friendly artifacts — Actions logs, PR links, and Linear state transitions form a chain of custody.
- Faster onboarding — new contributors read one manual chapter and see the same filenames in the tree.
Evidence
Screens from the live site
Product screenshots are from dev.elmundi.com staging; the last tile is the Ship manual chapter for operators who need diffable wiring detail.
