Dependencies and Impact Analysis
Typed cross-object dependencies, prerequisites and constraints with scope and evidence. Does not imply automatic causality.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseWRK
- Industry
- Cross-industry
- Tags
- EM-WRK-06W2subjectDependencyDependencyTypeCriticalityAssessmentImpactScenarioDependencyEvidence
What it is Filled
Typed cross-object dependencies, prerequisites and constraints with scope and evidence. Does not imply automatic causality.
Why it exists Filled
Typed cross-object dependencies, prerequisites and constraints with scope and evidence. Does not imply automatic causality.
Distinguishing features Derived, awaiting review
- Type and direction are mandatory
- A cycle is allowed only under the rules of the specific type
- The absence of an edge does not prove independence
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: Any path in the graph is declared a proven causal chain.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
PMO / руководитель исполнения
Master systems
- Трекер задач
- PPM
- планы и протоколы приёмки
Links to other meta-models Filled
neighbor
- EM-TEC-01
- EM-TEC-04
- EM-WRK-01
- EM-WRK-02
references
- WM-XCT-037 - conceptual-candidate
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Derived, awaiting review
- Dependency
- DependencyType
- CriticalityAssessment
- ImpactScenario
- DependencyEvidence
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- 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
Open questions
- Which edges permit transitivity?
- How are blocking, usage, funding and a causal claim distinguished?
- How is graph incompleteness accounted for in impact analysis?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-wrk-06/brief.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.