This organization maintains software, infrastructure, interfaces, clients, services, and supporting documentation under a shared engineering baseline.
- Keep changes reviewable, tested, and reversible.
- Treat security, privacy, compatibility, and data durability as design constraints.
- Resolve merge conflicts semantically: reconstruct both sides' intent, preserve compatible behavior, and document deliberate trade-offs.
- Prefer canonical repositories and short, stable names; deprecate duplicates with migration notes rather than silently deleting history.
- Keep cross-repository dependencies explicit and pinned where reproducibility matters.
Organization-wide contribution and security guidance lives in this .github repository.
- GitHub Project: declarative-migrations-project
- Linear planning project
- Detailed project-routing contract
GitHub owns code and delivery evidence; Linear owns planning and dependencies. The linked organization Project provides the cross-repository execution view.
- Canonical Linear project: https://linear.app/denman/project/githubcomdeclarative-migrations-ffa3841a100d
- Organization defaults: https://github.com/declarative-migrations/.github
- Canonical agent policy: https://github.com/declarative-migrations/.github/blob/main/agents.md
- Security policy: https://github.com/declarative-migrations/.github/security/policy
Repositories in this organization use semantic conflict resolution with 3–10 relevant prior commits when useful, full cross-repository context, pull-request delivery, and a hard automated-agent denylist for destructive or history-rewriting operations.
declarative-migrations declares repository roles, dependency edges, cross-organization capabilities, deployment ownership, and the git-submodule/Zed-package contract:
The public registry withholds private repository names and edges.