Canonical: https://hypler.com/technical-library/ai-workflow-architecture

[Technical library](https://hypler.com/technical-library)
Technical guide

# SI workflow architecture

A reference pattern for composing SI capabilities with explicit model, tool, and configuration authority boundaries.

SI workflow architecture illustration.

## Capability contract

Define a capability by its inputs, outputs, instructions, allowed context, declared tools, evaluation expectations, and version identity. This gives engineering and review the same object to discuss when a change is proposed.

## Context assembly

Build a bounded context packet rather than passing broad document or database access. Include selected evidence, source references, visibility rules, missing fields, and the expected output shape.

{ task, actor, sources[], missingContext[], policy, expectedOutput }

## Evaluation evidence

Run stated cases against versioned fixtures or evidence sets. Test ordinary outputs, unsupported requests, missing context, and refusal behavior. Results provide bounded evidence for review, interface validation, and operational controls.

- Known input and output contract
- Expected refusal cases
- Versioned test data
- Result and failure note retained

## Policy and review

Validate schema, citations, allowed interfaces, record scope, and action risk. A review surface should show the proposed output, evidence, missing context, policy result, and exact action a person would approve.

## Bounded action

When a consequence is requested, bind it to an exact actor, target, operation, parameters, scope, and decision. A changed request needs a new decision; a tool or connector does not grant broad authority.

## Continue the architecture review.

Read how capability records and exact action authority remain separate concerns.
[Read engineering note](https://hypler.com/technical-library/capability-and-authority)