A folder structure based off 10 years of manufacturing experience. I've been overseeing delivery of systems from design through manufacturing and deployment in my professional work. Everyone has their own system for organizing and building their solutions; this is a natural extension of the environment I work in every day and managing these projects the same way I would any other. The beauty is just like the lean practices inspiring this, this is a framework. All the specifics and magic in the workflow live in the context files, template details, and addition resources. Want to add in your specific quality guidelines? Throw it in config and reference it in the quality stage context file. Want to always build a specific component the same way? Add another file and reference it in design and assembly. This framework can be shaped any way to fit your workflow but the principals remain the same. Here's a brief breakdown of the process flow as well as the files produced. The intention is that this is the flow of objects created called "systems". A system can be anything inside a folder: an artifact, and ICM workflow, a collection of files. As long as it can fit in a folder, it’s applicable. The system folder template is: - References - inspiration or applicable documents relevant to that specific system build - Work Instructions - Where all the documents named below are stored and read from during the workflow. Documents are moved from active to processed subfolders as they are used in the sequence. - System - Where the actual output of the build is placed. This is the resulting files, or workspace produced. - travel-sheet.md - a document recording progress and a summary of every step executed on the project as it progresses. The workflow is as follows: 01 Design: 1. Scope - Define the goal of the project. The outcome written in one statement. What success looks like. Produces scope.md 2. Design - Define a full breakdown of the intent of the system/artifact/solution to be built. What it is, what it isn't. What success looks like with a wider explanation as well as what failure looks like. The gritty details. Produces design-brief.md 3. Review - A sanity check of design-brief.md that all pieces are in place. Was anything missed? Will the build team need more information? Produces design-review.md 4. Manufacturing Kickoff - Converts design-brief.md into a condensed format for handoff to the build agents. Removes reasoning and intent for build and only provides instructions for build for context tightening. Also provides instruction for quality check and testing down the road. Produces blueprint.md, qa-brief.md, test-plan.md

Tell us three things: 1. What you do (job, industry, student, career-changer, whatever) 2. What brought you to Clief Notes 3. One thing you're trying to figure out right now related to computing or AI I'll respond to every single one. And read each other's intros too because the person who's stuck on the same problem as you might already be in this thread. I'll go first I am Jake, I have been working in tech for 15 Years, building with Generative AI for 3 Years straight now! Excited to teach and learn! That's it. Simple, scannable, gives you data on who's joining and what they need, and keeps the feed clear for content that retains people past week one.