8.1.0 Chief Operating Office (dCOO) [Operations Platform Metadata]

[trainfarb]

Use Bullet Journal as the operating system Use this as digital interface, then paste notes into GitHub Issues: https://www.qownnotes.org Basis of Design: Day in the life of a Field Engineer https://youtube.com/watch?v=hej-XJiyuu0&si=fYC104g0rO879ReI

[trainfarb]

LOOM VIDEO: ourStory 0.9_b81 gr45v1: Onboarding Golden Path v0.00.00 - Setting Project Management Process Intention

gr45v1belief: Talking through my intentions of splitting up all tasks for onboarding in the lp81-operations-platform. How each tasks is atomized into onboarding metadata and deliverable. Talking about splitting each task up into a repetitive 3-step process.

• ourStory; Satirical; Awareness; gr45v1belief - tell hypothesis of why I think task will support
• openSource; Spiritual; Acceptance; gr45v2science - work through the steps to test out the hypothesis
• operatingSystem; Singularity; Appreciation; gr45v3sensemaking - reflect on the steps taken and talk about what the next round will be

Next, I'll turn each Golden Path into an issue in the lp81-operations-platform and add initial videos for this process.

[trainfarb]

ourStory 0.9_b81 gr45v2 v0.00.00: Onboarding Golden Path - Add Golden Path Items to Operations Platform

LOOM VIDEO: ourStory 0.9_b81 gr45v2 v0.00.00: Onboarding Golden Path - Add Golden Path Items to Operations Platform

gr45v2science: Walking through the onboard golden path milestones and adding them all to the lp81-operations-platform repository on GitHub and finding the structure for the comments.

Next, I'll record a video reflecting on what I did and coming up with the next step that I'll take to improve this and how it relates to the onboarding application. As an example, maybe the threads app can have each of the questions pre-loaded, and people respond to each and load in these types of comments as "commit statements" for their proof of work. Then, whey they hit publish it adds it as a comment to the GitHub issue or discussion and posts it on the wellnessWallet app (like talking about the platform through the lens of balance period because it helps remove my ego from the idea).

[trainfarb]

Will be combining GitHub Issues and Threads as a Nostr client as a Bullet Journal Inspired project management tool is pretty valuable. That's the backend portfolioWallet that the wellnessWallet and other wallets can be transformed with.

These GitHub Issues will have clear headers for proof of work and these comments in between will be the intentional discussions that people have within a project.

BENEFIT: Helpful for reducing the cognitive load of having to manage so many different ideas. Do the upfront work of prioritizing your 10 most important project teams, choosing a single task to focus on for each one, and funneling all proof-of-work and constructive conversation within the same thread so it's easier to write effective stories/publications/podcasts/case studies/beatDrops once it's done.

BENEFIT: Easiest way to create a case study to demonstrate the value that I can provide to myself and others.

[trainfarb]

8.1.0 v0.00.00 - Brainstorm Metadata Structure

2023 09 06

Minimum Problem

Hard to give a snapshot view of how oS3 Platform Ecosystems operate.

Viable Solution

Descriptive and consistent metadata structure that provides an easy to understand how oS3 Platform Ecosystems operate.

Product Delivery

• 8.1.0 Operations Metadata v0.00 (YAML file)
• 8.1.0 Operations Metadata v0.00 (GitHub Project)
• 8.1.3 openSource Work Breakdown Structure v0.00 (YAML file)
• 8.1.3 openSource Work Breakdown Structure v0.00 (GitHub Project)
• lp81-operations-platform repository updated for 8.1.0 & 8.1.3

Proof of Work

Thinking of new ways to map this out.

• Almost considered moving it up to 9.0.2 Lesson Plan since this really does act as a lesson plan.
• Then started thinking about the structure and focus for 0.9 and 9.0
  • 0.9 Onboarding
  • 0.9.0 Application Programming Interface
  • 0.9.1 Application
  • 0.9.2 Programming
  • 0.9.3 Interface
  • How can this be applied to 9.0?
  • First thought of this, since I was still thinking 9.0.2 lesson plan would be represented by the work that's currently here in 8.1.2
  • 9.0 Training
  • 9.0.0 Work Breakdown Structure
  • 9.0.1 Work
  • 9.0.2 Breakdown
  • 9.0.3 Structure
  • "Work" kinda worked, because 9.0.1 is currently "frameWorkbook" (probably will be chanced to workbook)...now thinking the physical workbook should be launched as a tool for superintendents who don't want to live on their screens. Great remix).
  • Then decided to apply Work Breakdown Structure to 8.1 and to change the name.
  • I think 9.0 and 8.1 can both represent the same structure pretty closely since they're both in the GOUND/Root Chakra within the Quantum MeMoir Earth Cycle.
  • 0.9:9.0 Application Programming Interface
  • 8.1: Work Breakdown Structure
  • Application = Work
  • Programming = Breakdown
  • Interface = Structure
• 1.8 should align, too since these 4 are clustered together like this. 8.1 and 1.8 can be thought of as being quantum entangled so the same convention will have to apply, but in a completely different way at a different scale
• Having a thought about how 9.0.3 Playlist can be a detailed "tic tock" list for every atomic step a person needs to take to carry out any of these steps. Embedded in a music playlist
• Here's how 0.9:9.0, 1.8, and 8.1 are quantum entangled

  GitHub Feature request / Streams Feature: A button that allows people to add a table at the size of their choosing within GitHub Issues

• [x] Add this link to resources for documentation / tutorial: https://www.codecademy.com/resources/docs/markdown/tables

0.9/9.0	1.8/5.4 // 8.1
Application/Ecological	Public // Work
Programming/Succession	Private // Breakdown
Interface/Plan	Partnership // Structure

• Keeping QM pairings in mind and linking the spheres that don't fall into primary chakras, things are grouped like this
  • Ground Chakra (1) and Heart Chakra (7)
  • [Image of where these are located on QM Base Code]

    3.6 Story Platform: Here's how things play out in this storyboard. Ground (Operations) Sphere/Operations Platform forms vesica pines with CONNECT (Partners) Sphere/Portfolio Platform Define PURPOSE Sphere/Product Platform form between the two of them to create an MVP MVP get's designed by the INTEND Design/Design Platform, etc.

Here's the final structure that I came up with for the platforms covered

• 0.9 Onboarding Platform
  • 0.9.0 Onboarding Metadata
  • 0.9.1 Application Abstract
  • 0.9.2 Programming Protocol
  • 0.9.3 Service Interface
• 9.0 Training Platform
  • 9.0.0 Training Metadata
  • 9.0.1 Ecological frameWorkbook
  • 9.0.2 Succession Lesson Plan
  • 9.0.3 Process Playlist
• 1.8 Governance Platform
  • 1.8.0 Training Metadata
  • 1.8.1 Public Canvas
  • 1.8.2 Private Tokenomics
  • 1.8.3 Partnership Technology
• 5.4 Portfolio Platform (Heart chakra is the first to form)
  • 5.4.0 Portfolio Metadata
  • 5.4.1 Public Pitch
  • 5.4.2 Private Investment
  • 5.4.3 Partnership Agreements
• 8.1 Operations Platform
  • 8.1.0 Operations Metadata
  • 8.1.1 Ecological Directory
  • 8.1.2 Succession Milestones
  • 8.1.3 Process Calendars
• 2.7 Product Platform
  • 2.7.0 Product Metadata
  • 2.7.1 Minimum Problem
  • 2.7.2 Viable Solution
  • 2.7.3 Product Delivery

Naming convention for the rest of these are all based on the values that were set in 1.8.2 Private Tokenomics (ex. ourStory/openSource/operationgSystem; Satirical/Spiritual/Singularity; etc)

• 7.2 Design Platform
  • 7.2.0 Design Metadata
  • 7.2.1 ourStory Research
  • 7.3.2 openSource Components
  • 7.2.3 Design operatingSystem
• 6.3 Marketing Platform
  • 6.3.0 Marketing Metadata
  • 6.3.1 ourStory Risk Analysis
  • 6.3.2 openSource Mitigation Plan
  • 6.3.3 Marketing operatingSystem

This should be the naming convention across all of the teams. Always end with the platform name and operatingSystem

• 0.9 Onboarding Platform
  • 0.9.0 Onboarding Metadata
  • 0.9.1 ourStory Abstract
  • 0.9.2 openSource Protocol
  • 0.9.3 Onboarding operatingSystem
• 9.0 Training Platform
  • 9.0.0 Training Metadata
  • 9.0.1 ourStory Workbook
  • 9.0.2 openSource Lesson Plan
  • 9.0.3 Training operatingSystem
• 1.8 Governance Platform
  • 1.8.0 Training Metadata
  • 1.8.1 ourStory Canvas
  • 1.8.2 openSource Tokenomics
  • 1.8.3 Governance operatingSystem
• 5.4 Portfolio Platform (Heart chakra is the first to form)
  • 5.4.0 Portfolio Metadata
  • 5.4.1 ourStory Pitch Package
  • 5.4.2 openSource Investment
  • 5.4.3 Portfolio operatingSystem
• 8.1 Operations Platform
  • 8.1.0 Operations Metadata
  • 8.1.1 ourStory Contributors
  • 8.1.2 openSource Work Breakdown Structure
  • 8.1.3 Operations operatingSystem
• 2.7 Product Platform
  • 2.7.0 Product Metadata
  • 2.7.1 ourStory Problem
  • 2.7.2 openSource Solution
  • 2.7.3 Product operatingSystem
• 7.2 Design Platform
  • 7.2.0 Design Metadata
  • 7.2.1 ourStory Research
  • 7.3.2 openSource Components
  • 7.2.3 Design operatingSystem
• 6.3 Marketing Platform
  • 6.3.0 Marketing Metadata
  • 6.3.1 ourStory Risk Analysis
  • 6.3.2 openSource Mitigation Plan
  • 6.3.3 Marketing operatingSystem
• 4.5 Publication Platform
  • 4.5.0 Publication Metadata
  • 4.5.1 ourStory Hypothesis
  • 4.5.2 openSource Experiment
  • 4.5.3 Publication operatingSystem
• 3.6 Story Platform
  • 3.6.0 Story Metadata
  • 3.6.1 ourStory Plot
  • 3.6.2 openSource Worldbuilding
  • 3.6.3 Story operatingSystem

Next Steps

• [ ] Write all of this out in a YAML file
• [ ] Add the 8.1 onboarding questions for the metadata
• [ ] Add the YAML file to the lp81-operations-platform repository
• [ ] Add the structure of the YAML file to the Work Breakdown Structure TEMPLATE issue for 8.1.0
• [ ] Create a 8.1.0 GitHub Project
• [ ] Publish to GitHub Sponsors
• [ ] Begin marketing the stream

[trainfarb]

MERGED from https://github.com/trainfarb/trainfarb/issues/43

8.1.0 v0.00.00 [DEG pt2] Metadata

• PURPOSE - MLNG: African Malanga Supply Chain Network
• GROUND - Rwanda Development Board
• INTEND - Self-Sovereignty
• OBSERVE - What can 1 acre produce?; Rural Development Initiative
• CONNECT - Wasoco
• EXPRESS - Sketch Video Tutorials for plot design
• REFINE - Organize by Asake

Product Brainstorming

• Ecosystem Owner:
  • Git
  • Quantum MeMoir
  • DEG
  • Arc (Boosts) (Remix GitHub in DEG Colors)
• Stream Producer:
  • GitHub
  • Google Workspace
  • Deg Entreprises - lp81coo
  • Linkedin
• Platform Provider:
  • Open BIM
  • Notion
  • Rwanda Development Board
  • Instagram
• Stream Consumers:
  • Backstage: MLNG (Nostr client for malanga farmers to control their platform)
  • FarmBot
  • Small Holder Malanga Farmers, Rural Development Initiative
  • Plebstr (Nostr)

NEXT STEPS

• Create Google Sheet of the onboarding form
• Create outline of the 8.1 in each folder for DEG