Foundry IQ
Read one procedure before questions/actions; invocation is not a read.
Read the owning procedure before blocked/unsupported responses too.
Before mutation plans/approval, successfully read its required pre-action references, selected
branches only. Do not reload successful reads. On failure, try only permitted
bounded exact-path reads with any supported reader; never bypass restrictions
or search broadly. If still unavailable: blocked: reference-unavailable, name
missing references and inability to plan. Never invent requirements/plans.
Failures first.
Cleanup and receipt-backed execution go directly to their lifecycle/producer owner;
do not reopen Search intake, provisioning or hardening.
Before expensive service discovery, reuse supplied resource/intent; otherwise ask
one early USE EXISTING / FIND CANDIDATES / CREATE NEW choice.
Only FIND enumerates; supplied identity uses exact/minimum scoped resolution.
CREATE checks its proposed name, not existing-service inventories. Preserve these
answers across source/KB/CU/model handoffs; selection is not write approval.
Searchable docs: KB + validated retrieval. Confirm intent once; KS-only must be explicit.
Child success is not KB completion.
Unclear/compound/mode/completion: read.
Route by requested operation, not existing KB source count.
Connecting an existing KB with two or more sources, without changing the KB, uses Connect.
Read-only operations use their owning procedure and actual helper constraints;
this does not add retrieval modes or supported source kinds.
Explicit unsupported provisioning or multi-source KB creation/reconfiguration uses Diagnose
and stops before discovery, even when connecting an agent is also requested.
This routing takes precedence over classic-search terms (e.g. hybrid search) in compound requests.
Never end in a plain refusal: Diagnose gives the boundary, docs pointer and agent handoff; writes still need an approved concrete plan.
Do not silently execute only the supported part of a compound request.
If existing-KB connection versus KB creation/reconfiguration is unclear, read
intent-routing and clarify that scope before Azure discovery. Never infer KB mutation.
Generic agents: microsoft-foundry.
Reads: no approval; approve unchanged plans before writes.
Hide hashes. No Search/Storage keys, scope widening, guessed identity/boundaries,
drift repair or joint cleanup/creation approval. Acceptance != success.