generated from coulomb/repo-seed
tegwick
6973440b3c
Record two foundational principles that emerged while aligning ecosystem INTENT.md files: 1. Orchestration != dependency. NetKingdom orchestrates a repo when that repo holds resources NetKingdom must manage (users, roles, scopes, policies, infra resources). It depends on a repo when it merely uses it as a tool. Defining question: does the repo hold resources NetKingdom needs to orchestrate? (railiance-fabric = dependency; railiance-infra/cluster/platform = orchestrated.) 2. Intent is self-coherent. A repo's INTENT.md describes its own purpose abstractly; it must not reference NetKingdom, sister projects' intents, or even dependencies. Relationships live in the responsibility map / ADRs / interface contracts, not in intent. Rejects the earlier "place in the NetKingdom landscape" block idea as a Principle 2 violation. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
NetKingdom
NetKingdom provides a dynamic self optimizing full circle security-platform for kubernetes deployed IT-infrastructures.