I'm working on something I haven't seen discussed much here and genuinely want to know if others are in the same territory. We are trying to solve 2 problems. The first is that every team in our organisation is building AI context in isolation. Same knowledge being captured five different ways, no shared foundation, nothing governed or reusable. We've got enterprise knowledge that technically lives in SharePoint but is effectively invisible to any AI system. We want to fix that by building structured context at two levels: enterprise-wide knowledge that any team can draw on, and domain-specific knowledge owned by each business area — both stored as markdown, governed properly, with SharePoint as the interface for people who don't want to think about files. The second problem is how Technology handles demand from the business. The process for defining requirements, producing the right documentation has always been difficult as business areas often leave it to Technology. The outcome we are trying to achieve would be when a business area raises a need, an AI system — already loaded with the right enterprise and domain context — takes it through a defined process and produces a brief that engineers and their AI coding tools can act on directly. No discovery from scratch every time. The knowledge is in the system, not locked in someone's head or their OneDrive folders. The hard parts are not the AI. They're: - Getting operational detail out of each business domain at the granularity AI can actually reason about - Stopping teams building their own siloed context again the moment you turn your back - Building governance so the system earns autonomy progressively - Getting stakeholders to engage through the system rather than around it We have a later phase in mind where the system proactively surfaces opportunities by monitoring operational data — but we're keeping that parked until the core is stable. We are a small team in the early stages of planning the work.

We run a startup and we've been using Obsidian as our company knowledge base. Great tool but there's one big gap, no security. Everyone with vault access sees everything. API keys, strategy docs, client info, all wide open. And when you connect AI tools they burn through tokens reading raw markdown with all the noise. We ended up building a plugin called VaultGuard that adds encryption and access control to Obsidian. Built it for ourselves first, now we are testing it. If anyone else ran into this, how do you handle sensitive info when sharing an Obsidian vault with your team? And if you're interested in VaultGuard let us know, we'd love to hear your feedback.