Inspect the current Nick Agentforce source implementation from /Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/salesforce-metadata without editing files or deploying, and identify how to make it reusable across attorney hubs with each attorney or team's own data.
Read project instructions, Agentforce workup guidance, aiAuthoringBundle metadata, genAiFunction schemas, Apex invocable source and tests, Nick Team Resources LWC metadata/controller wiring, Nick flexipage/tab metadata, custom metadata attorney mappings, smoke Apex, permission sets/groups, and current diary/ledger notes.
The Apex invocable action AttorneyHubAgentforceCaseSearchAction is already team-parameterized. It accepts teamName, caseRating, stageKeyword, minTreatmentAgeDays, maxDamages, and maxResults, maps teamName through Hub_Eligible_Attorney__mdt.First_Name__c to User_Id__c, caps results at 25, and returns summary, result count, and JSON rows.
Attorney_Hub_Case_Search is generalized once as a GenAiFunction and points to the Apex action. Its input and output schemas are scalar Lightning types and can support multiple attorney agents as long as each agent passes its own team name.
The current Nick AiAuthoringBundle is Nick-specific in copy, default user, labels, variables, router/subagent labels, action name, and hardcoded teamName = Nick. It should be cloned per attorney unless a template generation workflow is introduced.
Most attorney hub Lightning UI remains clone-per-attorney. The Team Resources LWC is the strongest generalized piece because it exposes a teamName design property and can run the same Apex action through AttorneyHubNickTeamResourcesController.runAgentQuery; however the class and bundle names are still Nick-branded.
AttorneyHubNickShared hardcodes Nick's user Id, and Payton has a parallel shared class with Payton's user Id. This confirms the dashboard tabs are not yet generally parameterized by metadata.
The repo notes say direct GenAiPlannerBundle custom action/topic injection failed three consecutive validations due to restricted picklist/source issues after deactivation/reactivation of an existing agent. The safer path is to create the topic/action through Agentforce Builder or Agent Script/AiAuthoringBundle so Salesforce generates valid IDs, then retrieve and deploy generated metadata.
This was a read-only source reconnaissance pass. No files were edited and no deploy or live command was run. Ending because the requested report is complete.
A future implementation pass can generalize the attorney hub by keeping one Apex/genAiFunction action, generating per-attorney AiAuthoringBundles from a template, and gradually replacing cloned LWC/controller/shared-class patterns with metadata-driven team parameters.