Skip to main content

Service Update

When you have significant new information about an existing service, delegate the update to the update-service subagent. The subagent verifies your claims, extends the documentation, adds new technologies, and ensures quality.

When to Use This​

  • Discovered new technologies (found framework from error page, language from headers)
  • Better understanding of service purpose (initial description was vague)
  • Found hosting details (AWS region, CDN, load balancer)
  • Auth mechanism identified or changed
  • Found version info for existing technologies

Do NOT use for minor observations — use save_memory(references=["service://ID"]) for small notes.

Quality Rules​

  1. Description only grows — new description must be ≥ current length
  2. Reason required — explain what you discovered
  3. Technologies are additive — new ones are added, existing preserved
  4. Verify before updating — subagent re-fingerprints to confirm

How to Delegate​

Agent("update-service", "Service 5 (api.target.com) needs update. Triggered a
500 error and found it's Django 4.2, not Express as originally documented.
Stack trace reveals Python 3.11, PostgreSQL database. Also found debug mode
is enabled showing full tracebacks.")
Agent("update-service", "Service 12 (monitoring.target.com) needs update.
Found Elasticsearch 8.10 exposed on port 9200 without auth. Also Kibana
on port 5601. These are new technologies not in the original registration.")

Rules​

  • To update service documentation, always delegate to the update-service subagent
  • For small observations, use save_memory(references=["service://ID"]) instead
  • Wait for the subagent to complete before continuing