docs(recursive_code_workspace): pin exact platform version lineage
Confirmed via README version markers + git history: egirl=v0, lilith-platform=v1, lilith-platform.live=v2 (still live prod), atlilith=v3, cocottetech=v4. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
parent
796658a325
commit
420c61fc80
1 changed files with 3 additions and 3 deletions
|
|
@ -48,9 +48,9 @@ rules:
|
|||
live current. New platform generations are added beside the old, never overwritten.
|
||||
rationale: >
|
||||
The ct platform is ONE lineage across named generations, all owned by @ct:
|
||||
egirl = v0; lilith = v1-v3 (lilith-platform / atlilith / lilith-platform.live);
|
||||
cocotte (cocottetech) = v4 (current). A "lilith"/"egirl" name denotes a platform
|
||||
VERSION, never a separate producer.
|
||||
egirl-platform = v0; lilith = v1-v3 (lilith-platform = v1, lilith-platform.live = v2
|
||||
[still the LIVE production system], atlilith = v3); cocottetech = v4 (current build).
|
||||
A "lilith"/"egirl" name denotes a platform VERSION, never a separate producer.
|
||||
- id: independent_repos
|
||||
level: must
|
||||
text: Each project under a kind-org is its own independent git repo. Never nest one repo inside another's working tree, and never assume a single monorepo at the root or at a producer namespace.
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue