Meeting 2/9/26

Meeting 2/9/26

Presentation:

Recording
Quick Recap

Code Updates

Snowflake Project

Demo - demo the snowflake marketplace offering

Apply : finish application to Snowflake Accelerator

Open

Report on Snowflake project roadmap

Meeting 2/2/26

• How to install AIFAQ from Marketplace (only for selected users) with a click-on button process?

• Is it possible to use Data in Snowflake to ingest the KB?

• While the upload files process should extend the KB

• How to grant access permission to each user?

• New instance of AIFAQ for Home

• Send an email to easter: https://founderstudio.aifaq.pro/ (homepage, application, expert-page)

Don said: anyone want to build a "recorder alliance" with me? fathom otter fireflies read.ai etc all recording 1 or multiple vers

Presentation

I am currently optimizing the code to get the app ready for the Snowflake Marketplace. To answer the advisors: Yes, all requested features are possible.

• Installation: We will use a Private Listing for the "click-to-install" process for selected users.

• Data & KB: We can ingest data from tables, and the Knowledge Base will reside entirely within Snowflake.
  
  

• Functionality: File uploads will extend the KB, and we can configure granular permissions for each user from the admin panel.

Quick Recap

Gianluca and MADUGULA discussed the installation and setup of a Snowflake database and Streamlit app for version 2. They walked through the process of creating a new Snowflake account, running SQL code, and configuring the Streamlit app. They addressed issues with document uploads and discussed the need for a user guide. MADUGULA shared updates on security improvements for the marketplace, including SQL injection prevention and prompt injection patterns. They agreed that Gianluca would update Bob and Peter about the working code and document upload process, while MADUGULA would focus on creating a user guide and further security enhancements.

Next Steps

• MADUGULA: Update the code in the GitHub Norfolk branch with the latest changes and improvements.

• MADUGULA: Create a short guide (with screenshots if possible) detailing the installation and setup process for the system, including Snowflake account creation, SQL file setup, and Streamlit app configuration.

• MADUGULA: Continue working on marketplace integration and security improvements (e.g., SQL injection prevention, prompt injection prevention) for invite-only testing.

• Gianluca: Update Bob and Peter on the current status of the code and inform them that the system is ready for testing.

• MADUGULA: Be prepared to provide instructions to Bob and Peter on how to upload documents to test the system when requested.

Summary

Snowflake Database and Streamlit Setup:Gianluca and Jeram discussed the installation and setup of a Snowflake database and Streamlit app. They clarified steps for creating a Snowflake account, uploading SQL files, and configuring the Streamlit app to connect with the database. Jeram guided Gianluca through troubleshooting steps, including rebooting the app and adjusting the user interface view. They identified the need for a short guide and updates to the GitHub README to help others set up and use the system. The next steps include creating a user guide, updating documentation, and adding categories and access control for document uploads.

Marketplace Testing and Security Enhancements:Gianluca and MADUGULA discussed the configuration and testing of a system, emphasizing the importance of providing a guide for users like Peter and Bobby. MADUGULA suggested making the marketplace invite-only for testing to simplify the process. They also talked about improving the marketplace components, breaking the code into modular parts for easier checking and modification. Security audits were addressed, focusing on preventing SQL injection and prompt injection to enhance app security.

Problem Detection and Code Updates:MADUGULA reported on implementing problem detection techniques including input validation and prompt injection patterns. Gianluca asked MADUGULA to update the code in the Norfolk branch on GitHub and create a short guide, with MADUGULA agreeing to do so. Gianluca also planned to update Bob and Peter about the working code, which requires only copying two files and running it, and mentioned that they might ask about uploading documents for testing.

Meeting 1/26/26

Presentation
Quick Recap

The team discussed their project's transition within the Linux Foundation, considering a move from the Decentralized Trust lab to the AI and Data community. Bobbi proposed pursuing both paths simultaneously, emphasizing the importance of completing the Snowflake integration before exploring blockchain features. The team addressed recent security issues with Snowflake access and discussed ongoing development work, including new features for the admin dashboard and hybrid search functionality. LaToya introduced herself to the team, sharing her background in electrical engineering and blockchain, and expressed interest in contributing to the project. The conversation ended with a brief discussion about rescheduling an upcoming advisor meeting to accommodate Bobbi's schedule.

Next Steps

• Bobbi: Feel out David regarding how long the project can remain in the current lab status while preparing to transition to LF AI & Data, and report back to the team next week.

• Bobbi: Work on the new website using the proposed template, with assistance from Muhammad.

• Bobbi: Research and implement Snowflake network policy, including collecting team IP addresses for whitelist.

• Bobbi: Change the Snowflake account password to a stronger one and share it privately (e.g., via Slack) with JARAM.

• JARAM: Continue development on new features for the Snowflake connector (hybrid search, audit logging, admin dashboard, activity dashboard, configuration export/import, rate limiting, and agent integration), and prepare a clear roadmap for adding agents within the next week.

• Gianluca: Attempt to install and test the new version of the code for the Snowflake connector after receiving the updated code from JARAM.

• Peter: Move the advisor meeting to 1:00 PM and confirm with advisors.

• Gianluca: Work on updating the analytics UI to include activity data prior to December (as time allows, after Snowflake work).

Summary

Linux Project Transition Strategy:The team discussed their project's status within the Linux Foundation and potential transition to the AI and Data community. Bobbi proposed pursuing both the Decentralized Trust TAC and AI community paths, with a focus on completing the Snowflake connector before adding blockchain features. The team agreed to seek David's input on how long they can remain in their current lab status while preparing for a move to incubation. Additionally, they addressed a recent Snowflake security violation, with Bobbi working on implementing required network policies and password changes. Gianluca and Jaram discussed ongoing code installation issues, while Madugula provided an update on his work on features including hybrid search, audit logging, and configuration export/import capabilities.

AI Documentation Integration Project:The team discussed their AI documentation project, which aims to help open source communities create private chatbots and knowledge bases. Bobbi explained that they are working with Snowflake to integrate their tool with data warehouses, allowing users to add private information while leveraging insights from their data. LaToya shared her background in electrical engineering and blockchain, including her work on the first Bitcoin ETF and tokenization projects at BlackRock. The team also briefly discussed the possibility of proposing their project for a Linux Foundation mentorship program.

AI Tools and Community Engagement:LaToya joined the meeting to explore potential use cases for AI tools, particularly for note-taking, and expressed her intention to participate more consistently in the community. Bobbi and Peter welcomed her and discussed their locations, with Peter mentioning challenges due to weather-related issues. Bobbi shared her plans to work on submissions, website updates, and Snowflake-related tasks, encouraging LaToya to join a Snowflake meeting if available.

Snowflake Integration and Marketplace Strategy:The team discussed their integration of their tool with Snowflake, with Bobbi explaining that they want their tool to sit on top of Snowflake's data to ask questions, and LaToya mentioned BlackRock's account with Snowflake. Gianluca provided details on the technical stack, which includes Python for backend and SQL for the relational database, with Streamlit as the UI library. The team is working on getting their code from the open source environment into the Snowflake marketplace, with help from an advisor named Tim who is a high-ranking Snowflake employee.

UI Fix and Project Priorities:The team discussed several topics, including analytics data and scheduling. Gianluca agreed to work on fixing the UI to show data from before December, but Peter emphasized that the snowflake project should be the priority. Bobbi requested to move an advisor meeting to 1 PM the next day due to childcare commitments, and Peter agreed to reschedule it. They also briefly discussed Peter's potential visit to the DMV.

Incubation Letter From David

Bobbi,

Thanks again for sharing your AIFAQ project proposal with us. We're happy that we've been able to support the work that you, Gianluca and others have been doing with AIFAQ over the years and it is great to see how the lab is maturing.

We reviewed the project proposal and our thought is that you would find a better fit for this work going forward in a Linux Foundation community dedicated to AI.  As you know, LFDT is focused on building an ecosystem of blockchain, ledger, identity, cryptographic, and related technologies and that isn't the domain that you're working in.

It certainly made sense to help incubate AIFAQ through our mentorship program and through the Labs since this looked like a tool that could be very useful for the maintainers in our community, but we don't think the TAC would accept this as a project since it isn't a decentralized trust technology.

Have you taken a look at the LF AI & Data community?  They also offer hosting and have a large number of open source AI projects. We think that could be a good environment to continue your work and would give you more of an opportunity to find other collaborators since you'd be in a community with other people working on AI projects and tools. For reference, you can find out more about the hosting they provide at:

Host Your Project – LFAI & Data

If you'd be interested in having a conversation with someone at LF AI & Data about hosting, let me know and I'm happy to make an introduction.

Please keep in mind that this is our opinion and LFDT staff don't make decisions on what projects the TAC approves. You would be welcome to share your proposal with members of the TAC and get their thoughts on this as well.

Thanks,

David

WEBSITE

Open

Snowflake

Open

A new security violation has been found for your account:

Ensure that an account-level network policy has been configured to only allow access from trusted IP addresses

Go to Trust Center

Meeting 1/19/26

Presentation: https://docs.google.com/presentation/d/1qKVtaAgGufR9ety7fY0eego1THDtuzDIyKOqvkYpmjM/edit

Recording
Quick Recap

The meeting began with Bobbi and Gianluca addressing technical formalities and reviewing various policies before discussing several ongoing initiatives including stakeholder approvals, speaking engagements, and a collaboration that wasn't moving forward as planned. The team then focused on technical installations and code updates, particularly regarding Snowflake's Cortex AI features and the process for installing version 2 of their code. Bobbi concluded by outlining her plans for Linux Foundation engagement and consolidating meetups, while also discussing her participation in a Snowflake AI Startup Challenge course.

Next Steps

• Bobbi: Follow up with David to get everything needed for Linux Foundation incubation process and pursue additional speaking engagements at Linux Foundation events

• Bobbi: Set up a meeting with David as soon as possible

• Bobbi: Complete Snowflake's AI Startup Challenge course/reading materials this week

• Bobbi: Consolidate multiple meetups into one to reduce costs

• Gianluca: Merge the PR, check the code, and install app version 2 using the README file

• Gianluca: Update team (Bobbi, Peter, and others) on the results of the version 2 installation

• MADUGULA: Update documentation/code to include cross-region instructions for Cortex AI access

• Bobbi: Share Snowflake challenge materials in the team chat

Summary

Policy Review and Technical Setup:Bobbi and Gianluca began their meeting by discussing technical difficulties and formalities. Bobbi shared her screen and mentioned that they should review the privacy policy, code of conduct, and antitrust policy, which were displayed on the screen.

Initiatives and Event Updates:Bobbi shared updates on several initiatives. She mentioned that David had received permission from key stakeholders to review their proposal, with a decision expected this week. Bobbi also shared that she had been invited to speak at a Linux Foundation event in May about AI FAQ, which she was excited about as it could provide significant exposure. Finally, she noted that the Founders Institute was not moving forward with their collaboration, suggesting that the existing benefits were the most they could expect.

Founders Institute Support and Progress:Bobbi expressed concerns about Founders Institute's lack of organization and support after graduation, suggesting that the current relationship should be maintained as it is the best they can expect. She emphasized the importance of showcasing their presence on Founders Institute to demonstrate their progress. Additionally, Bobbi mentioned plans to attend meetings related to the Linux Foundation Decentralized Trust to generate interest among maintainers and encourage usage of their technology.

Linux Foundation and Snowflake Initiatives:Bobbi discussed the Linux Foundation incubation process, aiming to move forward by the end of the month, and mentioned she would manage the initiative with help from the team. She also talked about applying for the Snowflake startup challenge and joining their community working groups, with plans to provide more information to JAYAM. Gianluca was tasked with attempting to install from READMEs for Snowflake.

Snowflake Cortex AI Region Access:Gianluca and MADUGULA discussed issues with Snowflake's Cortex AI features in the US East North Virginia region. They determined that the current setup was not supporting Cortex AI, and MADUGULA promised to update the code to enable cross-region access for Cortex AI features. Gianluca agreed to accept MADUGULA's PR, update the code, and install version 2 of the app. They planned to test the system installation and keep the team updated on progress.

Version 2 Installation and Updates:The team discussed the installation process for version 2 of their code, with Madugula explaining that only two files are needed: setup.SQL and app version.2pi. Gianluca confirmed he would merge the PR and install version 2 using the README file in version 1. Bobbi announced she would follow up with David regarding Linux Foundation setup and speaking engagements, and mentioned she was taking a Snowflake AI Startup Challenge course. She also shared her plan to consolidate three separate meetups into one to reduce costs.

Code Base Recap

Project Recap

1.Snowflake

• Gianluca Test from Readme

• Test instance for team to work on ( readiness for deployment, user guides)

• Discuss Thank you for registering for the 2026 Startup Challenge!

2. Founders Institute

   1. How to leverage FI Keystone Live Chatbot

3. LFDT

   1. Incubation

   2. Mentorship

Meeting 1/12/26

Presentation
https://docs.google.com/presentation/d/1tyqzO8Yg77wJwbnkytTi5ypnTtHYY02ohdvAF7u0t8c/edit?slide=id.g2a7ffc9cce9_0_5#slide=id.g2a7ffc9cce9_0_5

Trello Card:

Recording
Last weeks
Quick Recap

The team met to discuss the AIFAQ project's progress and next steps, focusing on the Snowflake implementation and documentation needs. Jaram demonstrated the new admin dashboard functionality, which allows for user management, team configuration, and document access controls within Snowflake. The team discussed repository cleanup needs with David Boswell, including removing old configuration settings and addressing DCO (Developer Certificate of Origin) compliance issues. Gianluca and Bobby reviewed documentation requirements, agreeing that three user guides are needed: a developer guide, an administrator guide, and a user guide, with the developer guide being prioritized first. The team also addressed authentication issues for accessing the Snowflake marketplace instance and discussed potential ways to support Jaram's ongoing development work, though no immediate financial compensation was available as the project is not yet revenue-generating.

Next Steps

• Bobbi: Send email to David Boswell to schedule a meeting (tomorrow or Wednesday) to discuss the incubation document and repository questions

• Bobbi: Ask David Boswell for examples of good repositories suitable for incubation stage in Linux Foundation Decentralized Trust

• Bobbi: Ask David Boswell/LF staff how to handle old commits without DCO sign-off and clean the repository while maintaining forks/stars

• Bobbi: Ask David Boswell/LF staff how to resolve continuous integration check issues related to old configuration

• Gianluca: Test installation of the system using the current README documentation in the repository

• MADUGULA: Create additional test instance of the system for Bobbi to experiment with

• MADUGULA: Review and provide list of 3 specific support tasks that Gianluca and Bobbi can help with

• Bobbi: Update and store Snowflake login information on the wiki page

• Bobbi: Fix email configuration/password issues for the Snowflake account

• Team: Use Slack channel for ongoing system questions/communications with MADUGULA

Summary

Repository Cleanup and Production Move:The team discussed moving their project to production and addressed issues with the current repository. Gianluca highlighted the need to clean the repository, including removing old commits and configuring continuous integration actions. They plan to ask David Boswell for guidance on repository cleanup and for an example of a good repository for incubation. Bobbi will send an email to David requesting a meeting to discuss these matters. The team also acknowledged Jairam's hard work during his illness and expressed hope for his continued recovery.

Repository Clean-Up and Security Discussion:Gianluca discussed issues with their repository, including unsigned commits and outdated configurations, and expressed a desire for support from the Linux Foundation to address these problems while maintaining followers and stars. Bobbi suggested that requiring two-factor authentication for GitHub and the Linux Foundation might help identify forkers, but Gianluca believed this would not resolve the main issues. They considered creating a new repository to clean the code base and remove unnecessary configurations, with the hope that skilled GitHub personnel could assist in this process. Gianluca also mentioned a personal update about avoiding kayaking due to a minor shoulder pain.

User Guide Development Strategy:Bobbi and Gianluca discussed the development of user guides for their product. Bobbi explained that she had moved information from Trello to a wiki page due to cost concerns. They agreed on the need for three types of user guides: a developer's guide, an administrator's guide, and a user guide. Bobbi outlined the contents of each guide, emphasizing the need for detailed information for developers and customized content for administrators. They also briefly touched on the need for general user guides that could be adapted for specific clients.

User Guides Development Strategy:Gianluca and Bobbi discussed creating user guides for a project, focusing on installation, configuration, and usage. They agreed to create separate guides for the standard version and Snowflake, with Bobbi taking the lead on developing modular user guides using Ledger Academy as a test example. Gianluca emphasized the need to update the installation guide for the Snowflake version, as the current guide is too long and needs revision.

Snowflake Application Access Setup:The team discussed documentation and access to their application in Snowflake. Gianluca agreed to test the stellation guide in the Rhythmi file using a trial account. Bobbi and MADUGULA helped Gianluca set up multi-factor authentication for access. They also discussed how the application would be listed in the Snowflake marketplace once ready, and Bobbi shared login credentials with Gianluca.

Snowflake Account Access Resolution:Bobbi and Gianluca discussed accessing a Snowflake account, initially encountering issues with the wrong login credentials. Bobbi found the correct login information in their shared mail and updated it on a wiki page for future reference. They resolved the login problem, and Bobbi noted that the correct login details would be documented for future use.

Snowflake TBC Login Resolution:Bobbi and Gianluca discussed login issues with the TBC instance of Snowflake, where Gianluca was experiencing multi-factor authentication problems. Bobbi helped resolve the authentication issues by sharing the correct login credentials and email configuration. They confirmed that the correct Snowflake login details are for the TBC instance with the username "snowflake@pro" and password "password12345XLANI". Bobbi mentioned she would send an email to David to arrange a meeting, copying Gianluca on the correspondence.

Snowflake Document Management System Demo:The team demonstrated a new system for managing documents in Snowflake, where an admin can configure users, teams, and access levels, and upload or link documents from various sources including local drives and cloud databases. Bobbi expressed satisfaction with the demo and offered support, suggesting they could help test the system, create documentation, or assist with development activities. The team agreed to continue communication via Slack and discussed potential future mentorship opportunities, with Bobbi mentioning she would send a letter to David regarding an incubation meeting.

Introduction

SNOWFLAKE MARKETPLACE UPDATE

Log in:
snowflakeapp mail id and password
Mail id - snowflakeapp@aifaq.pro
JamesBond@25$$Dollar$$

MADUGULA JAYARAM 9:48 AM
Username: AIFAQPRO
Dedicated Login URL: https://joflnlg-tbc54248.snowflakecomputing.com
password : JamesBond@25$$Dollar$$

AFAQ AI Lab calls - 2026/01/05Preview
AIFAQ Pro Snowflake version 1.mp4Preview (A.I.F.A.Q ?)

One Pager

Infographic - Unlocking Conversational IntelligencePreview Remove Marketing hype/ add features available now

Infographic - AIFAQ Application InfoPreview

Mentorship

User Guides:

Development - Complete with all sections

aifaq/version_2/readme.md at snowflake · Jayaram007/aifaq
https://docs.google.com/document/d/1_B43zb1K8DgM5YATZIcVldAyxjboFa3eApaG0JRV4z4/edit?tab=t.0#heading=h.igw6xd4q5kvb

Administrator User Guides

End User Guides ( customizable per client)

Founders Institute Update

AI Startup Prompt Library: Copy, Customize & Accelerate
Just a list of successful prompts to assist cohort members create materials and answer questions

INCUBATION

Project Incubation Entry Considerations - Technical Advisory Council

AIFAQ for Linux Foundation IncubationPreview

Project Incubation Entry Considerations - Technical Advisory Council

Approved project proposals enter into Incubation. For new components and modules, a repository is created under the Hyperledger Github org . New features or capabilities must be handled through pull requests labeled with tags that identify the project and tag it as incubator. Pull requests ideally are capable of being enabled and disabled with feature-flags.

Projects in Incubation can overlap with one another. Entering Incubation is meant to be fairly easy to allow for community exploration of different ideas.

After a project qualifies to be declared Graduated, the project maintainers can then vote to request a graduation review by the TOC.

Entering Incubation does not guarantee that the project will eventually get to the Graduated state. Projects may never get to the Graduated state.

Projects seeking to graduate from Incubation must meet the criteria defined in the Incubation Exit Criteria document.

LINKEDIN POSTS
BM

New features and code cleanup

COST ISSUES:
cost estimatorPreview

AIFAQ PROJECT 2025

ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ

✨ AIFAQ 2025 Goals

1. Overall Project Goals for AIFAQ (Organizational Level)

(To move from Sandbox to Incubation at LFDT and get early paying customers)

a. Technical and Community Goals (to qualify for Incubation at LFDT):

• Expand Active Contributors: Grow to at least 5+ consistent contributors outside the founding team, documented in GitHub activity.

• Establish Governance: Implement a clear Technical Steering Committee (TSC) charter and lightweight governance model aligned with LFDT best practices.

• Production-Ready MVP: Deliver a production-quality MVP for the AIFAQ platform, showing enterprise-grade performance, security, and usability.

• Document Use Cases: Publish 2–3 real-world case studies demonstrating AIFAQ solving enterprise FAQs or documentation automation.

• Community Engagement: Host at least 2 public webinars, 1 workshop, and quarterly updates to the LFDT and open-source community.

• Security and Compliance: Complete basic security audits and compliance documentation (e.g., data handling policies).

b. Business Goals (to build customer traction):

• Land 2–3 Pilot Customers: Sign early-stage pilot programs with at least 2–3 enterprise customers (offering free or discounted pilots initially).

• Launch Paid Offering: Define pricing tiers and launch a beta paid service (SaaS or managed service model) by Q4 2025.

• Marketing & Sales Enablement:

  • Publish one white paper describing AIFAQ’s unique value proposition.

  • Create sales deck, website landing page, and downloadable 1-pager for outreach.

• Investor and Grant Readiness: Prepare a pitch deck and start conversations with potential grants or impact investors aligned with AI/OSS innovation.

Mentorship Project Goals

A. Multi-Agent RAG (Retrieval-Augmented Generation) System

Technical Goals:

• Multi-Agent Architecture: Build a working prototype of modular agents (retriever, router, summarizer, responder) communicating through an orchestrator.

• Plugin Support: Enable pluggable data sources (e.g., Confluence, GitHub Wikis, custom PDFs).

• Scalable RAG Pipeline: Implement efficient document chunking, embedding caching, and vector search optimizations.

• Agent Collaboration Logic: Develop logic for agents to delegate subtasks among themselves dynamically (example: a retriever agent passes relevant docs to a summarizer agent).

• Baseline Evaluation Metrics: Create benchmark tests to measure precision, latency, and accuracy improvements vs. a simple single-agent model.

Community Deliverables:

• Public Demo Repository with a clean README and deployment instructions (Docker optional).

• Technical Blog Post: Write a blog post showcasing how multi-agent RAG outperforms single-agent baseline.

B. Snowflake Connector for AIFAQ

Technical Goals:

• Data Pipeline Integration: Build a robust connector to extract structured FAQ or knowledge base data from Snowflake tables.

• Authentication & Security: Implement secure authentication (OAuth, token-based) for enterprise Snowflake accounts.

• Connector API: Develop a simple API interface to trigger data pulls, syncs, and refreshes on-demand.

• Auto-Sync and Scheduling: Allow scheduled pull jobs and delta updates (new or modified rows only).

Business/Strategic Deliverables:

• Enterprise Use Case Demo: Showcase pulling an enterprise customer’s knowledge base into AIFAQ using Snowflake in a demo environment.

• Documentation & SDK: Release an open-source SDK or connector package on GitHub with easy-to-follow examples.

• Outbound Messaging: Write 1 LinkedIn article or case study targeting Snowflake’s huge enterprise customer base (joint marketing potential if successful).

MEETING NOTES

Meeting 12/14/25

Presentation

Trello Card:

Recording
FAQ AI Lab calls - 2026/01/05Preview

Introduction

SNOWFLAKE MARKETPLACE UPDATE - Jayaram

Are we in the Marketplace????
AIFAQ Pro Snowflake version 1.mp4Preview (A.I.F.A.Q ?)

One Pager

Infographic - Unlocking Conversational IntelligencePreview Remove Marketing hype/ add features available now

Infographic - AIFAQ Application InfoPreview

Mentorship

Completed

Available Now – Version 1

• Read unstructured data directly from Snowflake stages: PDF, DOC/DOCX, CSV, TXT.

• 100% Snowflake-native — your data never leaves your account.

• Enterprise-grade security, compliance, and auditability.

• Role-based access and granular permissions.

• Instant deployment via Snowflake Marketplace.

• Zero infrastructure — no external systems required.

• Instant answers using multi-agent Retrieval-Augmented Generation (RAG).

Coming Soon – Version 2

• Iceberg-based connectivity.

• Read structured & unstructured data from AWS S3, Azure Blob, Google Cloud Storage.

• Large-scale ingestion for enterprise datasets.

• Advanced multi-agent orchestration workflows.

Fast setup. Maximum security. Zero friction.

MULTI AGENT / Gitmesh -

multitenant_ryanPreview

Lochan_Separate_DataPreview

Founders Institute
AI Startup Prompt Library: Copy, Customize & Accelerate
Just a list of successful prompts to assist cohort members create materials and answer questions

INCUBATION

AIFAQ for Linux Foundation IncubationPreview

Project Incubation Entry Considerations - Technical Advisory Council

Approved project proposals enter into Incubation. For new components and modules, a repository is created under the Hyperledger Github org . New features or capabilities must be handled through pull requests labeled with tags that identify the project and tag it as incubator. Pull requests ideally are capable of being enabled and disabled with feature-flags.

Projects in Incubation can overlap with one another. Entering Incubation is meant to be fairly easy to allow for community exploration of different ideas.

After a project qualifies to be declared Graduated, the project maintainers can then vote to request a graduation review by the TOC.

Entering Incubation does not guarantee that the project will eventually get to the Graduated state. Projects may never get to the Graduated state.

Projects seeking to graduate from Incubation must meet the criteria defined in the Incubation Exit Criteria document.

LINKEDIN POSTS
BM

New features and code cleanup

COST ISSUES:
cost estimatorPreview

Project Incubation Entry Considerations - Technical Advisory Council

Meeting 10/08/25

Presentation
https://docs.google.com/presentation/d/118Iw3P4b7Oz4roTyvBuCm_2WNX0TYso-oKG5lJBUZFU/edit?slide=id.g2a7ffc9cce9_0_5#slide=id.g2a7ffc9cce9_0_5

Trello Card:

https://trello.com/c/AB4nQmqw

Recording

Introduction
Welcome Back Tripur

MENTORSHIP

SNOWFLAKE MARKETPLACE UPDATE - Jayaram

Mentorship

Completed

Are we in the Marketplace????
AIFAQ Pro Snowflake version 1.mp4Preview (A.I.F.A.Q ?)

One Pager

Infographic - Unlocking Conversational IntelligencePreview Remove Marketing hype/ add features available now

Infographic - AIFAQ Application InfoPreview

Available Now – Version 1

• Read unstructured data directly from Snowflake stages: PDF, DOC/DOCX, CSV, TXT.

• 100% Snowflake-native — your data never leaves your account.

• Enterprise-grade security, compliance, and auditability.

• Role-based access and granular permissions.

• Instant deployment via Snowflake Marketplace.