Tech Stack Assesment - SS67/project-docs GitHub Wiki

  1. Audience and ask. Who is in the room, CIO, security leadership, or both? Are you asking for a mandate, budget, headcount, or all three? A: I would be used by everyone. Basically the idea is have robust, reliable, continuous documentation which then can be pointed to approved AI agent for easy retrieval. User with Admin access to agent ( or may be with periodic review for articles) will get pop to mark KB approved, retired, needs review based on KB creation and edited date.

  2. Plan and licenses. Which Freshservice plan, and which Freddy pieces are live today: Copilot, AI Agent, Insights? Is the M365 Copilot connector for Freshservice already enabled? We have High tier subscript with more budget line to but extra features. It’s already enabled for Copilot, I have API access to Freshservcie to scrape KBs. I also think if it requires RAG/Topic for easy retrieval - I can index KB data in AWS RedShift with continuous update and then point that RedShift table through Custom MCP to Agents would be sound workflow. Becuase of storage, we can also correct, iterate, SME approve this articles/KBs.

  3. KB state. Rough article count, who owns them, is approval workflow on, and what does usage look like? Any existing deflection or helpfulness numbers? A: will be owned by SMEs and Project Owners

  4. Doc classes in scope. End user how to, agent resolution articles, ops runbooks, remediation guides, architecture and design records? My recommendation is the first four in the KB, design records stay in git. Agree? My main goal is MVP where I can leverage Freshservice KB, auto generation, upload/auto update new approved KBs, automate auto update/approval etc.

  5. Where docs live today. Confluence, SharePoint, git, Teams wiki, Word? Which of those must survive, and which can become read only mirrors? A:

  6. The vuln agent. Is it a Copilot Studio agent? Can its notification carry links today? Does it read Fabric only, or also Freshservice? Yes it’s a copilot agent, reads from RedShift table over MCP for bulbs data. Yes it can carry links. It doesn’t have to be the same agent. I shared that for your context. I was thinking of deploying a a subagent just for KB

  7. Owner. Is there a candidate team or person to run the service? Any appetite for a technical writer, even fractional? A: If the architecture is sound and seamless, I don’t think in Today’s time maintenance is a big deal . We have high subscription Cursor access, unlimited Github copilot license - so maintaining a code base, workflow shouldn’t be that difficult.

  8. Policy levers. Are you willing to propose that every problem record closure produces a known error article, and every change record links a runbook? Those two rules drive adoption more than any tool. A: I am not sure, my goal is to implement like a Freshservice golden asset record vSphere sync which worked for other collector development as well because of reconciliation engine. I am thinking of something similar. May be one aggregator that gets feedback, can do periodic scarping, maintain timely, relevancy etc. and then go from there Just brainstorming, feel free to rebut.

  9. Security content. Does the security team co own remediation articles, and who approves what requesters can see? A: I think it should be irrelevant because once the product is ready, we can build the narrative, define ownership etc.

  10. Metrics you already report. QuickSight and Fabric dashboards exist. Should KB health metrics land there, or inside Freddy Insights? A: If possible, why not. I would prefer either QuickSight or Grafana.

  11. Timeline. Is this a 90 day pilot pitch or a 12 month program pitch? The slide count you asked for says pilot. Confirm. A: Yes it’s a pilot/MVP pitch with seamless potential to integrate any system. I am being industrious here