Arche AIP · Giz Agents

Connect a goal, the permitted tools and an inspectable result

Arche AIP describes how Giz Agents are applied to enterprise work. Use the existing agent execution contract for goals, source material, tools and outcomes rather than introducing a separate consultation engine or duplicate task state.

The working flow

A person defines the goal and usable material, and the agent acts through connected capabilities. It can read files, produce artifacts, call permitted external tools or work in Computer. Inspect execution state, errors and cancellation, then review the resulting deliverables. Actual actions depend on the connected capabilities and user permissions.

Public consultation and enterprise execution

The website consultation uses approved public product material for implementation guidance and technical article drafts. It has no enterprise-file or system-write permissions. In an authenticated workspace, select accessible material, Computer and external applications and define the actual execution scope.

Agree on the execution contract

Define source material, expected outputs, permitted tools, read and write authority, approval points and cost and time criteria. Specify how failures, retries, partial completion and changes remaining after cancellation will be assessed. A written answer and an applied system change are distinct outcomes.

Verify completion

Run representative tasks and expected failure cases. Check accuracy, source evidence, permissions, duplicate handling, cancellation and recovery, and record any additional human work. Introduce into operations the scope that passes repeatable success criteria.

Try the consultation agent · Enterprise automation scope · The Computer workspace