Sam asked whether the old option C, build a dashboard for the remaining 182, still makes sense in an aging thread. I refreshed live numbers instead of trusting the old label.
Needs Follow-up count: 327 from /Users/samaguiar/Documents/Projects/Skills/kb_live_backlog.py at 2026-06-14T13:32:52Z.Needs Follow-up backlog consolidation to 182 - 2026-06-04 is historical. Its own evidence says 182 was valid at 2026-06-04T18:43:43Z.sf org list --all --json confirmed LITIFY_ORG connected.sf org list metadata --metadata-type Bot --target-org LITIFY_ORG --json returned 4 Bot metadata records: Nick_Attorney_Hub_Agent, Jon_Hollan_Attorney_Hub_Agent, Litify_Conflict_Check_Agent, and Litify_Matter_Summary_Agent.sf data query --target-org LITIFY_ORG --query "SELECT Id, DeveloperName, MasterLabel FROM BotDefinition ORDER BY DeveloperName" --json returned the same 4 BotDefinition rows.Sam_Hub_Executive_Agent.GenAiPlugin and GenAiFunction object names failed with INVALID_TYPE; future agents should use the working planner-definition readback plus metadata/deploy evidence rather than assuming those object names are queryable.The dashboard idea still makes sense, but it should be for the current 327, not the historical 182. For the Agentforce lane, the blocker is not Nick. Nick remains closed by the 2026-06-01 verified page and 2026-06-13 cleanup. Jon has live Bot and planner metadata. Sam Hub has a live planner foundation from 2026-06-12, but the handoff still lists a visible AI panel/control as pending. Other attorney hubs need a readiness matrix before more building: Bot exists, planner exists, permissions assigned, hub access exists, published/activated, published Agent API QA passed, and team can reach it.
Needs Follow-up backlog consolidation to 182 - 2026-06-04, historical source of the 182.Sam Hub Agentforce Live Foundation - 2026-06-12, complete but with visible AI panel and expanded functions pending.Attorney Hub fallback drilldowns staged and validated - 2026-06-14, pending go-live approval for validated Salesforce metadata.