Skip to content
img-forge Voice Services Plans Company Docs Blog

Field guide · v0.1.1

The Edge That Thinks

A field guide to edge-native generative systems

Static public edition. Verified through . Published .

Public v0.1 includes

  • Free introduction and Chapter 2
  • Production checklist
  • Reference architecture
  • Dated release ledger

Reference architecture

This architecture is intentionally small. It describes the minimum separation of concerns for a system that accepts a user request, may invoke generative inference, and may cause a consequential side effect.

Reference architecture showing client requests flowing through an edge gateway, admission, policy, job records, queues, coordinators, inference, artifacts, and telemetry.
Reference architecture. The minimum separation of concerns for a generative system that may invoke inference or cause a consequential side effect.

The responsibilities

Edge gateway
Authenticate, validate, set request identity, and apply cheap admission controls. It should not conceal a multi-minute job behind a single response.
Identity and policy
Resolve acting user, tenant, scopes, data policy, and spend authority. This is independent from model selection.
Job record
Persist the request’s business identity, state, idempotency key, reservation, and result references. It is the source of truth for work.
Queue or workflow
Defer and retry work without treating redelivery as a new business event. Use a workflow when the workflow itself is the durable unit.
Coordinator
Serialize transitions that must not race. A Durable Object is often suitable for a job, session, or scarce resource coordinator.
Tool boundary
Expose narrowly scoped operations, validate each invocation, and preserve the user and tenant context.
Inference boundary
Select models by capability, policy, price, latency, and evaluation evidence. The application still owns semantic routing.
Artifacts and evidence
Store large outputs outside relational state; record references, hashes, retention class, and provenance.

Minimum viable invariants

Before launch, ensure that:

  • a retry cannot create a second charge or duplicate external side effect;
  • every tool operation has an authenticated principal and scope;
  • every terminal job is either settled or explicitly marked for reconciliation;
  • a provider error never becomes the user-facing source of truth;
  • a model, tool, or retrieval result can be traced to its request and policy;
  • deletion and retention rules cover prompts, artifacts, logs, and embeddings.
Routing ladder from deterministic code through replayed procedures, small models, specialist models, expensive reasoning, and human review.
Routing ladder. Start with the cheapest proven capability. Escalate only when evidence, capability, risk, or policy requires it.

Diagram sources

Public assets live under /public/field-guide. Each figure has Mermaid source and an exported SVG so the public site remains static and diagrams remain editable.

Early access

Get updates or request a reviewer copy

The paid edition is not linked yet. Use this form for early-access updates, reviewer-copy interest, or companion-resource notices.

Data owner
Stackbilt LLC · admin@stackbilt.dev
Retention
Field-guide interest records are retained for 12 months unless a working relationship starts or deletion is requested.

See the privacy policy.

Sources policy

Externally checkable release claims cite official Cloudflare documentation, changelog, or blog sources and carry a visible verification date.