EM-WRK-05 · Subject model · W2
Capacity and Resource Allocation
Demand, available capacity and assignments of human and other resources to work. Human engagement, money and compute have different units.
Partially published; research continues
Claude: complete-initial-study-plus-single-frozen-audit-remediated; Grok: complete-reconciled.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- ResourceDemand
- ResourcePool
- CapacityPlan
- ResourceAllocation
- AllocationScenario
Deep research questions
- How are a competency demand and available capacity matched?
- How are shared teams and indivisible resources accounted for?
- When is exceeding 100% an error, and when different scenarios?
Verifiable invariants
- Units and a calendar are mandatory
- A plan does not substitute for the actuals
- A conflict is checked within one scenario and interval
End-to-end acceptance scenario
Two projects compete for one specialist and a GPU pool; the plan surfaces the overlap without changing the employment terms.
Negative case
FTE, GPU hours and a money budget are summed into one capacity.
Approaches to compare
- PMI: project/program/portfolio
- Process-based and flow-based organization of work; compare Scrum/Kanban against primary sources
- Tracker object practice: container, issue, workflow and binding to the business initiative
Candidates in the live catalogue
- WM-ORG-016 · Work Assignment · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-ECO-012 · Budget · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.