Skip to content

Turn dependency rules into executable architecture checks #94

Description

@mikaelbjorn

Convert the documented dependency rules into executable checks that fail when adapters import service-local internals, when capability layers import UI- or protocol-specific code, or when new code bypasses the approved public surfaces. Implement the smallest viable enforcement first using restricted-import rules, dependency graph assertions, or focused architecture tests wired into CI. Acceptance notes: illegal dependency direction must become visible in automation rather than depending on human review only.


Imported from backlog CSV.

Project metadata:

  • Lane: Platform Foundation
  • Feature: Boundary Enforcement
  • EstimateDays: 1
  • Status: Backlog
  • Priority: High
  • Repository: execution-layer
  • Labels: architecture,governance,ci
  • Source CSV row: 2

Metadata

Metadata

Assignees

No one assigned

    Labels

    architectureImported backlog labelciImported backlog labelgovernanceImported backlog label

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions