Glossary
Fireweave terms, defined
Short, quotable definitions for the entities that show up when teams ship with coding agents and Fireweave.
- AI release engineer
- Software that automates safe production shipping for coding-agent changes: control-point wrapping, cohort ramps, guardrails, rollback, and live stability/adoption signals.
- Control point
- A versioned switch that decides which version of your code a user runs. Fireweave mints, versions, coordinates, and retires control points so teams do not hand-wire flags per change.
- Rollout
- The unit of shipping in Fireweave: advancing a change through cohorts with evidence of stability and adoption, rather than treating a merged PR or container deploy as “done.”
- Rollout-ready
- A change that leaves the coding agent already wrapped at a control point, with ship-safe instructions and adoption telemetry wired — ready for cohort ramps without a separate release checklist.
- Cohort
- A slice of traffic or users that receives a new version during a ramp. Fireweave advances only when each cohort proves stability and adoption.
- Guardrail
- A monitored threshold on stability or adoption signals that can pause or auto-revert a rollout when metrics dip — so rollback is a control-point flip, not a war room.
- Adoption signal
- Live evidence that users are exercising the new behavior in production. Fireweave uses adoption alongside stability so silent “green” metrics do not advance a ramp alone.
- Coding agent
- An AI-assisted development tool (for example Cursor, Claude Code, Codex, OpenCode, or Cline) that writes or edits code. Fireweave installs ship-safe skills so agent-built changes are born rollout-ready.
- Promote, not wrap
- Fireweave’s client path: features ship already rollout-ready from the agent workflow. Promotion advances an existing package; post-hoc wrapping after the feature is built is not the intended path.