Training: Daily oS3 Meeting Process v0

[trainfarb]

DEG Entreprises - Training Minutes

MINUTES: Training - Daily oS3 Meeting Process v0

Start Date: 2024.03.14.THU End Date: 2024.03.17.SUN

A.2.7 Meeting Platform Header

A.2.7.0 Meeting Memo

• Meeting Memo Draft
• Meeting Mastery Protocol For Effortless Delegation and Productivity so You Have More Time for Creativity
• Inspired the Internal Developer Platform goal of helping people become self-suffiencnt
• IDP Inspired Meeting Protocol: Each meeting ties directly into an IDP for seamless productivity
• Platform As A Product -> Meeting Platform As A Product

A.2.7.1 Agenda

-

A.2.7.2 Minutes

• Everything in meeting minutes are action items.
• ex. add to risk register, add to research log, add to drawings, etc.
• This makes it easier for people who might be creating meetings without everyone on the team involved.
• Risk Management team might not want the owner adding items that are already in the log.
• If the OWNER just states what needs to get done, then the PRODUCER team can simply assign the task to the appropriate team based on what the OWNER wrote, and then the Risk Management team can choose to do with it what's best based on their knowledge and experience.
• This allows owners to put all of their focus on memos.
• Just say what you want done, and then the PRODUCER/Management Team will get it in the hands of the people who are most qualified.
• Reduce the amount that an owner needs to understand about the whole ecosystem so they can focus on the vision

A.2.7.3 Debrief

• Define Debrief format as "8 Paragraphs * 3 Sentences = 24 Sentence Debrief"
• Draft oS3 Meeting Process v0 Debrief: [DEG] A.2.7.1.1 - Create P3 Agenda workSheet Process
• Publish oS3 Meeting Process v0 Debrief based on What Is Platform Engineering? video

B.0.9 Onboarding Platform Header

B.0.9.0 Onboarding Memo

-

B.0.9.1 Prompts

-

B.0.9.2 Documentation

• Turn the GitHub Projects IDP3 Template into a Self Serve Product with each item being a set of documentation
• Split meeting Protocol Documentation across all of the different issues

B.0.9.3 Models

-

D.8.1 Management Platform Header

D.8.1.0 Management Memo

-

D.8.1.1 Work Breakdown Structure

• Decentralize Memo, Agenda, Minutes, and Debriefs across different teams
  • [hu3] Move Debrief from DEG/P3 Agenda to Debrief for Training: Daily oS3 Meeting Process v0 - Ultimately will move this to Debrief for Governance: Daily oS3 Meeting Process v0. This will ensure that DEG only focuses on Memos, trainfarb only focuses on agendas, hu3agency only focuses on minutes, and ourStory only focuses on debriefs.
  • [hu3] Move Minutes from DEG/P3 Agenda to these Minutes

D.8.1.2 Schedules

• Add default schedule for Meeting Process v0
  • Day 0 - 2.7 OWNER Memo: create meeting memo to define PURPOSE
  • Day 1 - 0.9 PRODUCER Agenda: create documentation based on PURPOSE
  • Day 2 - 8.1 PRODUCER Agenda: create schedule based on agenda
  • Day 3 - 7.2 PRODUCER Agenda: create design based on schedule
  • Day 4 - 9.0 PROVIDER Minutes: create cohort meeting based on design
  • Day 5 - 6.3 PROVIDER Minutes: create meeting minutes based on cohort meeting
  • Day 6 - 5.4 PROVIDER Minutes: create case study based on meeting minutes
  • Day 7 - 1.8 CONSUMER Debrief: create agreement based on case study
  • Day 8 - 4.5 CONSUMER Debrief: create debrief based on agreement
  • Day 9 - 3.6 CONSUMER Debrief: create storyboard based on debrief

D.8.1.3 Logistics

• GOLDEN PATH: Here's the updated Meeting to Go-To-Market Strategy Approach
  • OWNER: Transform CONSUMER Debrief into Memo summarizing the agenda, minutes, and debrief of the next meeting
  • PUBLISH a memo about the Situation (Agenda)
  • Complication (Minutes)
  • and Resolution (Debrief) for an upcoming meeting
  • PRODUCER: Transforms OWNER Memo into an Agenda with 0.9 Onboarding, 8.1 Management, and 7.2 Design so it's ready for PROVIDER
  • FINALIZE the 0.9 Onboarding (AGENDA)
    • 0.9.0 Review OWNER Memo and add notes
    • 0.9.1 Define prompts that map to each agenda item
    • 0.9.2 Create documentation for how training team will work through each agenda item
    • 0.9.3 Link each agenda item to visual API Model
  • Develop a DRAFT of the 8.1 Management (MINUTES)
    • 8.1.0 Review OWNER Memo/Onboarding Notes and add Notes
    • 8.1.1 Translate prompts and agenda items into a Work Breakdown Structure
    • 8.1.2 Review documentation and assign durations to each task for schedule
    • 8.1.3 Review agenda/visual API Model and map flow of work
  • DRAFT the 7.2 Design (DEBRIEF)
    • 7.2.0 Review OWNER Memo/Onboarding/Management Notes and add Notes
    • 7.2.1 Find relevant research articles associated with Work Breakdown Structure
    • 7.2.2 Create design for agenda/schedule
    • 7.2.3 Add any lessons learned from previous steps to Specifications (Appendix)
  • PROVIDER: Transforms PRODUCER Agenda into Meeting Minutes with 9.0 Training, 6.3 Marketing, and 5.4 Sales so it's ready for CONSUMER
  • PUBLISH minutes by working through agenda: PROVIDER
  • Carry out 9.0 Training (AGENDA)
    • 9.0.0 Review OWNER Memo/PRODUCER Notes and add Notes
    • 9.0.1 Turn Work Breakdown Structure into Meeting Curriculum
    • 9.0.2 Transform agenda/schedule design into Meeting Unit Plan
    • 9.0.3 Turned "Lessons Learned" specifications into Meeting Lesson Plan
  • FINALIZE the 6.3 Marketing (MINUTES)
    • 6.3.0 Review OWNER Memo/PRODUCER/Training Notes and add Notes
    • 6.3.1 Turn Meeting Curriculum into a Risk Register
    • 6.3.2 Transform Unit Plan into Contingency Plan
    • 6.3.3 Turn Lesson Plan into Ecosystem Marketing Campaign
  • UPDATE the DRAFT 5.4 Sales (DEBRIEF)
    • 5.4.0 Review OWNER Memo/PRODUCER/Training/Marketing Notes and add Notes
    • 5.4.1 Turn Risk Register into Proposal
    • 5.4.2 Transform Contingency Plan into Financial Plan
    • 5.4.3 Turn Ecosystem Marketing Campaign into Case Study
  • CONSUMER: Transform PROVIDER Minutes into Debrief with 1.8 Governance, 4.5 Communications, and 3.6 Story so it's ready for OWNER
  • Submit posts to 1.8 Governance (AGENDA)
    • 1.8.0 Review OWNER Memo/PRODUCER/PROVIDER Notes and add Notes
    • 1.8.1 Link Proposal to Long Term Platform Goals (Vision 2050)
    • 1.8.2 Link Financial Plan to Platform Agreements
    • 1.8.3 Link Case Study to Platform Wallets who will carry out actions
  • Work through ideas with 4.5 Communication (MINUTES)
    • 4.5.0 Review OWNER Memo/PRODUCER/PROVIDER/Governance Notes and add Notes
    • 4.5.1 Link Long Term Platform Goals (Vision 2050) to Platform Theory/Belief
    • 4.5.2 Transform Platform Agreement into Ongoing Experiment/Discussion
    • 4.5.3 Use Platform Wallets to publish blog posts/articles/etc.
  • FINALIZE the 3.6 Story (DEBRIEF)
    • 3.6.0 Review OWNER Memo/PRODUCER/PROVIDER/Governance/Communications Notes and add Notes
    • 3.6.1 Turn Platform Theory/Belief into worldBuilding strategy
    • 3.6.2 Turn Ongoing Experiment into Operations Plan
    • 3.6.3 Turn Blog Posts/Articles/etc. into Maintenance Plans

E.7.2 Design Platform Header

E.7.2.0 Design Memo

-

E.7.2.1 Research

• Add "What is a Minimum Viable Platform (MVP) by Luca Galante @ Humanitec" to Research Log
• What Is Platform Engineering? Video
  • DEFAULT STRUCTURE FOR DEBRIEFS
  • Use this as a way to describe what these meeting protocols are meant to be
  • Each meeting is meant to be a smaller version of an entire Internal Developer Platform
  • By someone walking through meeting minutes, they get a full view of how a platform works
  • And it follows the same structure between ecosystems, so it's easier for different teams to share and exchange resources to improve productivity.
• Mini Essays: The Ultimate Learning Tool
  • Use this to drive how debriefs are written as short stories to inspire OWNER to read the minutes to see how it plays into the platform.
  • Also apply this to the concept of mini meetings. The idea behind this approach to meeting minutes is that each meeting is split off into various mini meetings that are each tackled one by one to give them the attention they deserve to ensure the entire platform understandings the context they're operating within.
• Satirical National Convention: A Parallel Structure to the Republican and Democratic National Conventions to inform open source governance
  • https://youtu.be/2apJ95D8vX4?si=q5jM3oZMYNxzlx72
  • https://youtu.be/3BDqfqt9OQU?si=VYopZZRiSJxnNoFV
  • https://youtu.be/HpLdjG20oe4?si=HQuMgIiVdLYWrCk0
  • https://youtu.be/btVHFQpSfEQ?si=cbdntLAVXpkwYoQU
  • https://youtu.be/f4mu8IhYQmg?si=iKDIqqA0OReL5-i-

E.7.2.2 Drawings

• Add 0.9.3 Models drawings for oS3 Meeting Process v0
  • 
• Draw Tree of Life to represent the different aspects of the meeting. Header of each section can be the tree of life with a zoomed in projection of the specific sacred geometry form that we used in DEG's Go-To-Market Strategy Pitch Deck.
  • 
• Notes after convo with hu3 advisor
  • 
• 
• 

E.7.2.3 Specifications

-

B.9.0 Training Platform Header

B.9.0.0 Training Memo

-

B.9.0.1 Curriculum

• Add the high level Curriculum operatingSystem process flow/transformation that will be taught with this meeting
  • OWNER MEMO summarizes the...
  • PRODUCER AGENDA (prompts, documentation, model)...
  • PROVIDER MINUTES (curriculum, unit plan, lesson plan)...
  • CONSUMER DEBRIEF (goals, agreements, wallets)...

B.9.0.2 Unit Plans

B.9.0.3 Lesson Plans

• Create training material with HuggingChat
  • "What is an MVP" blog as basis of design
  • Create a tutorial script for the importance of memo, agenda, minutes, and debriefs
  • In depth tutorial outlines that teach people how to do each step
  • Freshman in high school comprehension to gain interest before college
• Add high level benefits that are taught:
  • Much more detailed and intentional approach to meeting minutes. This forces people to catalog each meeting into each of the different sections that make up a platform so everything is logged and tracked immediately when the minutes are published. Nothing get's lost in the cracks.
  • Owners are able to FOCUS on the meeting, and when they get proficient at this, their PRODUCTIVITY increases so they're able to invest more energy into the CREATIVITY required to drive the vision
  • PRODUCERS are able to FOCUS on onboarding, mamegement, and/or design tasks. This increases their PRODUCTIVITY so they can improve the KNOWLEDGE BASE for themselves and the entire ecosystem.
  • PROVIDERS are able to FOCUS on training, marketing, and/or sales tasks. This increases their PRODUCTIVITY so they can increase COLLABORATION across the entire community.
  • CONSUMER are able to FOCUS on governance, communication, and/or story tasks. This increases their COMMUNICATION skills so they can invest the majority of their time in CREATIVITY.

F.6.3 Marketing Platform Header

F.6.3.0 Marketing Memo

-

F.6.3.1 Risks

-

F.6.3.2 Contingencies

-

F.6.3.3 Campaigns

• Turn the Daily P3 Meeting Protocol v0 Meeting into a Go-To-Market Strategy across each team with beats
• beatDrop (Instagram as primary to lead people to different platforms):
  • b7data institution: DEG Entreprises (Git (paper/bujo/UI)/ GitHub Issue (meeting/OS), Lgem)
  • Meeting Memo Outline: Carousel to drive people to the website to download and read full investment memo
  • Road to the singularity (Git, Paper, etc)
  • Teach people about Git through the lens of singularity/single cell/spore/seed/nervous system
  • Bullet Journal
  • Open Source
  • Backstage (IDP) Tutorial: https://youtube.com/playlist?list=PLGVPcLSzJXQos1O18dvKoW2XSczz2I2lH&si=cJaRuyoA006HciKA
  • b9language institution: (Fabric (prompts), GitBook (docs), HuggingFace (models), Ecovative)
  • Meeting Agenda: Documentation outline described in a 1.5 minute reel -> drive to Notion
  • Hugging Face
  • Google Generative AI Document
  • Discovered Fabric on GitHub feed
  • Will use this as a resource for 0.9.1 Prompts
  • b0education institution: (Backstage/ Payhip/ Framer, Andrew Millison)
  • Meeting Minutes: Overview of course description, unit plan, and lesson plan related to biomimicry
  • OWNER: Cell Nucleus
  • PRODUCER: Fungi Spore
  • PROVIDER: Water/ Human Nervous System
  • CONSUMER: Hemp/ Tree Seed
  • Unit Plans for A.2.7 Meeting Platform
    • Day 0-3 = Nucleus, Membrane, Cytoplasm, Cytoskeleton
    • Day 4-11 = Lysosome, ribosomes
    • Day 12-19 = Endoplasmic Reticulum, Mitochondria
    • Day 20-27 = Golgi Body, Centrosome
  • b8government institution: (GitHub Projects, Web5.js, Highway Vodka)
  • Meeting Debriefs: Description of how this plan plays into longterm goal for ourStory, Haiti, Refugee camps, and space migration settlements
  • b1infrastructure institution: (Kafka/ Ecovative)
  • Instagram Carousel as documentation preview. Healthy Intentions calendar to show how long it will take to get through the documentation. -> send to lemonsqueezy to access open source notion template
  • b2research institution: (Kafka/ Ecovative)
  • Nicole's Magic to show how the meetings can be applied to flower subscriptions and physically represented. Sacred Geometry Sketches and Designs as Figma design template -> send to lemonsqueezy to access open source Figma design template
  • b3marketing institution: (Framer, Andrew Millison)
  • Instagram risks/3at3/etc - contingency campaign highlights all posts and how we make merch from a meeting - meeting merch
  • Meeting Merch related to 9.0.1 Curriculum (v0gr1ego) about people’s ego showing: People in the huniverse getting offended with people’s ego is on display similar to someone’s johnson slipping out of their pantaloons.
  • b4economic institution: (Payhip/ Relay, Andrew Millison)
  • Website and Linkedin as consolidation of Instagram campaign to drive people to purchase course
  • b5media institution: (Nostr, Highway Vodka)
  • Longform blog post based on the debrief
  • MLOI making it funny.
  • Joking about how impossible it is to want to plan and organize a meeting when you have zero desire to do so, so it just leads to more self-sabotage and keeping you from what you want.
  • How can this be adapted to how Ashley runs her meetings with clients or how she plans her days, etc.
  • See where she can run with it.
  • Enter the debrief into MLOI AI Assistant with different guidance to evolve the story and punch it up.
  • b6entertainment institution: (Nostr, Highway Vodka)
  • YouTube storyboard that turns blog post from MLOI into a comic strip scored by Wesley. Story relates to how he can use these meetings to drive his vision forward and how that applies to Schine.
  • Evocation comic with audio overlay
  • First flower equals the first meeting that a person completes to build their platform

G.5.4 Sales Platform Header

G.5.4.0 Sales Memo

-

G.5.4.1 Proposals

• List Meeting Memo, Agenda, Minutes, and Debrief as MVP (Minimum Viable Platform) for oS3
  • OWNER Product = BuJo Templates
  • PRODUCER Product = GitHub Issues & Project Templates
  • PROVIDER Product = Google Workspace Templates
  • CONSUMER Product = Notion Templates
• Add "Help people focus on what matters" to benefits section of proposal
• Add Meeting Booklet as product output
  • Memo is the inside cover
  • Agenda is the table of contents
  • Minutes are the book
  • Debrief is the back cover
• Create Producer Template: [TEMPLATE] PRODUCER Internal Developer Parallel Permaculture Platform (IDP3)
• Create Provider Template: [TEMPLATE] PROVIDER Internal Developer Parallel Permaculture Platform (IDP3)

G.5.4.2 Financials

-

G.5.4.3 Case Studies

• Define case study format
  • Situation
  • Complication
  • Resolution
• [hu3] Clone PRODUCER IDP3 to hu3 GitHub and Update Naming (LOOM VIDEO)
• Situation:
  • Retroactively creating the Rwanda 2023 Trip to develop a system that turns meetings into go-to-market strategies moving forward
  • Ultimately, I want each day from the trip to be an engaging story that adds value
  • Important that we can capture everything that happened in the context of each pillar
• Complication:
  • Analysis paralysis
  • Wanted to create a system that allowed meetings to flow seamlessly into workflows
  • Currently March 2024, and it's difficult consolidating all of the different locations that the story was captured (Emails, Google Workspace, Notebooks, WhatsApp, Photos, Videos, etc.)
  • Meetings were always a pain point in previous companies
  • Fragmented approach across teams with little to no buy in because everyone is busy
  • A lot falls through the cracks
• Resolution:
  • End result will be an automated system that acts as a front-end to GitHub
  • MVP is in GitHub Projects.
  • Decide to focus on the Trip Recap as storytelling, so it aligns perfectly with the Balance Period Wellness Wallet.
• Create a case study showing how a single meeting can turn into content across 13 different platforms

C.1.8 Governance Platform Header

C.1.8.0 Governance Memo

• 1.8 Governance Tab in the GitHub Project IDP3 to serve as the MVP of the wellness wallet for DEG.
• This acts as a single source of truth for the content shared each day.
• This can be thought of as the consumer wallet that captures all notes/interactions from participants in the ecosystem.
• Wallet consists of three main parts
  • Goals (Balance Period: Awareness)
  • Agreements (Balance Period: Accountability)
  • Wallets (Balance Period: Appreciation)

C.1.8.1 Goals

• Outline goals of oS3 Meeting Process v0's Go-to-Market Strategy
• Goals (BP_Awareness): Rwanda Vision 2050 pillar that posts will align with
• Add as long-term goals:
  • Run all past DEG meetings through the oS3 Meeting Process v0 to refine IDP3
  • Using satire to reverse engineer how different companies govern meetings to inform how we approach open source governance with DEG
  • Republican and Democratic National Conventions are Influenced by Private Equity
  • Satirical National Convention is influence by Open Equity (Open Source Private Equity as a P3 Ecosystem)
  • Republican and Democratic National Conventions centralize on One Candidate
  • Satirical National Convention create a shared story of all open source contributors
  • Stand for a collaborative vision from every contributor, even the Dem and Rep Nominees
  • Gamified meetings: Meant to be a party that's actually fun...like parties are supposed to be
  • Plan for Citigroup to be the main investor in ourStory’s P3 Ecosystem in Haiti to show a more practical approach to reparations.
  • https://www.instagram.com/reel/C4dynDdr_T8/?igsh=am51bmUyZWJsMXV4

C.1.8.2 Agreements

• Define criteria that OWNER will look for from completed meeting
  • Incorporate these into the Go-To-Market Strategy Approval
• Define Agreements for each Action Item Approval
• Agreements (BP_Accountability): Simple baseline confirmation of the platform team that the post is associated with (Fundraising, Supply Chain, Manufacturing, Market).
• One of the 10 beats.

C.1.8.3 Wallets

• Define Wallets Used for Go-To-Market Strategy
  • DEG = We enable Rwandan Alcoholic Beverage Manufacturers to participate in the future of African Neutral Alcohol Supply Chains.
  • trainfarb = We enable small businesses to participate in the future of meeting platforms.
  • hu3agency = We enable manufacturers to participate in the future of project platforms.
  • ourStory = We enable families to participate in the future of story platforms.
• Wallets (BP_Appreciation): Draft of what someone is sharing as a contribution to the go-to-market strategy to resolve an open item from the meeting minutes. Any of the beats.

H.4.5 Communications Platform Header

H.4.5.0 Communications

H.4.5.1 Theories

• hu3agency's theory (every contributor can have a different theory): If we can develop an open source go-to-market strategy for governing meetings for DEG in Rwanda, then we can bring a similar model to DEG's original location in Haiti

H.4.5.2 Experiments

• longPlay Vision for a Satirical Party Convention (As governance story) - Turn lesson plan into a goal, agreement, and wallet so each platform can agree on the output that they'll be generating (beats)

H.4.5.3 Publications

I.3.6 Story Platform Header

I.3.6.0 Story Memo

I.3.6.1 Building

• Haiti is the central challenge that the Satirical Party (hu3's version) is focused on to curb immigration, address immigration, and become a foundation to an international space race
  • https://www.instagram.com/reel/C4axkUVrWiH/?utm_source=ig_web_copy_link
• Space Race is defined by creating EarthShip (City) Factories
• Self-Sovereign City Blocks centered around Permaculture Manufacturing
• Signed Up for Beyond earth: blueprint for SMBs in space innovation Webinar on April 9th.

I.3.6.2 Operations

I.3.6.3 Maintenance

• https://www.cosmopolitan.com/lifestyle/a46001206/1515-angel-number-meaning/ Saw 15:15 when realizing the ideal Daily P3 Onboarding Protocol

  Seeing angel number 1515 means that your career will go through a change or take a new direction. You are in line for something bigger and better. Whatever you decide—to focus on your current career path, apply for a new job, or start your own business—know that your angels support your decision. Sometimes, a new area of interest or different a different career path may unexpectedly come your way. Even though it may be surprising, it’s more important to remember that the universe is supporting you and guiding you towards a path that will bring you spiritual satisfaction.

Use this to onboard OWNERS into a new meeting

This angel number serves as a divine signal that you are about to embark on a transformative journey. Harness your inner strength and pay attention. You are about to make positive choices with your guardian angels supporting you. Angel number 1515 is a sign of new beginnings and opportunities coming your way. This number will keep following you until you open your heart to receive its blessings. Notice the way in which you might be holding yourself back or resisting change. While change isn’t always easy, it’s necessary. This angel number lets you know that you can access the best outcomes with aligned action.

[trainfarb]

2024.03.16.SAT.1030CST

• (Added to 7.2.1 Research) Focus on MVP blog from the Platform Engineering company
• (Added to 5.4.1 Proposals) MVP is a memo, agenda, minutes, and debrief
• (Added to 5.4.1 Proposals) MVP output will be a worksheet printout, Google doc template, Google sheets template, Notion template, GitHub issues template, airtable template, etc for filling them out
• (Added to 5.4.1 Proposals) GitHub projects is only for the platform design engineer on the backend
• (Added to 5.4.1 Proposals) Help people only focus on what matters
• (Added to 5.4.1 Proposals) Memo is the inside cover, Agenda is the table of contents, minutes are the book, debrief is the back cover
• (Added to 9.0.3 Lesson Plans) Use HuggingChat to build out training material to create a tutorial script for the importance of memo, agenda, minutes, and debriefs based on blog inputs. Then have it create in depth tutorial outlines that teach people how to do each step (freshman in high school comprehension so they can get interested in this before choosing what to do in college). Those tutorials will be the minutes

---

Proof of Work Minutes

2024.03.21.THU Proof-of-Work Minutes

(Added to 1.8.3 Wallets) trainfarb = We enable small businesses to participate in the future of meeting platforms.

(Added to 1.8.3 Wallets) hu3agency = We enable manufacturers to participate in the future of project platforms.

(Added to 1.8.3 Wallets) ourStory = We enable families to participate in the future of story platforms.

(Added to 8.1.2 Schedules) Meeting Protocol (Added to 8.1.2 Schedules) Day 0 - 2.7 OWNER Memo: create meeting memo to define PURPOSE (Added to 8.1.2 Schedules) Day 1 - 0.9 PRODUCER Agenda: create documentation based on PURPOSE (Added to 8.1.2 Schedules) Day 2 - 8.1 PRODUCER Agenda: create schedule based on agenda (Added to 8.1.2 Schedules) Day 3 - 7.2 PRODUCER Agenda: create design based on schedule (Added to 8.1.2 Schedules) Day 4 - 9.0 PROVIDER Minutes: create cohort meeting based on design (Added to 8.1.2 Schedules) Day 5 - 6.3 PROVIDER Minutes: create meeting minutes based on cohort meeting (Added to 8.1.2 Schedules) Day 6 - 5.4 PROVIDER Minutes: create case study based on meeting minutes (Added to 8.1.2 Schedules) Day 7 - 1.8 CONSUMER Debrief: create agreement based on case study (Added to 8.1.2 Schedules) Day 8 - 4.5 CONSUMER Debrief: create debrief based on agreement (Added to 8.1.2 Schedules) Day 9 - 3.6 CONSUMER Debrief: create storyboard based on debrief

2024.03.15.FRI Proof-of-Work Minutes

• 3 hours 00 minutes: Draft Debrief
• Notes to Update
• Minutes based on Training: P3 Meeting Protocol v0
  • Meeting minute notes from Feb 14th and January (TBD)
  • (Added to 4.5.3 Publications) Write a draft of the debrief while watching What Is Platform Engineering?
• 0 hours 33 minutes: [hu3] Clone PRODUCER IDP3 to hu3 PROVIDER IDP3 and Update Naming
  • (Added to 5.4.1 Proposals) Producer Template: [TEMPLATE] PRODUCER Internal Developer Parallel Permaculture Platform (IDP3)
  • (Added to 5.4.1 Proposals) Provider Template: [TEMPLATE] PROVIDER Internal Developer Parallel Permaculture Platform (IDP3)
  • (Added to 5.4.3 Case Studies) LOOM Video: [hu3] Clone PRODUCER IDP3 to hu3 GitHub and Update Naming
• 0 hours 19 minutes: [hu3] Move Debrief from DEG/P3 Agenda to Debrief for Training: Daily oS3 Meeting Process v0
  • (Added to 4.5.3 Publications) Move From: [DEG] A.2.7.1.1 - Create P3 Agenda workSheet Process
  • (Added to 8.1.1 Work Breakdown Structure) LOOM Video: [hu3] Move Debrief from DEG/P3 Agenda to Debrief for Training: Daily oS3 Meeting Process v0
• 0 hours 07 minutes: [hu3] Move Minutes from DEG/P3 Agenda to these Minutes
  • Move From: [DEG] A.2.7.1.1 - Create P3 Agenda workSheet Process
  • (Added to 8.1.1 Work Breakdown Structure) LOOM Video: [hu3] Move Minutes from DEG/P3 Agenda to these Minutes
• X hours XX minutes: [hu3] Move "Random Notes" from tf Onboarding Protocol v0 Meeting to these Minutes
  • Move From: MINUTES: Develop Daily P3 Onboarding Protocol v0
  • LOOM Video: [hu3] Move "Random Notes" from tf Onboarding Protocol v0 Meeting to these Minutes
  • (Added to 0.9.3 Models)

2024.03.15.FRI Training: Daily oS3 Meeting Process v0 Brainstorm

(Added to 2.7.0 Memo) Meeting Mastery Protocol For Effortless Delegation and Productivity so You Have More Time for Creativity

• (Added to 2.7.0 Memo) Inspired the Internal Developer Platform goal of helping people become self-suffiencnt
• (Added to 2.7.0 Memo) IDP Inspired Meeting Protocol: Each meeting ties directly into an IDP for seamless productivity
• (Added to 2.7.0 Memo) Platform As A Product -> Meeting Platform As A Product

(Added to 5.4.3 Case Study) Situation: Retroactively creating the Rwanda 2023 Trip to develop a system that turns meetings into go-to-market strategies moving forward. Ultimately, I want each day from the trip to be an engaging story that adds value, so it's important that we can capture everything that happened in the context of each pillar. End result will be an automated system that acts as a front-end to GitHub. MVP is in GitHub Projects.

(Added to 5.4.3 Case Study) Complication: Currently March 2024, and it's difficult consolidating all of the different locations that the story was captured (Emails, Google Workspace, Notebooks, WhatsApp, Photos, Videos, etc.)

(Added to 5.4.3 Case Study) Resolution: Realization that the Trip Recap is telling the story, so it aligns perfectly with the Balance Period Wellness Wallet. Use the 1.8 Governance Tab in the GitHub Project IDP to serve as the MVP of the wellness wallet for DEG. This acts as a single source of truth for the content shared each day. This can be thought of as the consumer wallet that captures all notes/interactions from participants in the ecosystem. Since this is the wallet, we created a spreadsheet with the columns:

• (Added to 1.8.0 Governance Memo) Goals

• (Added to 1.8.0 Governance Memo) Agreements

• (Added to 1.8.0 Governance Memo) Wallets

• (Added to 1.8.0 Governance Memo) This follows the wellness wallet approach:

• (Added to 1.8.0 Governance Memo) The Goal will be the Rwanda Vision 2050 pillar that the event will align with, agreement for this will be a simple baseline confirmation of the platform team that the post is associated with (Fundraising, Supply Chain, Manufacturing, Market), and finally being submitted in the persons wallet as a draft before being shared to 4.5 and 3.6.

• (Added to 8.1.3 Logistics) Here's the updated Meeting to Go-To-Market Strategy Approach:

• OWNER: Meeting

  • (Added to 2.7.3 Minutes) Meeting Minutes: Everything in meeting minutes are action items. (ex. add to risk register, add to research log, add to drawings, etc. This makes it easier for people who might be creating meetings without everyone on the team involved. Risk Management team might not want the owner adding items that are already in the log. If the OWNER just adds an action item, then the management team can simply assign the task to the appropriate team based on what the OWNER wrote, and then the Risk Management team can choose to do with it what's best based on their knowledge and experience. This allows owners to increase their focus during meetings. Just say what you want done, and then the PRODUCER/Management Team will get it in the hands of the people who are most qualified. Reduce the amount that an owner needs to understand about the whole ecosystem so they can focus on the vision)
    • (Added to 7.2.1 Research) 7.2.1 Research: Mini Essays: The Ultimate Learning Tool - Use this to drive how debriefs are written as short stories to inspire OWNER to read the minutes to see how it plays into the platform. - Also apply this to the concept of mini meetings. The idea behind this approach to meeting minutes is that each meeting is split off into various mini meetings that are each tackled one by one to give them the attention they deserve to ensure the entire platform understandings the context they're operating within.
    • (Added to 7.2.1 Research) 7.2.1 Research: What is Platform Engineering? - DEFAULT STRUCTURE FOR DEBRIEFS - Use this as a way to describe what these meeting protocols are meant to be. Each meeting is meant to be a smaller version of an entire Internal Developer Platform. By someone walking through meeting minutes, they get a full view of how a platform works. And it follows the same structure between ecosystems, so it's easier for different teams to share and exchange resources to improve productivity.
    • (Added to 7.2.2 Drawings) 7.2.2 Drawing: Draw Tree of Life to represent the different aspects of the meeting. Header of each section can be the tree of life with a zoomed in projection of the specific sacred geometry form that we used in DEG's Go-To-Market Strategy Pitch Deck.
    • (Added to 7.2.2 Drawings)
    • 7.2.3 Specification: N/A

(Added to 9.0.3 Lesson Plans) Much more detailed and intentional approach to meeting minutes. This forces people to catalog each meeting into each of the different sections that make up a platform so everything is logged and tracked immediately when the minutes are published. Nothing get's lost in the cracks.

• (Added to 9.0.3 Lesson Plans) Owners are able to FOCUS on the meeting, and when they get proficient at this, their PRODUCTIVITY increases so they're able to invest more energy into the CREATIVITY required to drive the vision
• (Added to 9.0.3 Lesson Plans) PRODUCERS are able to FOCUS on onboarding, mamegement, and/or design tasks. This increases their PRODUCTIVITY so they can improve the KNOWLEDGE BASE for themselves and the entire ecosystem.
• (Added to 9.0.3 Lesson Plans) PROVIDERS are able to FOCUS on training, marketing, and/or sales tasks. This increases their PRODUCTIVITY so they can increase COLLABORATION across the entire community.
• (Added to 9.0.3 Lesson Plans) CONSUMER are able to FOCUS on governance, communication, and/or story tasks. This increases their COMMUNICATION skills so they can invest the majority of their time in CREATIVITY.

2024.03.13.WED Notes after PapAchille Convo

(Added to 7.2.2 Drawings)

2024.03.13.WED Proof-of-Work Minutes

(Added to 9.0.1 Curriculum) What is the process flow? How does the operating system work? (Create a visual for a walkthrough)

• (Added to 9.0.1 Curriculum) OWNER organizes a meeting (memo, agenda, minutes, debrief) using…
• (Added to 9.0.1 Curriculum) PRODUCER’s visual API (prompts, documentation, model) so…
• (Added to 9.0.1 Curriculum) PROVIDER can develop a biomimicry strategy (curriculum, unit plan, lesson plan) that enables…
• (Added to 9.0.1 Curriculum) CONSUMERs to self govern (goals, agreements, wallets)

What’s next?

• (Added to 2.7.0 Memo) Turn meeting minutes from this meeting into an onboarding strategy: https://github.com/orgs/deg-entreprises/projects/8/views/1?pane=issue&itemId=56235587
• (Added to 1.8.1 Goals) Start running all past meetings of each of these teams through the P3 Daily Meeting Protocol
• Goals:
  • (Added to 0.9.2 Documentation) Turn the Template into a Self Serve IDP Product with each item being a set of documentation
  • (Added to 0.9.2 Documentation) Split meeting Protocol Documentation across all of the different issues
  • (Added to 6.3.3 Campaigns) Turn the Daily P3 Meeting Protocol v0 Meeting into a Go-To-Market Strategy across each team with beats
  • (Added to 5.4.3 Case Study) Create a case study showing how a single meeting can turn into content across 13 different platforms

[HU3] 2024.03.12.TUE.1944CST_B.9.0_Develop Daily P3 Training Protocol v0_Draft 1-day Lesson Plan

Duration: 38 Minutes LOOM Link: Click Here

• Brainstorm Meeting Minutes
• Outline each team with a singular focus for the day

  Teams

• OWNER Complete DEG Meeting: Develop Daily P3 Meeting Protocol v0
• PRODUCER Complete trainfarb Onboarding: Develop Daily P3 Onboarding Protocol v0 - Turn meeting minutes into prompts, documentation, and a model to teach all platform participants about the most up to date practices
• PROVIDER Complete hu3agency Training: Develop Daily P3 Training Protocol v0 (Below as a cohort based course) - Turn onboarding model into a curriculum, unit plan, and lesson plan so all platform participants can put the meeting best practices into action
• CONSUMER Complete ourStory Governance: longPlay Vision for a Satirical Party Convention (As governance story) - Turn lesson plan into a goal, agreement, and wallet so each platform can agree on the output that they'll be generating (beats)
  • Satirical National Convention: A Parallel Structure to the Republican and Democratic National Conventions
  • https://youtu.be/2apJ95D8vX4?si=q5jM3oZMYNxzlx72
  • https://youtu.be/3BDqfqt9OQU?si=VYopZZRiSJxnNoFV
  • https://youtu.be/HpLdjG20oe4?si=HQuMgIiVdLYWrCk0
  • https://youtu.be/btVHFQpSfEQ?si=cbdntLAVXpkwYoQU
  • https://youtu.be/f4mu8IhYQmg?si=iKDIqqA0OReL5-i-
  • Republican and Democratic National Conventions are Influenced by Private Equity
  • Satirical National Convention is influence by Open Equity (Open Source Private Equity as a P3 Ecosystem)
  • Republican and Democratic National Conventions centralize on One Candidate
  • Satirical National Convention create a shared story of all candidates who weren't selected
  • Stand for a collaborative vision from every candidate, even the Dem and Rep Nominees
  • Meant to be a party that's actually fun...like parties are supposed to be
  • Focus of hu3agency's Satirical Party (Anyone can create one) is focused on Haiti
  • Haiti is the central challenge that the Satirical Party (hu3's version) is focused on to curb immigration, address immigration, and become a foundation to an international space race
  • https://www.instagram.com/reel/C4axkUVrWiH/?utm_source=ig_web_copy_link
  • Space Race is defined by creating EarthShip (City) Factories
  • Self-Sovereign City Blocks centered around Permaculture Manufacturing
  • Signed Up for Beyond earth: blueprint for SMBs in space innovation Webinar on April 9th.
  • 2024.03.13.WED.1550CST - Plan for Citigroup to be the main investor in ourStory’s P3 Ecosystem in Haiti to show a more practical approach to reparations.
  • https://www.instagram.com/reel/C4dynDdr_T8/?igsh=am51bmUyZWJsMXV4

    Players

• [D.8.1] Healthy Intentions, Quantum MeMoir
• [E.7.2] Nicole's Magic: Discuss Daily Strategy for Launch and Complete workPad
• [F.6.3] JRs Joyous Creations: N/A
• [G.5.4] The School of Bitcoin: N/A
• [H.4.5] Make Light of It: Create GitHub Organization
• [I.3.6] Pangium: N/A
• [A.2.7] Elephant & Falcon
• [C.1.8] Balance Period/oS: Reschedule meeting to friday

[trainfarb]

Agenda

[trainfarb]

DEG Entreprises - Training Debrief

DEBRIEF: Training - Daily oS3 Meeting Process v0

Start Date: 2024.03.14.THU End Date: 2024.03.17.SUN

Introduction

Have you heard about DEG's operatingSystem to openSource ourStory (oS3) Agendas but not sure if the process makes sense for you? DEG might center its entire Management Platform around oS3 Agendas, but does that mean you should incorporate it into your daily practice? In this oS3 Debrief, we'll introduce you to the new discipline of Parallel Permaculture Platform (P3) Design Engineering and how it relates to oS3 Agendas.

We'll be giving you a simple definition on oS3 Agendas, explain how it fits into a broader P3 Ecosystem, and what its main differences from your current approach to agendas are. We'll also dive into the value of P3 Agendas for your platform team and how it connects to your Internal Developer Platform. Finally, we'll talk about the main challenges P3 Design Engineers face with agendas along with some tips on how to address them.

Situation

oS3 Agenda Design is the art of turning all of the processes associated with meetings into simple checklists that reduce confusion and increase productivity for everyone involved. The sum of these simple checklists is commonly called an Internal Developer Platform (IDP). The IDP is built by P3 Design Engineers who use the "Platform as a Product" approach, which means we treat our coworkers and partners as our own internal customer.

P3 Design Engineering is the answer of innovative organizations to avoid the headaches of traditional business processes. While having the creative freedom to develop our own work processes is a great concept in theory, the day to day process of most employees is broken. The reality is that work becomes overwhelming when we have to waste energy on mundane tasks like agendas when could spend time on more meaningful work that would add actual value to our team.

Complication

As DEG started mapping out all of the different partners that we'd be working with on various continents, we quickly realized that the only way to maintain efficiency was by adding a platform layer for mundane tasks like oS3 Agendas. This layer is the Internal Developer Platform, and it's the end product of P3 Design Engineering. With an oS3 Agenda/IDP, less questions are asked, more time is worked on important work, and work is produced faster.

P3 Design Engineering is still in its infancy, so there are still some challenges that we need to address. Mainly, we need to improve our communication by having a better feedback loop with people who use processes like the oS3 Agenda. Also, it's difficult to explain the true value of P3 Design engineering to executives, so don't get the buy in for this to pay off as much as it could.

Resolution

This is why it's so important for us to keep this open source so we can grow a collaborative community that can develop best practices together. As different people use and adapt oS3 Agendas for themselves, we'll get a growing library of useful tools that help us work faster so we can spend more time being creative. Also, if we can create a shared language for how we approach work, it'll drastically improve communication between teams within and between organizations so we can get even more done together.

If you're interested in seeing if an out-of-the box approach to collaboration would help you save time to do what you want, read through our meeting minutes to learn a bit more. If you like what you see, you can try it for yourself. Let us know if you have any questions, comments, or feedback.

References

• What is Platform Engineering? by Platform Engineering
• [DEG] A.2.7.1.1 - Create P3 Agenda workSheet Process