Human-governed. Agent-built. Agent-ready.
@teqfw/web coordinates deterministic web request processing through a built-in Node.js server and ordered handler pipeline. It is part of the Tequila Framework (TeqFW): created and evolved by coding agents under the architectural direction and final responsibility of Alex Gusev, and shipped with a version-matched Agent Skill so other agents can understand, integrate, and use it correctly.
The package gives independently developed TeqFW packages one predictable request lifecycle while leaving runtime assembly under application control. It provides:
- a unified server boundary for
http,http2, andhttps; - deterministic handler ordering from declarative
before/aftermetadata; - the fixed
INIT -> PROCESS -> FINALIZErequest lifecycle; - request completion and safe
404 Not Found/500 Internal Server Errorfallbacks; - optional static-file delivery and a CLI command for starting the server.
It is an orchestration layer, not a routing or controller framework. Routing, business logic, persistence, sessions, authentication, and application architecture remain outside the package.
Each request passes through three stages:
INIT -> PROCESS -> FINALIZE
Handlers are registered before the runtime starts. The Pipeline Engine derives their effective order from registration metadata and coordinates execution. A PROCESS handler sets context.completed = true when it takes responsibility for the response. This stops later PROCESS handlers and fallback responses; it does not close the response. FINALIZE runs when handlers return, even if a stream remains open.
Install the package in a TeqFW application:
npm install @teqfw/webRegister the package namespace with the host application's TeqFW DI container, add application handlers before server start, and configure the transport:
pipeline.addHandler(helloHandler);
await server.start({
host: "127.0.0.1",
port: 3000,
type: "http",
});Before startup, applications can use runtimeFactory.configureTransport() to supply native HTTP or HTTP/2 server creation options. See server configuration for protocol boundaries and reserved fields.
The server listens on 127.0.0.1:3000 by default. On shutdown it stops admitting requests, aborts TeqFw_Web_Back_ServerLifecycle$.shutdownSignal, and allows active connections to finish for shutdownTimeout milliseconds (default 5000) before forcing closure. Stream owners should observe that signal, close their responses, and remove listeners on client disconnect.
The package requires Node.js >=20 and a configured TeqFW DI container. See the Agent Skill for the complete composition and configuration contract.
The package distributes a version-matched consumer skill at skills/teqfw-web/. Its SKILL.md and references cover lifecycle semantics, handlers, server configuration, static files, distribution, and TeqFW integration.
TeqFW is built through the same development model that it is designed to enable: one human defines the intent, architecture, constraints, and acceptance criteria; coding agents implement and maintain the products; other agents use those products in different combinations to create applications.
@teqfw/web is part of TeqFW and provides its web runtime orchestration layer. The package includes a version-matched Agent Skill in skills/teqfw-web/. The README provides a human-facing product overview; the skill provides agents with the package concepts, contracts, integration rules, examples, and boundaries.
Mount the skill into a host project:
mkdir -p .agents/skills
ln -s ../../node_modules/@teqfw/web/skills/teqfw-web \
.agents/skills/teqfw-webEach TeqFW package is both a practical software component and a working demonstration of human-governed, agent-driven development. This work follows the Agent-Driven Software Management (ADSM) approach: human intent, architectural authority, acceptance, and responsibility remain authoritative; agents act as implementation and reasoning partners.
Apache-2.0