Assistant
The assistant helps you draft, summarise, and navigate Harold using context from your workspace. It is designed to be helpful without replacing professional judgement or bypassing approvals.
Summary
Evidence from code: this module exists as route /platform/assistant, with navigation label "Overview".
This page documents implemented surfaces only. Detailed behaviour is intentionally omitted where repository evidence is incomplete.
Before you start
[Placeholder: prerequisites for Assistant are not fully specified in code-level docs.]
Validated setup requirements should be added from implemented checks, guards, and settings screens.
How it works
Evidence from code structure: Assistant is treated as a documentation tab with its own TOC and body rendering path.
[Placeholder: step-by-step execution flow for Assistant requires stronger endpoint/component evidence.]
Tasks
[Placeholder: core user tasks for Assistant are not yet extracted from concrete UI handlers/API contracts.]
When available, list only actions directly mapped to implemented buttons, forms, routes, and responses.
Settings
[Placeholder: settings/options for Assistant need evidence from settings components and validated API payloads.]
Do not infer configuration semantics from naming alone.
Examples
[Placeholder: real usage example for Assistant pending confirmed workflow evidence.]
Examples should be added only from tested, implemented paths.
Troubleshooting
[Placeholder: known errors and fixes for Assistant require explicit error-state evidence.]
Capture troubleshooting entries from actual API errors, guard clauses, and UI error components.
Was this page helpful?