Default Architecture commitment . A required system behavior that still needs deployment evidence.
Shape
Default advisory mode. Provides context, review routing, and optimization recommendations without blocking customer traffic.
05 / The serving path
A serving path that stays fail-open.
The decision-time interceptor reads a precomputed attribution index within a 50 ms architecture budget. It does not traverse the graph, call billing systems, depend on evidence collection, or require control-plane reachability.
Question
How can Venturi provide decision-time attribution context without becoming a blocking dependency?
Mechanism
How the mechanism works
- 01Receive request context
Use only the context already available to the interceptor.
- 02Read materialized index
Perform a bounded lookup. No graph traversal occurs.
- 03Evaluate available policy context
Use the customer-controlled workload and policy configuration if it is reachable.
- 04Return decision context
Return Shape advisory context or customer-controlled Gate context.
- 05Forward the request
Venturi failure always forwards the request.
Explicit opt-in Architecture commitment . A required system behavior that still needs deployment evidence.
Customer-controlled Gate path
Separate, customer-controlled, per-workload opt-in path. It is never activated by low-confidence ownership. Venturi component failure always forwards the request.
Annotated visual
Inspect the path and its unresolved states
Request context→Index lookup
Architecture budget: 50 ms→Advisory or configured context→Forward request
Architecture budget: 50 ms→Advisory or configured context→Forward request
Forbidden synchronous dependencies
- Live graph traversal
- Billing-system query
- Connector call
- Evidence processing
- Control-plane reachability
In summary: request context reaches a bounded materialized-index lookup, then receives advisory or explicitly configured policy context before forwarding. Live graph traversal, billing, connectors, evidence processing, and control-plane reachability are excluded from the synchronous path.
Concrete example
Apply the mechanism to one synthetic workload
Illustrative synthetic example
Index unavailable during a support-routing request
- Available context
- Workload and request metadata
- Failure
- Materialized attribution index unavailable
- Venturi behavior
- Skip decision context and emit operator evidence
- Customer-traffic result
- Request proceeds unmodified
- Follow-up
- Restore or re-materialize the index; no customer traffic replay required
Evidence and implementation boundary
What the current claim supports
The 50 ms value is an architecture budget, not a measured production result. Production load and reliability evidence are still required.
Architecture state: index-only lookup, fail-open forwarding, advisory Shape, and explicit Gate configuration are required behaviors. Evidence state: production latency, availability, and load validation remain pending.
No production traffic may be blocked because Venturi is unavailable, stale, slow, or misconfigured. The six-condition failure table, with the customer-traffic outcome for each condition, lives in the trust model: inspect the fail-open failure modes.
Known limitations
Unknown and unresolved states remain valid outcomes
- 01A stale index can reduce decision freshness even when the serving lookup is available.
- 02A low-confidence or unknown owner path remains advisory and Gate-ineligible.
- 03The serving path cannot compensate for uncapturable source evidence or a missing materialized relationship.
Decision enabled
Determine whether advisory context is available and whether an explicitly configured workload and policy may enter the customer-controlled Gate path.
A customer-controlled Gate path may act only where the workload and policy have been explicitly configured. Low confidence and Venturi component failure never authorize blocking.