← Back to docs

Concepts

Every FreeRide project is made of the same few parts. Your agents create and keep most of them up to date as you work, and you can see and change all of them on the dashboard.

Projects and workspaces

A project is one thing you're building or running: an app, a client, a pipeline, a launch. Each has its own areas, ideas, decisions, docs and history. A repo is linked to one project, and a chat can work with any of yours.

A workspace is a team. Its projects are shared with everyone in it, and each member's agent works from the same record. Projects you keep to yourself are personal. See Teams & Workspaces →.

The Focus

The project's direction for now, in one to three plain lines: the goal of this phase, what matters most on the way, and what ends it. It shows on Home, and every agent reads it first.

It's direction, not status, so it changes only when the direction does. As work goes on, FreeRide asks your agent whether it still holds, and the agent keeps your goal if you wrote it. You can change it any time.

Areas

An area is a lasting place in the project where work happens and knowledge builds up: a product part, a client, a pipeline, marketing. Work, ideas, decisions, docs and waits belong to an area, or to the project as a whole.

  • Stage. Where the area is in its life: Backlog, Planned, Building, Review, Live, and Archived or Canceled when it ends. It changes at real milestones. Live means in real use, and work goes on in a live area without reopening it.
  • Active or Quiet. FreeRide works this out for you: Active when there's been work in the last 14 days, Quiet otherwise.
  • Parts. An area can hold parts, one level deep, like Marketing with Brand and Landing Page under it.

An area doesn't end when a piece of work in it does. A game's Promotion area lasts as long as the game. A launch campaign inside it is a plan, done when the campaign is, and the area carries on. Areas don't have dates; planned work does.

Notes on where it stands

A short note on where something is now: what's happening, what's next and who's on it. Every area has one at the top of its page, and every plan has one too.

Agents rewrite the note when their work changes the picture, and FreeRide reminds them when it falls behind. You can write or edit it yourself, and agents keep your words unless the work changes them. Earlier versions are kept.

Ideas

Ideas, planned items, plans and steps are one kind of record at different stages. Item is the word for any of them.

An idea is something worth doing, captured as it comes up in conversation. It belongs to an area or to the project, and has a priority. It stays open until it's done or dismissed, and once it's done, it links to the work that finished it.

Every idea has a short number, your project's letters and a count like FR-142, that stays the same from backlog to done. Say "continue FR-142" to any agent.

Planned items

The backlog can be long and loose: anything worth keeping, with no promise to do it. An idea becomes a planned item when you decide to do it, now or later. Planned items show on Planned and Home, apart from the backlog.

  • They're the agenda. Agents bring up planned items first when they catch up, and ask how you'd like to go on. Ideas get a short mention, most important first.
  • They can carry a date for when it matters, but only one you gave. Agents bring it up as the day gets close, and ask once it has passed. Ideas don't get dates.
  • They show when work has started, and how long since anything happened. An item is marked started when work is logged on it, when a box in its checklist is ticked, or when you or your agent say so. It stays planned until it's done.
  • Bigger work can become a plan with steps (below).

Work done in one go stays one planned item, with its to-dos as a checklist in its description. Agents tick the boxes as their work finishes them.

Plans and steps

A plan is a planned item with steps under it. Work becomes a plan when it happens over separate sessions, waits on someone, or has its own dates or people. It's the shape of the work that decides, not its length: a plan can last three days or three months. Each step is its own item, with its own date and person.

A plan has its own note on where it stands, and its Activity shows the work on it and on its steps. Only planned work has steps; an idea you're still exploring stays an idea.

Waits

A wait is something that can't move until someone or something acts. There are two kinds:

  • Done work that still waits on a deploy, a review, an app store, a client's reply or your OK.
  • Work that can't start or go on until someone sends or decides something: a key, an address, a go-ahead. The wait holds up those items, and one wait can hold up several.

When what's in the way is another item, someone else's or in another plan, the wait waits for that item. It's on whoever is on that item, and it closes by itself when that item is done, so the people it held up are told they can go ahead.

A wait is judged from the side of whoever the item is on. On a teammate's item, something you have to do first is a wait for them, even if you could do it yourself, so their item shows it's held up and they're told when it clears.

A wait can need a person, you or a teammate. It shows under Needs you for them, and their agent gets its full text, so the steps you wrote reach them. A wait stays open until someone closes it, often the work that finishes it, and closing it frees what it held up. Until then, every new session and catch-up shows it. See Waiting →.

Work

A piece of work is the record of something done: what changed and why, logged by the agent at a real stopping point and tagged to its area. When you ask for changes to work just logged, they're added to the same piece of work as an update, so each piece tells one story.

An item's progress shows in its Activity: the work logged on it and, for a plan, its steps. Its description keeps what the work doesn't show, like the goal and what was learned.

Decisions

A decision is a choice that matters, with its reasoning: the answer to "why did we do it this way?". Each has a short number too, like FR-D12: say "per D12" to your agent. The team can pin the ones that matter most.

When a new decision changes an old one, the old one is marked replaced and points to the new one. One that no longer holds and has no replacement is retired. Neither is deleted: they're kept as history, and agents don't treat them as current.

Docs

A doc is a page of the project's knowledge, in Markdown, that people and agents write and edit together. Each has a type: overview, implementation, architecture, guide, plan, UX flow or vision.

A doc is one of two kinds:

  • Kept current: says how things work now. When agents change something, FreeRide shows them the docs that mention it, anywhere in the project, so they can update what's no longer true.
  • Dated: a plan, a design or research, marked As of its date. It follows what you agree, and is marked replaced or retired once it's built or dropped.

Links written into work, ideas, decisions and waits are gathered by area on Links. The team can pin the ones it keeps opening, and pinned links show on Home.

Sessions

In a coding app, a session is one conversation's stretch of work in a project. It starts with a briefing on where the project stands and ends with a summary of what happened, so the next conversation picks up from there. Chat apps don't use sessions: they catch up on a project and save to it.

Coming from Linear or Jira

The same work, in FreeRide's words:

In a trackerIn FreeRide
A project with an endA plan, inside the area it belongs to
An ongoing project (maintenance, evergreen)An area
An issue, a sub-issueAn idea or planned item, a step
A project updateThe note on where it stands
Blocked by something outside the work: a reply, a key, an approvalA wait that holds up the item
Blocked by another issueA wait that waits for the other item; it closes by itself when that item is done. Inside your own plan, the plan's text says the order
Done, but waiting on a deploy or a reviewA wait left by the work, closed when it happens
Sprints, cyclesNone: planned items carry a date when it matters