🗺️ Roadmap Explained
VaultTerm is built with a clear philosophy:
⚙️ Stability before features.
🛡️ Security before convenience.
🧱 Foundations before expansion.
🔐 Why TOFU First?
SSH without host verification is unsafe.
Before adding features, VaultTerm ensures:
✅ Host key storage
✅ Host key validation
✅ MITM protection
Security is not optional — it is foundational.
🖥️ Why Terminal Rendering Comes Early?
A terminal client lives or dies by rendering quality.
VaultTerm prioritizes:
✅ Correct ANSI color handling
✅ Stable scrollback buffer
✅ Reliable cursor rendering
✅ IME-safe layout handling
Without a stable rendering engine, additional features would only multiply bugs.
📜 Why Scrollback Matters
Terminal history is core usability.
Without reliable scrollback:
- Debugging becomes painful
- Logs become unreadable
- Long-running commands lose context
That’s why scrollback stability comes before advanced features.
🔑 Why Public Key Authentication Later?
Password authentication allows:
- Faster alpha testing
- Simpler configuration
- Easier onboarding
Public key authentication will be added once:
- Input system is fully stable
- Terminal rendering is regression-safe
- Core SSH workflow is solid
📦 Why Not Add Everything at Once?
Because feature stacking creates instability.
VaultTerm avoids:
❌ Rushed refactors near release
❌ Breaking stable components
❌ Adding features on unstable foundations
Every layer must be reliable before the next one is added.
🧠 Development Philosophy
VaultTerm is not a demo project.
It is built with:
✔ Minimal regressions
✔ Clean architecture
✔ Small, controlled changes
✔ Release discipline
Quality scales. Hacks do not.
Future updates will expand capabilities —
but never at the cost of stability.
Suomeksi: Roadmap selitettynä