TeamDefinition

@forge/monorepo

---

@forge/monorepo / backend/src / TeamDefinition

Type Alias: TeamDefinition

TeamDefinition = object

Defined in: backend/src/flows/index.ts:208

Properties

budget

readonly budget: FlowBudget

Defined in: backend/src/flows/index.ts:223

---

id

readonly id: string

Defined in: backend/src/flows/index.ts:209

---

manager?

readonly optional manager?: string

Defined in: backend/src/flows/index.ts:222

Required when process is manager-led, and refused otherwise: a sequential team with a manager is ambiguous.

---

maxDelegationDepth?

readonly optional maxDelegationDepth?: number

Defined in: backend/src/flows/index.ts:224

---

members

readonly members: readonly TeamMember[]

Defined in: backend/src/flows/index.ts:220

---

name

readonly name: string

Defined in: backend/src/flows/index.ts:211

---

process

readonly process: TeamProcess

Defined in: backend/src/flows/index.ts:219

Sequential or manager-led, as a property rather than two code paths — #186 AC-2.

The interpreter branches on this in one place: which member runs next. Everything else — budgets, delegation, failure handling, attribution — is identical, which is the point. Two code paths would mean two places for every later property to be added, and one of them would eventually not get it.

---

version

readonly version: number

Defined in: backend/src/flows/index.ts:210