Executive summary
AngelMunoz/Kipo falls short of our standard for production because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 57 out of 100 and is rated Adequate, and all eight of its critical findings are security problems in the build pipeline.
Production Readiness, at 36, is the weakest lens and counts most in the score. The best first step is adding a diagnostic log, worth about 9 points. Adding a release approval comes next, worth about 4 points. Raising Production Readiness to 70 would lift the score to about 72.
Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline. Pinning each tool to an exact version and limiting each secret to its own step would close both risks.
The product code is 24,921 lines, about €32,000 to rebuild.
If Production Readiness rose from 36 to 70, the lowest score rated Strong, the score would rise from 57 to about 72.
Fixed since the last survey: 1 finding
- Code Coverage · Coverage not measured — no coverage collector is wired up
Rebuild cost: about €32,000 · Estimate
| Cost to rebuild | €11,000 to €53,000, for 176 to 560 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 57. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 24,921 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Domain.Action | 2 Domain.Animation | 3 Domain.Core | 4 Domain.Formula | 5 Systems.Systems | 6 Domain.Camera | 7 Domain.Entity | 8 Domain.Orbital | 9 Domain.Projectile | 10 Domain.Spatial | 11 Domain.Skill | 12 Domain.UI | 13 Domain.AI | 14 Domain.BlockMap | 15 Domain.Item | 16 Domain.Particles | 17 Domain.Scenes | 18 Editor | 19 Graphics | 20 JsonFileLoader | 21 Stores | 22 Domain.Events.SystemCommunications | 23 Rendering | 24 Domain.Events | 25 Systems.AIContext | 26 Domain.World | 27 EventBus | 28 Projections | 29 Projections.DerivedStatsCalculator | 30 UI | 31 Environment | 32 Systems.HUDComponents | 33 Systems.AbilityActivation | 34 Systems.Combat | 35 Systems.EntitySpawnerLogic | 36 Systems.HoverFeedback | 37 Systems.Navigation3D | 38 Systems.Projectile | 39 Systems.StateWrite | 40 Systems.Targeting |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Domain.Action | ||||||||||||||||||||||||||||||||||||||||
| 2 Domain.Animation | ||||||||||||||||||||||||||||||||||||||||
| 3 Domain.Core | ||||||||||||||||||||||||||||||||||||||||
| 4 Domain.Formula | ||||||||||||||||||||||||||||||||||||||||
| 5 Systems.Systems | ||||||||||||||||||||||||||||||||||||||||
| 6 Domain.Camera | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 Domain.Entity | 2 | |||||||||||||||||||||||||||||||||||||||
| 8 Domain.Orbital | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 Domain.Projectile | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 Domain.Spatial | 4 | |||||||||||||||||||||||||||||||||||||||
| 11 Domain.Skill | 7 | 3 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 12 Domain.UI | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 Domain.AI | 4 | 2 | ||||||||||||||||||||||||||||||||||||||
| 14 Domain.BlockMap | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 Domain.Item | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 Domain.Particles | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 Domain.Scenes | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 Editor | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 19 Graphics | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 JsonFileLoader | 2 | 1 | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 21 Stores | 2 | 1 | 5 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 22 Domain.Events.SystemCommunications | 1 | 2 | 2 | 3 | 1 | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 23 Rendering | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 Domain.Events | 2 | 2 | 4 | 1 | 1 | 24 | ||||||||||||||||||||||||||||||||||
| 25 Systems.AIContext | 1 | 2 | 1 | 4 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 26 Domain.World | 3 | 1 | 3 | 4 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||||
| 27 EventBus | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 Projections | 2 | 7 | 4 | 2 | 1 | 5 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 29 Projections.DerivedStatsCalculator | 2 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 30 UI | 1 | 1 | 1 | 5 | ||||||||||||||||||||||||||||||||||||
| 31 Environment | 2 | 1 | 4 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 2 | 9 | 1 | 2 | 3 | 1 | 1 | |||||||||||||||||||||||
| 32 Systems.HUDComponents | 2 | 2 | 1 | 4 | 1 | 1 | 2 | 2 | 2 | 1 | 2 | |||||||||||||||||||||||||||||
| 33 Systems.AbilityActivation | 2 | 1 | 1 | 2 | 2 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 34 Systems.Combat | 1 | 2 | 2 | 1 | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 35 Systems.EntitySpawnerLogic | 1 | 2 | 1 | 1 | 1 | 1 | 3 | 3 | 2 | |||||||||||||||||||||||||||||||
| 36 Systems.HoverFeedback | 1 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 37 Systems.Navigation3D | 3 | 2 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 38 Systems.Projectile | 1 | 4 | 1 | 2 | 1 | 1 | 2 | 3 | 1 | 2 | ||||||||||||||||||||||||||||||
| 39 Systems.StateWrite | 2 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 4 | 1 | |||||||||||||||||||||||||||
| 40 Systems.Targeting | 1 | 1 | 2 | 1 | 2 | 1 | 3 |
6→3 Domain.Camera uses Domain.Core✕
- Connections
- 1 pair of types, where a type in Domain.Camera uses a type in Domain.Core.
- The types involved
Pomo.Core.Domain.Camera.CameraService→Pomo.Core.Domain.Core.WorldPosition
- Direction
- Domain.Camera uses Domain.Core, so a change to Domain.Core can break Domain.Camera, while a change to Domain.Camera can't break Domain.Core.
- Position
- Below the diagonal: Domain.Camera uses a module listed above it, which is the healthy direction.
7→3 Domain.Entity uses Domain.Core✕
- Connections
- 2 pairs of types, where a type in Domain.Entity uses a type in Domain.Core.
- The types involved
Pomo.Core.Domain.Entity.DerivedStats→Pomo.Core.Domain.Core.ElementPomo.Core.Domain.Entity.EntitySnapshot→Pomo.Core.Domain.Core.WorldPosition
- Direction
- Domain.Entity uses Domain.Core, so a change to Domain.Core can break Domain.Entity, while a change to Domain.Entity can't break Domain.Core.
- Position
- Below the diagonal: Domain.Entity uses a module listed above it, which is the healthy direction.
8→3 Domain.Orbital uses Domain.Core✕
- Connections
- 1 pair of types, where a type in Domain.Orbital uses a type in Domain.Core.
- The types involved
Pomo.Core.Domain.Orbital.OrbitalConfig→Pomo.Core.Domain.Core.VisualManifest
- Direction
- Domain.Orbital uses Domain.Core, so a change to Domain.Core can break Domain.Orbital, while a change to Domain.Orbital can't break Domain.Core.
- Position
- Below the diagonal: Domain.Orbital uses a module listed above it, which is the healthy direction.
9→3 Domain.Projectile uses Domain.Core✕
- Connections
- 1 pair of types, where a type in Domain.Projectile uses a type in Domain.Core.
- The types involved
Pomo.Core.Domain.Projectile.ProjectileInfo→Pomo.Core.Domain.Core.VisualManifest
- Direction
- Domain.Projectile uses Domain.Core, so a change to Domain.Core can break Domain.Projectile, while a change to Domain.Projectile can't break Domain.Core.
- Position
- Below the diagonal: Domain.Projectile uses a module listed above it, which is the healthy direction.
10→3 Domain.Spatial uses Domain.Core✕
- Connections
- 4 pairs of types, where a type in Domain.Spatial uses a type in Domain.Core.
- The types involved
Pomo.Core.Domain.Spatial.Cone3D→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Domain.Spatial.Cylinder→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Domain.Spatial.Spatial→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Domain.Spatial.Sphere→Pomo.Core.Domain.Core.WorldPosition
- Direction
- Domain.Spatial uses Domain.Core, so a change to Domain.Core can break Domain.Spatial, while a change to Domain.Spatial can't break Domain.Core.
- Position
- Below the diagonal: Domain.Spatial uses a module listed above it, which is the healthy direction.
11→3 Domain.Skill uses Domain.Core✕
- Connections
- 7 pairs of types, where a type in Domain.Skill uses a type in Domain.Core.
- The types involved
Pomo.Core.Domain.Skill.ActiveSkill→Pomo.Core.Domain.Core.VisualManifestPomo.Core.Domain.Skill.ChargeConfig→Pomo.Core.Domain.Core.VisualManifestPomo.Core.Domain.Skill.Effect→Pomo.Core.Domain.Core.VisualManifestPomo.Core.Domain.Skill.EffectModifier→Pomo.Core.Domain.Core.ElementPomo.Core.Domain.Skill.EffectModifier→Pomo.Core.Domain.Core.StatPomo.Core.Domain.Skill.EffectModifier→Pomo.Core.Domain.Core.StatModifierPomo.Core.Domain.Skill.ElementFormula→Pomo.Core.Domain.Core.Element
- Direction
- Domain.Skill uses Domain.Core, so a change to Domain.Core can break Domain.Skill, while a change to Domain.Skill can't break Domain.Core.
- Position
- Below the diagonal: Domain.Skill uses a module listed above it, which is the healthy direction.
11→4 Domain.Skill uses Domain.Formula✕
- Connections
- 3 pairs of types, where a type in Domain.Skill uses a type in Domain.Formula.
- The types involved
Pomo.Core.Domain.Skill.ActiveSkill→Pomo.Core.Domain.Formula.MathExprPomo.Core.Domain.Skill.EffectModifier→Pomo.Core.Domain.Formula.MathExprPomo.Core.Domain.Skill.ElementFormula→Pomo.Core.Domain.Formula.MathExpr
- Direction
- Domain.Skill uses Domain.Formula, so a change to Domain.Formula can break Domain.Skill, while a change to Domain.Skill can't break Domain.Formula.
- Position
- Below the diagonal: Domain.Skill uses a module listed above it, which is the healthy direction.
11→7 Domain.Skill uses Domain.Entity✕
- Connections
- 2 pairs of types, where a type in Domain.Skill uses a type in Domain.Entity.
- The types involved
Pomo.Core.Domain.Skill.EffectModifier→Pomo.Core.Domain.Entity.ResourceTypePomo.Core.Domain.Skill.ResourceCost→Pomo.Core.Domain.Entity.ResourceType
- Direction
- Domain.Skill uses Domain.Entity, so a change to Domain.Entity can break Domain.Skill, while a change to Domain.Skill can't break Domain.Entity.
- Position
- Below the diagonal: Domain.Skill uses a module listed above it, which is the healthy direction.
11→8 Domain.Skill uses Domain.Orbital✕
- Connections
- 1 pair of types, where a type in Domain.Skill uses a type in Domain.Orbital.
- The types involved
Pomo.Core.Domain.Skill.ChargeConfig→Pomo.Core.Domain.Orbital.OrbitalConfig
- Direction
- Domain.Skill uses Domain.Orbital, so a change to Domain.Orbital can break Domain.Skill, while a change to Domain.Skill can't break Domain.Orbital.
- Position
- Below the diagonal: Domain.Skill uses a module listed above it, which is the healthy direction.
11→9 Domain.Skill uses Domain.Projectile✕
- Connections
- 1 pair of types, where a type in Domain.Skill uses a type in Domain.Projectile.
- The types involved
Pomo.Core.Domain.Skill.Delivery→Pomo.Core.Domain.Projectile.ProjectileInfo
- Direction
- Domain.Skill uses Domain.Projectile, so a change to Domain.Projectile can break Domain.Skill, while a change to Domain.Skill can't break Domain.Projectile.
- Position
- Below the diagonal: Domain.Skill uses a module listed above it, which is the healthy direction.
12→7 Domain.UI uses Domain.Entity✕
- Connections
- 1 pair of types, where a type in Domain.UI uses a type in Domain.Entity.
- The types involved
Pomo.Core.Domain.UI.IHUDService→Pomo.Core.Domain.Entity.Faction
- Direction
- Domain.UI uses Domain.Entity, so a change to Domain.Entity can break Domain.UI, while a change to Domain.UI can't break Domain.Entity.
- Position
- Below the diagonal: Domain.UI uses a module listed above it, which is the healthy direction.
13→7 Domain.AI uses Domain.Entity✕
- Connections
- 4 pairs of types, where a type in Domain.AI uses a type in Domain.Entity.
- The types involved
Pomo.Core.Domain.AI.AIArchetype→Pomo.Core.Domain.Entity.BaseStatsPomo.Core.Domain.AI.AIEntityDefinition→Pomo.Core.Domain.Entity.BaseStatsPomo.Core.Domain.AI.AIEntityDefinition→Pomo.Core.Domain.Entity.FamilyPomo.Core.Domain.AI.MapEntityGroup→Pomo.Core.Domain.Entity.Faction
- Direction
- Domain.AI uses Domain.Entity, so a change to Domain.Entity can break Domain.AI, while a change to Domain.AI can't break Domain.Entity.
- Position
- Below the diagonal: Domain.AI uses a module listed above it, which is the healthy direction.
13→11 Domain.AI uses Domain.Skill✕
- Connections
- 2 pairs of types, where a type in Domain.AI uses a type in Domain.Skill.
- The types involved
Pomo.Core.Domain.AI.AIController→Pomo.Core.Domain.Skill.SkillIntentPomo.Core.Domain.AI.AIFamilyConfig→Pomo.Core.Domain.Skill.SkillIntent
- Direction
- Domain.AI uses Domain.Skill, so a change to Domain.Skill can break Domain.AI, while a change to Domain.AI can't break Domain.Skill.
- Position
- Below the diagonal: Domain.AI uses a module listed above it, which is the healthy direction.
14→3 Domain.BlockMap uses Domain.Core✕
- Connections
- 1 pair of types, where a type in Domain.BlockMap uses a type in Domain.Core.
- The types involved
Pomo.Core.Domain.BlockMap.MapObject→Pomo.Core.Domain.Core.WorldPosition
- Direction
- Domain.BlockMap uses Domain.Core, so a change to Domain.Core can break Domain.BlockMap, while a change to Domain.BlockMap can't break Domain.Core.
- Position
- Below the diagonal: Domain.BlockMap uses a module listed above it, which is the healthy direction.
14→7 Domain.BlockMap uses Domain.Entity✕
- Connections
- 1 pair of types, where a type in Domain.BlockMap uses a type in Domain.Entity.
- The types involved
Pomo.Core.Domain.BlockMap.SpawnProperties→Pomo.Core.Domain.Entity.Faction
- Direction
- Domain.BlockMap uses Domain.Entity, so a change to Domain.Entity can break Domain.BlockMap, while a change to Domain.BlockMap can't break Domain.Entity.
- Position
- Below the diagonal: Domain.BlockMap uses a module listed above it, which is the healthy direction.
14→10 Domain.BlockMap uses Domain.Spatial✕
- Connections
- 2 pairs of types, where a type in Domain.BlockMap uses a type in Domain.Spatial.
- The types involved
Pomo.Core.Domain.BlockMap.BlockMapDefinition→Pomo.Core.Domain.Spatial.GridCell3DPomo.Core.Domain.BlockMap.PlacedBlock→Pomo.Core.Domain.Spatial.GridCell3D
- Direction
- Domain.BlockMap uses Domain.Spatial, so a change to Domain.Spatial can break Domain.BlockMap, while a change to Domain.BlockMap can't break Domain.Spatial.
- Position
- Below the diagonal: Domain.BlockMap uses a module listed above it, which is the healthy direction.
14→11 Domain.BlockMap uses Domain.Skill✕
- Connections
- 1 pair of types, where a type in Domain.BlockMap uses a type in Domain.Skill.
- The types involved
Pomo.Core.Domain.BlockMap.BlockType→Pomo.Core.Domain.Skill.Effect
- Direction
- Domain.BlockMap uses Domain.Skill, so a change to Domain.Skill can break Domain.BlockMap, while a change to Domain.BlockMap can't break Domain.Skill.
- Position
- Below the diagonal: Domain.BlockMap uses a module listed above it, which is the healthy direction.
15→3 Domain.Item uses Domain.Core✕
- Connections
- 1 pair of types, where a type in Domain.Item uses a type in Domain.Core.
- The types involved
Pomo.Core.Domain.Item.EquipmentProperties→Pomo.Core.Domain.Core.StatModifier
- Direction
- Domain.Item uses Domain.Core, so a change to Domain.Core can break Domain.Item, while a change to Domain.Item can't break Domain.Core.
- Position
- Below the diagonal: Domain.Item uses a module listed above it, which is the healthy direction.
15→11 Domain.Item uses Domain.Skill✕
- Connections
- 1 pair of types, where a type in Domain.Item uses a type in Domain.Skill.
- The types involved
Pomo.Core.Domain.Item.UsabilityProperties→Pomo.Core.Domain.Skill.Effect
- Direction
- Domain.Item uses Domain.Skill, so a change to Domain.Skill can break Domain.Item, while a change to Domain.Item can't break Domain.Skill.
- Position
- Below the diagonal: Domain.Item uses a module listed above it, which is the healthy direction.
16→11 Domain.Particles uses Domain.Skill✕
- Connections
- 1 pair of types, where a type in Domain.Particles uses a type in Domain.Skill.
- The types involved
Pomo.Core.Domain.Particles.EffectOverrides→Pomo.Core.Domain.Skill.SkillArea
- Direction
- Domain.Particles uses Domain.Skill, so a change to Domain.Skill can break Domain.Particles, while a change to Domain.Particles can't break Domain.Skill.
- Position
- Below the diagonal: Domain.Particles uses a module listed above it, which is the healthy direction.
17→14 Domain.Scenes uses Domain.BlockMap✕
- Connections
- 1 pair of types, where a type in Domain.Scenes uses a type in Domain.BlockMap.
- The types involved
Pomo.Core.Domain.Scenes.Scene→Pomo.Core.Domain.BlockMap.BlockMapDefinition
- Direction
- Domain.Scenes uses Domain.BlockMap, so a change to Domain.BlockMap can break Domain.Scenes, while a change to Domain.Scenes can't break Domain.BlockMap.
- Position
- Below the diagonal: Domain.Scenes uses a module listed above it, which is the healthy direction.
18→10 Editor uses Domain.Spatial✕
- Connections
- 2 pairs of types, where a type in Editor uses a type in Domain.Spatial.
- The types involved
Pomo.Core.Editor.EditorAction→Pomo.Core.Domain.Spatial.GridCell3DPomo.Core.Editor.EditorState→Pomo.Core.Domain.Spatial.GridCell3D
- Direction
- Editor uses Domain.Spatial, so a change to Domain.Spatial can break Editor, while a change to Editor can't break Domain.Spatial.
- Position
- Below the diagonal: Editor uses a module listed above it, which is the healthy direction.
18→14 Editor uses Domain.BlockMap✕
- Connections
- 2 pairs of types, where a type in Editor uses a type in Domain.BlockMap.
- The types involved
Pomo.Core.Editor.EditorAction→Pomo.Core.Domain.BlockMap.PlacedBlockPomo.Core.Editor.EditorState→Pomo.Core.Domain.BlockMap.BlockMapDefinition
- Direction
- Editor uses Domain.BlockMap, so a change to Domain.BlockMap can break Editor, while a change to Editor can't break Domain.BlockMap.
- Position
- Below the diagonal: Editor uses a module listed above it, which is the healthy direction.
19→16 Graphics uses Domain.Particles✕
- Connections
- 1 pair of types, where a type in Graphics uses a type in Domain.Particles.
- The types involved
Pomo.Core.Graphics.BillboardCommand→Pomo.Core.Domain.Particles.BlendMode
- Direction
- Graphics uses Domain.Particles, so a change to Domain.Particles can break Graphics, while a change to Graphics can't break Domain.Particles.
- Position
- Below the diagonal: Graphics uses a module listed above it, which is the healthy direction.
20→2 JsonFileLoader uses Domain.Animation✕
- Connections
- 2 pairs of types, where a type in JsonFileLoader uses a type in Domain.Animation.
- The types involved
Pomo.Core.JsonFileLoader.JsonFileLoader→Pomo.Core.Domain.Animation.AnimationClipPomo.Core.JsonFileLoader.JsonFileLoader→Pomo.Core.Domain.Animation.ModelConfig
- Direction
- JsonFileLoader uses Domain.Animation, so a change to Domain.Animation can break JsonFileLoader, while a change to JsonFileLoader can't break Domain.Animation.
- Position
- Below the diagonal: JsonFileLoader uses a module listed above it, which is the healthy direction.
20→11 JsonFileLoader uses Domain.Skill✕
- Connections
- 1 pair of types, where a type in JsonFileLoader uses a type in Domain.Skill.
- The types involved
Pomo.Core.JsonFileLoader.JsonFileLoader→Pomo.Core.Domain.Skill.Skill
- Direction
- JsonFileLoader uses Domain.Skill, so a change to Domain.Skill can break JsonFileLoader, while a change to JsonFileLoader can't break Domain.Skill.
- Position
- Below the diagonal: JsonFileLoader uses a module listed above it, which is the healthy direction.
20→13 JsonFileLoader uses Domain.AI✕
- Connections
- 5 pairs of types, where a type in JsonFileLoader uses a type in Domain.AI.
- The types involved
Pomo.Core.JsonFileLoader.JsonFileLoader→Pomo.Core.Domain.AI.AIArchetypePomo.Core.JsonFileLoader.JsonFileLoader→Pomo.Core.Domain.AI.AIEntityDefinitionPomo.Core.JsonFileLoader.JsonFileLoader→Pomo.Core.Domain.AI.AIFamilyConfigPomo.Core.JsonFileLoader.JsonFileLoader→Pomo.Core.Domain.AI.DecisionTreePomo.Core.JsonFileLoader.JsonFileLoader→Pomo.Core.Domain.AI.MapEntityGroup
- Direction
- JsonFileLoader uses Domain.AI, so a change to Domain.AI can break JsonFileLoader, while a change to JsonFileLoader can't break Domain.AI.
- Position
- Below the diagonal: JsonFileLoader uses a module listed above it, which is the healthy direction.
20→15 JsonFileLoader uses Domain.Item✕
- Connections
- 1 pair of types, where a type in JsonFileLoader uses a type in Domain.Item.
- The types involved
Pomo.Core.JsonFileLoader.JsonFileLoader→Pomo.Core.Domain.Item.ItemDefinition
- Direction
- JsonFileLoader uses Domain.Item, so a change to Domain.Item can break JsonFileLoader, while a change to JsonFileLoader can't break Domain.Item.
- Position
- Below the diagonal: JsonFileLoader uses a module listed above it, which is the healthy direction.
20→16 JsonFileLoader uses Domain.Particles✕
- Connections
- 1 pair of types, where a type in JsonFileLoader uses a type in Domain.Particles.
- The types involved
Pomo.Core.JsonFileLoader.JsonFileLoader→Pomo.Core.Domain.Particles.EmitterConfig
- Direction
- JsonFileLoader uses Domain.Particles, so a change to Domain.Particles can break JsonFileLoader, while a change to JsonFileLoader can't break Domain.Particles.
- Position
- Below the diagonal: JsonFileLoader uses a module listed above it, which is the healthy direction.
21→2 Stores uses Domain.Animation✕
- Connections
- 2 pairs of types, where a type in Stores uses a type in Domain.Animation.
- The types involved
Pomo.Core.Stores.AnimationStore→Pomo.Core.Domain.Animation.AnimationClipPomo.Core.Stores.ModelStore→Pomo.Core.Domain.Animation.ModelConfig
- Direction
- Stores uses Domain.Animation, so a change to Domain.Animation can break Stores, while a change to Stores can't break Domain.Animation.
- Position
- Below the diagonal: Stores uses a module listed above it, which is the healthy direction.
21→11 Stores uses Domain.Skill✕
- Connections
- 1 pair of types, where a type in Stores uses a type in Domain.Skill.
- The types involved
Pomo.Core.Stores.SkillStore→Pomo.Core.Domain.Skill.Skill
- Direction
- Stores uses Domain.Skill, so a change to Domain.Skill can break Stores, while a change to Stores can't break Domain.Skill.
- Position
- Below the diagonal: Stores uses a module listed above it, which is the healthy direction.
21→13 Stores uses Domain.AI✕
- Connections
- 5 pairs of types, where a type in Stores uses a type in Domain.AI.
- The types involved
Pomo.Core.Stores.AIArchetypeStore→Pomo.Core.Domain.AI.AIArchetypePomo.Core.Stores.AIEntityStore→Pomo.Core.Domain.AI.AIEntityDefinitionPomo.Core.Stores.AIFamilyStore→Pomo.Core.Domain.AI.AIFamilyConfigPomo.Core.Stores.DecisionTreeStore→Pomo.Core.Domain.AI.DecisionTreePomo.Core.Stores.MapEntityGroupStore→Pomo.Core.Domain.AI.MapEntityGroup
- Direction
- Stores uses Domain.AI, so a change to Domain.AI can break Stores, while a change to Stores can't break Domain.AI.
- Position
- Below the diagonal: Stores uses a module listed above it, which is the healthy direction.
21→15 Stores uses Domain.Item✕
- Connections
- 1 pair of types, where a type in Stores uses a type in Domain.Item.
- The types involved
Pomo.Core.Stores.ItemStore→Pomo.Core.Domain.Item.ItemDefinition
- Direction
- Stores uses Domain.Item, so a change to Domain.Item can break Stores, while a change to Stores can't break Domain.Item.
- Position
- Below the diagonal: Stores uses a module listed above it, which is the healthy direction.
21→16 Stores uses Domain.Particles✕
- Connections
- 1 pair of types, where a type in Stores uses a type in Domain.Particles.
- The types involved
Pomo.Core.Stores.ParticleStore→Pomo.Core.Domain.Particles.EmitterConfig
- Direction
- Stores uses Domain.Particles, so a change to Domain.Particles can break Stores, while a change to Stores can't break Domain.Particles.
- Position
- Below the diagonal: Stores uses a module listed above it, which is the healthy direction.
22→1 Domain.Events.SystemCommunications uses Domain.Action✕
- Connections
- 1 pair of types, where a type in Domain.Events.SystemCommunications uses a type in Domain.Action.
- The types involved
Pomo.Core.Domain.Events.SystemCommunications.SlotActivated→Pomo.Core.Domain.Action.GameAction
- Direction
- Domain.Events.SystemCommunications uses Domain.Action, so a change to Domain.Action can break Domain.Events.SystemCommunications, while a change to Domain.Events.SystemCommunications can't break Domain.Action.
- Position
- Below the diagonal: Domain.Events.SystemCommunications uses a module listed above it, which is the healthy direction.
22→3 Domain.Events.SystemCommunications uses Domain.Core✕
- Connections
- 2 pairs of types, where a type in Domain.Events.SystemCommunications uses a type in Domain.Core.
- The types involved
Pomo.Core.Domain.Events.SystemCommunications.ShowNotification→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Domain.Events.SystemCommunications.SpawnEntityIntent→Pomo.Core.Domain.Core.WorldPosition
- Direction
- Domain.Events.SystemCommunications uses Domain.Core, so a change to Domain.Core can break Domain.Events.SystemCommunications, while a change to Domain.Events.SystemCommunications can't break Domain.Core.
- Position
- Below the diagonal: Domain.Events.SystemCommunications uses a module listed above it, which is the healthy direction.
22→7 Domain.Events.SystemCommunications uses Domain.Entity✕
- Connections
- 2 pairs of types, where a type in Domain.Events.SystemCommunications uses a type in Domain.Entity.
- The types involved
Pomo.Core.Domain.Events.SystemCommunications.FactionSpawnInfo→Pomo.Core.Domain.Entity.FactionPomo.Core.Domain.Events.SystemCommunications.ResourceRestored→Pomo.Core.Domain.Entity.ResourceType
- Direction
- Domain.Events.SystemCommunications uses Domain.Entity, so a change to Domain.Entity can break Domain.Events.SystemCommunications, while a change to Domain.Events.SystemCommunications can't break Domain.Entity.
- Position
- Below the diagonal: Domain.Events.SystemCommunications uses a module listed above it, which is the healthy direction.
22→11 Domain.Events.SystemCommunications uses Domain.Skill✕
- Connections
- 3 pairs of types, where a type in Domain.Events.SystemCommunications uses a type in Domain.Skill.
- The types involved
Pomo.Core.Domain.Events.SystemCommunications.EffectApplicationIntent→Pomo.Core.Domain.Skill.EffectPomo.Core.Domain.Events.SystemCommunications.EffectDamageIntent→Pomo.Core.Domain.Skill.EffectPomo.Core.Domain.Events.SystemCommunications.EffectResourceIntent→Pomo.Core.Domain.Skill.Effect
- Direction
- Domain.Events.SystemCommunications uses Domain.Skill, so a change to Domain.Skill can break Domain.Events.SystemCommunications, while a change to Domain.Events.SystemCommunications can't break Domain.Skill.
- Position
- Below the diagonal: Domain.Events.SystemCommunications uses a module listed above it, which is the healthy direction.
22→13 Domain.Events.SystemCommunications uses Domain.AI✕
- Connections
- 1 pair of types, where a type in Domain.Events.SystemCommunications uses a type in Domain.AI.
- The types involved
Pomo.Core.Domain.Events.SystemCommunications.FactionSpawnInfo→Pomo.Core.Domain.AI.MapEntityOverride
- Direction
- Domain.Events.SystemCommunications uses Domain.AI, so a change to Domain.AI can break Domain.Events.SystemCommunications, while a change to Domain.Events.SystemCommunications can't break Domain.AI.
- Position
- Below the diagonal: Domain.Events.SystemCommunications uses a module listed above it, which is the healthy direction.
22→15 Domain.Events.SystemCommunications uses Domain.Item✕
- Connections
- 3 pairs of types, where a type in Domain.Events.SystemCommunications uses a type in Domain.Item.
- The types involved
Pomo.Core.Domain.Events.SystemCommunications.EquipItemIntent→Pomo.Core.Domain.Item.SlotPomo.Core.Domain.Events.SystemCommunications.PickUpItemIntent→Pomo.Core.Domain.Item.ItemInstancePomo.Core.Domain.Events.SystemCommunications.UnequipItemIntent→Pomo.Core.Domain.Item.Slot
- Direction
- Domain.Events.SystemCommunications uses Domain.Item, so a change to Domain.Item can break Domain.Events.SystemCommunications, while a change to Domain.Events.SystemCommunications can't break Domain.Item.
- Position
- Below the diagonal: Domain.Events.SystemCommunications uses a module listed above it, which is the healthy direction.
22→17 Domain.Events.SystemCommunications uses Domain.Scenes✕
- Connections
- 1 pair of types, where a type in Domain.Events.SystemCommunications uses a type in Domain.Scenes.
- The types involved
Pomo.Core.Domain.Events.SystemCommunications.SceneTransition→Pomo.Core.Domain.Scenes.Scene
- Direction
- Domain.Events.SystemCommunications uses Domain.Scenes, so a change to Domain.Scenes can break Domain.Events.SystemCommunications, while a change to Domain.Events.SystemCommunications can't break Domain.Scenes.
- Position
- Below the diagonal: Domain.Events.SystemCommunications uses a module listed above it, which is the healthy direction.
22→24 Domain.Events.SystemCommunications uses Domain.Events part of a loop✕
- Connections
- 1 pair of types, where a type in Domain.Events.SystemCommunications uses a type in Domain.Events.
- The types involved
Pomo.Core.Domain.Events.SystemCommunications.TargetSelected→Pomo.Core.Domain.Events.Selection
- Direction
- Domain.Events.SystemCommunications uses Domain.Events, so a change to Domain.Events can break Domain.Events.SystemCommunications, while a change to Domain.Events.SystemCommunications can't break Domain.Events.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→3 Rendering uses Domain.Core✕
- Connections
- 1 pair of types, where a type in Rendering uses a type in Domain.Core.
- The types involved
Pomo.Core.Rendering.ParticleRenderData→Pomo.Core.Domain.Core.WorldPosition
- Direction
- Rendering uses Domain.Core, so a change to Domain.Core can break Rendering, while a change to Rendering can't break Domain.Core.
- Position
- Below the diagonal: Rendering uses a module listed above it, which is the healthy direction.
23→9 Rendering uses Domain.Projectile✕
- Connections
- 1 pair of types, where a type in Rendering uses a type in Domain.Projectile.
- The types involved
Pomo.Core.Rendering.EntityRenderData→Pomo.Core.Domain.Projectile.LiveProjectile
- Direction
- Rendering uses Domain.Projectile, so a change to Domain.Projectile can break Rendering, while a change to Rendering can't break Domain.Projectile.
- Position
- Below the diagonal: Rendering uses a module listed above it, which is the healthy direction.
23→14 Rendering uses Domain.BlockMap✕
- Connections
- 1 pair of types, where a type in Rendering uses a type in Domain.BlockMap.
- The types involved
Pomo.Core.Rendering.MapSource→Pomo.Core.Domain.BlockMap.BlockMapDefinition
- Direction
- Rendering uses Domain.BlockMap, so a change to Domain.BlockMap can break Rendering, while a change to Rendering can't break Domain.BlockMap.
- Position
- Below the diagonal: Rendering uses a module listed above it, which is the healthy direction.
23→21 Rendering uses Stores✕
- Connections
- 1 pair of types, where a type in Rendering uses a type in Stores.
- The types involved
Pomo.Core.Rendering.EntityRenderData→Pomo.Core.Stores.ModelStore
- Direction
- Rendering uses Stores, so a change to Stores can break Rendering, while a change to Rendering can't break Stores.
- Position
- Below the diagonal: Rendering uses a module listed above it, which is the healthy direction.
24→1 Domain.Events uses Domain.Action✕
- Connections
- 2 pairs of types, where a type in Domain.Events uses a type in Domain.Action.
- The types involved
Pomo.Core.Domain.Events.EntitySpawnBundle→Pomo.Core.Domain.Action.GameActionPomo.Core.Domain.Events.EntitySpawnBundle→Pomo.Core.Domain.Action.RawInput
- Direction
- Domain.Events uses Domain.Action, so a change to Domain.Action can break Domain.Events, while a change to Domain.Events can't break Domain.Action.
- Position
- Below the diagonal: Domain.Events uses a module listed above it, which is the healthy direction.
24→3 Domain.Events uses Domain.Core✕
- Connections
- 2 pairs of types, where a type in Domain.Events uses a type in Domain.Core.
- The types involved
Pomo.Core.Domain.Events.EntitySpawnBundle→Pomo.Core.Domain.Core.SlotProcessingPomo.Core.Domain.Events.MovementState→Pomo.Core.Domain.Core.WorldPosition
- Direction
- Domain.Events uses Domain.Core, so a change to Domain.Core can break Domain.Events, while a change to Domain.Events can't break Domain.Core.
- Position
- Below the diagonal: Domain.Events uses a module listed above it, which is the healthy direction.
24→7 Domain.Events uses Domain.Entity✕
- Connections
- 4 pairs of types, where a type in Domain.Events uses a type in Domain.Entity.
- The types involved
Pomo.Core.Domain.Events.EntitySpawnBundle→Pomo.Core.Domain.Entity.BaseStatsPomo.Core.Domain.Events.EntitySpawnBundle→Pomo.Core.Domain.Entity.EntitySnapshotPomo.Core.Domain.Events.EntitySpawnBundle→Pomo.Core.Domain.Entity.FactionPomo.Core.Domain.Events.EntitySpawnBundle→Pomo.Core.Domain.Entity.Resource
- Direction
- Domain.Events uses Domain.Entity, so a change to Domain.Entity can break Domain.Events, while a change to Domain.Events can't break Domain.Entity.
- Position
- Below the diagonal: Domain.Events uses a module listed above it, which is the healthy direction.
24→13 Domain.Events uses Domain.AI✕
- Connections
- 1 pair of types, where a type in Domain.Events uses a type in Domain.AI.
- The types involved
Pomo.Core.Domain.Events.EntitySpawnBundle→Pomo.Core.Domain.AI.AIController
- Direction
- Domain.Events uses Domain.AI, so a change to Domain.AI can break Domain.Events, while a change to Domain.Events can't break Domain.AI.
- Position
- Below the diagonal: Domain.Events uses a module listed above it, which is the healthy direction.
24→15 Domain.Events uses Domain.Item✕
- Connections
- 1 pair of types, where a type in Domain.Events uses a type in Domain.Item.
- The types involved
Pomo.Core.Domain.Events.EntitySpawnBundle→Pomo.Core.Domain.Item.ItemInstance
- Direction
- Domain.Events uses Domain.Item, so a change to Domain.Item can break Domain.Events, while a change to Domain.Events can't break Domain.Item.
- Position
- Below the diagonal: Domain.Events uses a module listed above it, which is the healthy direction.
24→22 Domain.Events uses Domain.Events.SystemCommunications✕
- Connections
- 24 pairs of types, where a type in Domain.Events uses a type in Domain.Events.SystemCommunications.
- The types involved
Pomo.Core.Domain.Events.GameEvent→Pomo.Core.Domain.Events.SystemCommunications.CollisionEventsPomo.Core.Domain.Events.IntentEvent→Pomo.Core.Domain.Events.SystemCommunications.AbilityIntentPomo.Core.Domain.Events.IntentEvent→Pomo.Core.Domain.Events.SystemCommunications.AttackIntentPomo.Core.Domain.Events.IntentEvent→Pomo.Core.Domain.Events.SystemCommunications.EffectApplicationIntentPomo.Core.Domain.Events.IntentEvent→Pomo.Core.Domain.Events.SystemCommunications.EffectDamageIntentPomo.Core.Domain.Events.IntentEvent→Pomo.Core.Domain.Events.SystemCommunications.EffectResourceIntentPomo.Core.Domain.Events.IntentEvent→Pomo.Core.Domain.Events.SystemCommunications.PortalTravelPomo.Core.Domain.Events.IntentEvent→Pomo.Core.Domain.Events.SystemCommunications.SetMovementTargetPomo.Core.Domain.Events.IntentEvent→Pomo.Core.Domain.Events.SystemCommunications.SlotActivatedPomo.Core.Domain.Events.IntentEvent→Pomo.Core.Domain.Events.SystemCommunications.TargetSelectedPomo.Core.Domain.Events.ItemIntentEvent→Pomo.Core.Domain.Events.SystemCommunications.DropItemIntentPomo.Core.Domain.Events.ItemIntentEvent→Pomo.Core.Domain.Events.SystemCommunications.EquipItemIntentPomo.Core.Domain.Events.ItemIntentEvent→Pomo.Core.Domain.Events.SystemCommunications.PickUpItemIntentPomo.Core.Domain.Events.ItemIntentEvent→Pomo.Core.Domain.Events.SystemCommunications.UnequipItemIntentPomo.Core.Domain.Events.ItemIntentEvent→Pomo.Core.Domain.Events.SystemCommunications.UseItemIntentPomo.Core.Domain.Events.LifecycleEvent→Pomo.Core.Domain.Events.SystemCommunications.ChargeCompletedPomo.Core.Domain.Events.LifecycleEvent→Pomo.Core.Domain.Events.SystemCommunications.EntityDiedPomo.Core.Domain.Events.LifecycleEvent→Pomo.Core.Domain.Events.SystemCommunications.ProjectileImpactedPomo.Core.Domain.Events.NotificationEvent→Pomo.Core.Domain.Events.SystemCommunications.DamageDealtPomo.Core.Domain.Events.NotificationEvent→Pomo.Core.Domain.Events.SystemCommunications.ResourceRestoredPomo.Core.Domain.Events.NotificationEvent→Pomo.Core.Domain.Events.SystemCommunications.ShowNotificationPomo.Core.Domain.Events.SceneEvent→Pomo.Core.Domain.Events.SystemCommunications.SceneTransitionPomo.Core.Domain.Events.SpawningEvent→Pomo.Core.Domain.Events.SystemCommunications.RegisterSpawnZonesPomo.Core.Domain.Events.SpawningEvent→Pomo.Core.Domain.Events.SystemCommunications.SpawnEntityIntent
- Direction
- Domain.Events uses Domain.Events.SystemCommunications, so a change to Domain.Events.SystemCommunications can break Domain.Events, while a change to Domain.Events can't break Domain.Events.SystemCommunications.
- Position
- Below the diagonal: Domain.Events uses a module listed above it, which is the healthy direction.
25→3 Systems.AIContext uses Domain.Core✕
- Connections
- 1 pair of types, where a type in Systems.AIContext uses a type in Domain.Core.
- The types involved
Pomo.Core.Systems.AIContext.WorldSnapshot→Pomo.Core.Domain.Core.WorldPosition
- Direction
- Systems.AIContext uses Domain.Core, so a change to Domain.Core can break Systems.AIContext, while a change to Systems.AIContext can't break Domain.Core.
- Position
- Below the diagonal: Systems.AIContext uses a module listed above it, which is the healthy direction.
25→7 Systems.AIContext uses Domain.Entity✕
- Connections
- 2 pairs of types, where a type in Systems.AIContext uses a type in Domain.Entity.
- The types involved
Pomo.Core.Systems.AIContext.EntityContext→Pomo.Core.Domain.Entity.FactionPomo.Core.Systems.AIContext.WorldSnapshot→Pomo.Core.Domain.Entity.Faction
- Direction
- Systems.AIContext uses Domain.Entity, so a change to Domain.Entity can break Systems.AIContext, while a change to Systems.AIContext can't break Domain.Entity.
- Position
- Below the diagonal: Systems.AIContext uses a module listed above it, which is the healthy direction.
25→10 Systems.AIContext uses Domain.Spatial✕
- Connections
- 1 pair of types, where a type in Systems.AIContext uses a type in Domain.Spatial.
- The types involved
Pomo.Core.Systems.AIContext.WorldSnapshot→Pomo.Core.Domain.Spatial.GridCell
- Direction
- Systems.AIContext uses Domain.Spatial, so a change to Domain.Spatial can break Systems.AIContext, while a change to Systems.AIContext can't break Domain.Spatial.
- Position
- Below the diagonal: Systems.AIContext uses a module listed above it, which is the healthy direction.
25→13 Systems.AIContext uses Domain.AI✕
- Connections
- 4 pairs of types, where a type in Systems.AIContext uses a type in Domain.AI.
- The types involved
Pomo.Core.Systems.AIContext.AIContext→Pomo.Core.Domain.AI.AIStatePomo.Core.Systems.AIContext.AIOutput→Pomo.Core.Domain.AI.AIStatePomo.Core.Systems.AIContext.PerceptionContext→Pomo.Core.Domain.AI.AIArchetypePomo.Core.Systems.AIContext.PerceptionContext→Pomo.Core.Domain.AI.AIController
- Direction
- Systems.AIContext uses Domain.AI, so a change to Domain.AI can break Systems.AIContext, while a change to Systems.AIContext can't break Domain.AI.
- Position
- Below the diagonal: Systems.AIContext uses a module listed above it, which is the healthy direction.
25→21 Systems.AIContext uses Stores✕
- Connections
- 1 pair of types, where a type in Systems.AIContext uses a type in Stores.
- The types involved
Pomo.Core.Systems.AIContext.AbilityContext→Pomo.Core.Stores.SkillStore
- Direction
- Systems.AIContext uses Stores, so a change to Stores can break Systems.AIContext, while a change to Systems.AIContext can't break Stores.
- Position
- Below the diagonal: Systems.AIContext uses a module listed above it, which is the healthy direction.
25→22 Systems.AIContext uses Domain.Events.SystemCommunications✕
- Connections
- 2 pairs of types, where a type in Systems.AIContext uses a type in Domain.Events.SystemCommunications.
- The types involved
Pomo.Core.Systems.AIContext.AIOutput→Pomo.Core.Domain.Events.SystemCommunications.AbilityIntentPomo.Core.Systems.AIContext.AIOutput→Pomo.Core.Domain.Events.SystemCommunications.SetMovementTarget
- Direction
- Systems.AIContext uses Domain.Events.SystemCommunications, so a change to Domain.Events.SystemCommunications can break Systems.AIContext, while a change to Systems.AIContext can't break Domain.Events.SystemCommunications.
- Position
- Below the diagonal: Systems.AIContext uses a module listed above it, which is the healthy direction.
26→1 Domain.World uses Domain.Action✕
- Connections
- 3 pairs of types, where a type in Domain.World uses a type in Domain.Action.
- The types involved
Pomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Action.GameActionPomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Action.InputActionStatePomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Action.RawInput
- Direction
- Domain.World uses Domain.Action, so a change to Domain.Action can break Domain.World, while a change to Domain.World can't break Domain.Action.
- Position
- Below the diagonal: Domain.World uses a module listed above it, which is the healthy direction.
26→2 Domain.World uses Domain.Animation✕
- Connections
- 1 pair of types, where a type in Domain.World uses a type in Domain.Animation.
- The types involved
Pomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Animation.AnimationState
- Direction
- Domain.World uses Domain.Animation, so a change to Domain.Animation can break Domain.World, while a change to Domain.World can't break Domain.Animation.
- Position
- Below the diagonal: Domain.World uses a module listed above it, which is the healthy direction.
26→3 Domain.World uses Domain.Core✕
- Connections
- 3 pairs of types, where a type in Domain.World uses a type in Domain.Core.
- The types involved
Pomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Core.SlotProcessingPomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Domain.World.WorldText→Pomo.Core.Domain.Core.WorldPosition
- Direction
- Domain.World uses Domain.Core, so a change to Domain.Core can break Domain.World, while a change to Domain.World can't break Domain.Core.
- Position
- Below the diagonal: Domain.World uses a module listed above it, which is the healthy direction.
26→7 Domain.World uses Domain.Entity✕
- Connections
- 4 pairs of types, where a type in Domain.World uses a type in Domain.Entity.
- The types involved
Pomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Entity.BaseStatsPomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Entity.DerivedStatsPomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Entity.FactionPomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Entity.Resource
- Direction
- Domain.World uses Domain.Entity, so a change to Domain.Entity can break Domain.World, while a change to Domain.World can't break Domain.Entity.
- Position
- Below the diagonal: Domain.World uses a module listed above it, which is the healthy direction.
26→8 Domain.World uses Domain.Orbital✕
- Connections
- 1 pair of types, where a type in Domain.World uses a type in Domain.Orbital.
- The types involved
Pomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Orbital.ActiveOrbital
- Direction
- Domain.World uses Domain.Orbital, so a change to Domain.Orbital can break Domain.World, while a change to Domain.World can't break Domain.Orbital.
- Position
- Below the diagonal: Domain.World uses a module listed above it, which is the healthy direction.
26→9 Domain.World uses Domain.Projectile✕
- Connections
- 1 pair of types, where a type in Domain.World uses a type in Domain.Projectile.
- The types involved
Pomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Projectile.LiveProjectile
- Direction
- Domain.World uses Domain.Projectile, so a change to Domain.Projectile can break Domain.World, while a change to Domain.World can't break Domain.Projectile.
- Position
- Below the diagonal: Domain.World uses a module listed above it, which is the healthy direction.
26→11 Domain.World uses Domain.Skill✕
- Connections
- 1 pair of types, where a type in Domain.World uses a type in Domain.Skill.
- The types involved
Pomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Skill.ActiveEffect
- Direction
- Domain.World uses Domain.Skill, so a change to Domain.Skill can break Domain.World, while a change to Domain.World can't break Domain.Skill.
- Position
- Below the diagonal: Domain.World uses a module listed above it, which is the healthy direction.
26→13 Domain.World uses Domain.AI✕
- Connections
- 1 pair of types, where a type in Domain.World uses a type in Domain.AI.
- The types involved
Pomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.AI.AIController
- Direction
- Domain.World uses Domain.AI, so a change to Domain.AI can break Domain.World, while a change to Domain.World can't break Domain.AI.
- Position
- Below the diagonal: Domain.World uses a module listed above it, which is the healthy direction.
26→14 Domain.World uses Domain.BlockMap✕
- Connections
- 1 pair of types, where a type in Domain.World uses a type in Domain.BlockMap.
- The types involved
Pomo.Core.Domain.World.Scenario→Pomo.Core.Domain.BlockMap.BlockMapDefinition
- Direction
- Domain.World uses Domain.BlockMap, so a change to Domain.BlockMap can break Domain.World, while a change to Domain.World can't break Domain.BlockMap.
- Position
- Below the diagonal: Domain.World uses a module listed above it, which is the healthy direction.
26→15 Domain.World uses Domain.Item✕
- Connections
- 2 pairs of types, where a type in Domain.World uses a type in Domain.Item.
- The types involved
Pomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Item.ItemInstancePomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Item.Slot
- Direction
- Domain.World uses Domain.Item, so a change to Domain.Item can break Domain.World, while a change to Domain.World can't break Domain.Item.
- Position
- Below the diagonal: Domain.World uses a module listed above it, which is the healthy direction.
26→16 Domain.World uses Domain.Particles✕
- Connections
- 1 pair of types, where a type in Domain.World uses a type in Domain.Particles.
- The types involved
Pomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Particles.VisualEffect
- Direction
- Domain.World uses Domain.Particles, so a change to Domain.Particles can break Domain.World, while a change to Domain.World can't break Domain.Particles.
- Position
- Below the diagonal: Domain.World uses a module listed above it, which is the healthy direction.
26→22 Domain.World uses Domain.Events.SystemCommunications✕
- Connections
- 2 pairs of types, where a type in Domain.World uses a type in Domain.Events.SystemCommunications.
- The types involved
Pomo.Core.Domain.World.ActiveCharge→Pomo.Core.Domain.Events.SystemCommunications.SkillTargetPomo.Core.Domain.World.WorldText→Pomo.Core.Domain.Events.SystemCommunications.NotificationType
- Direction
- Domain.World uses Domain.Events.SystemCommunications, so a change to Domain.Events.SystemCommunications can break Domain.World, while a change to Domain.World can't break Domain.Events.SystemCommunications.
- Position
- Below the diagonal: Domain.World uses a module listed above it, which is the healthy direction.
26→24 Domain.World uses Domain.Events✕
- Connections
- 1 pair of types, where a type in Domain.World uses a type in Domain.Events.
- The types involved
Pomo.Core.Domain.World.MutableWorld→Pomo.Core.Domain.Events.MovementState
- Direction
- Domain.World uses Domain.Events, so a change to Domain.Events can break Domain.World, while a change to Domain.World can't break Domain.Events.
- Position
- Below the diagonal: Domain.World uses a module listed above it, which is the healthy direction.
27→24 EventBus uses Domain.Events✕
- Connections
- 1 pair of types, where a type in EventBus uses a type in Domain.Events.
- The types involved
Pomo.Core.EventBus.RingEventBus→Pomo.Core.Domain.Events.GameEvent
- Direction
- EventBus uses Domain.Events, so a change to Domain.Events can break EventBus, while a change to EventBus can't break Domain.Events.
- Position
- Below the diagonal: EventBus uses a module listed above it, which is the healthy direction.
28→1 Projections uses Domain.Action✕
- Connections
- 2 pairs of types, where a type in Projections uses a type in Domain.Action.
- The types involved
Pomo.Core.Projections.ProjectionService→Pomo.Core.Domain.Action.GameActionPomo.Core.Projections.Projections→Pomo.Core.Domain.Action.GameAction
- Direction
- Projections uses Domain.Action, so a change to Domain.Action can break Projections, while a change to Projections can't break Domain.Action.
- Position
- Below the diagonal: Projections uses a module listed above it, which is the healthy direction.
28→3 Projections uses Domain.Core✕
- Connections
- 7 pairs of types, where a type in Projections uses a type in Domain.Core.
- The types involved
Pomo.Core.Projections.Movement3DSnapshot→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Projections.MovementSnapshot→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Projections.ProjectionService→Pomo.Core.Domain.Core.CombatStatusPomo.Core.Projections.ProjectionService→Pomo.Core.Domain.Core.SlotProcessingPomo.Core.Projections.ProjectionService→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Projections.Projections→Pomo.Core.Domain.Core.CombatStatusPomo.Core.Projections.Projections→Pomo.Core.Domain.Core.SlotProcessing
- Direction
- Projections uses Domain.Core, so a change to Domain.Core can break Projections, while a change to Projections can't break Domain.Core.
- Position
- Below the diagonal: Projections uses a module listed above it, which is the healthy direction.
28→7 Projections uses Domain.Entity✕
- Connections
- 4 pairs of types, where a type in Projections uses a type in Domain.Entity.
- The types involved
Pomo.Core.Projections.ProjectionService→Pomo.Core.Domain.Entity.DerivedStatsPomo.Core.Projections.Projections→Pomo.Core.Domain.Entity.DerivedStatsPomo.Core.Projections.RegenerationContext→Pomo.Core.Domain.Entity.DerivedStatsPomo.Core.Projections.RegenerationContext→Pomo.Core.Domain.Entity.Resource
- Direction
- Projections uses Domain.Entity, so a change to Domain.Entity can break Projections, while a change to Projections can't break Domain.Entity.
- Position
- Below the diagonal: Projections uses a module listed above it, which is the healthy direction.
28→10 Projections uses Domain.Spatial✕
- Connections
- 2 pairs of types, where a type in Projections uses a type in Domain.Spatial.
- The types involved
Pomo.Core.Projections.Movement3DSnapshot→Pomo.Core.Domain.Spatial.GridCell3DPomo.Core.Projections.MovementSnapshot→Pomo.Core.Domain.Spatial.GridCell
- Direction
- Projections uses Domain.Spatial, so a change to Domain.Spatial can break Projections, while a change to Projections can't break Domain.Spatial.
- Position
- Below the diagonal: Projections uses a module listed above it, which is the healthy direction.
28→11 Projections uses Domain.Skill✕
- Connections
- 1 pair of types, where a type in Projections uses a type in Domain.Skill.
- The types involved
Pomo.Core.Projections.Projections→Pomo.Core.Domain.Skill.ActiveEffect
- Direction
- Projections uses Domain.Skill, so a change to Domain.Skill can break Projections, while a change to Projections can't break Domain.Skill.
- Position
- Below the diagonal: Projections uses a module listed above it, which is the healthy direction.
28→15 Projections uses Domain.Item✕
- Connections
- 5 pairs of types, where a type in Projections uses a type in Domain.Item.
- The types involved
Pomo.Core.Projections.ProjectionService→Pomo.Core.Domain.Item.ItemDefinitionPomo.Core.Projections.ProjectionService→Pomo.Core.Domain.Item.SlotPomo.Core.Projections.Projections→Pomo.Core.Domain.Item.ItemDefinitionPomo.Core.Projections.Projections→Pomo.Core.Domain.Item.SlotPomo.Core.Projections.ResolvedItemStack→Pomo.Core.Domain.Item.ItemDefinition
- Direction
- Projections uses Domain.Item, so a change to Domain.Item can break Projections, while a change to Projections can't break Domain.Item.
- Position
- Below the diagonal: Projections uses a module listed above it, which is the healthy direction.
28→21 Projections uses Stores✕
- Connections
- 1 pair of types, where a type in Projections uses a type in Stores.
- The types involved
Pomo.Core.Projections.Projections→Pomo.Core.Stores.ItemStore
- Direction
- Projections uses Stores, so a change to Stores can break Projections, while a change to Projections can't break Stores.
- Position
- Below the diagonal: Projections uses a module listed above it, which is the healthy direction.
28→26 Projections uses Domain.World✕
- Connections
- 2 pairs of types, where a type in Projections uses a type in Domain.World.
- The types involved
Pomo.Core.Projections.EntityScenarioContext→Pomo.Core.Domain.World.ScenarioPomo.Core.Projections.Projections→Pomo.Core.Domain.World.World
- Direction
- Projections uses Domain.World, so a change to Domain.World can break Projections, while a change to Projections can't break Domain.World.
- Position
- Below the diagonal: Projections uses a module listed above it, which is the healthy direction.
29→3 Projections.DerivedStatsCalculator uses Domain.Core✕
- Connections
- 2 pairs of types, where a type in Projections.DerivedStatsCalculator uses a type in Domain.Core.
- The types involved
Pomo.Core.Projections.DerivedStatsCalculator.DerivedStatsCalculator→Pomo.Core.Domain.Core.StatPomo.Core.Projections.DerivedStatsCalculator.DerivedStatsCalculator→Pomo.Core.Domain.Core.StatModifier
- Direction
- Projections.DerivedStatsCalculator uses Domain.Core, so a change to Domain.Core can break Projections.DerivedStatsCalculator, while a change to Projections.DerivedStatsCalculator can't break Domain.Core.
- Position
- Below the diagonal: Projections.DerivedStatsCalculator uses a module listed above it, which is the healthy direction.
29→7 Projections.DerivedStatsCalculator uses Domain.Entity✕
- Connections
- 2 pairs of types, where a type in Projections.DerivedStatsCalculator uses a type in Domain.Entity.
- The types involved
Pomo.Core.Projections.DerivedStatsCalculator.DerivedStatsCalculator→Pomo.Core.Domain.Entity.BaseStatsPomo.Core.Projections.DerivedStatsCalculator.DerivedStatsCalculator→Pomo.Core.Domain.Entity.DerivedStats
- Direction
- Projections.DerivedStatsCalculator uses Domain.Entity, so a change to Domain.Entity can break Projections.DerivedStatsCalculator, while a change to Projections.DerivedStatsCalculator can't break Domain.Entity.
- Position
- Below the diagonal: Projections.DerivedStatsCalculator uses a module listed above it, which is the healthy direction.
29→11 Projections.DerivedStatsCalculator uses Domain.Skill✕
- Connections
- 1 pair of types, where a type in Projections.DerivedStatsCalculator uses a type in Domain.Skill.
- The types involved
Pomo.Core.Projections.DerivedStatsCalculator.DerivedStatsCalculator→Pomo.Core.Domain.Skill.ActiveEffect
- Direction
- Projections.DerivedStatsCalculator uses Domain.Skill, so a change to Domain.Skill can break Projections.DerivedStatsCalculator, while a change to Projections.DerivedStatsCalculator can't break Domain.Skill.
- Position
- Below the diagonal: Projections.DerivedStatsCalculator uses a module listed above it, which is the healthy direction.
29→15 Projections.DerivedStatsCalculator uses Domain.Item✕
- Connections
- 1 pair of types, where a type in Projections.DerivedStatsCalculator uses a type in Domain.Item.
- The types involved
Pomo.Core.Projections.DerivedStatsCalculator.DerivedStatsCalculator→Pomo.Core.Domain.Item.Slot
- Direction
- Projections.DerivedStatsCalculator uses Domain.Item, so a change to Domain.Item can break Projections.DerivedStatsCalculator, while a change to Projections.DerivedStatsCalculator can't break Domain.Item.
- Position
- Below the diagonal: Projections.DerivedStatsCalculator uses a module listed above it, which is the healthy direction.
29→21 Projections.DerivedStatsCalculator uses Stores✕
- Connections
- 1 pair of types, where a type in Projections.DerivedStatsCalculator uses a type in Stores.
- The types involved
Pomo.Core.Projections.DerivedStatsCalculator.DerivedStatsCalculator→Pomo.Core.Stores.ItemStore
- Direction
- Projections.DerivedStatsCalculator uses Stores, so a change to Stores can break Projections.DerivedStatsCalculator, while a change to Projections.DerivedStatsCalculator can't break Stores.
- Position
- Below the diagonal: Projections.DerivedStatsCalculator uses a module listed above it, which is the healthy direction.
29→26 Projections.DerivedStatsCalculator uses Domain.World✕
- Connections
- 1 pair of types, where a type in Projections.DerivedStatsCalculator uses a type in Domain.World.
- The types involved
Pomo.Core.Projections.DerivedStatsCalculator.DerivedStatsCalculator→Pomo.Core.Domain.World.World
- Direction
- Projections.DerivedStatsCalculator uses Domain.World, so a change to Domain.World can break Projections.DerivedStatsCalculator, while a change to Projections.DerivedStatsCalculator can't break Domain.World.
- Position
- Below the diagonal: Projections.DerivedStatsCalculator uses a module listed above it, which is the healthy direction.
30→3 UI uses Domain.Core✕
- Connections
- 1 pair of types, where a type in UI uses a type in Domain.Core.
- The types involved
Pomo.Core.UI.MiniMap→Pomo.Core.Domain.Core.WorldPosition
- Direction
- UI uses Domain.Core, so a change to Domain.Core can break UI, while a change to UI can't break Domain.Core.
- Position
- Below the diagonal: UI uses a module listed above it, which is the healthy direction.
30→7 UI uses Domain.Entity✕
- Connections
- 1 pair of types, where a type in UI uses a type in Domain.Entity.
- The types involved
Pomo.Core.UI.MiniMap→Pomo.Core.Domain.Entity.Faction
- Direction
- UI uses Domain.Entity, so a change to Domain.Entity can break UI, while a change to UI can't break Domain.Entity.
- Position
- Below the diagonal: UI uses a module listed above it, which is the healthy direction.
30→11 UI uses Domain.Skill✕
- Connections
- 1 pair of types, where a type in UI uses a type in Domain.Skill.
- The types involved
Pomo.Core.UI.StatusEffectWidget→Pomo.Core.Domain.Skill.EffectKind
- Direction
- UI uses Domain.Skill, so a change to Domain.Skill can break UI, while a change to UI can't break Domain.Skill.
- Position
- Below the diagonal: UI uses a module listed above it, which is the healthy direction.
30→26 UI uses Domain.World✕
- Connections
- 5 pairs of types, where a type in UI uses a type in Domain.World.
- The types involved
Pomo.Core.UI.ActionSlot→Pomo.Core.Domain.World.TimePomo.Core.UI.CombatIndicator→Pomo.Core.Domain.World.TimePomo.Core.UI.ItemSlot→Pomo.Core.Domain.World.TimePomo.Core.UI.ResourceBar→Pomo.Core.Domain.World.TimePomo.Core.UI.StatusEffectWidget→Pomo.Core.Domain.World.Time
- Direction
- UI uses Domain.World, so a change to Domain.World can break UI, while a change to UI can't break Domain.World.
- Position
- Below the diagonal: UI uses a module listed above it, which is the healthy direction.
31→1 Environment uses Domain.Action✕
- Connections
- 2 pairs of types, where a type in Environment uses a type in Domain.Action.
- The types involved
Pomo.Core.Environment.IInputWriteService→Pomo.Core.Domain.Action.GameActionPomo.Core.Environment.IInputWriteService→Pomo.Core.Domain.Action.InputActionState
- Direction
- Environment uses Domain.Action, so a change to Domain.Action can break Environment, while a change to Environment can't break Domain.Action.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→2 Environment uses Domain.Animation✕
- Connections
- 1 pair of types, where a type in Environment uses a type in Domain.Animation.
- The types involved
Pomo.Core.Environment.IAnimationWriteService→Pomo.Core.Domain.Animation.AnimationState
- Direction
- Environment uses Domain.Animation, so a change to Domain.Animation can break Environment, while a change to Environment can't break Domain.Animation.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→3 Environment uses Domain.Core✕
- Connections
- 4 pairs of types, where a type in Environment uses a type in Domain.Core.
- The types involved
Pomo.Core.Environment.IEntityLifecycleService→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Environment.IPhysicsWriteService→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Environment.ListenerServices→Pomo.Core.Domain.Core.CoreEventListenerPomo.Core.Environment.TargetingService→Pomo.Core.Domain.Core.CoreEventListener
- Direction
- Environment uses Domain.Core, so a change to Domain.Core can break Environment, while a change to Environment can't break Domain.Core.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→6 Environment uses Domain.Camera✕
- Connections
- 1 pair of types, where a type in Environment uses a type in Domain.Camera.
- The types involved
Pomo.Core.Environment.GameplayServices→Pomo.Core.Domain.Camera.CameraService
- Direction
- Environment uses Domain.Camera, so a change to Domain.Camera can break Environment, while a change to Environment can't break Domain.Camera.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→7 Environment uses Domain.Entity✕
- Connections
- 1 pair of types, where a type in Environment uses a type in Domain.Entity.
- The types involved
Pomo.Core.Environment.ICombatWriteService→Pomo.Core.Domain.Entity.Resource
- Direction
- Environment uses Domain.Entity, so a change to Domain.Entity can break Environment, while a change to Environment can't break Domain.Entity.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→8 Environment uses Domain.Orbital✕
- Connections
- 1 pair of types, where a type in Environment uses a type in Domain.Orbital.
- The types involved
Pomo.Core.Environment.IOrbitalWriteService→Pomo.Core.Domain.Orbital.ActiveOrbital
- Direction
- Environment uses Domain.Orbital, so a change to Domain.Orbital can break Environment, while a change to Environment can't break Domain.Orbital.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→9 Environment uses Domain.Projectile✕
- Connections
- 1 pair of types, where a type in Environment uses a type in Domain.Projectile.
- The types involved
Pomo.Core.Environment.IEntityLifecycleService→Pomo.Core.Domain.Projectile.LiveProjectile
- Direction
- Environment uses Domain.Projectile, so a change to Domain.Projectile can break Environment, while a change to Environment can't break Domain.Projectile.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→11 Environment uses Domain.Skill✕
- Connections
- 2 pairs of types, where a type in Environment uses a type in Domain.Skill.
- The types involved
Pomo.Core.Environment.IEffectsWriteService→Pomo.Core.Domain.Skill.ActiveEffectPomo.Core.Environment.TargetingService→Pomo.Core.Domain.Skill.Targeting
- Direction
- Environment uses Domain.Skill, so a change to Domain.Skill can break Environment, while a change to Environment can't break Domain.Skill.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→12 Environment uses Domain.UI✕
- Connections
- 1 pair of types, where a type in Environment uses a type in Domain.UI.
- The types involved
Pomo.Core.Environment.CoreServices→Pomo.Core.Domain.UI.IHUDService
- Direction
- Environment uses Domain.UI, so a change to Domain.UI can break Environment, while a change to Environment can't break Domain.UI.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→13 Environment uses Domain.AI✕
- Connections
- 1 pair of types, where a type in Environment uses a type in Domain.AI.
- The types involved
Pomo.Core.Environment.IAIWriteService→Pomo.Core.Domain.AI.AIController
- Direction
- Environment uses Domain.AI, so a change to Domain.AI can break Environment, while a change to Environment can't break Domain.AI.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→15 Environment uses Domain.Item✕
- Connections
- 2 pairs of types, where a type in Environment uses a type in Domain.Item.
- The types involved
Pomo.Core.Environment.IInventoryWriteService→Pomo.Core.Domain.Item.ItemInstancePomo.Core.Environment.IInventoryWriteService→Pomo.Core.Domain.Item.Slot
- Direction
- Environment uses Domain.Item, so a change to Domain.Item can break Environment, while a change to Environment can't break Domain.Item.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→21 Environment uses Stores✕
- Connections
- 9 pairs of types, where a type in Environment uses a type in Stores.
- The types involved
Pomo.Core.Environment.StoreServices→Pomo.Core.Stores.AIArchetypeStorePomo.Core.Environment.StoreServices→Pomo.Core.Stores.AIEntityStorePomo.Core.Environment.StoreServices→Pomo.Core.Stores.AIFamilyStorePomo.Core.Environment.StoreServices→Pomo.Core.Stores.AnimationStorePomo.Core.Environment.StoreServices→Pomo.Core.Stores.DecisionTreeStorePomo.Core.Environment.StoreServices→Pomo.Core.Stores.ItemStorePomo.Core.Environment.StoreServices→Pomo.Core.Stores.ModelStorePomo.Core.Environment.StoreServices→Pomo.Core.Stores.ParticleStorePomo.Core.Environment.StoreServices→Pomo.Core.Stores.SkillStore
- Direction
- Environment uses Stores, so a change to Stores can break Environment, while a change to Environment can't break Stores.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→22 Environment uses Domain.Events.SystemCommunications✕
- Connections
- 1 pair of types, where a type in Environment uses a type in Domain.Events.SystemCommunications.
- The types involved
Pomo.Core.Environment.ICombatWriteService→Pomo.Core.Domain.Events.SystemCommunications.SkillTarget
- Direction
- Environment uses Domain.Events.SystemCommunications, so a change to Domain.Events.SystemCommunications can break Environment, while a change to Environment can't break Domain.Events.SystemCommunications.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→24 Environment uses Domain.Events✕
- Connections
- 2 pairs of types, where a type in Environment uses a type in Domain.Events.
- The types involved
Pomo.Core.Environment.IEntityLifecycleService→Pomo.Core.Domain.Events.EntitySpawnBundlePomo.Core.Environment.IMovementWriteService→Pomo.Core.Domain.Events.MovementState
- Direction
- Environment uses Domain.Events, so a change to Domain.Events can break Environment, while a change to Environment can't break Domain.Events.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→26 Environment uses Domain.World✕
- Connections
- 3 pairs of types, where a type in Environment uses a type in Domain.World.
- The types involved
Pomo.Core.Environment.CoreServices→Pomo.Core.Domain.World.WorldPomo.Core.Environment.ICombatWriteService→Pomo.Core.Domain.World.ActiveChargePomo.Core.Environment.INotificationWriteService→Pomo.Core.Domain.World.WorldText
- Direction
- Environment uses Domain.World, so a change to Domain.World can break Environment, while a change to Environment can't break Domain.World.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→27 Environment uses EventBus✕
- Connections
- 1 pair of types, where a type in Environment uses a type in EventBus.
- The types involved
Pomo.Core.Environment.CoreServices→Pomo.Core.EventBus.EventBus
- Direction
- Environment uses EventBus, so a change to EventBus can break Environment, while a change to Environment can't break EventBus.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
31→28 Environment uses Projections✕
- Connections
- 1 pair of types, where a type in Environment uses a type in Projections.
- The types involved
Pomo.Core.Environment.GameplayServices→Pomo.Core.Projections.ProjectionService
- Direction
- Environment uses Projections, so a change to Projections can break Environment, while a change to Environment can't break Projections.
- Position
- Below the diagonal: Environment uses a module listed above it, which is the healthy direction.
32→1 Systems.HUDComponents uses Domain.Action✕
- Connections
- 2 pairs of types, where a type in Systems.HUDComponents uses a type in Domain.Action.
- The types involved
Pomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.Action.GameActionPomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.Action.RawInput
- Direction
- Systems.HUDComponents uses Domain.Action, so a change to Domain.Action can break Systems.HUDComponents, while a change to Systems.HUDComponents can't break Domain.Action.
- Position
- Below the diagonal: Systems.HUDComponents uses a module listed above it, which is the healthy direction.
32→3 Systems.HUDComponents uses Domain.Core✕
- Connections
- 2 pairs of types, where a type in Systems.HUDComponents uses a type in Domain.Core.
- The types involved
Pomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.Core.SlotProcessingPomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.Core.WorldPosition
- Direction
- Systems.HUDComponents uses Domain.Core, so a change to Domain.Core can break Systems.HUDComponents, while a change to Systems.HUDComponents can't break Domain.Core.
- Position
- Below the diagonal: Systems.HUDComponents uses a module listed above it, which is the healthy direction.
32→6 Systems.HUDComponents uses Domain.Camera✕
- Connections
- 1 pair of types, where a type in Systems.HUDComponents uses a type in Domain.Camera.
- The types involved
Pomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.Camera.Camera
- Direction
- Systems.HUDComponents uses Domain.Camera, so a change to Domain.Camera can break Systems.HUDComponents, while a change to Systems.HUDComponents can't break Domain.Camera.
- Position
- Below the diagonal: Systems.HUDComponents uses a module listed above it, which is the healthy direction.
32→7 Systems.HUDComponents uses Domain.Entity✕
- Connections
- 4 pairs of types, where a type in Systems.HUDComponents uses a type in Domain.Entity.
- The types involved
Pomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.Entity.BaseStatsPomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.Entity.DerivedStatsPomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.Entity.FactionPomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.Entity.Resource
- Direction
- Systems.HUDComponents uses Domain.Entity, so a change to Domain.Entity can break Systems.HUDComponents, while a change to Systems.HUDComponents can't break Domain.Entity.
- Position
- Below the diagonal: Systems.HUDComponents uses a module listed above it, which is the healthy direction.
32→11 Systems.HUDComponents uses Domain.Skill✕
- Connections
- 1 pair of types, where a type in Systems.HUDComponents uses a type in Domain.Skill.
- The types involved
Pomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.Skill.ActiveEffect
- Direction
- Systems.HUDComponents uses Domain.Skill, so a change to Domain.Skill can break Systems.HUDComponents, while a change to Systems.HUDComponents can't break Domain.Skill.
- Position
- Below the diagonal: Systems.HUDComponents uses a module listed above it, which is the healthy direction.
32→12 Systems.HUDComponents uses Domain.UI✕
- Connections
- 1 pair of types, where a type in Systems.HUDComponents uses a type in Domain.UI.
- The types involved
Pomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.UI.HUDConfig
- Direction
- Systems.HUDComponents uses Domain.UI, so a change to Domain.UI can break Systems.HUDComponents, while a change to Systems.HUDComponents can't break Domain.UI.
- Position
- Below the diagonal: Systems.HUDComponents uses a module listed above it, which is the healthy direction.
32→15 Systems.HUDComponents uses Domain.Item✕
- Connections
- 2 pairs of types, where a type in Systems.HUDComponents uses a type in Domain.Item.
- The types involved
Pomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.Item.ItemInstancePomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.Item.Slot
- Direction
- Systems.HUDComponents uses Domain.Item, so a change to Domain.Item can break Systems.HUDComponents, while a change to Systems.HUDComponents can't break Domain.Item.
- Position
- Below the diagonal: Systems.HUDComponents uses a module listed above it, which is the healthy direction.
32→21 Systems.HUDComponents uses Stores✕
- Connections
- 2 pairs of types, where a type in Systems.HUDComponents uses a type in Stores.
- The types involved
Pomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Stores.ItemStorePomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Stores.SkillStore
- Direction
- Systems.HUDComponents uses Stores, so a change to Stores can break Systems.HUDComponents, while a change to Systems.HUDComponents can't break Stores.
- Position
- Below the diagonal: Systems.HUDComponents uses a module listed above it, which is the healthy direction.
32→26 Systems.HUDComponents uses Domain.World✕
- Connections
- 2 pairs of types, where a type in Systems.HUDComponents uses a type in Domain.World.
- The types involved
Pomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.World.ActiveChargePomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Domain.World.Time
- Direction
- Systems.HUDComponents uses Domain.World, so a change to Domain.World can break Systems.HUDComponents, while a change to Systems.HUDComponents can't break Domain.World.
- Position
- Below the diagonal: Systems.HUDComponents uses a module listed above it, which is the healthy direction.
32→28 Systems.HUDComponents uses Projections✕
- Connections
- 1 pair of types, where a type in Systems.HUDComponents uses a type in Projections.
- The types involved
Pomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.Projections.ResolvedItemStack
- Direction
- Systems.HUDComponents uses Projections, so a change to Projections can break Systems.HUDComponents, while a change to Systems.HUDComponents can't break Projections.
- Position
- Below the diagonal: Systems.HUDComponents uses a module listed above it, which is the healthy direction.
32→30 Systems.HUDComponents uses UI✕
- Connections
- 2 pairs of types, where a type in Systems.HUDComponents uses a type in UI.
- The types involved
Pomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.UI.CombatIndicatorPomo.Core.Systems.HUDComponents.HUDComponents→Pomo.Core.UI.MiniMap
- Direction
- Systems.HUDComponents uses UI, so a change to UI can break Systems.HUDComponents, while a change to Systems.HUDComponents can't break UI.
- Position
- Below the diagonal: Systems.HUDComponents uses a module listed above it, which is the healthy direction.
33→3 Systems.AbilityActivation uses Domain.Core✕
- Connections
- 2 pairs of types, where a type in Systems.AbilityActivation uses a type in Domain.Core.
- The types involved
Pomo.Core.Systems.AbilityActivation.PendingCastExecutionParams→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Systems.AbilityActivation.ValidationContext→Pomo.Core.Domain.Core.CombatStatus
- Direction
- Systems.AbilityActivation uses Domain.Core, so a change to Domain.Core can break Systems.AbilityActivation, while a change to Systems.AbilityActivation can't break Domain.Core.
- Position
- Below the diagonal: Systems.AbilityActivation uses a module listed above it, which is the healthy direction.
33→5 Systems.AbilityActivation uses Systems.Systems✕
- Connections
- 1 pair of types, where a type in Systems.AbilityActivation uses a type in Systems.Systems.
- The types involved
Pomo.Core.Systems.AbilityActivation.AbilityActivationSystem→Pomo.Core.Systems.Systems.GameSystem
- Direction
- Systems.AbilityActivation uses Systems.Systems, so a change to Systems.Systems can break Systems.AbilityActivation, while a change to Systems.AbilityActivation can't break Systems.Systems.
- Position
- Below the diagonal: Systems.AbilityActivation uses a module listed above it, which is the healthy direction.
33→7 Systems.AbilityActivation uses Domain.Entity✕
- Connections
- 1 pair of types, where a type in Systems.AbilityActivation uses a type in Domain.Entity.
- The types involved
Pomo.Core.Systems.AbilityActivation.ValidationContext→Pomo.Core.Domain.Entity.Resource
- Direction
- Systems.AbilityActivation uses Domain.Entity, so a change to Domain.Entity can break Systems.AbilityActivation, while a change to Systems.AbilityActivation can't break Domain.Entity.
- Position
- Below the diagonal: Systems.AbilityActivation uses a module listed above it, which is the healthy direction.
33→11 Systems.AbilityActivation uses Domain.Skill✕
- Connections
- 2 pairs of types, where a type in Systems.AbilityActivation uses a type in Domain.Skill.
- The types involved
Pomo.Core.Systems.AbilityActivation.PendingCastExecutionParams→Pomo.Core.Domain.Skill.ActiveSkillPomo.Core.Systems.AbilityActivation.SkillActivationParams→Pomo.Core.Domain.Skill.ActiveSkill
- Direction
- Systems.AbilityActivation uses Domain.Skill, so a change to Domain.Skill can break Systems.AbilityActivation, while a change to Systems.AbilityActivation can't break Domain.Skill.
- Position
- Below the diagonal: Systems.AbilityActivation uses a module listed above it, which is the healthy direction.
33→21 Systems.AbilityActivation uses Stores✕
- Connections
- 2 pairs of types, where a type in Systems.AbilityActivation uses a type in Stores.
- The types involved
Pomo.Core.Systems.AbilityActivation.AbilityActivationContext→Pomo.Core.Stores.SkillStorePomo.Core.Systems.AbilityActivation.ValidationContext→Pomo.Core.Stores.SkillStore
- Direction
- Systems.AbilityActivation uses Stores, so a change to Stores can break Systems.AbilityActivation, while a change to Systems.AbilityActivation can't break Stores.
- Position
- Below the diagonal: Systems.AbilityActivation uses a module listed above it, which is the healthy direction.
33→22 Systems.AbilityActivation uses Domain.Events.SystemCommunications✕
- Connections
- 2 pairs of types, where a type in Systems.AbilityActivation uses a type in Domain.Events.SystemCommunications.
- The types involved
Pomo.Core.Systems.AbilityActivation.PendingCastExecutionParams→Pomo.Core.Domain.Events.SystemCommunications.SkillTargetPomo.Core.Systems.AbilityActivation.SkillActivationParams→Pomo.Core.Domain.Events.SystemCommunications.SkillTarget
- Direction
- Systems.AbilityActivation uses Domain.Events.SystemCommunications, so a change to Domain.Events.SystemCommunications can break Systems.AbilityActivation, while a change to Systems.AbilityActivation can't break Domain.Events.SystemCommunications.
- Position
- Below the diagonal: Systems.AbilityActivation uses a module listed above it, which is the healthy direction.
33→27 Systems.AbilityActivation uses EventBus✕
- Connections
- 1 pair of types, where a type in Systems.AbilityActivation uses a type in EventBus.
- The types involved
Pomo.Core.Systems.AbilityActivation.AbilityActivationContext→Pomo.Core.EventBus.EventBus
- Direction
- Systems.AbilityActivation uses EventBus, so a change to EventBus can break Systems.AbilityActivation, while a change to Systems.AbilityActivation can't break EventBus.
- Position
- Below the diagonal: Systems.AbilityActivation uses a module listed above it, which is the healthy direction.
33→31 Systems.AbilityActivation uses Environment✕
- Connections
- 2 pairs of types, where a type in Systems.AbilityActivation uses a type in Environment.
- The types involved
Pomo.Core.Systems.AbilityActivation.AbilityActivationContext→Pomo.Core.Environment.IStateWriteServicePomo.Core.Systems.AbilityActivation.AbilityActivationSystem→Pomo.Core.Environment.PomoEnvironment
- Direction
- Systems.AbilityActivation uses Environment, so a change to Environment can break Systems.AbilityActivation, while a change to Systems.AbilityActivation can't break Environment.
- Position
- Below the diagonal: Systems.AbilityActivation uses a module listed above it, which is the healthy direction.
34→3 Systems.Combat uses Domain.Core✕
- Connections
- 1 pair of types, where a type in Systems.Combat uses a type in Domain.Core.
- The types involved
Pomo.Core.Systems.Combat.EntityContext→Pomo.Core.Domain.Core.WorldPosition
- Direction
- Systems.Combat uses Domain.Core, so a change to Domain.Core can break Systems.Combat, while a change to Systems.Combat can't break Domain.Core.
- Position
- Below the diagonal: Systems.Combat uses a module listed above it, which is the healthy direction.
34→5 Systems.Combat uses Systems.Systems✕
- Connections
- 2 pairs of types, where a type in Systems.Combat uses a type in Systems.Systems.
- The types involved
Pomo.Core.Systems.Combat.CombatSystem→Pomo.Core.Systems.Systems.GameSystemPomo.Core.Systems.Combat.CombatSystem→Pomo.Core.Systems.Systems.SystemKind
- Direction
- Systems.Combat uses Systems.Systems, so a change to Systems.Systems can break Systems.Combat, while a change to Systems.Combat can't break Systems.Systems.
- Position
- Below the diagonal: Systems.Combat uses a module listed above it, which is the healthy direction.
34→7 Systems.Combat uses Domain.Entity✕
- Connections
- 2 pairs of types, where a type in Systems.Combat uses a type in Domain.Entity.
- The types involved
Pomo.Core.Systems.Combat.EntityContext→Pomo.Core.Domain.Entity.DerivedStatsPomo.Core.Systems.Combat.EntityContext→Pomo.Core.Domain.Entity.Resource
- Direction
- Systems.Combat uses Domain.Entity, so a change to Domain.Entity can break Systems.Combat, while a change to Systems.Combat can't break Domain.Entity.
- Position
- Below the diagonal: Systems.Combat uses a module listed above it, which is the healthy direction.
34→8 Systems.Combat uses Domain.Orbital✕
- Connections
- 1 pair of types, where a type in Systems.Combat uses a type in Domain.Orbital.
- The types involved
Pomo.Core.Systems.Combat.WorldContext→Pomo.Core.Domain.Orbital.ActiveOrbital
- Direction
- Systems.Combat uses Domain.Orbital, so a change to Domain.Orbital can break Systems.Combat, while a change to Systems.Combat can't break Domain.Orbital.
- Position
- Below the diagonal: Systems.Combat uses a module listed above it, which is the healthy direction.
34→16 Systems.Combat uses Domain.Particles✕
- Connections
- 1 pair of types, where a type in Systems.Combat uses a type in Domain.Particles.
- The types involved
Pomo.Core.Systems.Combat.WorldContext→Pomo.Core.Domain.Particles.VisualEffect
- Direction
- Systems.Combat uses Domain.Particles, so a change to Domain.Particles can break Systems.Combat, while a change to Systems.Combat can't break Domain.Particles.
- Position
- Below the diagonal: Systems.Combat uses a module listed above it, which is the healthy direction.
34→21 Systems.Combat uses Stores✕
- Connections
- 2 pairs of types, where a type in Systems.Combat uses a type in Stores.
- The types involved
Pomo.Core.Systems.Combat.WorldContext→Pomo.Core.Stores.ParticleStorePomo.Core.Systems.Combat.WorldContext→Pomo.Core.Stores.SkillStore
- Direction
- Systems.Combat uses Stores, so a change to Stores can break Systems.Combat, while a change to Systems.Combat can't break Stores.
- Position
- Below the diagonal: Systems.Combat uses a module listed above it, which is the healthy direction.
34→26 Systems.Combat uses Domain.World✕
- Connections
- 1 pair of types, where a type in Systems.Combat uses a type in Domain.World.
- The types involved
Pomo.Core.Systems.Combat.WorldContext→Pomo.Core.Domain.World.Time
- Direction
- Systems.Combat uses Domain.World, so a change to Domain.World can break Systems.Combat, while a change to Systems.Combat can't break Domain.World.
- Position
- Below the diagonal: Systems.Combat uses a module listed above it, which is the healthy direction.
34→27 Systems.Combat uses EventBus✕
- Connections
- 1 pair of types, where a type in Systems.Combat uses a type in EventBus.
- The types involved
Pomo.Core.Systems.Combat.WorldContext→Pomo.Core.EventBus.EventBus
- Direction
- Systems.Combat uses EventBus, so a change to EventBus can break Systems.Combat, while a change to Systems.Combat can't break EventBus.
- Position
- Below the diagonal: Systems.Combat uses a module listed above it, which is the healthy direction.
34→31 Systems.Combat uses Environment✕
- Connections
- 2 pairs of types, where a type in Systems.Combat uses a type in Environment.
- The types involved
Pomo.Core.Systems.Combat.CombatSystem→Pomo.Core.Environment.PomoEnvironmentPomo.Core.Systems.Combat.WorldContext→Pomo.Core.Environment.IStateWriteService
- Direction
- Systems.Combat uses Environment, so a change to Environment can break Systems.Combat, while a change to Systems.Combat can't break Environment.
- Position
- Below the diagonal: Systems.Combat uses a module listed above it, which is the healthy direction.
35→1 Systems.EntitySpawnerLogic uses Domain.Action✕
- Connections
- 1 pair of types, where a type in Systems.EntitySpawnerLogic uses a type in Domain.Action.
- The types involved
Pomo.Core.Systems.EntitySpawnerLogic.PlayerLoadoutData→Pomo.Core.Domain.Action.GameAction
- Direction
- Systems.EntitySpawnerLogic uses Domain.Action, so a change to Domain.Action can break Systems.EntitySpawnerLogic, while a change to Systems.EntitySpawnerLogic can't break Domain.Action.
- Position
- Below the diagonal: Systems.EntitySpawnerLogic uses a module listed above it, which is the healthy direction.
35→3 Systems.EntitySpawnerLogic uses Domain.Core✕
- Connections
- 2 pairs of types, where a type in Systems.EntitySpawnerLogic uses a type in Domain.Core.
- The types involved
Pomo.Core.Systems.EntitySpawnerLogic.PendingSpawn→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Systems.EntitySpawnerLogic.PlayerLoadoutData→Pomo.Core.Domain.Core.SlotProcessing
- Direction
- Systems.EntitySpawnerLogic uses Domain.Core, so a change to Domain.Core can break Systems.EntitySpawnerLogic, while a change to Systems.EntitySpawnerLogic can't break Domain.Core.
- Position
- Below the diagonal: Systems.EntitySpawnerLogic uses a module listed above it, which is the healthy direction.
35→5 Systems.EntitySpawnerLogic uses Systems.Systems✕
- Connections
- 1 pair of types, where a type in Systems.EntitySpawnerLogic uses a type in Systems.Systems.
- The types involved
Pomo.Core.Systems.EntitySpawnerLogic.EntitySpawnerSystem→Pomo.Core.Systems.Systems.GameSystem
- Direction
- Systems.EntitySpawnerLogic uses Systems.Systems, so a change to Systems.Systems can break Systems.EntitySpawnerLogic, while a change to Systems.EntitySpawnerLogic can't break Systems.Systems.
- Position
- Below the diagonal: Systems.EntitySpawnerLogic uses a module listed above it, which is the healthy direction.
35→7 Systems.EntitySpawnerLogic uses Domain.Entity✕
- Connections
- 1 pair of types, where a type in Systems.EntitySpawnerLogic uses a type in Domain.Entity.
- The types involved
Pomo.Core.Systems.EntitySpawnerLogic.EntitySpawnerLogic→Pomo.Core.Domain.Entity.Faction
- Direction
- Systems.EntitySpawnerLogic uses Domain.Entity, so a change to Domain.Entity can break Systems.EntitySpawnerLogic, while a change to Systems.EntitySpawnerLogic can't break Domain.Entity.
- Position
- Below the diagonal: Systems.EntitySpawnerLogic uses a module listed above it, which is the healthy direction.
35→13 Systems.EntitySpawnerLogic uses Domain.AI✕
- Connections
- 1 pair of types, where a type in Systems.EntitySpawnerLogic uses a type in Domain.AI.
- The types involved
Pomo.Core.Systems.EntitySpawnerLogic.EntitySpawnerLogic→Pomo.Core.Domain.AI.AIArchetype
- Direction
- Systems.EntitySpawnerLogic uses Domain.AI, so a change to Domain.AI can break Systems.EntitySpawnerLogic, while a change to Systems.EntitySpawnerLogic can't break Domain.AI.
- Position
- Below the diagonal: Systems.EntitySpawnerLogic uses a module listed above it, which is the healthy direction.
35→15 Systems.EntitySpawnerLogic uses Domain.Item✕
- Connections
- 1 pair of types, where a type in Systems.EntitySpawnerLogic uses a type in Domain.Item.
- The types involved
Pomo.Core.Systems.EntitySpawnerLogic.PlayerLoadoutData→Pomo.Core.Domain.Item.ItemInstance
- Direction
- Systems.EntitySpawnerLogic uses Domain.Item, so a change to Domain.Item can break Systems.EntitySpawnerLogic, while a change to Systems.EntitySpawnerLogic can't break Domain.Item.
- Position
- Below the diagonal: Systems.EntitySpawnerLogic uses a module listed above it, which is the healthy direction.
35→21 Systems.EntitySpawnerLogic uses Stores✕
- Connections
- 3 pairs of types, where a type in Systems.EntitySpawnerLogic uses a type in Stores.
- The types involved
Pomo.Core.Systems.EntitySpawnerLogic.EntitySpawnerLogic→Pomo.Core.Stores.AIArchetypeStorePomo.Core.Systems.EntitySpawnerLogic.EntitySpawnerLogic→Pomo.Core.Stores.AIEntityStorePomo.Core.Systems.EntitySpawnerLogic.EntitySpawnerLogic→Pomo.Core.Stores.AIFamilyStore
- Direction
- Systems.EntitySpawnerLogic uses Stores, so a change to Stores can break Systems.EntitySpawnerLogic, while a change to Systems.EntitySpawnerLogic can't break Stores.
- Position
- Below the diagonal: Systems.EntitySpawnerLogic uses a module listed above it, which is the healthy direction.
35→22 Systems.EntitySpawnerLogic uses Domain.Events.SystemCommunications✕
- Connections
- 3 pairs of types, where a type in Systems.EntitySpawnerLogic uses a type in Domain.Events.SystemCommunications.
- The types involved
Pomo.Core.Systems.EntitySpawnerLogic.PendingSpawn→Pomo.Core.Domain.Events.SystemCommunications.SpawnTypePomo.Core.Systems.EntitySpawnerLogic.SpawnZoneConfig→Pomo.Core.Domain.Events.SystemCommunications.FactionSpawnInfoPomo.Core.Systems.EntitySpawnerLogic.SpawnedEntityInfo→Pomo.Core.Domain.Events.SystemCommunications.FactionSpawnInfo
- Direction
- Systems.EntitySpawnerLogic uses Domain.Events.SystemCommunications, so a change to Domain.Events.SystemCommunications can break Systems.EntitySpawnerLogic, while a change to Systems.EntitySpawnerLogic can't break Domain.Events.SystemCommunications.
- Position
- Below the diagonal: Systems.EntitySpawnerLogic uses a module listed above it, which is the healthy direction.
35→31 Systems.EntitySpawnerLogic uses Environment✕
- Connections
- 2 pairs of types, where a type in Systems.EntitySpawnerLogic uses a type in Environment.
- The types involved
Pomo.Core.Systems.EntitySpawnerLogic.EntitySpawnerLogic→Pomo.Core.Environment.IStateWriteServicePomo.Core.Systems.EntitySpawnerLogic.EntitySpawnerSystem→Pomo.Core.Environment.PomoEnvironment
- Direction
- Systems.EntitySpawnerLogic uses Environment, so a change to Environment can break Systems.EntitySpawnerLogic, while a change to Systems.EntitySpawnerLogic can't break Environment.
- Position
- Below the diagonal: Systems.EntitySpawnerLogic uses a module listed above it, which is the healthy direction.
36→6 Systems.HoverFeedback uses Domain.Camera✕
- Connections
- 1 pair of types, where a type in Systems.HoverFeedback uses a type in Domain.Camera.
- The types involved
Pomo.Core.Systems.HoverFeedback.HoverFeedback→Pomo.Core.Domain.Camera.CameraService
- Direction
- Systems.HoverFeedback uses Domain.Camera, so a change to Domain.Camera can break Systems.HoverFeedback, while a change to Systems.HoverFeedback can't break Domain.Camera.
- Position
- Below the diagonal: Systems.HoverFeedback uses a module listed above it, which is the healthy direction.
36→7 Systems.HoverFeedback uses Domain.Entity✕
- Connections
- 1 pair of types, where a type in Systems.HoverFeedback uses a type in Domain.Entity.
- The types involved
Pomo.Core.Systems.HoverFeedback.HoverFeedback→Pomo.Core.Domain.Entity.Faction
- Direction
- Systems.HoverFeedback uses Domain.Entity, so a change to Domain.Entity can break Systems.HoverFeedback, while a change to Systems.HoverFeedback can't break Domain.Entity.
- Position
- Below the diagonal: Systems.HoverFeedback uses a module listed above it, which is the healthy direction.
36→11 Systems.HoverFeedback uses Domain.Skill✕
- Connections
- 1 pair of types, where a type in Systems.HoverFeedback uses a type in Domain.Skill.
- The types involved
Pomo.Core.Systems.HoverFeedback.HoverFeedback→Pomo.Core.Domain.Skill.Targeting
- Direction
- Systems.HoverFeedback uses Domain.Skill, so a change to Domain.Skill can break Systems.HoverFeedback, while a change to Systems.HoverFeedback can't break Domain.Skill.
- Position
- Below the diagonal: Systems.HoverFeedback uses a module listed above it, which is the healthy direction.
36→14 Systems.HoverFeedback uses Domain.BlockMap✕
- Connections
- 1 pair of types, where a type in Systems.HoverFeedback uses a type in Domain.BlockMap.
- The types involved
Pomo.Core.Systems.HoverFeedback.HoverFeedback→Pomo.Core.Domain.BlockMap.BlockMapDefinition
- Direction
- Systems.HoverFeedback uses Domain.BlockMap, so a change to Domain.BlockMap can break Systems.HoverFeedback, while a change to Systems.HoverFeedback can't break Domain.BlockMap.
- Position
- Below the diagonal: Systems.HoverFeedback uses a module listed above it, which is the healthy direction.
36→26 Systems.HoverFeedback uses Domain.World✕
- Connections
- 2 pairs of types, where a type in Systems.HoverFeedback uses a type in Domain.World.
- The types involved
Pomo.Core.Systems.HoverFeedback.HoverFeedback→Pomo.Core.Domain.World.ScenarioPomo.Core.Systems.HoverFeedback.HoverFeedback→Pomo.Core.Domain.World.World
- Direction
- Systems.HoverFeedback uses Domain.World, so a change to Domain.World can break Systems.HoverFeedback, while a change to Systems.HoverFeedback can't break Domain.World.
- Position
- Below the diagonal: Systems.HoverFeedback uses a module listed above it, which is the healthy direction.
36→28 Systems.HoverFeedback uses Projections✕
- Connections
- 1 pair of types, where a type in Systems.HoverFeedback uses a type in Projections.
- The types involved
Pomo.Core.Systems.HoverFeedback.HoverFeedback→Pomo.Core.Projections.ProjectionService
- Direction
- Systems.HoverFeedback uses Projections, so a change to Projections can break Systems.HoverFeedback, while a change to Systems.HoverFeedback can't break Projections.
- Position
- Below the diagonal: Systems.HoverFeedback uses a module listed above it, which is the healthy direction.
36→31 Systems.HoverFeedback uses Environment✕
- Connections
- 1 pair of types, where a type in Systems.HoverFeedback uses a type in Environment.
- The types involved
Pomo.Core.Systems.HoverFeedback.HoverFeedback→Pomo.Core.Environment.TargetingService
- Direction
- Systems.HoverFeedback uses Environment, so a change to Environment can break Systems.HoverFeedback, while a change to Systems.HoverFeedback can't break Environment.
- Position
- Below the diagonal: Systems.HoverFeedback uses a module listed above it, which is the healthy direction.
37→3 Systems.Navigation3D uses Domain.Core✕
- Connections
- 3 pairs of types, where a type in Systems.Navigation3D uses a type in Domain.Core.
- The types involved
Pomo.Core.Systems.Navigation3D.MovementContext→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Systems.Navigation3D.Navigation3D→Pomo.Core.Domain.Core.CoreEventListenerPomo.Core.Systems.Navigation3D.Navigation3D→Pomo.Core.Domain.Core.WorldPosition
- Direction
- Systems.Navigation3D uses Domain.Core, so a change to Domain.Core can break Systems.Navigation3D, while a change to Systems.Navigation3D can't break Domain.Core.
- Position
- Below the diagonal: Systems.Navigation3D uses a module listed above it, which is the healthy direction.
37→14 Systems.Navigation3D uses Domain.BlockMap✕
- Connections
- 2 pairs of types, where a type in Systems.Navigation3D uses a type in Domain.BlockMap.
- The types involved
Pomo.Core.Systems.Navigation3D.MovementContext→Pomo.Core.Domain.BlockMap.BlockMapDefinitionPomo.Core.Systems.Navigation3D.Navigation3D→Pomo.Core.Domain.BlockMap.BlockMapDefinition
- Direction
- Systems.Navigation3D uses Domain.BlockMap, so a change to Domain.BlockMap can break Systems.Navigation3D, while a change to Systems.Navigation3D can't break Domain.BlockMap.
- Position
- Below the diagonal: Systems.Navigation3D uses a module listed above it, which is the healthy direction.
37→22 Systems.Navigation3D uses Domain.Events.SystemCommunications✕
- Connections
- 1 pair of types, where a type in Systems.Navigation3D uses a type in Domain.Events.SystemCommunications.
- The types involved
Pomo.Core.Systems.Navigation3D.Navigation3D→Pomo.Core.Domain.Events.SystemCommunications.SetMovementTarget
- Direction
- Systems.Navigation3D uses Domain.Events.SystemCommunications, so a change to Domain.Events.SystemCommunications can break Systems.Navigation3D, while a change to Systems.Navigation3D can't break Domain.Events.SystemCommunications.
- Position
- Below the diagonal: Systems.Navigation3D uses a module listed above it, which is the healthy direction.
37→27 Systems.Navigation3D uses EventBus✕
- Connections
- 1 pair of types, where a type in Systems.Navigation3D uses a type in EventBus.
- The types involved
Pomo.Core.Systems.Navigation3D.Navigation3D→Pomo.Core.EventBus.EventBus
- Direction
- Systems.Navigation3D uses EventBus, so a change to EventBus can break Systems.Navigation3D, while a change to Systems.Navigation3D can't break EventBus.
- Position
- Below the diagonal: Systems.Navigation3D uses a module listed above it, which is the healthy direction.
37→28 Systems.Navigation3D uses Projections✕
- Connections
- 2 pairs of types, where a type in Systems.Navigation3D uses a type in Projections.
- The types involved
Pomo.Core.Systems.Navigation3D.Navigation3D→Pomo.Core.Projections.Movement3DSnapshotPomo.Core.Systems.Navigation3D.Navigation3D→Pomo.Core.Projections.ProjectionService
- Direction
- Systems.Navigation3D uses Projections, so a change to Projections can break Systems.Navigation3D, while a change to Systems.Navigation3D can't break Projections.
- Position
- Below the diagonal: Systems.Navigation3D uses a module listed above it, which is the healthy direction.
37→31 Systems.Navigation3D uses Environment✕
- Connections
- 1 pair of types, where a type in Systems.Navigation3D uses a type in Environment.
- The types involved
Pomo.Core.Systems.Navigation3D.Navigation3D→Pomo.Core.Environment.IStateWriteService
- Direction
- Systems.Navigation3D uses Environment, so a change to Environment can break Systems.Navigation3D, while a change to Systems.Navigation3D can't break Environment.
- Position
- Below the diagonal: Systems.Navigation3D uses a module listed above it, which is the healthy direction.
38→2 Systems.Projectile uses Domain.Animation✕
- Connections
- 1 pair of types, where a type in Systems.Projectile uses a type in Domain.Animation.
- The types involved
Pomo.Core.Systems.Projectile.Projectile→Pomo.Core.Domain.Animation.AnimationState
- Direction
- Systems.Projectile uses Domain.Animation, so a change to Domain.Animation can break Systems.Projectile, while a change to Systems.Projectile can't break Domain.Animation.
- Position
- Below the diagonal: Systems.Projectile uses a module listed above it, which is the healthy direction.
38→3 Systems.Projectile uses Domain.Core✕
- Connections
- 4 pairs of types, where a type in Systems.Projectile uses a type in Domain.Core.
- The types involved
Pomo.Core.Systems.Projectile.Projectile→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Systems.Projectile.ProjectileContext→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Systems.Projectile.VisualEffectContext→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Systems.Projectile.WorldContext→Pomo.Core.Domain.Core.WorldPosition
- Direction
- Systems.Projectile uses Domain.Core, so a change to Domain.Core can break Systems.Projectile, while a change to Systems.Projectile can't break Domain.Core.
- Position
- Below the diagonal: Systems.Projectile uses a module listed above it, which is the healthy direction.
38→5 Systems.Projectile uses Systems.Systems✕
- Connections
- 1 pair of types, where a type in Systems.Projectile uses a type in Systems.Systems.
- The types involved
Pomo.Core.Systems.Projectile.ProjectileSystem→Pomo.Core.Systems.Systems.GameSystem
- Direction
- Systems.Projectile uses Systems.Systems, so a change to Systems.Systems can break Systems.Projectile, while a change to Systems.Projectile can't break Systems.Systems.
- Position
- Below the diagonal: Systems.Projectile uses a module listed above it, which is the healthy direction.
38→9 Systems.Projectile uses Domain.Projectile✕
- Connections
- 2 pairs of types, where a type in Systems.Projectile uses a type in Domain.Projectile.
- The types involved
Pomo.Core.Systems.Projectile.Projectile→Pomo.Core.Domain.Projectile.LiveProjectilePomo.Core.Systems.Projectile.ProjectileContext→Pomo.Core.Domain.Projectile.LiveProjectile
- Direction
- Systems.Projectile uses Domain.Projectile, so a change to Domain.Projectile can break Systems.Projectile, while a change to Systems.Projectile can't break Domain.Projectile.
- Position
- Below the diagonal: Systems.Projectile uses a module listed above it, which is the healthy direction.
38→11 Systems.Projectile uses Domain.Skill✕
- Connections
- 1 pair of types, where a type in Systems.Projectile uses a type in Domain.Skill.
- The types involved
Pomo.Core.Systems.Projectile.Projectile→Pomo.Core.Domain.Skill.SkillArea
- Direction
- Systems.Projectile uses Domain.Skill, so a change to Domain.Skill can break Systems.Projectile, while a change to Systems.Projectile can't break Domain.Skill.
- Position
- Below the diagonal: Systems.Projectile uses a module listed above it, which is the healthy direction.
38→14 Systems.Projectile uses Domain.BlockMap✕
- Connections
- 1 pair of types, where a type in Systems.Projectile uses a type in Domain.BlockMap.
- The types involved
Pomo.Core.Systems.Projectile.VisualEffectContext→Pomo.Core.Domain.BlockMap.BlockMapDefinition
- Direction
- Systems.Projectile uses Domain.BlockMap, so a change to Domain.BlockMap can break Systems.Projectile, while a change to Systems.Projectile can't break Domain.BlockMap.
- Position
- Below the diagonal: Systems.Projectile uses a module listed above it, which is the healthy direction.
38→16 Systems.Projectile uses Domain.Particles✕
- Connections
- 2 pairs of types, where a type in Systems.Projectile uses a type in Domain.Particles.
- The types involved
Pomo.Core.Systems.Projectile.Projectile→Pomo.Core.Domain.Particles.VisualEffectPomo.Core.Systems.Projectile.VisualEffectContext→Pomo.Core.Domain.Particles.VisualEffect
- Direction
- Systems.Projectile uses Domain.Particles, so a change to Domain.Particles can break Systems.Projectile, while a change to Systems.Projectile can't break Domain.Particles.
- Position
- Below the diagonal: Systems.Projectile uses a module listed above it, which is the healthy direction.
38→21 Systems.Projectile uses Stores✕
- Connections
- 3 pairs of types, where a type in Systems.Projectile uses a type in Stores.
- The types involved
Pomo.Core.Systems.Projectile.Projectile→Pomo.Core.Stores.ParticleStorePomo.Core.Systems.Projectile.VisualEffectContext→Pomo.Core.Stores.ParticleStorePomo.Core.Systems.Projectile.VisualEffectContext→Pomo.Core.Stores.SkillStore
- Direction
- Systems.Projectile uses Stores, so a change to Stores can break Systems.Projectile, while a change to Systems.Projectile can't break Stores.
- Position
- Below the diagonal: Systems.Projectile uses a module listed above it, which is the healthy direction.
38→22 Systems.Projectile uses Domain.Events.SystemCommunications✕
- Connections
- 1 pair of types, where a type in Systems.Projectile uses a type in Domain.Events.SystemCommunications.
- The types involved
Pomo.Core.Systems.Projectile.Projectile→Pomo.Core.Domain.Events.SystemCommunications.ProjectileImpacted
- Direction
- Systems.Projectile uses Domain.Events.SystemCommunications, so a change to Domain.Events.SystemCommunications can break Systems.Projectile, while a change to Systems.Projectile can't break Domain.Events.SystemCommunications.
- Position
- Below the diagonal: Systems.Projectile uses a module listed above it, which is the healthy direction.
38→31 Systems.Projectile uses Environment✕
- Connections
- 2 pairs of types, where a type in Systems.Projectile uses a type in Environment.
- The types involved
Pomo.Core.Systems.Projectile.Projectile→Pomo.Core.Environment.IStateWriteServicePomo.Core.Systems.Projectile.ProjectileSystem→Pomo.Core.Environment.PomoEnvironment
- Direction
- Systems.Projectile uses Environment, so a change to Environment can break Systems.Projectile, while a change to Systems.Projectile can't break Environment.
- Position
- Below the diagonal: Systems.Projectile uses a module listed above it, which is the healthy direction.
39→1 Systems.StateWrite uses Domain.Action✕
- Connections
- 2 pairs of types, where a type in Systems.StateWrite uses a type in Domain.Action.
- The types involved
Pomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.Action.GameActionPomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.Action.InputActionState
- Direction
- Systems.StateWrite uses Domain.Action, so a change to Domain.Action can break Systems.StateWrite, while a change to Systems.StateWrite can't break Domain.Action.
- Position
- Below the diagonal: Systems.StateWrite uses a module listed above it, which is the healthy direction.
39→2 Systems.StateWrite uses Domain.Animation✕
- Connections
- 1 pair of types, where a type in Systems.StateWrite uses a type in Domain.Animation.
- The types involved
Pomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.Animation.AnimationState
- Direction
- Systems.StateWrite uses Domain.Animation, so a change to Domain.Animation can break Systems.StateWrite, while a change to Systems.StateWrite can't break Domain.Animation.
- Position
- Below the diagonal: Systems.StateWrite uses a module listed above it, which is the healthy direction.
39→3 Systems.StateWrite uses Domain.Core✕
- Connections
- 2 pairs of types, where a type in Systems.StateWrite uses a type in Domain.Core.
- The types involved
Pomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.Core.WorldPositionPomo.Core.Systems.StateWrite.NonAdaptiveCommand→Pomo.Core.Domain.Core.WorldPosition
- Direction
- Systems.StateWrite uses Domain.Core, so a change to Domain.Core can break Systems.StateWrite, while a change to Systems.StateWrite can't break Domain.Core.
- Position
- Below the diagonal: Systems.StateWrite uses a module listed above it, which is the healthy direction.
39→7 Systems.StateWrite uses Domain.Entity✕
- Connections
- 1 pair of types, where a type in Systems.StateWrite uses a type in Domain.Entity.
- The types involved
Pomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.Entity.Resource
- Direction
- Systems.StateWrite uses Domain.Entity, so a change to Domain.Entity can break Systems.StateWrite, while a change to Systems.StateWrite can't break Domain.Entity.
- Position
- Below the diagonal: Systems.StateWrite uses a module listed above it, which is the healthy direction.
39→8 Systems.StateWrite uses Domain.Orbital✕
- Connections
- 1 pair of types, where a type in Systems.StateWrite uses a type in Domain.Orbital.
- The types involved
Pomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.Orbital.ActiveOrbital
- Direction
- Systems.StateWrite uses Domain.Orbital, so a change to Domain.Orbital can break Systems.StateWrite, while a change to Systems.StateWrite can't break Domain.Orbital.
- Position
- Below the diagonal: Systems.StateWrite uses a module listed above it, which is the healthy direction.
39→9 Systems.StateWrite uses Domain.Projectile✕
- Connections
- 1 pair of types, where a type in Systems.StateWrite uses a type in Domain.Projectile.
- The types involved
Pomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.Projectile.LiveProjectile
- Direction
- Systems.StateWrite uses Domain.Projectile, so a change to Domain.Projectile can break Systems.StateWrite, while a change to Systems.StateWrite can't break Domain.Projectile.
- Position
- Below the diagonal: Systems.StateWrite uses a module listed above it, which is the healthy direction.
39→11 Systems.StateWrite uses Domain.Skill✕
- Connections
- 1 pair of types, where a type in Systems.StateWrite uses a type in Domain.Skill.
- The types involved
Pomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.Skill.ActiveEffect
- Direction
- Systems.StateWrite uses Domain.Skill, so a change to Domain.Skill can break Systems.StateWrite, while a change to Systems.StateWrite can't break Domain.Skill.
- Position
- Below the diagonal: Systems.StateWrite uses a module listed above it, which is the healthy direction.
39→13 Systems.StateWrite uses Domain.AI✕
- Connections
- 1 pair of types, where a type in Systems.StateWrite uses a type in Domain.AI.
- The types involved
Pomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.AI.AIController
- Direction
- Systems.StateWrite uses Domain.AI, so a change to Domain.AI can break Systems.StateWrite, while a change to Systems.StateWrite can't break Domain.AI.
- Position
- Below the diagonal: Systems.StateWrite uses a module listed above it, which is the healthy direction.
39→15 Systems.StateWrite uses Domain.Item✕
- Connections
- 2 pairs of types, where a type in Systems.StateWrite uses a type in Domain.Item.
- The types involved
Pomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.Item.ItemInstancePomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.Item.Slot
- Direction
- Systems.StateWrite uses Domain.Item, so a change to Domain.Item can break Systems.StateWrite, while a change to Systems.StateWrite can't break Domain.Item.
- Position
- Below the diagonal: Systems.StateWrite uses a module listed above it, which is the healthy direction.
39→22 Systems.StateWrite uses Domain.Events.SystemCommunications✕
- Connections
- 1 pair of types, where a type in Systems.StateWrite uses a type in Domain.Events.SystemCommunications.
- The types involved
Pomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.Events.SystemCommunications.SkillTarget
- Direction
- Systems.StateWrite uses Domain.Events.SystemCommunications, so a change to Domain.Events.SystemCommunications can break Systems.StateWrite, while a change to Systems.StateWrite can't break Domain.Events.SystemCommunications.
- Position
- Below the diagonal: Systems.StateWrite uses a module listed above it, which is the healthy direction.
39→24 Systems.StateWrite uses Domain.Events✕
- Connections
- 2 pairs of types, where a type in Systems.StateWrite uses a type in Domain.Events.
- The types involved
Pomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.Events.EntitySpawnBundlePomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.Events.MovementState
- Direction
- Systems.StateWrite uses Domain.Events, so a change to Domain.Events can break Systems.StateWrite, while a change to Systems.StateWrite can't break Domain.Events.
- Position
- Below the diagonal: Systems.StateWrite uses a module listed above it, which is the healthy direction.
39→26 Systems.StateWrite uses Domain.World✕
- Connections
- 4 pairs of types, where a type in Systems.StateWrite uses a type in Domain.World.
- The types involved
Pomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.World.ActiveChargePomo.Core.Systems.StateWrite.AdaptiveCommand→Pomo.Core.Domain.World.WorldTextPomo.Core.Systems.StateWrite.CommandBuffer`1→Pomo.Core.Domain.World.MutableWorldPomo.Core.Systems.StateWrite.StateWrite→Pomo.Core.Domain.World.MutableWorld
- Direction
- Systems.StateWrite uses Domain.World, so a change to Domain.World can break Systems.StateWrite, while a change to Systems.StateWrite can't break Domain.World.
- Position
- Below the diagonal: Systems.StateWrite uses a module listed above it, which is the healthy direction.
39→31 Systems.StateWrite uses Environment✕
- Connections
- 1 pair of types, where a type in Systems.StateWrite uses a type in Environment.
- The types involved
Pomo.Core.Systems.StateWrite.StateWrite→Pomo.Core.Environment.IStateWriteService
- Direction
- Systems.StateWrite uses Environment, so a change to Environment can break Systems.StateWrite, while a change to Systems.StateWrite can't break Environment.
- Position
- Below the diagonal: Systems.StateWrite uses a module listed above it, which is the healthy direction.
40→1 Systems.Targeting uses Domain.Action✕
- Connections
- 1 pair of types, where a type in Systems.Targeting uses a type in Domain.Action.
- The types involved
Pomo.Core.Systems.Targeting.Targeting→Pomo.Core.Domain.Action.GameAction
- Direction
- Systems.Targeting uses Domain.Action, so a change to Domain.Action can break Systems.Targeting, while a change to Systems.Targeting can't break Domain.Action.
- Position
- Below the diagonal: Systems.Targeting uses a module listed above it, which is the healthy direction.
40→3 Systems.Targeting uses Domain.Core✕
- Connections
- 1 pair of types, where a type in Systems.Targeting uses a type in Domain.Core.
- The types involved
Pomo.Core.Systems.Targeting.Targeting→Pomo.Core.Domain.Core.SlotProcessing
- Direction
- Systems.Targeting uses Domain.Core, so a change to Domain.Core can break Systems.Targeting, while a change to Systems.Targeting can't break Domain.Core.
- Position
- Below the diagonal: Systems.Targeting uses a module listed above it, which is the healthy direction.
40→11 Systems.Targeting uses Domain.Skill✕
- Connections
- 2 pairs of types, where a type in Systems.Targeting uses a type in Domain.Skill.
- The types involved
Pomo.Core.Systems.Targeting.HandleSelectedTargetArgs→Pomo.Core.Domain.Skill.SkillPomo.Core.Systems.Targeting.Targeting→Pomo.Core.Domain.Skill.Skill
- Direction
- Systems.Targeting uses Domain.Skill, so a change to Domain.Skill can break Systems.Targeting, while a change to Systems.Targeting can't break Domain.Skill.
- Position
- Below the diagonal: Systems.Targeting uses a module listed above it, which is the healthy direction.
40→21 Systems.Targeting uses Stores✕
- Connections
- 1 pair of types, where a type in Systems.Targeting uses a type in Stores.
- The types involved
Pomo.Core.Systems.Targeting.Targeting→Pomo.Core.Stores.SkillStore
- Direction
- Systems.Targeting uses Stores, so a change to Stores can break Systems.Targeting, while a change to Systems.Targeting can't break Stores.
- Position
- Below the diagonal: Systems.Targeting uses a module listed above it, which is the healthy direction.
40→27 Systems.Targeting uses EventBus✕
- Connections
- 2 pairs of types, where a type in Systems.Targeting uses a type in EventBus.
- The types involved
Pomo.Core.Systems.Targeting.HandleSelectedTargetArgs→Pomo.Core.EventBus.EventBusPomo.Core.Systems.Targeting.Targeting→Pomo.Core.EventBus.EventBus
- Direction
- Systems.Targeting uses EventBus, so a change to EventBus can break Systems.Targeting, while a change to Systems.Targeting can't break EventBus.
- Position
- Below the diagonal: Systems.Targeting uses a module listed above it, which is the healthy direction.
40→28 Systems.Targeting uses Projections✕
- Connections
- 1 pair of types, where a type in Systems.Targeting uses a type in Projections.
- The types involved
Pomo.Core.Systems.Targeting.Targeting→Pomo.Core.Projections.ProjectionService
- Direction
- Systems.Targeting uses Projections, so a change to Projections can break Systems.Targeting, while a change to Systems.Targeting can't break Projections.
- Position
- Below the diagonal: Systems.Targeting uses a module listed above it, which is the healthy direction.
40→31 Systems.Targeting uses Environment✕
- Connections
- 3 pairs of types, where a type in Systems.Targeting uses a type in Environment.
- The types involved
Pomo.Core.Systems.Targeting.HandleSelectedTargetArgs→Pomo.Core.Environment.IStateWriteServicePomo.Core.Systems.Targeting.Targeting→Pomo.Core.Environment.IStateWriteServicePomo.Core.Systems.Targeting.Targeting→Pomo.Core.Environment.TargetingService
- Direction
- Systems.Targeting uses Environment, so a change to Environment can break Systems.Targeting, while a change to Systems.Targeting can't break Environment.
- Position
- Below the diagonal: Systems.Targeting uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 8 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
Top priorities: Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it; Resolve the 1 No ADRs found finding(s) in ADR Quality.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +8.8 pts | Medium | Observability |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +3.6 pts | Medium | Deployment & Rollback |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +1.8 pts | Low | ADR Quality |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.0 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.0 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +1.0 pts | Low | Supply-chain Provenance & Signing |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +1.0 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| Pomo.Core/Systems/Combat.fs | 7.0 | Mixed | Cyclomatic Complexity: Handlers.handleChargeCompleted (cyclomatic 29) |
| Pomo.Core/Systems/AISystem.fs | 7.0 | Mixed | Cyclomatic Complexity: BehaviorTreeExecution.evaluateCondition (cyclomatic 28) |
| Pomo.Core/Scenes/BlockMapScene.fs | 7.0 | Mixed | Code Duplication: Near-duplicate member pair (294 shared lines) |
| Pomo.Core/UI/Widgets.fs | 7.0 | Mixed | Cyclomatic Complexity: MiniMap.InternalRender (cyclomatic 18) |
| Pomo.Core/Projections.fs | 7.0 | Mixed | Cognitive Complexity: Projections.create (cognitive 45) |
| Pomo.Core/Domain/Skill.fs | 7.1 | Mixed | Cyclomatic Complexity: FormulaParser.classifyVar (cyclomatic 31) |
| Pomo.Core/Systems/ParticleSystem.fs | 7.1 | Mixed | Cyclomatic Complexity: ParticleSystem.updateEmitter (cyclomatic 19) |
| Pomo.Core/Editor/Input.fs | 7.2 | Mixed | Cyclomatic Complexity: EditorInput.handleEditorInput (cyclomatic 47) |
| Pomo.Core/Stores.fs | 7.2 | Mixed | Code Duplication: Duplicated block (14 lines × 2) |
| Pomo.Core/Systems/AbilityActivation.fs | 7.4 | Mixed | Cyclomatic Complexity: AbilityActivationSystem.Update (cyclomatic 24) |
| Pomo.Core/Editor/UI.fs | 7.4 | Mixed | Cyclomatic Complexity: EditorUI.build (cyclomatic 22) |
| Pomo.Core/Systems/EffectApplication.fs | 7.4 | Mixed | Cognitive Complexity: EffectApplication.applyEffect (cognitive 21) |
| Pomo.Core/Domain/Spatial.fs | 7.4 | Mixed | Cognitive Complexity: Spatial.circleChainMTV (cognitive 20) |
| Pomo.Core/Systems/Targeting.fs | 7.4 | Mixed | Cognitive Complexity: Targeting.handleTargetSelected (cognitive 16) |
| Pomo.Core/Systems/HUDComponents.fs | 7.4 | Mixed | God Classes: FileTooLong: Systems/HUDComponents.fs |
| Pomo.Core/UI/MyraExtensions.fs | 7.4 | Mixed | God Classes: FileTooLong: UI/MyraExtensions.fs |
| Pomo.Core/Domain/Core.fs | 7.4 | Mixed | Code Duplication: Edited copy of a member (50 corresponding lines) |
| Pomo.Core/Systems/State.fs | 7.8 | Mixed | Cyclomatic Complexity: StateWrite.applyAdaptiveCommand (cyclomatic 38) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 39 of 39 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 39 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 135 of 148 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
- D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: /usr/share/dotnet/sdk/10.0.400/NuGet.targets(521,5): error MSB3202: The project file "Pomo.WindowsDX/Pomo.Vulkan.fsproj" was not found. [Pomo.slnx].
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 157 commit(s) sampled, automation and bot accounts excluded). One of them holds 99% of the history; the other 1 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository's source is written only in languages whose packages are published through a manifest, and no manifest in the tree makes a publication act: either there is no package manifest of any ecosystem (no package.json, pyproject.toml, setup.py, gemspec, Cargo.toml, pom.xml, build.gradle, composer.json, pubspec.yaml or mix.exs), or every one present declares in its package manager's own terms that it is not published (an npm package marked "private": true, a Cargo package with publish = false, a pubspec with publish_to: none, a Composer "project", a Poetry project with package-mode = false, or the "Private :: Do Not Upload" classifier). With no publication act there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D39 IL Efficiency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. `dotnet build` exited 1 with a compiler/MSBuild diagnostic, so there were no assemblies to read IL from. The build itself is D18's row, with the ask; nothing further is charged here.
- AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in Pomo.Core/CompositionRoot.fs, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (Pomo.iOS/LaunchScreen.storyboard). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. Watchdog then boots it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- DM8 Value-object opportunities — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X6 Hand-rolled structured-format parsing — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X7 Silent fallback defaults — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
Dimensions
D1 · Cyclomatic Complexity
22 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was EditorInput.handleEditorInput at 47. A further 9 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Effect.formulaEncoder at 38 — they are counted neither in the figure above nor in this dimension's score. 6 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Pomo.Core/Domain/Core.fs (Stat.decoder at 32), Pomo.Core/Systems/FormulaEvaluator.fs (FormulaEvaluator.getValue at 22), Pomo.Core/Projections.fs (DerivedStatsCalculator.updateStat at 18), Pomo.Core/Systems/HUDService.fs (HUDService.create at 17), Pomo.Core/Domain/Entity.fs (Faction.decoder at 16), and 1 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 22 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with EditorInput.handleEditorInput (cyclomatic 47), StateWrite.applyAdaptiveCommand (cyclomatic 38), OrbitalSystem.Update (cyclomatic 35). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 22 together lifts Cyclomatic Complexity from 7.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
45 method(s) exceeded the cognitive complexity threshold of 15; the worst was OrbitalSystem.Update at 92.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with OrbitalSystem.Update (cognitive 92). — Refactoring it lifts Cognitive Complexity from 4.2 to about 5.1/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
8 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 8 FileTooLong finding(s) in God Classes — start with AISystem.fs, Skill.fs, HUDComponents.fs. — One of this dimension's main actionable groups (8 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
46 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 6 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with Extensions.fs, BlockMapScene.fs, Stores.fs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with BlockMap.fs, Spatial.fs, BlockMapScene.fs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with Combat.fs, EffectApplication.fs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
7 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D6 · Cohesion (LCOM4)
0 of 11 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 1 measured tier(s). unit: measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 223 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 18 direct `PackageReference`(s), and 199 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 6 build units (MSBuild) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
93 % of calls cross a namespace and 6 % go through an interface, but 96 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
8 finding(s): 0 critical, 8 high, 0 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 6 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (6 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 90 of the 117 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: World.fs↔PomoGame.fs 82%; Events.fs↔PomoGame.fs 70%; PomoGame.fs↔State.fs 69%
What to do
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with PomoGame.fs. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 7 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
DM12 · Ambient inputs in the domain
DM6 · Domain ↔ infrastructure boundary
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
- Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
- Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 8555 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
- `Pomo.Android/Pomo.Android.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Pomo.Android/Pomo.Android.fsproj:23
What to do
- Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
PF2 · Allocation hygiene
X20 · Mistyped argument guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 72% | Strong | Solid. |
| Architecture | 97% | Exemplary | Solid. |
| Maturity | 75% | Strong | Solid. |
| Readiness | 36% | Weak — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 68% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 85 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~2121 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
- D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .fs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — IL not measured — the target did not build
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — no coverage collector is wired up
- D9 Test Distribution — Test source is present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
- DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X7 Silent fallback defaults — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 8 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 127 finding(s)
- FileTooLong: Systems/AISystem.fs Pomo.Core/Systems/AISystem.fs
- FileTooLong: Domain/Skill.fs Pomo.Core/Domain/Skill.fs
- FileTooLong: Systems/HUDComponents.fs Pomo.Core/Systems/HUDComponents.fs
- FileTooLong: Systems/Combat.fs Pomo.Core/Systems/Combat.fs
- FileTooLong: Systems/ParticleSystem.fs Pomo.Core/Systems/ParticleSystem.fs
- FileTooLong: Systems/State.fs Pomo.Core/Systems/State.fs
- FileTooLong: UI/MyraExtensions.fs Pomo.Core/UI/MyraExtensions.fs
- FileTooLong: Pomo.Core/Projections.fs Pomo.Core/Projections.fs
- Duplicated block (14 lines × 2) Pomo.Core/Extensions.fs:126
- Duplicated block (14 lines × 2) Pomo.Core/Scenes/BlockMapScene.fs:190
- Duplicated block (14 lines × 2) Pomo.Core/Stores.fs:136
- Duplicated block (14 lines × 2) Pomo.Core/Systems/Combat.fs:75
- Duplicated block (14 lines × 2) Pomo.Core/Systems/Equipment.fs:1
- Duplicated block (14 lines × 2) Pomo.Core/Systems/Targeting.fs:150
- Duplicated block (10 lines × 2) Pomo.Core/Domain/BlockMap.fs:409
- Duplicated block (10 lines × 2) Pomo.Core/Domain/Spatial.fs:141
- Duplicated block (10 lines × 2) Pomo.Core/Scenes/BlockMapScene.fs:387
- Duplicated block (15 lines × 2) Pomo.Core/Systems/Combat.fs:970
- Duplicated block (15 lines × 2) Pomo.Core/Systems/EffectApplication.fs:309
- Duplicated block (13 lines × 2) Pomo.Core/Systems/ParticleSystem.fs:285
- Duplicated block (13 lines × 2) Pomo.Core/UI/Widgets.fs:116
- Duplicated block (11 lines × 2) Pomo.Core/Stores.fs:83
- Duplicated block (11 lines × 2) Pomo.Core/Editor/UI.fs:94
- Duplicated block (10 lines × 3) Pomo.Core/Stores.fs:84
- Duplicated block (10 lines × 3) Pomo.Core/UI/Widgets.fs:116
- Duplicated block (8 lines × 2) Pomo.Core/Domain/Skill.fs:1223
- Duplicated block (8 lines × 2) Pomo.Core/UI/MyraExtensions.fs:283
- EditorInput.handleEditorInput (cyclomatic 47) Pomo.Core/Editor/Input.fs:110
- StateWrite.applyAdaptiveCommand (cyclomatic 38) Pomo.Core/Systems/State.fs:506
- OrbitalSystem.Update (cyclomatic 35) Pomo.Core/Systems/OrbitalSystem.fs:100
- EmitterConfigCodec.decoder (cyclomatic 32) Pomo.Core/Domain/Particles.fs:465
- FormulaParser.classifyVar (cyclomatic 31) Pomo.Core/Domain/Skill.fs:233
- Handlers.handleChargeCompleted (cyclomatic 29) Pomo.Core/Systems/Combat.fs:914
- BehaviorTreeExecution.evaluateCondition (cyclomatic 28) Pomo.Core/Systems/AISystem.fs:455
- Handlers.handleInstantDelivery (cyclomatic 25) Pomo.Core/Systems/Combat.fs:575
- AbilityActivationSystem.Update (cyclomatic 24) Pomo.Core/Systems/AbilityActivation.fs:465
- UnitMovementSystem.Update (cyclomatic 23) Pomo.Core/Systems/UnitMovement.fs:40
- EditorUI.build (cyclomatic 22) Pomo.Core/Editor/UI.fs:15
- AISystem.Update (cyclomatic 20) Pomo.Core/Systems/AISystem.fs:1265
- Handlers.handleProjectileImpact (cyclomatic 20) Pomo.Core/Systems/Combat.fs:781
- ParticleSystem.updateEmitter (cyclomatic 19) Pomo.Core/Systems/ParticleSystem.fs:427
- ParticleSystem.updateSingleEffect (cyclomatic 18) Pomo.Core/Systems/ParticleSystem.fs:830
- CombatSystem.Initialize (cyclomatic 18) Pomo.Core/Systems/Combat.fs:1127
- MiniMap.InternalRender (cyclomatic 18) Pomo.Core/UI/Widgets.fs:421
- Camera.tryGetViewBoundsFromMatrices (cyclomatic 18) Pomo.Core/Graphics/RenderMath.fs:90
- BehaviorTreeExecution.executeAction (cyclomatic 17) Pomo.Core/Systems/AISystem.fs:514
- TextEmitter.emit (cyclomatic 17) Pomo.Core/Rendering/TextEmitter.fs:19
- EditorInput.handleCameraInput (cyclomatic 16) Pomo.Core/Editor/Input.fs:42
- Perception.gatherCues (cyclomatic 16) Pomo.Core/Systems/AISystem.fs:322
- OrbitalSystem.Update (cognitive 92) Pomo.Core/Systems/OrbitalSystem.fs:100
- EditorInput.handleEditorInput (cognitive 57) Pomo.Core/Editor/Input.fs:110
- UnitMovementSystem.Update (cognitive 54) Pomo.Core/Systems/UnitMovement.fs:40
- Camera.tryGetViewBoundsFromMatrices (cognitive 50) Pomo.Core/Graphics/RenderMath.fs:90
- Projections.create (cognitive 45) Pomo.Core/Projections.fs:621
- AbilityActivationSystem.Update (cognitive 42) Pomo.Core/Systems/AbilityActivation.fs:465
- MiniMap.InternalRender (cognitive 42) Pomo.Core/UI/Widgets.fs:421
- BehaviorTreeExecution.evaluateCondition (cognitive 36) Pomo.Core/Systems/AISystem.fs:455
- FormulaParser.classifyVar (cognitive 35) Pomo.Core/Domain/Skill.fs:233
- AISystem.Update (cognitive 33) Pomo.Core/Systems/AISystem.fs:1265
- Handlers.handleChargeCompleted (cognitive 33) Pomo.Core/Systems/Combat.fs:914
- Perception.gatherVisualCues (cognitive 31) Pomo.Core/Systems/AISystem.fs:233
- Handlers.handleProjectileImpact (cognitive 31) Pomo.Core/Systems/Combat.fs:781
- Evaluator.backtrackToNextChild (cognitive 30) Pomo.Core/Systems/AISystem.fs:757
- ParticleEmitter.loadAssets (cognitive 29) Pomo.Core/Rendering/ParticleEmitter.fs:70
- AStar.findPathWithHeight (cognitive 29) Pomo.Core/Algorithms/Pathfinding3D.fs:184
- ParticleSystem.updateEmitter (cognitive 26) Pomo.Core/Systems/ParticleSystem.fs:427
- EditorInput.handleCameraInput (cognitive 25) Pomo.Core/Editor/Input.fs:42
- Navigation3D.trySnapToNearestWalkable (cognitive 23) Pomo.Core/Systems/Navigation3D.fs:57
- EditorUI.build (cognitive 22) Pomo.Core/Editor/UI.fs:15
- BehaviorTreeExecution.evaluate (cognitive 21) Pomo.Core/Systems/AISystem.fs:798
- EffectApplication.applyEffect (cognitive 21) Pomo.Core/Systems/EffectApplication.fs:49
- Handlers.handlePendingCast (cognitive 21) Pomo.Core/Systems/AbilityActivation.fs:223
- EntityPicker.pickEntityBlockMap3D (cognitive 21) Pomo.Core/Rendering/EntityPicker.fs:16
- Perception.gatherCues (cognitive 20) Pomo.Core/Systems/AISystem.fs:322
- BehaviorTreeExecution.executeAction (cognitive 20) Pomo.Core/Systems/AISystem.fs:514
- BlockEmitter.emit (cognitive 20) Pomo.Core/Rendering/BlockEmitter.fs:47
- Spatial.circleChainMTV (cognitive 20) Pomo.Core/Domain/Spatial.fs:402
- Helpers.generateIntervalEvents (cognitive 19) Pomo.Core/Systems/EffectApplication.fs:234
- BlockMapCameraSystem.create (cognitive 18) Pomo.Core/Systems/BlockMapCameraSystem.fs:24
- Spatial3D.canOccupyWithConfig (cognitive 18) Pomo.Core/Algorithms/Spatial3D.fs:93
- Spatial3D.canTraverseWithConfig (cognitive 18) Pomo.Core/Algorithms/Spatial3D.fs:212
- EmitterConfigCodec.decoder (cognitive 18) Pomo.Core/Domain/Particles.fs:465
- ModelMetrics.computeNodeOffset (cognitive 17) Pomo.Core/Graphics/ModelMetrics.fs:42
- RingEventBus.FlushToObservable (cognitive 17) Pomo.Core/EventBus.fs:41
- SpanToken.peek (cognitive 17) Pomo.Core/Domain/Skill.fs:287
- Decision.selectBestCue (cognitive 16) Pomo.Core/Systems/AISystem.fs:861
- ParticleSystem.updateSingleEffect (cognitive 16) Pomo.Core/Systems/ParticleSystem.fs:830
- Inventory.handleUseItemIntent (cognitive 16) Pomo.Core/Systems/Inventory.fs:28
- RenderPasses.renderMeshes (cognitive 16) Pomo.Core/Systems/RenderOrchestratorV2.fs:55
- RenderPasses.renderGhost (cognitive 16) Pomo.Core/Systems/RenderOrchestratorV2.fs:173
- Targeting.handleTargetSelected (cognitive 16) Pomo.Core/Systems/Targeting.fs:228
- Handlers.handleInstantDelivery (cognitive 16) Pomo.Core/Systems/Combat.fs:575
- PhysicsCache.calculateSnapshot (cognitive 16) Pomo.Core/Projections.fs:383
- PhysicsCache.calculate3DSnapshot (cognitive 16) Pomo.Core/Projections.fs:457
- Change-coupling hub: PomoGame.fs → Events.fs, World.fs, AbilityActivation.fs, State.fs Pomo.Core/PomoGame.fs
- REDACTED
- Near-duplicate member pair (294 shared lines) Pomo.Core/Scenes/BlockMapScene.fs:1
- Edited copy of a member (50 corresponding lines) Pomo.Core/Domain/Core.fs:1
- Duplicated block (89–92 lines × 2) Pomo.Core/Scenes/BlockMapScene.fs:209
- Duplicated block (37 lines × 2) Pomo.Core/Scenes/BlockMapScene.fs:94
- Duplicated block (32 lines × 2) Pomo.Core/Scenes/BlockMapScene.fs:141
- Duplicated block (2–30 lines × 4) Pomo.Core/Domain/Core.fs:230
- Duplicated block (24–26 lines × 2) Pomo.Core/Scenes/BlockMapScene.fs:361
- Duplicated block (24 lines × 2) Pomo.Core/Scenes/BlockMapScene.fs:47
- Duplicated block (23 lines × 2) Pomo.Core/Scenes/BlockMapScene.fs:71
- Duplicated block (21 lines × 2) Pomo.Core/Systems/Combat.fs:263
- Duplicated block (20–21 lines × 2) Pomo.Core/Systems/Targeting.fs:114
- Duplicated block (18 lines × 2) Pomo.Core/Rendering/BlockEmitter.fs:15
- Duplicated block (14–18 lines × 2) Pomo.Core/Systems/HUDComponents.fs:473
- Duplicated block (17 lines × 2) Pomo.Core/UI/Widgets.fs:132
- Duplicated block (16 lines × 2) Pomo.Core/Scenes/BlockMapScene.fs:1
- Duplicated block (13–15 lines × 2) Pomo.Core/Scenes/BlockMapScene.fs:25
- Duplicated block (12 lines × 3) Pomo.Core/UI/MyraExtensions.fs:556
- Duplicated block (12 lines × 2) Pomo.Core/Systems/HUDComponents.fs:144
- Duplicated block (9–11 lines × 2) Pomo.Core/UI/Widgets.fs:55
- Duplicated block (8–10 lines × 3) Pomo.Core/Graphics/Camera.fs:116
- Duplicated block (7–10 lines × 2) Pomo.Core/Projections.fs:418
- Duplicated block (9–10 lines × 2) Pomo.Core/Scenes/BlockMapScene.fs:350
- Duplicated block (9 lines × 6) Pomo.Core/Stores.fs:34
- Duplicated block (9 lines × 3) Pomo.Core/UI/Widgets.fs:137
- Duplicated block (2–9 lines × 4) Pomo.Core/Domain/Core.fs:260
- Duplicated block (7–8 lines × 3) Pomo.Core/Domain/Spatial.fs:141
- Duplicated block (6 lines × 2) Pomo.Core/Projections.fs:390
- Duplicated block (5 lines × 2) Pomo.Core/Projections.fs:384
- Duplicated block (9 lines × 2) Pomo.Core/Domain/Skill.fs:1116
- No structured logging
- NuGet dependencies are not locked
Minor — 13 finding(s)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No src/ separation
- No SAST REDACTED:4
- No dependency-update automation Pomo.Android/Pomo.Android.fsproj:23
- No release approval gate
- Duplicated predicate Pomo.Core/Algorithms/BlockMap.fs:273
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f6189be80e5249049b8e8bcff43481e4/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f6189be80e5249049b8e8bcff43481e4/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (no readable dependency manifest) | — | none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet). | 0 | — |