Intent is declarative¶
Statement¶
Desired outcomes, policies and consumption intent should be declared in machine-readable form where practical, leaving platforms to determine and reconcile the implementation.
Rationale¶
Declarative intent separates the architectural promise from a particular tool or execution mechanism.
Implications¶
A platform should increasingly behave as a reconciler of declared intent rather than a collection of manual workflows and scripts.
This creates room for policy-as-code, automated provisioning, contract validation and repeatable lifecycle management without coupling architectural knowledge to one technology.
Join the argument
Agree, challenge or add evidence
Architecture improves when its assumptions are challenged. Say which kind of contribution you're making:
- Challenge I disagree because…
- Evidence We've seen this too…
- Question How would this work when…?
- Alternative Another way to approach this…
- Extension This also implies…
Please keep clients, employers and colleagues unidentifiable. Strong contributions may be quoted and credited on this site. Read the contribution guidelines and the privacy notice.
Comments are provided by giscus and stored on GitHub. Posting requires a GitHub account.