New in UAT New in PROD EstablishedTip: turn on “Highlight what's new” to dim everything except recent changes.
Build console
Behind the scenes: how content flows in, what's covered, what access we still need, and the decisions waiting on Marko.
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 / send to Decisions
Structured store
one source of truth, role-aware
Guide
team, role-filtered
AI feed
same store, as data
Detection → Alert
watches data, emails the manager
Decisions
conflicts → Marko, then publish
↺ Conflicts are quarantined and sent to Decisions. Once Marko rules, that content publishes and can fire alerts.
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.
Decisions for Marko
Where the manuals disagree, the AI can't pick. Marko settles each one; answers save permanently. This list grows as we review more data.
📈 Right now there are 5 open. Expect many more as we go through the manuals together, point by point.
⚠ Known gap on C3 (data turnaround): Marko's answer was based on 2 of the 3 source tables. A 3rd table (Operational Leadership Manual) disagrees on ZoomInfo/Apollo/Cognism/Target Accounts/HGI, and names 3 vendors never asked about (RevenueBase, Ampliz, DnB). Keeping his answer as final for now — logged here, not silently changed.
⚠ Couldn't reach the server to load saved answers. You can still type, but check your internet before saving.