#Request Design Draft

Design Preview / Unreleased: this page records request design choices that have not entered the complete contract. It is not a production import guide.

#Purpose

The request runtime is planned as the first real commflow runtime module. Its job is to move common request orchestration concerns into a framework-agnostic core while keeping VextJS as the first integration target.

#What You Can Do Now

Today, you can:

• install commflow
• read the released Manifest API
• inspect the request descriptor
• compare unsettled request design choices

#What Not To Import Yet

Do not import request runtime names from commflow@0.0.2. The package does not yet export a request client, retry policy, timeout helper, proxy selector, hook runner, or VextJS adapter.

If you need to verify the current package, use Quick Start instead.

#Planned Capabilities

The current design direction includes:

• timeout handling
• retry handling for network errors and response-based failures
• trace and metadata propagation
• proxy selection
• safe observer lifecycle hooks
• normalized request failures

#Hook Semantics

Observer-style hooks are expected to be safe by default: a secondary hook failure should be reported without turning a successful request into a failed request.

#What Is Intentionally Not Promised

This page does not promise:

• a released request client import path
• a finalized options object
• a migration path from VextJS app.fetch
• production support for timeout, retry, proxy, or hook behavior

Treat these details as production imports only after Current Release Quick Start and release notes list them as released.

#How To Tell When It Is Available

Use current-release documentation as authority. An import path, option, return shape, or failure behavior is usable only after it appears in Current Release Quick Start or the matching release API reference. Request remains the complete task guide.