Unified JavaScript
Browser and server code stay in one language because the browser is the universal runtime and JavaScript is native to it.
Ecosystem Philosophy
TeqFW is a philosophy for JavaScript web applications built and evolved with LLM agents.
A compact orientation to the architectural principles behind TeqFW, with a link to the maintained source document.
Context
TeqFW is built for web applications that LLM agents can evolve.
TeqFW is an architectural philosophy for JavaScript web applications in the era of LLM agents. It is not a universal architecture and not a generic framework manifesto; it is contextual work optimized for modular monolith products that must remain understandable, composable, and governable over time.
Key Principles
A compact summary of structure that remains explicit at runtime and readable to agents.
Late binding
Runtime composition keeps dependencies visible and replaceable without hiding product structure behind static coupling.
Explicit contracts
Interfaces, namespaces, and metadata make component relationships readable to humans, tools, and LLM agents.
Pure JavaScript with JSDoc
The codebase uses standard JavaScript and documented types rather than introducing a TypeScript layer.
Predictable namespaces
Stable names and file paths make modules addressable across documentation, tests, and dependency injection.
Agent-oriented structure
Code and documentation are arranged so agents can recover intent, boundaries, and change rules from context.
Machine interfaces
Packages expose structured documentation that helps agents understand public contracts, integration patterns, and architectural assumptions.
Response
TeqFW makes application structure explicit and analyzable.
Traditional architectures often hide relationships behind imports, reflection, build pipelines, or undocumented conventions. TeqFW makes dependencies and module relationships visible through explicit contracts, predictable namespaces, runtime linking, and machine-oriented documentation.
Canonical Source
This page is an entry point, not the maintained philosophy text.
The full philosophy is maintained with the dependency-container work that forms the technical base of TeqFW.