TPG Knowledge Base

LaunchQ guide & build console
The Pipeline GroupUAT
๐Ÿ””  Hi, Yonatan Nudman
As
New in UAT New in PROD Established Tip: turn on โ€œHighlight what's newโ€ to dim everything except recent changes.
๐Ÿ‘‹ You're auditing the LaunchQ knowledge base

Curated triage/ops Guide (deduped from Markoโ€™s packs). Managers: use Reorder pages to drag the nav into any order (live for everyone). Pencil = rich text; paste or insert screenshots/images inline.

How to contribute: highlight text โ†’ Comment for notes, or click the pencil to edit the whole page live (bold, lists, links โ€” open wiki; saves go live for everyone).

Build console

Behind the scenes: how content flows in, what's covered, and what access we still need.

How content flows into the terminal

From the four manuals (and their hyperlinked docs) to a live alert. Each stage is reviewed by you before anything reaches the team. Delivered in the same docs UI as the roadmap app.

Sources
4 manuals + hyperlinked docs
Ingest & clean
split, flag conflicts, capture links
Review gate
you: keep / fix
Structured store
one source of truth, role-aware
Guide
team, role-filtered
AI feed
same store, as data
Detection โ†’ Alert
watches the data, emails the manager
Task HubPlanned
auto-creates the task to fix it
Handled checkPlanned
confirms it was resolved; loops back until it is

๐Ÿ”œ Planned (next 2-3 months): when the system raises an issue, it opens a task in Task Hub automatically, then checks back to confirm it was handled and closed. Nothing gets elevated and then quietly forgotten.

Sources & access

For each manual: how much is pulled into the guide, and exactly which hyperlinked docs we still need access to. Request access right here.