Add CALM Architecture documentation for TraderX

[jimthompson5802]

Feature Request

Given that TraderX and CALM are both FINOS projects, showcasing CALM version of TraderX architecture representation would be a good demonstration of these projects.

Description of Problem:

Currently the only architecture documentation available is based on C4 and separate markdown file for workflows. The various architecture views are generated through CI/CD GH Actions.

Potential Solutions:

No changes are recommended for the current architecture documentation.

The intent of this proposal is to add the CALM related artifacts to match, as closely as possible, the current TraderX architecture documentation. Specifically, these changes are proposed:

• create following files

docs/
└── calm/
    ├── trading-system.architecture.json
    ├── trading-system-architecture-views.md
    ├── trading-system-process-flows.md
    ├── create-diagrams.sh
    └── templates/
        ├── trading-system-process-template.md
        └── architecture-diagram-template.md

• trading-system.architecture.json CALM architecture file for TraderX
• trading-system-architecture.md Generated views of the CALM architecture that is equivalent to the current architecture images structurizr-*.png
• trading-system-process-flows.md Process flows for TraderX
• create-diagrams.sh shell script that runs calm docify to generate the architecture views
• templates/architecture-diagram-template.md CALM template file to generate the architecture views.
• templates/trading-system-process-template.md CALM template file to generate business process flows

[jimthompson5802]

If this an acceptable proposal, I'm willing to create a PR to add the CALM content.

[DovOps]

@jimthompson5802 - Thanks again - As commented on #333 - We're moving this entire repo to a spec-driven approach, most likely using GitHub's Spec Kit. This will allow us to generate all of the relevant permutations.

Currently this is in a branch https://github.com/finos/traderX/tree/feature/agentic-renovation - But will eventually replace main branch as the default content.

Once this happens we will likely need to rethink how CALM is generated on a per-code-state basis as the repos are generated. This is a bit more work, but far more rewarding and impactful to illustrate the differences between architectures in the repos themselves.

@rocketstack-matt @matthewgardner @jpgough @yt-ms @masterkhal