Memory #91 CURRENT
overnight-tribernachi git is intentionally deferred D:/GitHub/overnight-tribernachi/ stays out of git until the v1.0 seeding sprint produces the catalog database; do not propose `git init` there before then `D:/GitHub/overnight-tribernachi/` is **intentionally not under git** through the kernel-development phase. Mark will move it to a git repo only after the overnight agent is executed and the catalog database is built. **Why:** The shift in perspective for the paper (TTI.RES.GEOMETRIC-COVERAGE-001 reframing of anchor validation) has been successful, and the agent's iteration speed during kernel-tuning is higher without commit overhead. Version-control safety lives one level up — at `D:/GitHub/tribernachi-empirical-catalog/` (on GestaltCE), which is the contract the agent has to satisfy. Any agent regression is caught by the catalog's tests/coherence checks rather than by git history of the agent itself. **How to apply:** Do not propose `git init` or push of the overnight-tribernachi repo during kernel-v0.x development. After step 8 of TTI.SPEC.AGENT-TEC-FEEDER-001 (the v1.0 seeding sprint) lands a populated catalog, Mark will git-init the agent and push it as the build-of-record alongside the released catalog. Stated 2026-05-03 in response to a `git init` suggestion after the v0.4 fix list landed. — [feedback_overnight_tribernachi_no_git_pre_database.md]
| Composite | FCF1CC3AA6F049909 |
| Project prime | 13 |
| Domain prime | 59 |
| Type prime | 61 |
| Importance | 1.000000 (CRITICAL) |
| Decay epoch | 0 |
| Created | 2026-05-04 15:46:49 |
| Valid from | (unset) |
| Valid to | NULL — still believed true |
Outgoing Edges
No outgoing edges.