2.1 ZAI quick start (QS) (WIP)
A detailed QS that starts from 0, giving you core Foundry skills (and a real understanding of key Foundry concepts). Stays laser-focused on
- the core mechanics of using Foundry
- how to navigate the UI and the terminology
- using FDE (Foundry’s built-in AI assistant)
See also
- foundry_qs (a test converting about 5% of the docx source file to markdown for display on this website).
- Docx #695 is my working version of this demo (open that doc; I will not be (for now) adding anything on this webpage).
- C2 The future of programming Foundry (and documentation) is here today (WIP).
THE REASON FOR THIS DOCX
- I spent several months doing various Foundry demos. These were all “realistic” demos, step by step. The problem was the “realistic” aspect. I needed a demo that focused on the mechanics of how to create all the mechanisms (Projects, apps, UI (very compicated), ObjectTypes, actions, etc etc etc) with minimalistic non-real-world demos (eventually I would want such demos, but at first).
- Using AI (FDE) to create demos is probably the most important thing to learn. This docx show my interaction with GPT and FDE.
Foundry solves some very complicated problems. Its a fantastic tool. Proven in the marketplace. So its well worth the effort to learn. But you need to learn to walk before you can run, and this demo starts with crawling.
The first UI created in this demo
26.1027
OLD (the original idea for a QS)
I eventually decided to create my own from scratch.
CREATE 2.2a ZAI VERSION OF FOLLOWING
========================================================
**TL;DR**? Then skip to **[Demo D3 "Speedrun -- Your First Agentic AIP Workflow"](/3c.3_pal_agentic_ai/)**, a great example of the direction this part of ZiptieAI is heading.
<br>
**These demos are not for show. They are for do-it-yourselfers. Those like myself who want minimal text/diagrams and maximum useful info for getting hands-on experience.** The main focus is on
- Organizing the demos into a series that intros Foundry in logical order.
- Getting the workflows correct and explaining the big picture concepts.
- (1) Creating ZAI versions of existing PAL demos and (2) creating (from scratch with AI assistance) original ZAI demos (such as **"3.1 D9 Haystack needle demo"**).
- Generating the ZAI website docs from docx files (using GPT).
See also (these are outdated... I will update them later)
- **[PAL demo strategy](/3c.aaa_pal_strategy_demos/)**.
- **[Important info about doing these demos](/3c.2.0_info_about_demos/)**. The advantages of website tutorials over Youtube videos (at least for beginners) and the critical importance of FDE (Foundry's built-in AI chat tool).
TOC:
START-TO-FINISH [1]-[5] ZAI DEMO
- [1] 3 Core Foundry analytics // without LLMs (D9, D5) (finding “needles in the haystack”). Foundry’s core value proposition predates generative AI. It integrates data from different systems, represents entities and relationships through the Ontology, and helps users discover patterns, anomalies, connections, and business processes that are difficult to see in isolated datasets. In these demos, the LLM is an optional analytical assistant; the underlying data integration, Ontology, analysis, applications, and Actions remain useful without it.
- [2] 2a Data protection // and AI security (D3b, D3c) (added 26.0905). Data security = How do we prevent unauthorized access, disclosure, modification, or loss?
- [3] 1 External AI models (D1-D3). This is the first set of demos because (1) ZAI focuses primarily on AI and (2) external models are simpler than internal models.
- [4] 2b Sovereignty (2b.1-2b.8) (added 26.0905). These demos compare external, internally controlled, and hybrid AI architectures to determine what the organization actually controls. The focus is not only data protection, but also model replaceability, application ownership, operational continuity, and control of decisions and outcomes.
- [5] 2 Internal AI models (D8a-D8g). Demos that show how to create and host internal models.
- xxxxxxxxxxxxxxxxxx[6] 4 Other demos. Duplicate or unimportant demos (or demos I could not get to work).
The basic idea for the Start-to-Finish demo project:
- Like the name says, you start with nothing, continue to develop until you have covered all the main topics.
- The demo is a generic demo, simple, meant as a tech demo, not a real-world business process demo.
- The progression of the StF project is not [1]-[5] above. Rather, you do whatever comes next logically, and you use [1]-[5] to classify what you are adding.