0.9.0 Chief Executive Platform v0.00 [oS3 Metadata]

[trainfarb]

Default: Chief Language Office Name: lp09_chiefLanguageOffice

Biomimicry: 2023 09 10

• Found the name for the skin of a tree: Periderm (knew bark wasn’t all of it) - https://youtube.com/watch?v=tG4Yw6eBotY&si=hj-gFdNqhFFxP-SW
• https://youtube.com/watch?v=QTZxv_A9FsQ&si=lwyn6_IPpfkBbmz3
• This explains it perfect: https://youtube.com/watch?v=V0FZNGn45ZE&si=FIHlrOoU_Wfu5yBd
  • 0.9.0 Periderm
  • 0.9.1 Phellem
  • 0.9.2 Phelogen - Cork Cambium
  • 0.9.3 Pelloderm

[trainfarb]

ourStory 0.9_b09 gr4v1 v0.00.00: Platform Profile Metadata Template - Explaining Onboarding Metadata Strategy

LOOM VIDEO: ourStory 0.9_b09 gr4v1 v0.00.00: Platform Profile Metadata Template - Explaining Onboarding Metadata Strategy

gr45v1belief: This sets the stage for the entire platform ecosystem. All of the metadata doesn't have to be figured out, but the singularity for what the platform will become is set here. This is the Big Bang and gives a rough projection of what each of the platforms can become from here.

Next steps: I'll be clarifying what the metadata for each team will be within the project (issue titles)

[trainfarb]

ourStory 0.9_b09 gr4v2 v0.00.00: Platform Profile: Clarifying structure and cleaning up naming conventions

BONUS: GitHub state management (not sure if that’s the name) really stood out to me because I didn’t save when creating a new column, but when I went to recreate my work, everything persisted. Reinforce why I want to learn front end development.

Note: Added a column for Open Source Platform Ecosystem (OSPE) Player and think the code convention needs to change:

• oS3Pi_CYTO > 144phiPi_MAMA: Producer because feminine energy creates something out of nothing
• 144phiPi_MAMA > oS3Pi_CYTO: Provider because the cells act as the canvas for our lives/cities
• 432ourPi_PAPA > 432ourPi_PAPA: Consumer because project managers consume everything to produce plans
• 369myPi_YOGA > 369myPi_YOGA: Owner because the offspring is the most valuable asset once they join

LOOM VIDEO: ourStory 0.9_b09 gr4v2 v0.00.00: Platform Profile: Clarifying structure and cleaning up naming conventions

[trainfarb]

ourStory 0.9_b09 gr4v3 v0.00.00: Platform Profile: Create Metadata Structure

Create YAML file of Platform Profile and each platform header Update metadata structure:

FAMBAM 8.1.0_b09 Chief Operating Office (dCOO)Metadata [TEMPLATE] FAMBAM 8.1.1_b81 Work Breakdown Structure (WBS) BENEFIT: This makes onboarding a lot more clear to help people make a mental model for how the teams relate to traditional businesses.

Note: In comments section of the YAML files, add alternatives for context, but keep the code clean with only one analogy to keep it simple for designers and engineers. Standards will be written in terms of “Chief Operating Office” and other alternatives like Scheduler, Project Engineer, or Mycelial Manager can be selected by any open source platform ecosystem, and they’ll just all translate back to that community’s Chief Operating Office so owners (individuals) can easily move from one ecosystem to another to exchange value even if they don’t have the exact same values

[trainfarb]

0.9.0 v0.00.00 - Brainstorm Metadata Structure

2023 09 06

Minimum Problem

You need to onboarding yourself and/or others into your creative idea, but finding the right language to explain your complex idea in a simple, but informative way is overwhelming. It's hard to organize all of the info.

Viable Solution

Create a simple outline that breaks down each complex concept into smaller chunks.

Product Delivery

0.9 Onboarding Platform - Explain Laravel / ourStory

• 0.9.0 Onboarding Metadata - Explain Git/GitHub Org
  • Person reads through Laravel Intro
  • Person reads through oS3's Intro
  • Person completes first question in onboarding questions to populate intro for themselves
  • Person reads through Git Intro
  • Person Reads through oS3 GitHub Org Intro
  • Person works through all questions that adds to their intro template
  • Download canvas to work through todo list items
  • Person creates a GitHub Org account
  • Person learns that this GitHub Org represents the PROVIDER of your ecosystem
  • Person adds link to issue to their 5.4.3 Proof-of-Work
• 0.9.1 ourStory Abstract - Explain Nostr/GitHub Issues
  • Read through Nostr Intro
  • Read through oS3 GitHub Issues Intro
  • Person downloads canvas to work through this todo list
  • Adds link of completed canvas to their 5.4.3 Proof-of-Work Project
• 0.9.2 openSource Tools - Explain Backstage/GitHub Repos
  • Read through Backstage Intro
  • Read through Backstage-Inspired oS3 GitHub Repo intro
  • Download canvas to work through the todo list
  • Add link of completed canvas to 5.4.3 Proof-of-Work Project
• 0.9.3 Onboarding operatingSystem - Explain Kafka/GitHub Projects
  • Read through Kafka Intro
  • Read through Kafka-Inspired oS3 GitHub Project Intro
  • Download canvas to work through the todo list
  • Add link of completed canvas to 5.4.3 Proof-of-Work Project

Next Step: 0.9.0 v0.00.01 - Research Lesson Topic

• Find reference intros for each
• Remix intro for each into a template
• Create todo list canvas for each
• Decide on Proof-of-Work Post that get's added to 5.4.3 Proof-of-Work

[trainfarb]

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

Don’t worry about having one basis of design for each, start a huge library of these in the repository and issues. Multiple landing page remixes / abstracts to serve as templates for people’s GitHub profile.

Process:

• 0.9.0 v0.00.00 - Mind Map Onboarding Metadata [ECOSYSTEM OWNER]
  • Deliverable: Quantum MeMoir Mind Map
• 0.9.0 v0.00.01 - Design Onboarding Metadata [PLATFORM PROVIDER]
  • Deliverable: Notion Template
• 0.9.0 v0.00.02 - Engineer Onboarding Metadata [STREAM PRODUCER]
  • Deliverable: Repository YAML File
• 0.9.0 v0.00.03 - Design Engineer Onboarding Metadata [STREAM CONSUMER]
  • Deliverable: GitHub Project

Steps:

• Complete onboarding questions for the following with
  • 0.9 Laravel, GitHub, & Arc
  • 09.90 - Ecosystem Owner: oS3 / GitHub Organization / Backstage
  • 18 - Application: Platform Provider: ourStory / GitHub Discussions / Nostr
  • 81 - Programming: Streamer: hu3agency / GitHub Projects / Kafka
  • 27 - Interface: Sponsor: trainfarb / GitHub Sponsors / Arc
  • 9.0 Maven Nostr TBD
  • 1.8 Hiro Polkadot Stacks
  • 8.1 Backstage buildingSMART openBIM
  • 2.7 Kafka Bullet Journal
  • 7.2 Partiful
  • 3.6 Krapopolis
  • 6.3 Polywork
  • 4.5 Brilliant Idiots
  • 5.4 Strike
• How each question goes (will seem cumbersome, but will become a really good interface online and helping people focus on just one question at a time.
  • They get notified that a stream they subscribe to grew
  • Following the link, they’re able to see the µcourse that they created by adding to the code
  • It’s part of 0.9, so it’s a very short course with 7 questions
  • Each question starts with a single circle in the middle of the page
  • Click the circle
  • It expands to the egg of life to work through the question prompts
  • They answer the first question (what’s the name of your ecosystem) in the express sphere
  • 0.9 - name of playlist (front of beatdrop)
  • 9.0 - playlist details (back of beatdrop)
  • 1.8 - details of game (Quantum MeMoir Base Code)
  • 2.7 - Name of your ecosystem?
  • 8.1 - primary platform? / institution?
  • 7.2 - brand values?
  • 6.3 - brand question?
  • 5.4 - brand inspiration?
  • 4.5 - content response?
  • 3.6 - playlist or song?
  • Each of these will be on its own sheet in my notebook…this will be the official start of my quantum pincer with each of these organizations
  • Document this with video

NOTE

How people onboard

• Application: ourStory (Survey) Streams is the 0.9 application. Define their info with an application (convert responses to images with OG)
• Programming: Software/tech stack/software catalog. Kafka, backstage, Nostr, etc...
• Interface: Electron is the software that will create the interface. Directory of ecosystems, platforms, streamers, and subscribers used in the ecosystem. The tools that the community is creating: Layout how the software, phone, tablet, and project will be defined and with what software

NOTE

https://youtube.com/watch?v=_ZvnD73m40o&si=eGhY_GGVF9woyob6

Prompt engineering is the baseline course

NOTE

This is a mind map generator for large language models

NOTE

This initial app will be a way for people to have a light weight local LLM that interacts with their GitHub and Notion. All social media posts are constructed w OG so every person can have a truly personal assistant.

Large language model can bring in designed quotes within responses based on how they're all saved to the repo.

MIND MAP ONBOARDING CLO METADATA

Create the following structure in Notion tomorrow and publish for ourStory

TABLE
0.9.0 Chief Language Office
  0.9.0 Mind Map Onboarding Platform Metadata
    ecosystem_owner: ourStory
    platform_focus: lp09_onboardingPlatform
    platform_value: self-sovereignty
    platform_question: What is a Platform?
    platform_inspiration: Git
    platform_expression: Instagram Guides
    platform_song: 174 Hz - Pain Reduction by Kev Thompson 
  0.9.1 Design Onboarding Platform Metadata
  0.9.2 Engineer Onboarding Platform Metadata
  0.9.3 Des Eng Onboarding Platform Metadata

• [ ] Next, turn it into a template

TABLE
0.9.0 Chief Language Office
  0.9.0 Mind Map Onboarding Platform Metadata
    ecosystem_owner: [ECOSYSTEM_OWNER]
    platform_focus: [PLATFORM_FOCUS]
    platform_value: [PLATFORM_VALUE]
    platform_question: [PLATFORM_QUESTION]
    platform_inspiration: [PLATFORM_INSPIRATION]
    platform_expression: [PLATFORM_EXPRESSION]
    platform_song: [PLATFORM_SONG]
  0.9.1 Design Onboarding Platform Metadata
  0.9.2 Engineer Onboarding Platform Metadata
  0.9.3 Des Eng Onboarding Platform Metadata

• [ ] Start saving each step in developing the wellnessWallet as a version control system. v0.00.00 will only be published once
• [ ] List Notion Version control at top of each page as a collapsible section

[trainfarb]

ADVANCE to https://github.com/trainfarb/trainfarb/issues/55

[trainfarb]

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

• [x] Create Google Docs responses for Git: 0.9.0 Git Responses - Google Docs
• [x] Create Google Docs template: 0.9.0 Google Docs Template
• [x] Update Basis of Design for 0.9.0
• [x] LOOM Video: https://www.loom.com/share/57c962cbd6064e51aabd44c2a671cab6
• Ecosystem Owner:
  • Git
  • Quantum MeMoir
  • oS3
  • Arc (Boosts)
• Stream Producer:
  • GitHub
  • Google
  • ourStory
  • Linkedin
• Platform Provider:
  • Backstage (Complex tool managed by institution)
  • Notion
  • hu3agency
  • Instagram
• Stream Consumer:
  • Hyper (Periderm for oS3) (Simple tool managed by trees so they can create internal streams (xylem/phloem)
  • Vercel
  • trainfarb
  • X (Twitter)
• [x] Add link to GitHub Sponsors

NEXT STEPS

TABLE 0.9.0 Chief Language Office 0.9.0 Mind Map Onboarding Platform Metadata ecosystem_owner: ourStory platform_focus: lp09_onboardingPlatform platform_value: self-sovereignty platform_question: What is a Platform? platform_inspiration: Git platform_expression: Instagram Guides platform_song: 174 Hz - Pain Reduction by Kev Thompson 0.9.1 Design Onboarding Platform Metadata 0.9.2 Engineer Onboarding Platform Metadata 0.9.3 Des Eng Onboarding Platform Metadata

- [ ] Next, turn it into a template

TABLE 0.9.0 Chief Language Office 0.9.0 Mind Map Onboarding Platform Metadata ecosystem_owner: [ECOSYSTEM_OWNER] platform_focus: [PLATFORM_FOCUS] platform_value: [PLATFORM_VALUE] platform_question: [PLATFORM_QUESTION] platform_inspiration: [PLATFORM_INSPIRATION] platform_expression: [PLATFORM_EXPRESSION] platform_song: [PLATFORM_SONG] 0.9.1 Design Onboarding Platform Metadata 0.9.2 Engineer Onboarding Platform Metadata 0.9.3 Des Eng Onboarding Platform Metadata