Milestone 3.5.D.5 — Config, Feature Flags, and Env Vars

Status: Planned
Goal: Track D — Proxy Integration
Phase: 3.5 — Extraction & Context Assembly
Estimated effort: 1 day
Track: Track D — Proxy Integration
Depends on: Milestones 3.5.D.1–3.5.D.4

Env Var Table

Variable	Required	Default	Notes
`IBEX_CONTEXT_ENABLED`	No	`false`	Master switch; `false` = pure Phase 2 static-directive behavior
`IBEX_CONTEXT_GRPC_ADDR`	Conditional	`127.0.0.1:9092`	Context Assembly Engine gRPC target
`IBEX_CONTEXT_TIMEOUT`	No	`45ms`	Client-side deadline
`IBEX_CONTEXT_EMBED_METADATA`	No	`false`	Enables embedded `ibex` JSON block
`IBEX_EXTRACTION_REDIS_URL`	Conditional	(falls back to `REDIS_URL`)	Allows separate Redis for Celery broker

Orientation (indicative)

Named paths, package layouts, libraries, schemas, env vars, and commands anywhere on this page are rough sketches for orientation — inspiration and a baseline, not a required change list.

During implementation, expect to:

open the live tree and follow existing patterns before inventing new ones
research current constraints (latency, tenancy, deploy shape, libraries) more deeply than this page can
advance the design beyond the sketch where measurement or code reality says so
land work in different filenames, merged packages, deferred docs, or new surfaces when the situation calls for it

Prefer outcomes over matching any particular file tree or command sequence.

Areas that may be involved (situational — not a checklist):

Proxy service (HTTP, bootstrap, config)
Context assembly service
Workers / task runtime

Success signals

Outcome-oriented signals that the milestone is in good shape. Exact filenames, package layouts, and commands may differ from any sketches above.

Env vars follow existing proxy convention (Required/Default/Notes/security column)
Documentation updated
Repo guards / CI checks still pass

Prerequisites

Milestones 3.5.D.1–3.5.D.4