Building Knowledge-Grounded AI Agents with Foundry IQ
#foundry #agents #ai #foundryiq #mcp #agentservice #knowledgebase #grounding
Building Knowledge-Grounded AI Agents with Foundry IQ
#foundry #agents #ai #foundryiq #mcp #agentservice #knowledgebase #grounding
Question: with @obsidian Publish, can I choose to publish a certain vault today and change it to another one tomorrow?
I'd need to use it for a product technical specification (complex) document, but once the project is completed I'll rather either stop paying for it or publish live another valut.
Or, is there a way to export the vault and send it to someone else?
A close friend of mine and myself have been working on this:
https://lighthouseinthestorm.org/
A human to human knowledge sharing site.
We publish references about articles, videos, books etc, what we found valueable.
Comments, feedbacks are more than welcome.
Its open for registrations.
I'm considering improving our development documentation. We used Notion, but it wasn't very effective. As a wiki or knowledge store, it was simply too expensive. We switched to Slack Canvas, which feels clunky.
However, I had an idea: why not use a docs directory in our source code folder to structure our knowledge base in markdown files?
Perhaps we could use Jekyll or Docusaurus to create an internal website through a CI/CD pipeline? Or, we could even use our Git repository as a markdown viewer, including its search functionality.
Has anyone tried something similar? Are there any significant drawbacks? I want our developers to have the most straightforward experience possible. Occasionally, Notion felt overly complex and cumbersome to use. Additionally, a mediawiki, bookstack, or Wiki.js doesn't seem like the ideal solution, too.
Using markdown files in a structured folder structure appears to be an straightforward approach with a low threshold for adding or updating documentation.
Do I miss something?
#wiki #knowledge #knowledgebase #jekyll #dev #development #documentation #docusaurus #github
Discover how Sampath’s new approach weaves AI agents, a shared knowledge base, and seamless workflow integration into a unified model system. It’s a blueprint for enterprise adoption and collaborative intelligence, even powering the Cursor editor. Dive in to see the future of AI infrastructure and open‑source teamwork. #AIAgents #KnowledgeBase #WorkflowIntegration #CollaborativeIntelligence
🔗 https://aidailypost.com/news/sampaths-approach-teams-stitch-agents-models-systems-future-work
Was hilft eine große Knowledgbase, wenn man dann nix findet? Meine Wissensdatenbank liegt in Obsidian, denn das Tool hält eine ausgefeilte Suche und smarte Lesezeichen bereit. Außerdem liegt das Wissen schön verschlüsselt synchronisiert lokal auf meinen Geräten.
@eludom There are awesome paper based methods out there. For example #BulletJournal.
However, that's focused on todo and project management and not so much on #knowledgebase management.
The original #Zettelkasten method was on paper and for that purpose.
Digital methods scale much better and require less effort though IMO.
(fixed interestingly wrong language tag)
Welcome to Nebula https://gioxx.org/2026/02/09/welcome-to-nebula
#github #inevidenza #knowledgebase #lavoro #microsoft #microsoft365 #microsoftentra #microsoftexchange #nebula #nebulakb #nebulaautomations #nebulacore #nebulalog #nebulascripts #nebulatools #opensource #opensourcesoftware #powershell #powershellpermicrosoft365
Как мы случайно сделали Semantic Wiki в Gramax
Всем привет! Меня зовут Катя, я развиваю Поехали!
https://habr.com/ru/companies/gram_ax/articles/993064/
#wiki #semantic_wiki #ontology #graph #knowledgebase #knowledge_management #база_знаний #управление_знаниями #управление_командой #docsascode
SaaS đội ngũ đang chuyển sang AI chatbot tích hợp trực tiếp trong hệ thống tài liệu như KnowledgeOwl hay Eddy AI trên Document360. Ưu điểm: giảm chênh lệch nội dung, đồng bộ tốt hơn, dễ bảo trì. Phù hợp khi cần truy vấn chính xác từ tài liệu sản phẩm & cơ sở tri thức nội bộ. Bạn dùng giải pháp riêng hay tích hợp? #AI #Chatbot #SaaS #KnowledgeBase #CustomerSupport #AI #Chatbot #SaaS #CơSởTriThức #HỗTrợKháchHàng
https://www.reddit.com/r/SaaS/comments/1qsupyx/how_are_saas_teams_choosing_between_ai