# Hybrid Task Routing

## Purpose

Guide tasks that cross boundaries, such as software + DevOps, tool implementation + agent behavior, or documentation + operational process.

## Core Rule

Do not collapse hybrid work into one vague task. Split it into independently understandable slices with clear ownership, verification, and rollback.

## Common Hybrid Patterns

### Software + DevOps

Examples:
- Build a ticket web UI and deploy it on Proxmox
- Create an API service for agents
- Add a dashboard backed by a server component

Required routing:
- Software QRSPI for app/API/code design and implementation
- DevOps QRSPI for deployment, DNS, TLS, backups, updates, dashboards, and rollback
- DevOps locks/registry only when mutating shared infrastructure
- Separate local prototype assumptions from managed service architecture

### Tool Implementation + Agent Adoption

Examples:
- Build a Pi TUI questionnaire extension
- Add a CLI helper agents should use
- Add a new retrieval/indexing tool

Required routing:
1. Build/design the tool.
2. Define adoption policy: when should Nimrod use it?
3. Define fallback behavior when the tool is unavailable.
4. Add tests/examples.
5. Update the relevant operating docs/templates.

A tool is not complete just because it exists. It is complete when agents know when and how to use it safely.

### Workflow System + Data Storage

Examples:
- Web CRUD over markdown tickets
- Migrating tickets to a Git service
- Moving Nimrod/Pi to a Proxmox LXC

Required routing:
- Decide canonical data location
- Decide write path and audit trail
- Avoid multiple agents/apps mutating the same dirty working tree
- Plan migration/rollback
- Keep markdown/source-of-truth readable and portable where possible

## Self-Hosted App Checklist

When the user asks for a self-hosted app/service, address:

- Service boundary: what runs as a service?
- Source/code location: which repo?
- Data ownership: where canonical data lives?
- Deployment target: usually Proxmox LXC by default
- Access: LAN + Tailscale by default
- DNS/TLS: use standard plans/defaults
- Backups/restore: required for important data
- Updates: update schedule/owner
- Dashboard/monitoring: register or ticket
- Agent integration: API, CLI, markdown, or tool interface

## Output Expectation

Initial responses should usually say:

```text
This is hybrid work. I would split it into:
1. <slice>
2. <slice>
3. <slice>

I will assume <documented defaults>. The decisions needed now are <few questions>.
```