Scenario Summary

In the context of ADRs, policies are created by implementing a well-known and structured model.

Problem Statement

If no explicit model is provided, users can create policies with their own models. Also, this could lead to unnecessary repeated work and reduce the overall clarity of the policies.

Proposed Solution

Create a template for a governance policy, according to the specification. The initial proposed format, which is well known to suit a version-controlled repository, is Markdown.

Scenario summary

The repo has a dedicated example section where some example GDR are reported

Problem statement

The single GDR reporting the details of each single decision lack providing an overall global vision about the current state of the art, according to the decisions.

Proposed solution

Add at top level in the example/ root a markdown document where the whole super high-level story is mentioned, this top level doc should report the related GDR ids for the described decisions.

After the first draft has been published, it's time to add some more meat on the grill.

The example policy can be updated according to a real use case (e.g. Financial Services), and be paired with related metadata example and policy-as-code validation file, to demonstrate how the policy can become "computational" (assuming a platform will then take care of it).

The basic policy documentation can be augmented with:

• different states for lifecycle and history
• license description
• next steps