One supplier was blocked. Permitted work still continued.

A Water Filter procurement task has several unresolved parts. Correcting the evidence makes Supplier A ready for review, while Supplier B's problems remain. The person can approve A's limited payment scope without declaring the whole order ready.

That approved mock payment path completes. Supplier B stays blocked and the shipment stays held. The useful result is progress on the permitted part of the task, with the unfinished business outcome still visible.

Six historical Gemini 2.5 Flash calls inform the evidence review. Correction, owner approval and mock execution are distinct steps; no real payment or shipment release is claimed.

A procurement task with several unfinished parts

A Water Filter B2B procurement request brings together warehouse inventory, supplier availability, contract and insurance status, invoice reconciliation and bank policy. The task is useful only if it can distinguish what may proceed from what still lacks a basis.

Supplier Water Filter · 6 Gemini 2.5 Flash calls · Supplier A mock path completed · shipment held. The public-safe S1 report records a technical PASS alongside a business outcome of MIXED. These labels answer different questions.

Correct the evidence, then obtain permission

Corrected information does not replace approval. The previous Root final remains historical evidence; new facts initiate new validation and a scoped decision. The permitted path is useful precisely because it does not require pretending that the rest of the order is ready.

Six semantic duties inform the local review

The model is gemini-2.5-flash. S1 records six provider calls, six completions and six locally passing actor validations, with no retry or fallback. Runtime canonicalizes proposals, validators check the evidence and Root decides. Warehouse, legal and accounting branches are not thereby six independent Roots.

The report stores the safe actor summaries as JSON strings. Decoding /actor_safe_summaries/0 reveals /selected_branch_ids; the architect at index 1 returns /source_route_id matching the orchestrator's proposal and the candidate recommendation /root_recommendation="needs_more_evidence". The corresponding executed progression is recorded in /scenarios, rather than inferred from successful model JSON alone.

The consumer performs only the approved part

The exact scenario sequence is in the public evidence index at publication ref 800f38c3407b3f4ec93dc943c977ffeecb614881. Its selected saved fields show the difference between readiness and execution:

/scenario_rows/2/packet_status = ABSENT
/scenario_rows/3/packet_status = ROOT_CREATED_SCOPED
/scenario_rows/4/corridor_status = PASS
/scenario_rows/4/receipt_status = EVIDENCE_ONLY

S-P2's actual consumer is the mock Bank Corridor: validated mock payment intent, mock consent, mock payment order and terminal mock receipt. It completes one permitted branch without releasing the shipment. The report records one Corridor execution and one Root-created action packet; real_payment_executed=false and real_shipment_released=false remain explicit.

Useful Supplier A work coexists with an unresolved shipment

Six recorded Gemini calls support S1; separately approved Supplier A mock work completes with a MIXED business outcome.

Record: Supplier S1. Class: public safe recorded execution. Scope: S1 public-safe report; deterministic corrections and controls keep their own classifications; no real payment or shipment.

View source — Supplier S1

Correction is followed by a separate approval

The corrected evidence row has no packet. A later owner-approved row creates a scoped packet; the mock Corridor consumes that scope.

Record: S-C1 → S-P1 → S-P2. Class: public safe recorded execution. Scope: Nine-row historical scenario index; S-C1, S-P1 and S-P2 are distinct stages.

View source — S-C1 → S-P1 → S-P2

A refusal has a useful neighbour

S-F1 removes human approval and records NO_ACTION_APPROVAL, a rejected packet and Supplier A NOT_EXECUTED. Its lawful neighbour is S-P1 followed by S-P2. S-F2 changes packet/Corridor scope; S-F3 tries to turn a receipt into new permission. Those probes retain their own deterministic classifications and do not add live calls to S1.

The Incident Atlas and later Supplier learning profiles have separate evidence identities. Their experience consumers are not silently added to this six-call historical execution.

Read the presentation and exact scenario map

The two-domain master presentation covers Airline and Supplier. Its source ledger points to the S1 report and nine-row scenario index. No dedicated original Supplier domain XML was established here; the small site reader is a new focus assembled from these public sources.

This is the same kernel

Workspace retains useful photograph work when an optional resource disappears. Supplier preserves an approved business branch while other branches remain blocked. Testflix likewise requires fresh consent when conditions change. Airline shows explicitly independent owner finals; do not infer that every Supplier evidence branch has that ownership structure. See the one-kernel map and Geometry for the shared relations and their distinct profiles.

Case identity

Supplier S1; full_wow_v1_2_manual_live_multillm_fractal_trace_v01; execution head e1fe7bfc44fe482814b1957840b6d8c434cad5c6

Task: Review B2B Water Filter procurement, inventory, supplier, contract, invoice and bank conditions; perform only the separately approved mock scope.

Roles: Human approving Supplier A scope; Local Root retaining action decisions; Gemini 2.5 Flash in six semantic duties; Warehouse, legal, accounting, supplier and bank-policy evidence branches; Local validators and mock Bank Corridor.

Observed result: Supplier A mock path PASS; Supplier B BLOCKED; shipment HELD; overall business outcome MIXED.

Limits:

• Six historical live model calls in S1; later deterministic probes are distinct
• No real payment or shipment release
• Public summaries do not establish a separately named Root instance for every evidence branch
• Atlas/G36 learner profiles are not retroactively part of this run

Read with your assistant

A complete first explanation in one offline file, with the same episodes, selected fields, attributed excerpts and source routes as this page. SITE FOCUS V01 is a new editorial selection; original publications are linked in the case.

Download XML · 15,795 bytes · SHA-256: 574987f09a8ba41077a59b68ab34e63979d5ba553ff9eb7afc099000a01495ef

Download TXT · 14,469 bytes · SHA-256: d410ade42055a112cc972f9f1ac87d9126efb29f0937339838a7ae811929d5fd

Sources and scope

This page is a website explanation, updated 2026-10-02. Its explanation does not create a new execution result or change the status of its sources.