Class ExtractDirectoryDoer

All Implemented Interfaces:
GuardedExecution, ScopeAuthority, Identifiable, Job<ExtractReport>, Doer<ExtractRequest, ExtractReport>, Orchestrator<ExtractRequest, ExtractReport>, Tool<ExtractRequest, ExtractReport>

public class ExtractDirectoryDoer extends AbstractDoer<ExtractRequest, ExtractReport>
The demo's workflow: every file under a directory, read-only, each routed to the cheapest tier that can read it, all of them in parallel under admission, and a report of what each one cost. Code reads what code can read; a model that can see reads scans and images; a small model judges what nothing else could place; and what came out is embedded into the index so a person can ask the directory a question afterwards.

A doer, because it coordinates and holds nothing: every file is a child job with its own admission, and the dispatcher drains them at the rate the account's limits allow. The request's budgets become the workflow's spend caps before the first child is submitted; a child refused at the cap is a row in the report and the run continues to its end, refusing the rest cheaply.

Since:
0.1 (2026-09-14)
Author:
Andrey Santrosyan