`flight-item-type`

A class of work item that flows through the organization — e.g. a standard order, a custom order, an innovation increment. It defines what a kind of work is, not an individual item.

Serialized type: flight-item-type

Frontmatter

Field	Required	Format	Meaning
`type`	yes	`flight-item-type`	Entity type
`uses-route`	no	wikilink	The flight route items of this type travel

Plus the shared optionals from conventions.

Relationships

uses-route — the flight route items of this type travel. The route points back with its for: key, making the pair bidirectional: the item type names its route, the route names its primary item type.
Route stages — in addition to the uses-route / for: pair, every route whose stages link this item type ([[Feature]] @ Train) references it. A stage written as text (feature @ Train) does not — see the flight route page.

Body

Free Markdown. Answer four standard questions as ## headings:

Where do Flight Items of this type come from?
Why are you working on these? What is the customer value?
To whom is the finished Flight Item delivered?
How long does it take?

Example

---
type: flight-item-type
uses-route: "[[Standard Order Fulfillment]]"
---
## Where do Flight Items of this type come from?

Customer places an order for a standard configuration (3P / 4P / 5P) via the Sales channel.

## Why are you working on these? What is the customer value?

Core revenue stream — standard drones are the predictable, repeatable business that
funds custom and innovation work.

## To whom is the finished Flight Item delivered?

Customer receives an assembled, tested drone with documentation.

## How long does it take?

Year-1 baseline: 2–4 weeks. Year-5 reality: 4–6 weeks.

Reading it

The question: what kind of work is this: where does it come from, why is it worth doing, to whom does it go, and how long does it take?
Look first: the four question headings in the body.
Go next: via uses-route to the flight route items of this type travel.
Backlinks: the route whose for: names it, and every route whose stages link it as a wikilink ([[Feature]] @ Train); a stage written as text does not count.
Pictured in: the flight route, as the item type of its stages. A board lane named after the type is just a named lane, not a link to it.

Notes

The four-question structure is a convention, not enforced.
A flight route names its primary flight-item-type in its for: key as a wikilink (e.g. for: "[[Standard Order]]"); the item type points back with uses-route. Inside a route’s path:, a stage references this item type only as a wikilink ("[[Standard Order]] @ Sales"); a plain token (order, contract, …) is a description local to that route — never looked up, never an error.

Like what you see? → Start — build your own org folder in ~2 min

# `flight-item-type`

> A *class* of work item that flows through the organization — e.g. a standard order, a
> custom order, an innovation increment. It defines what a kind of work *is*, not an
> individual item.

**Serialized `type`:** `flight-item-type`

## Frontmatter

| Field | Required | Format | Meaning |
|---|---|---|---|
| `type` | yes | `flight-item-type` | Entity type |
| `uses-route` | no | wikilink | The [flight route](flight-route.md) items of this type travel |

Plus the shared optionals from [conventions](../conventions.md).

## Relationships

- **`uses-route`** — the [flight route](flight-route.md) items of this type travel. The
  route points back with its `for:` key, making the pair bidirectional: the item type
  names its route, the route names its primary item type.
- **Route stages** — in addition to the `uses-route` / `for:` pair, every route whose
  **stages** link this item type (`[[Feature]] @ Train`) references it. A stage written as
  text (`feature @ Train`) does not — see the [flight route](flight-route.md) page.

## Body

Free Markdown. Answer four standard questions as `##` headings:

1. **Where do Flight Items of this type come from?**
2. **Why are you working on these? What is the customer value?**
3. **To whom is the finished Flight Item delivered?**
4. **How long does it take?**

## Example

```markdown
---
type: flight-item-type
uses-route: "[[Standard Order Fulfillment]]"
---
## Where do Flight Items of this type come from?

Customer places an order for a standard configuration (3P / 4P / 5P) via the Sales channel.

## Why are you working on these? What is the customer value?

Core revenue stream — standard drones are the predictable, repeatable business that
funds custom and innovation work.

## To whom is the finished Flight Item delivered?

Customer receives an assembled, tested drone with documentation.

## How long does it take?

Year-1 baseline: 2–4 weeks. Year-5 reality: 4–6 weeks.
```

## Reading it

- **The question:** what kind of work is this: where does it come from, why is it worth
  doing, to whom does it go, and how long does it take?
- **Look first:** the four question headings in the body.
- **Go next:** via `uses-route` to the flight route items of this type travel.
- **Backlinks:** the route whose `for:` names it, and every route whose stages link it as a
  wikilink (`[[Feature]] @ Train`); a stage written as text does not count.
- **Pictured in:** the flight route, as the item type of its stages. A board lane named
  after the type is just a named lane, not a link to it.

## Notes

- The four-question structure is a convention, not enforced.
- A [flight route](flight-route.md) names its primary flight-item-type in its `for:` key
  as a wikilink (e.g. `for: "[[Standard Order]]"`); the item type points back with
  `uses-route`. Inside a route's `path:`, a stage references this item type only as a
  wikilink (`"[[Standard Order]] @ Sales"`); a plain token (`order`, `contract`, …) is a
  description local to that route — never looked up, never an error.