灵珑·初啼

[knight6236]

LingFrame · First Cry

v0.1.0-preview – Initial Runtime Governance Release
January 30, 2026

LingFrame utters its first sound.
Fragile, yet real.
Direction frozen. Boundaries taking shape.
This is not a finished tool — it is a proof of concept:
Runtime governance within a single process — does it hold?

Project Positioning

LingFrame is a JVM runtime governance framework designed for long-running systems.
It keeps mature monolithic applications stable, controllable, and evolvable — without rewriting the system or forcing microservices splits.

Many systems aren’t poorly designed —
they’ve simply lived too long and been changed too hastily.

Core Capabilities (Validated So Far)

• Plugin isolation with zero-trust calls (Core as the sole arbiter)
• Fine-grained permission control (Annotation + Inference sources)
• Full call-chain auditing and real-time tracing logs (SSE-powered)
• Multi-version coexistence (stable + canary)
• Basic canary traffic shading (proportion-based + weighted routing)
• Optional reference Dashboard (real-time plugin status, canary progress, audit logs, IPC control)
• API documentation integration (SpringDoc + Knife4j support)
• Dashboard multi-language foundation (English/Chinese switching)

Current Stage

v0.1.x · Maiden Phase (Preview)

• No pursuit of feature completeness
• No backward compatibility guarantees
• Single focus: Validate runtime governance viability in a single process
  This is a phase of refusing to please everyone and starting to make deliberate choices.

Technical Boundaries (Overview)

• JVM: JDK 21 / JDK 8 (parallel support; JDK 8 compatibility planned)
• Spring Boot: 3.x / 2.x (compatible)
• Single-process architecture
• Clear distinction: Interface stability ≠ Implementation stability
• Does not hide complexity — only refuses to dump it all on the user at once

Recent Key Changes (Highlights Since Project Start)

• Implemented multi-version coexistence and weighted canary routing
• Added multi-language support and UI localization to Dashboard
• Integrated SpringDoc / Knife4j for improved API documentation
• Optimized plugin management, governance logic, permission strategies, and unit tests
• Switched logging language to English with refined expressions
• Replaced web governance interceptor with filter
• Enhanced simulation features (method-level permission checks, smart proxy lookup)
• Restructured README into bilingual format (primary English + Chinese link)

Known Limitations (Transparent)

• Current routing defaults to stable version; request dyeing (header-based precise canary routing) planned for next release
• Dashboard is an optional reference implementation; UI still needs iteration (primarily Chinese, multi-language basics supported)
• No production-scale cases or large benchmarks yet (early validation phase)
• Some edge scenarios (e.g., complex dependency conflicts) not fully tested

Get Started

See the docs:
👉 Getting Started
👉 Technical Entry
👉 Practical Entry

Interactive Documentation (AI-Generated)

Full English architecture and code explanations:
DeepWiki – LingFrame

Final Words

LingFrame will not make decisions for your system.
It only helps put things back where they belong —
while the system is still willing to be understood.

If you read this far and decide to stop,
that’s perfectly fine.

But if you choose to continue:
Feedback, issues, PRs are all welcome.
Even a simple “this looks interesting” or “this part feels off”
would be fuel for LingFrame to keep moving forward.

Thank you for reaching this point.
LingFrame · First Cry.
January 30, 2026