EM-WRK-01 · Subject model · W1
Work Items and Delivery Flow
Tasks and typed work items, backlog, iterations, workflow, estimates and completion criteria. Jira types are adapters, not a universal ontology.
Partially published; research continues
Claude: complete-frozen-study-and-single-audit-remediated; Grok: complete-exact-prompt-after-two-provider-failures.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- WorkItem
- WorkItemType
- WorkflowDefinition
- Transition
- Backlog
- Iteration
- Estimate
Deep research questions
- When is an Epic/Feature a work item, and when a product requirement?
- How is meaning preserved across different source workflows?
- Which statuses genuinely evidence an accepted result?
Verifiable invariants
- Done is defined by criteria and evidence
- A tracker container is not a project
- An effort estimate is not actual time
End-to-end acceptance scenario
Move tasks between two workflows while keeping cancelled, rejected and accepted as distinct outcomes; a repeated import does not duplicate tasks.
Negative case
All Closed statuses automatically mean a completed and accepted result.
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-ACT-006 · Task · 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.