Evolution and lessons
This system was built by removing repeated friction rather than by starting with a large process framework.Before → after
Evolution at a glance
Why GitHub became the center again
Project-management documents were useful for thinking, but they were not consistently consumed by the agents doing the real work. GitHub already had the strongest properties for durable engineering state:- versioned source
- reviewable changes
- executable tests
- immutable commits
- CI evidence
- issue coordination
- release history
Tela → Athena
A separate knowledge layer is still useful for rationale and cross-project history. Tela was evaluated, but source-count constraints made it a poor fit for the intended scale. The workflow is therefore moving toward Athena as the searchable derived knowledge layer. The key lesson is unchanged: the knowledge layer should help humans and AI find context, but it should not compete with GitHub for canonical product truth.Session continuity was the next bottleneck
Once source-of-truth and validation were clearer, the next large cost became context transfer itself:- ChatGPT → Cursor prompt
- Cursor → ChatGPT result
- ChatGPT → new ChatGPT handoff
Resume had to work before full adoption
A real release branch exposed an important edge case: the active product workstream could have a valid Work Packet while Engineering System adoption was intentionally isolated in a different PR. Treating missing localAGENTS.md or .engineering/* files as a hard resume failure would have mixed governance adoption into release work.
The resume flow was therefore hardened so an adoption-pending repository can record ENGINEERING_SYSTEM_ADOPTION=ABSENT_OR_PENDING, continue under the canonical default, and leave adoption files untouched unless the active workstream explicitly authorizes them.
The lesson: continuity tooling must observe repository state without changing product scope merely to make itself work.
Mobility became an operational requirement
The workflow also had to work away from a desk. A persistent development Linux server plustmux made the implementation process independent of the physical client device. Cursor CLI can continue running on the server while the user reconnects from a phone over SSH.
Telegram completion messages removed another small but repeated cost: checking the terminal simply to learn whether a long task had finished.
The remaining manual copy/paste between a completed mobile Cursor session and ChatGPT is treated as a transitional seam, not as durable engineering state.
Design principle
The system keeps evolving under one constraint:Add automation only when it removes repeated manual work or materially improves correctness.That rule prevents a solo-developer workflow from turning into enterprise process overhead.