Skip to content

Commit

Permalink
Fix some broken links to the monorepo and update to reference CALM (#176
Browse files Browse the repository at this point in the history
)
  • Loading branch information
rocketstack-matt committed Jan 23, 2024
1 parent 17b5595 commit 3c813ca
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/working-groups/aasc.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,16 +7,16 @@ sidebar_position: 4
"Architecture as Code" (AasC) aims to devise and manage software architecture via a readable and version-controlled codebase, fostering a robust understanding, efficient development, and seamless maintenance of complex software architectures.

## About this Working Group
The Architecture as Code Working Group is a forum for the discussion and coordination of the [Architecture as Code](https://github.com/finos-labs-/architecture-as-code) Manifest and its associated projects. The group is open to all interested parties, and we welcome contributions from all members of the community.
The Architecture as Code Working Group is a forum for the discussion and coordination of the [Architecture as Code](https://github.com/finos-labs/architecture-as-code) Manifest and its associated projects. The group is open to all interested parties, and we welcome contributions from all members of the community.

## Objectives

### Maintain the Architecture as Code Manifest
This Working Group is responsible for maintaining the [Architecture as Code Manifest](https://github.com/finos-labs/architecture-as-code/tree/main/manifest). The manifest is a collection of JSON schemas that defines the structure and content of a system architecture. The manifest is designed to be used as a single source of truth for the architecture of a system.
This Working Group is responsible for maintaining the [Common Architecture Language Model](https://github.com/finos-labs/architecture-as-code/tree/main/calm). The manifest is a collection of JSON schemas that defines the structure and content of a system architecture. The manifest is designed to be used as a single source of truth for the architecture of a system.

The manifest is split into a core schema, the key elements required to define a system architecture, and domains, which are supplementary schemas that provide additional context and capabilities for a specific domain of the architecture such as security, deployment, data, etc.

For more details on how the manifest is structured, please see the [manifest documentation](https://github.com/finos-labs/architecture-as-code/blob/main/manifest/README.md)
For more details on how the manifest is structured, please see the [CALM docs](https://finos-labs.github.io/architecture-as-code/)

### Develop Architecture Capabilities
In addition to the manifest, the working group also oversees the development of key capabilities. A capability is the implementation of a key feature to support the architecture community such as:
Expand Down

0 comments on commit 3c813ca

Please sign in to comment.