/Docs/G/ProseObject-Stack/CRUD_0.md
  Source views: Source JSON(ish) on GitHub (VSCode)   Doc views: Document (&k=3.sec): Visual Print Technical: OpenParameters Xray

---

The issue of versioning has many levels. Git provides at floor, and a very good one. But we need at least one other idea. We need a notion of next-draft. That can be done in the Cmacc model by making a new File2 that has a Key/Value list of changes and references the old File1. In some settings, we will want the names of these Files to indicate their order and meaning. This is a very wide practice in law and elsewhere. It corresponds to the practice in software release versioning. For the moment, we have chosen a convention of adding a _01.md at the end of File names, with _0.md being the current, without guarantee of stability other than the git history. The _01.md numbers currently have no technical guarantee of stability, it is more a promise by the maintainer than a certainty. If we use hashed names, this issue disappears, but another one arises of naming, organizing, efficiently using .gitinclude, etc.