Replace content with fixed, deduplicated architecture.

[croadfeldt]

Closes PR #7 — this PR replaces the content from PR #7 with the complete, fixed architecture documentation. All review comments from PR #7 are addressed:

Issues fixed from PR #7

• @jenniferubah, @gabriel-farache: Duplicate data-model/ and architecture/data-model/ directories → eliminated. Only architecture/data-model/ exists now (55 docs with number prefixes).
• @gabriel-farache: Broken links to foundations, provider-contract, policy-contract, capabilities matrix → all fixed. Zero broken cross-references verified.
• @gabriel-farache: "links broken, I think all links should be reviewed" → done. Full automated cross-reference scan, zero broken links.
• @machacekondra: Slug duplicates (e.g., foundations.md duplicating 00-foundations.md) → removed. 53 slug duplicates eliminated.
• @machacekondra: K8s operator SDK imperative vs declarative concern → addressed in updated dcm-operator-sdk-api.md
• @pkliczewski: Accreditation flow diagrams, data_classification ownership, GitOps handling → all clarified in updated docs

What changed vs PR #7

• 116 duplicate files removed (55 flat data-model copy + 53 slug dupes + 8 spec slug dupes)
• Provider count: 11 → 12 (ITSM Provider added)
• Policy count: 7 → 8 (ITSM Action added)
• data_classification enum: 5 → 8 values (phi, pci, classified added)
• All OpenAPI YAMLs synced with canonical schemas
• Capabilities Matrix deduplicated (6 duplicate summary tables removed)
• All Discussion Topics marked Resolved with cross-references

Content structure

content/
├── _index.md
└── docs/
    ├── architecture/
    │   ├── data-model/            ← 55 docs + _index.md (SINGLE location)
    │   └── specifications/        ← 15 specs + 4 OpenAPI YAMLs + _index.md
    ├── capabilities-matrix.md
    ├── DISCUSSION-TOPICS.md
    ├── taxonomy.md
    ├── project-overview.md
    ├── enhancements/
    ├── implementations/
    └── schemas/
static/
└── capabilities/
    └── DCM-Capabilities-Matrix.csv

[sourcery-ai]

Sorry, we are unable to review this pull request

The GitHub API does not allow us to fetch diffs exceeding 20000 lines

[gabriel-farache]

why is this file numbered while other in the folder are not?

[gabriel-farache]

why were all the enhancements files removed? Is it because in the index there is already a link to the enhancement repo? Or because they were scattered in other places?

[machacekondra]

So the only reason we need Kafka is for dcm-request-processor-> dcm-policy-engine communication?

[machacekondra]

So we wanna use AAP?

[croadfeldt]

My guess is that there will be a lot of providers that implement AAP. This is an example of how a provider might be implemented.

[machacekondra]

So we are not interested in status updates? Or why there is so many ways of sending status?

[machacekondra]

In above you use API to communicate with DCM, but you say the intent is stored in gitlab? So user is not using git to manage it's infra but API, which is creating a commits in git?

[croadfeldt]

This should be cleaned up. The intent was to have incoming requests via Git. The use of git internally has been removed and consolidated.

[machacekondra]

If I understand your architecture correctly, you are here missing the most important thing, which is something like /info. This should provide you name of the networks,storage,images,etc. Which will be used during mutation phase of the policy execution. Otherwise how can you have those fields in DCM, by hardcoding policies? IMHO that's unmaintainable.

[machacekondra]

How do you define the dependencies between those? depends_on is not enough, it's says what depends on what, but it doesn't say WHY. That's what is most imporant, because based on WHY you can construct the graph. WHY VM depends on Network Port? What it needs? How do I use it? How do I specify it? Where?

[machacekondra]

How VM could have dependencies, if it's just one resource? What's content of dependencies.yaml?

[machacekondra]

How do you keep those files in sync with real providers data?

[machacekondra]

Can you please show three-tier app, so we see how the three tier app is defined and the dependecies between the app? Like backend needs IP of database at least.