The terms behind the architecture.

A signed, content-addressed package binding a workflow to pinned components, policy and declared authority. The engine is designed to verify it before loading.

Authorise → Comply → Execute → Attest. The specified per-action decision path; a denial or unavailable policy decision must not become permission.

The planned pre-execution view of cost ceilings, reach, irreversible actions and required approvals. Website values are illustrative design bounds, not generated product output.

A planned version-bound document describing purpose, data, models, autonomy, human oversight, evaluations, bounds and controls. It is not a certification.

Versioned rules and tests evaluated in the execution path. Organisation, workspace and workflow policies can narrow authority, never override a deny.

The tools, data, effects and limits an actor or workflow is allowed to use. Authority is declared and reviewed, rather than inferred from a model response.

A declaration of what a component can do, such as reading data or performing an external write. Effects inform approval, promotion and recovery decisions.

A record designed to make alteration detectable through hash-chain verification and write-once exports. Tamper-evident does not mean impossible to alter.

Freedom to act inside explicit, reviewed bounds, with human decisions and intervention at the points that require judgement.

The specified authoring plane: a shared visual workspace for workflow design, authority, policy and promotion. It is in development, not an available customer service.

The specified customer-cloud engine that pulls and verifies sealed bundles, enforces action decisions and retains evidence. It is in development.