Generate and structure
Generate text and return application-defined structured results. The application specifies the work and expected format; DUDE validates supported results.
Distributed Utility Discovery Engine
Your AI work.
Your rules.
Request a capability, follow permitted routes, and know where the work ran. DUDE connects applications with local and configured cloud resources through explicit permissions and execution limits.
Live HarperDB integration Operational persistence, catalog discovery, and active broker moderation.
Request capabilitiesSet boundariesTrace execution
Application operation
Answer with context
request
1
Application connection
Explicit rules + allowed routes
organization or approved third party
valid
2
Network discovery
Compatible offers
3 found
Local resource0 / 6 slots
busy
Cloud resource30 / 40 slots
selected
3
Exact authorized offer
Selected provider resource
Time-limited permission · Content goes to the executor
01 / THE PROCESSAsk for the work.
Ask for the work.
Keep control of the route.
The application defines its operation and permitted routes. On a network route, discovery selects one compatible resource; the selected executor receives the content. Configured direct routes can operate without a network registry.
- 01op
Define the work
Name an operation such as answering a question, extracting image details, or preparing semantic search.
- 02[]
Set the boundaries
Declare the allowed routes, data boundary, and time limit. Fallback uses only permitted alternatives.
- 03⌁
Select a resource
For a network route, discovery matches the capability to a compatible offer with available capacity. The application connection checks the returned boundary.
- 04◇
Authorize execution
Bind network permission to the exact selected resource, implementation, limits, and deadline. The executor checks that permission.
- 05→
Return the result
Execute on the selected resource, validate the supported result, and return execution details and available usage information.
02 / CORE CAPABILITIESGoverned capability execution.
Governed capability execution.
Backed by HarperDB.
These implemented slices establish the process with live HarperDB 5.3.2 persistence, dynamic offer discovery, and policy enforcement. Capability review: October 24, 2026.
Extract and find
Extract structured information from images and create representations for semantic search. Applications retain responsibility for reviewing recognition quality.
Discover and route
Providers advertise separate resources with health and capacity. Network discovery selects a compatible available offer. Fallback follows explicitly configured routes and data boundaries.
Authorize and account
Bind network execution to the selected resource. Provider cloud gateways enforce request, usage, and concurrency allowances, retain replay records, and report execution details.
03 / ENTERPRISE PLATFORMBuild for teams.
Build for teams.
Make operations dependable.
Enterprise coordination platform that organizations can administer, operate, and recover with HarperDB durable clustering.
Give teams control
Organization sign-in, roles, application permissions, enrollment, and revocation. Private catalogs and policy administration would make resource access understandable and accountable.
Operate and recover
Durable discovery and execution records, backup and restore, key rotation, usage receipts, and operational visibility. Repeatable installation and upgrades would support independent deployments.
Connect accounts and capacity
Guided resource onboarding, broader cloud connections, and eligible account sign-in. Show who owns the account, who performs the work, and who pays. Subscription connections remain planned.
Delegate bounded tasks
Scoped workspaces, tools, approvals, progress, cancellation, and recoverable execution. Local task-admission foundations exist; integrated task execution and incremental inference responses remain future work.
04 / FURTHER AHEADMore ways to coordinate.
More ways to coordinate.
More choice in who provides.
Exploratory designs need contracts, implementation, and evidence before they become supported capabilities. They are not prerequisites for every private deployment.
Discover by requirements
Match explicit privacy, location, ownership, price, and environmental requirements. Separate hard rules from preferences and require suitable evidence. Current discovery does not optimize these dimensions.
Coordinate through a trusted broker
Optionally delegate policy, moderation, and bounded comparison of responses. Preserve disagreements, downstream permissions, and total usage. A broker that processes content must be authorized to receive it.
Connect provider networks
Federated discovery, independently operated capacity, verified offers, and reputation. Environmental and security claims would carry evidence, expiry, and clear limits.
Exchange capacity and value
Quotes, reservations, provider payments, settlement, refunds, and disputes. Internal usage accounting exists; marketplace billing and payouts remain future work.
05 / PROVIDE RESOURCESOffer capacity.
Offer capacity.
Keep authority.
Declare the capabilities and resources you control. Keep each offer's readiness and capacity current. The selected executor accepts work only with valid permission for that exact offer; provider cloud credentials stay with the provider.
Read the provider guide → Operational platform
From resource to authorized workoperational
- 01DeclareCapabilities, resources, boundaries, and limits
- 02CheckResource readiness and selected implementation
- 03AdvertiseSeparate offers, availability, and capacity
- 04ExecuteOnly the authorized work within its limits
Readiness now. Verified assurance planned.
Private enrollment and revocation exist. Hardware, energy, and security claims still need verification mechanisms; a healthy endpoint alone does not establish them.
06 / APPLICATION PROCESSOne operation.
One operation.
Explicit choices.
Applications describe the capability they need and the routes they permit. The same operation can use different compatible resources while preserving its boundaries and reporting the actual executor.
- 01Application-defined work
- 02Explicit fallback order
- 03Permission for the selected resource
- 04Visible execution details
- RequestGenerate an answer from the application's supplied context.
- PermitUse the private resource first. Allow a named cloud route only when the operation permits that disclosure.
- ExecuteAuthorize the selected resource and check the returned result.
- ExplainShow the route taken, the actual executor, and reported usage.
07 / OPERATIONAL FOUNDATIONActive persistence & broker
Active persistence & broker
with HarperDB.
Live integration
DUDE is powered by Harper (HarperDB 5.3.2) for resource catalogs, policy administration, and active broker moderation services.
DUDE's application-facing capabilities enforce explicit boundaries and admission policies. The HarperDB storage engine and broker policy engine actively journal admissions, verify boundaries, and guard execution routes across both private and distributed providers.
HELP SHAPE THE NEXT BUILDBring a workload.
Bring a workload.
Build toward a pilot.
Help test the enterprise direction with a concrete workflow, operating requirement, or focused development milestone.