An inspectable agent workflow that turns source material into an onboarding guide, with retrieval, intermediate artifacts and sensitivity filtering.
- Contribution
- Product design and development
- Organisation
- Independent build
- Period
- Prototype
- Agent stages
- 3
- Keyword and embedding retrieval
- Hybrid
The problem
An onboarding guide needs to connect scattered knowledge into a useful path for a new teammate. Generating a polished document is only part of the task: the workflow should also make it possible to inspect what was found and how the guide took shape.
What I built
An agent workflow in three stages. Explorer, Synthesizer and Writer divide discovery, structure and document creation, and each leaves an intermediate artifact (a scratchpad, an outline and the final document), so the process can be inspected before the output is treated as complete.
Retrieval combines BM25 keyword matching with embeddings, and sensitivity filtering controls what material enters the workflow.
The tradeoff
Imported material before live connectors
The workflow runs on imported material and an included synthetic corpus rather than live connectors, so it can be demonstrated without exposing private workplace documents. Direct Slack, Notion and GitHub connectors remain planned work, and this case study does not present them as built.
The result
A working prototype of agent orchestration around a defined job, with the intermediate state that makes a multi-stage workflow easier to understand and debug.
Three stages. Three inspectable artifacts.
Authored synthetic example · not a recorded agent run
Find what the guide needs.
The Explorer works through the imported material. The scratchpad keeps useful facts and unresolved questions visible before the guide is written.
Keep the missing answer visible. Don’t turn an information gap into a confident instruction.
- Product handbook: the fictional Atlas team owns the customer workspace.
- Release guide: every change needs a reviewer and a rollback note.
- Support notes: ask in the team channel before escalating an unfamiliar issue.
- Open question: who approves production access? The sources do not say.
View the synthetic source material
Product handbook. Atlas owns the customer workspace. New teammates begin by reading the handbook and meeting the team.
Release guide. Changes require a reviewer and a rollback note before release.
Support notes. Ask in the team channel before escalating an unfamiliar issue. No production-access approver is named in these example sources.
This illustration follows the implemented Explorer → Synthesizer → Writer structure. Imported material, hybrid retrieval and sensitivity filtering are implemented; direct Slack, Notion and GitHub connectors remain planned.
Keep exploring
Tellerpoint