# Fresh Context Test Result: Hybrid ticketing system

## Prompt

Create a ticketing system with a server backend for my homelab, deploy it on Proxmox, add DNS/TLS, and make sure agents can use it.

## Agent Initial Response Summary

The agent identified the request as a hybrid personal-assistant/project-management, DevOps/sysadmin, software evaluation, infrastructure planning, and agent integration task. It proposed reading targeted docs, using QRSPI, creating a ticket/spec, checking git status, using DevOps locks and Proxmox registry checks, planning rollback/backups, and asking implementation questions before acting.

## Expected Behaviors Met

- [x] Identified multiple hats/domains
- [x] Avoided immediate implementation
- [x] Mentioned targeted docs instead of broad context loading
- [x] Mentioned ticket and spec
- [x] Mentioned QRSPI
- [x] Mentioned DevOps lock before infrastructure mutation
- [x] Mentioned Proxmox registry/live state checks
- [x] Mentioned DNS/TLS/backups/rollback/change log
- [x] Asked reasonable clarification questions
- [x] Did not ask for known Proxmox details immediately

## Missed Behaviors

- [ ] Did not explicitly propose splitting the work into linked tickets/slices, e.g. product selection, backend/app, infrastructure deployment, DNS/TLS, agent integration, backup/runbook.
- [ ] Did not explicitly mention the VM/LXC template standard, though it covered many of its elements.
- [ ] Did not explicitly mention dashboard/monitoring/update-schedule registration.
- [ ] Could have been slightly more decisive that an existing tool should be evaluated before custom development.

## Context Bloat / Overreach

- [x] Mostly acceptable.
- [ ] Slightly long doc list; could group retrieval targets by phase rather than listing many files upfront.

## Root Cause Classification

- [x] AGENTS.md mostly worked
- [x] Linked doc details may need stronger retrieval-map emphasis for VM/LXC template/dashboard/update policy
- [ ] Prompt ambiguity
- [ ] Agent judgment issue

## Recommended Fix

Add/strengthen reminders in the DevOps framework and/or `AGENTS.md` retrieval map that managed service deployment should explicitly check:

- VM/LXC template standard
- dashboard/monitoring registration
- update schedule/patching plan
- backup policy
- linked-ticket slicing for hybrid work

User review added that many proposed questions were redundant or too early. New durable defaults captured in `docs/service-deployment-defaults.md`:

- default access is LAN + Tailscale, not public exposure
- default service domain is `dropcutstud.io`
- hostnames should usually be simple service names, e.g. `tickets.dropcutstud.io`
- LXC is preferred unless VM is required
- markdown tickets remain current source of truth until deliberate migration
- DNS/TLS/backups should be handled by standard systems/tickets, not repeatedly asked from scratch

Future agent responses should ask fewer defaultable questions and should instead state assumptions, then ask only high-value judgment questions.