Execution control
ImplementedBound work to durable intent, ownership, decisions, evidence, review, and promotion state.
Tasks · sessions · checkpoints · evidence · reviews
Fairway
Engineering continuity and control
Keep agent-driven engineering governed, resumable, and reviewable across providers, tools, and time. Fairway connects execution records, working memory, project knowledge, reusable rules, and promotion evidence without taking authority from the systems that perform the work.
Local-first and provider-neutral. Fairway records control state; it does not become your source-control, CI, identity, or deployment authority.
One durable engineering record
Control today's work. Preserve what the next agent needs.
Fairway begins with accountable execution and extends into continuity, operating knowledge, and evidence-backed assurance. Each layer has a distinct job and an explicit authority boundary.
Engineering continuity
ImplementedResume after context loss or provider replacement without making chat history the system of record.
Track memory · cold starts · handoffs · waitsOperating knowledge
ImplementedCarry source-grounded project knowledge and reusable engineering rules across work items.
Knowledge packets · rule packs · provenance · freshnessAssurance and profiles
Implemented + plannedMap recorded facts to bounded readiness claims, then compose them into specialized execution profiles.
Assurance profiles implemented · migration profile plannedThe control path
From declared intent to explicit promotion
The same accountability chain applies whether one agent handles a small fix or several providers execute a long-running program.
Declare intent
Define the task, scope, risk, owner, and authority boundary before implementation starts.
Record decisions
Keep material choices and deviations durable without treating provider transcripts as provenance.
Attach evidence
Link tests, CI, environment proof, and artifacts to the work they support.
Apply judgment
Route independent review according to risk and retain findings, not just approval status.
Promote explicitly
Make merge, release, deploy, and live-operation boundaries visible without granting them to Fairway.
Operational readback
See work, waits, evidence, and review state without turning the dashboard into a control console.
The read-only dashboard projects the same Fairway record used by the CLI, memory packets, and knowledge queries. Mutating work stays in trusted command and provider surfaces with explicit policy checks.
First value in minutes
Start with one bounded result, not the whole operating model.
Initialize Fairway in a clean repository, start one task, attach passing evidence, verify the boundary, and close the work. Add lanes, watchers, shared views, and policy profiles only when the project needs them.
Install the current releaseOpen the five-minute path
brew tap fairway-run/tap
brew install --cask fairway
fairway version