2 pointsby nxy4 hours ago1 comment
  • xms171892 hours ago
    Interesting approach. How do you define the boundary contracts so they stay strict enough for cheaper models without becoming too brittle when the architecture changes?
    • nxy29 minutes ago
      Through the use of module boundary level contracts and strict checks like dependencies/imports, because that’s where cheaper models would often stray. I think it’s important to keep the checks simple instead of complex coding checks. For example, “accounts is not allowed to import billing”.