SI workflow architecture

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.

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 }

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

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.

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.