Project approach
AI workflows and agent design
Connecting a model to a workflow is not enough on its own. Which source is used, what each tool may access and at which step a person must approve should be designed together.
At a glance
- Page type
- Approach note
- Line of work
- Automation and AI workflows
- Related product work
- Pharos Onion ResearcherSelf-hosted source project
- Bungalow OSIn development
This page is the approach note for the Automation and AI workflows line of work. What that line delivers and what stays outside its scope are on the services page.
Preparing the context
Context engineering means preparing the instructions, data and sources that fit the task. Instead of carrying unneeded data into every step, we plan what information the task needs access to.
Search and tool choice
Hybrid search uses keyword matching and vector similarity together. Pharos is the example of this approach in the portfolio. For tasks such as search, file processing and publishing, we choose tools to suit the job.
Approval and evaluation
Where a step changes something in an outside system, its authority and approval limits are set. Example tasks, expected outputs and failure cases are assessed within the project scope; this page claims no measured success rate and no unlimited autonomy.
Related product work
Let’s assess the scope together
Describe the work you want to solve, the current flow and the output you expect. We will assess a suitable approach and the scope of the work.
Describe your project ↗This page explains the approach for a project enquiry; it is not a binding offer or a service contract. The start and terms of any commercial work are settled in writing. Collaboration framework · Operator and contact
Last updated: