Customize

This page settles what is yours to change in Coxswain and where each piece of it lives: your team's cartridge, its fragments, the skills bound to your seats, your provider profile, and the policy knobs that shape how runs dispatch.

What's yours

• Your cartridge — the team layer on top of base and local. See Team cartridge.
• Your fragments — the individual pieces of context inside your cartridge's cartridge.d/. See Fragments.
• Your skill bindings — which skills fill which seats and roles for your runs. See Skills.
• Your provider profile — which provider, which tier, which tools per role. See Providers.
• Your policy — the knobs that change review tier, plan competition, build budgets, and how many runs are in flight at once. See Policy.
• Your dashboards — Superset over your own runs, with a dashboard to read and charts you can add. See Dashboards.
• Your lake — your runs in Iceberg tables, synced after each land and queried with SQL. See The lake.
• Your efficiency numbers — cost, landed rate, and quarantine causes, read from the run store. See Efficiency.
• Your several machines — a chair that launches and lands, lane machines that run, and one shared run store. See Several machines.
• Your plugins — the integrations that name a vendor (a tracker, a forge, a hosted decider, a runner), installed beside cox or the harness and chosen by name. See Plugins.

What isn't

The graph's own nodes and edges, the base conventions, and the crew and seat mechanism are the platform's concern — see Methodology. You extend them; you don't fork them. Every layer you add can tighten what came before it and never loosen it — see Cartridges for why.

Writing something new

If what you need isn't a cartridge, a fragment, a binding, or a policy value, but an actual new skill or graph, see Write a skill and Write a graph.