---
slug: "ResourceShapeSeparation"
name: "ResourceShapeSeparation"
type: "Coordination"
layer: "Society"
ref: "ResourceShapeSeparation#a134"
sema_id: "sema:ResourceShapeSeparation#mh:SHA-256:a134b6a1aba900011db79661ee8a6c3cb9a4cc1e0da8ff78e1286afc9954a657"
tags: ["Society","Coordination"]
updated: 2026-11-11
mindscape: "origin-of-risk"
index_url: https://mindscape.pages.dev/origin-of-risk/index.json
url: https://mindscape.pages.dev/origin-of-risk/ResourceShapeSeparation/
related: ["InformationDividend","Laterality","ShapeControl","BalancedScopeChange","VectorOptionTimeline"]
---

# ResourceShapeSeparation

Predict resources over the long range, and leave the shape of the work free to follow short-range information

Layer: Society · Category: Coordination

## Mechanism

A plan such as a Gantt chart merges two different predictions: how much resource the work will need, and exactly which tasks will use it, when and in what order. The first can be forecast accurately over the long range, like total rainfall for a month. The second is like which days it will rain: it is best decided close to the moment, on reliable short-range information, to collect the [InformationDividend](https://mindscape.pages.dev/origin-of-risk/InformationDividend.md). Fixing both up front locks in [ShapeControl](https://mindscape.pages.dev/origin-of-risk/ShapeControl.md) and also fails at its own aim: the more teams a rigid schedule needs at fixed times, the higher its [Laterality](https://mindscape.pages.dev/origin-of-risk/Laterality.md) and the more certain that some team will be unavailable when needed, so the 'irresistible force' of the plan meets the 'immovable object' of an operational constraint. Separate the two: commit to resource forecasts, keep task order and timing open within them, and communicate priorities as options rather than fixed slots.

## Invariants

- Long-range commitments concern resources, not the detailed order of tasks
- Task choices are taken as late as reliable short-range information allows
- Forecast accuracy and flexibility of shape are not in conflict

## Failure modes

- Locking the schedules of many teams to fixed dates, so the plan fails at its own goal of securing resources
- Treating flexibility as a sign of poor forecasting
- Over-planning detail that does not affect resource needs

## Builds on

- [InformationDividend](https://mindscape.pages.dev/origin-of-risk/InformationDividend.md) (Mind; References)
- [Laterality](https://mindscape.pages.dev/origin-of-risk/Laterality.md) (Society; References)
- [ShapeControl](https://mindscape.pages.dev/origin-of-risk/ShapeControl.md) (Mind; References)

## Used by

- [BalancedScopeChange](https://mindscape.pages.dev/origin-of-risk/BalancedScopeChange.md) (Society; References)
- [VectorOptionTimeline](https://mindscape.pages.dev/origin-of-risk/VectorOptionTimeline.md) (Society; References)

## Identity

- Sema ID: `sema:ResourceShapeSeparation#mh:SHA-256:a134b6a1aba900011db79661ee8a6c3cb9a4cc1e0da8ff78e1286afc9954a657`
- Ref: `ResourceShapeSeparation#a134`

## Links

- [Pattern page](https://mindscape.pages.dev/origin-of-risk/ResourceShapeSeparation/)
- [View in the interactive graph](https://mindscape.pages.dev/origin-of-risk/#ResourceShapeSeparation)
- [JSON](https://mindscape.pages.dev/origin-of-risk/ResourceShapeSeparation.json)
- [Index of all patterns](https://mindscape.pages.dev/origin-of-risk/index.json)