fix(aio): recognize AI observability aliases

[pauldambra]

Problem

PostHog AI can treat the common shorthand "AIO" as an unknown tool instead of recognizing the AI observability product.

Why: People use AIO, LLM analytics, and LLMA interchangeably. The agent should resolve those names before asking for clarification.

Changes

• Add AIO, LLM analytics, and LLMA as aliases in the PostHog product glossary injected into the agent system prompt.
• Extend the existing prompt test to protect the alias mapping.

How did you test this code?

• uv run hogli ci:preflight --fix passed for both changed files.
• ruff check products/posthog_ai/backend/services/system_prompt/prompt.py products/posthog_ai/backend/tests/test_system_prompt.py passed.
• Directly imported the system prompt and verified the alias text is present.
• uv run pytest products/posthog_ai/backend/tests/test_system_prompt.py -q could not complete because the local Postgres host db is unavailable in this workspace. The added assertion guards against removing the alias mapping.

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

Docs update

No docs update. This changes internal agent terminology resolution rather than a documented product workflow.

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

Codex CLI made this focused change after tracing discovery from the skill index to the PostHog AI system prompt. It used the /writing-skills, /working-with-skills, and /writing-tests guidance. The product glossary was chosen over adding a broad umbrella skill because the failure is terminology resolution, not a missing workflow.

---

Created with PostHog Code

[github-actions]

Hey @pauldambra! 👋

It looks like your git author email on this PR isn't your @posthog.com address (paul.dambra@gmail.com). Since you're on the PostHog team, it's worth pointing your local git author email at your @posthog.com address. Why it matters:

• Consistent work identity in git history — internal tooling that attributes commits to team members keys off your @posthog.com address.
• Keeps team contributions easy to tell apart from external community ones when scanning history.

You can fix it for this repo with:

git config user.email "you@posthog.com"

Or set it globally with git config --global user.email "you@posthog.com". No need to redo this PR — just a nudge for next time. 🙂

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[stamphog]

Trivial one-line copy addition to a system-prompt string plus a matching test assertion; no risky territory, no behavior change beyond terminology recognition.

• 👍 on the PR from chatgpt-codex-connector[bot], hex-security-app[bot].

Gate mechanics and policy version

Gate		Result
prerequisites	✓	all clear
deny-list	✓	no deny categories matched
size	✓	2L, 1F substantive, 3L/2F incl. docs/generated/snapshots — within ceiling
tier	✓	T1-agent / T1a-trivial (3L, 2F, single-area, fix)
stamphog 2.0.0b3		.stamphog/policy.yml @ d81afd0 · reviewed head 5b0161d

[deployment-status-posthog]

Deploy status

Environment	Status	Deployed At	Workflow
dev	✅ Deployed	2026-07-14 19:03 UTC	Run
prod-us	✅ Deployed	2026-07-14 19:24 UTC	Run
prod-eu	✅ Deployed	2026-07-14 20:00 UTC	Run