@powerhousedao/academy 5.1.0-dev.9 → 5.1.0

package/blog/BeyondCommunication-ABlueprintForDevelopment.md

@@ -1,8 +1,7 @@
 ---
 title: Beyond Communication - A Blueprint for Development
-description: GraphQL Schema's as a common language for software design
+description: GraphQL Schema’s as a common language for software design
 slug: Graphql-schema-as-a-common-language
-date: 2024-12-02
 authors:
   - name: Call me T.
     title: Product Manager at Powerhouse

package/blog/TheChallengeOfChange.md

@@ -2,7 +2,6 @@
 title: The Challenge of Change
 description: Rapid Application Development with document models.
 slug: Rapid-Application-Development-with-document-models.
-date: 2024-12-02
 authors:
   - name: Call me T.
     title: Product Manager at Powerhouse

package/docs/academy/00-EthereumArgentinaHackathon.md

@@ -0,0 +1,207 @@
+---
+id: EthereumArgentinaHackathon
+title: Ethereum Argentina Hackathon
+---
+
+# Ethereum Argentina Hackathon
+
+**November 19-20, 2024**
+
+Welcome to the Vetra hacker page for the Ethereum Argentina Hackathon! We're excited to support developers building with Powerhouse during this event.
+
+## Overview
+
+Join us for two days of intensive development support as you build decentralized applications using the Vetra framework. Our team will be available online and at the mentor's table to help you navigate the builder platform, answer questions, and guide you through best practices.
+
+## 📅 Event Details
+
+- **Dates**: November 19-20, 2024
+- **Format**: Online & IRL Developer Support
+- **Time Zone**: Argentina Time (ART)
+- **Support Hours at Mentor Table @ la Rural**: Please get in touch [on Discord to schedule](https://discord.gg/pwQJwgaQKd)
+- **Hackathon informations**: [Taiki Hackathon](https://taikai.network/ethargentina/hackathons/tierra-de-buidlers-2025/overview)
+
+## 🚀 Getting Started
+
+<details>
+<summary> Vetra Introduction & Follow Along Demo </summary>
+
+Please Rewatch our Hackathon introduction & follow along tutorial. 
+
+<iframe width="560" height="315" src="https://www.youtube.com/embed/R5MAaGaopJg" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>
+
+Find a complete overview of how to use the Vetra Studio for you project [here](./01-GetStarted/05-VetraStudio.md)
+
+**Quick Start Summary**
+
+- Step 1: Install the powerhouse-CLI: `pnpm install -g ph-cmd`
+- Step 2: Initialize a project & directory `ph init my-project-name`
+- Step 3: CD into you project directory
+- Step 4: Launch Vetra Studio with the `ph vetra`command
+- Step 5: Add the necessary document models & editors for your intended solution in Vetra Studio
+- Step 6: If you're well versed in schema creation or graphql. Just talk with an agent about your imagined solution.
+- Step 7: Start your preferred agent to help you with the initial scaffolding of your schema, operations and reducers. 
+- Step 8: Test your implementation in the "Vetra Preview Drive" with the `ph vetra --watch`command. 
+- Step 9: Run pnpm build and push your project to a remote repository. Follow the package publishing [Tutorial](./02-MasteryTrack/05-Launch/02-PublishYourProject.md)
+
+**Basic tips** 
+- 1️⃣ Write a detailed description of your intented functionality inside the document model specification manifest
+- 2️⃣ Ask your agent to ask for clarifying questions before starting any ideation process. 
+- 3️⃣ For each document model you'll want to create an accompanying editor in vetra studio. 
+- 4️⃣ An 'App' specifcation is an drive that can act as an app because of the specific interface you create for it. 
+
+### Before the Hackathon
+
+1. **Set Up Your Environment**
+   - Install the Powerhouse CLI
+   - Set up your development environment
+   - Review the [Get Started Guide](./01-GetStarted/home.mdx)
+
+2. **Explore the Platform**
+   - Check out the [Demo Package](./01-GetStarted/00-ExploreDemoPackage.mdx)
+   - Familiarize yourself with [Document Models](./02-MasteryTrack/02-DocumentModelCreation/01-WhatIsADocumentModel.md)
+
+3. **Join Our Community**
+   - Discord: [Join our server](#)
+
+
+</details>
+
+:::tip Use your preferred AI agent
+Vetra studio is compatible with Cursor, Claude and Gemini. Find the dedicated markdown files to guide your agent with the correct instruction in your directory. Your agent should also have access to the MCP's available. 
+::: 
+
+
+## **Hackathon Project Ideas**
+
+Powerhouse is perfect for building:
+
+- **Real World Use-cases**: Every document can act as a mini ledger/blockchain. 
+- **Decentralized Applications**: Create apps with built-in version control and collaboration.
+- **Document-Based Systems**: Build structured data applications.
+- **Collaborative Tools**: Enable real-time multi-user editing.
+- **Data Management Platforms**: Create systems with queryable, structured data.
+
+### Coordination & DAO Design
+
+- 🧩 **What if** DAOs weren't chaotic? What documents would you need to make them coordinate like space X and ship like stripe?
+- 🎯 **What if** making decisions as a group felt like playing a co-op strategy game. With a clearly aligned vision, instant dashboards and a way to capture hard won knowledge in expertise into custom software for the Dao?
+
+:::tip IDEA
+The ultimate DAO Template toolkit where vision & mission documents influence guidelines & onboarding for contributors.
+:::
+
+---
+
+### GovTech & Public Infrastructure
+
+- 🗳 **What if** local governments had to reach consensus with residents before making a decision? How would that look like?
+- 🚧 **What if** you could submit pothole fixes or transit complaints into a civic DAO, and track the response like GitHub issues?
+- 🧾 **What if** municipal budgets were editable public documents with community feedback loops?
+
+:::tip IDEA
+An Open Source Enterprise Resource Planning-suite for municipalities & governments
+:::
+
+---
+
+### Education & Group Work
+
+- 📝 **What if** your group project auto-divided work, tracked contributions, and paid out in real-time?
+- 👾 **What if** "homework" was a multiplayer quest, and grades came from the DAO?
+- 🏫 **What if** we DAO-ified a classroom and let the students vote on rules, roles, and rewards?
+
+:::tip IDEA
+The remote classroom SAAS back-end that fosters connection, gives purpose to bullies and empowers younger generation to dream big again.
+:::
+
+---
+
+### 💸 Grants, Crypto, and Incentive Design
+
+- 💰 **What if** grant tooling felt like bounty hunting across a galaxy of projects?
+- 📊 **What if** every grant had a live budget dashboard, contributor feed, and impact score?
+- 🎮 **What if** you could stake on coordination itself, betting that people will work together well?
+
+:::tip IDEA
+The future of grant platforms that dares to imagine grants in new ways. With follow up, tracking and impact visualisations of teams, time, risk & resources invested.
+:::
+
+---
+
+### 💸 Lawmaking, Legislation & Legal
+
+- 🧑‍⚖️ **What if** any government or DAO could fork a legal template, customize it, and track changes in a public, composable way?
+- 🎨 **What if** legislation could be transparently co-created by citizens, NGOs, and governments all with aligned incentives?
+- 💻 **What if** legislation, contracts & templates could exist on an open-source market place like software?
+- 🤖 **What if** a network agent could create a legal vehicle by simply inputing  set of requirements and risk preferences (in non legalese)?
+- 🤝 **What if** 2 agents in a network could negotiate terms of an agreement according to predefined functions and risk parameters, without lawyers?
+
+:::tip IDEA
+Build a Decentralized Lawmaking Engine using Reactive Document Models
+:::
+
+
+## 🛠️ Resources
+
+### Documentation
+
+- [Quick Start Guide](./01-GetStarted/home.mdx)
+- [Create a New Project](./01-GetStarted/01-CreateNewPowerhouseProject.md)
+- [Define Document Models](./01-GetStarted/02-DefineToDoListDocumentModel.md)
+- [Build Editors](./01-GetStarted/04-BuildToDoListEditor.md)
+- [API References](./04-APIReferences/00-PowerhouseCLI.md)
+
+### Tutorials
+
+- [To-Do List Example](./01-GetStarted/02-DefineToDoListDocumentModel.md)
+- [Chatroom Use Case](./03-ExampleUsecases/Chatroom/02-CreateNewPowerhouseProject.md)
+
+## 🏆 Judging Criteria
+
+Projects will be evaluated based on:
+
+- **Usefulness & Impact**: How well does it solve a certain job or problem?
+- **Composability/Structure**: How are the different document models and / or drive apps collaborating?
+- **Clarity of the developer or user experience**: Did you unlock the secret sauce of UX & reactive documents?
+- **Alignment with Vetra/Powerhouse principles**: Local-first, auditable, usefull for common good. 
+
+## 📋 Submission Guidelines
+
+### What to Submit
+
+- GitHub repository with your code
+- (Video) presentation (2-3 minutes)
+- README with:
+  - Project description
+  - Setup instructions
+  - Screenshots/demos
+  - Technologies used
+
+The Powerhouse team will add you as a builder on the Vetra platform and host your application and drive. 
+
+
+## Tips for Success
+
+### Development Tips
+
+1. **Start Simple**: Begin with a basic implementation and iterate
+2. **Use Templates**: Leverage existing examples and templates
+3. **Ask Questions**: Don't hesitate to reach out for help
+4. **Test Early**: Test your application frequently during development
+5. **Document**: Keep notes on your decisions and implementations
+
+### Presentation Tips
+
+1. **Show, Don't Tell**: Live demos are more impactful than slides
+2. **Tell a Story**: Explain the problem you're solving
+3. **Highlight Innovation**: Show what makes your solution unique
+4. **Be Concise**: Respect the time limits for presentations
+5. **Prepare Backup**: Have screenshots/video in case of technical issues
+
+---
+
+**Good luck, and happy hacking! 🚀**
+
+*Last updated: November 17, 2025*
+

package/docs/academy/01-GetStarted/00-ExploreDemoPackage.mdx

@@ -2,13 +2,13 @@
 
 ## Let's get started
 
-To give you a quick idea of how the Powerhouse Vetra builder platform operates on document models and packages, why don't you try installing a package?
+To give you a quick idea of how the Powerhouse ecosystem operates on document models and packages, why don't you try installing a package?
 We will show you how to install the Powerhouse command-line tool `ph-cmd` and then use it to install a pre-built demo package containing a document model, an editor, and a drive app.
 
 ## Step 1: Install the Powerhouse CLI
 
-You will use the Powerhouse CLI to launch a local environment with a "To-do List Demo Package" installed.
-This is also the package that you'll recreate during the tutorials and gets you familiar with Powerhouse Vetra.
+You will use the Powerhouse CLI to launch a local environment with a "To-do List Demo Package".
+This is also the package that you'll recreate during the tutorials and gets you familiar with Powerhouse.
 
 ```bash
 pnpm install -g ph-cmd
@@ -20,21 +20,16 @@ Verify the installation:
 ph --version
 ```
 
-## Step 2: Initialize a new project 
+## Step 2: Install the to-do list demo package
 
-Now use the `ph init` command to initialize a new project and install a Powerhouse package inside the project. 
-You'll be asked to name your project. Afterwards, move inside your project with `cd project-name`
-
-## Step 3: Install the to-do list demo package
-
-Now, use the `ph install` command to install the demo package inside the project. 
+Now, use the `ph` command to install the demo package into a global project.
 
 ```bash
 # Install the package
-ph install @powerhousedao/todo-demo
+ph install @powerhousedao/todo-demo-package
 ```
 
-This command downloads and sets up the `@powerhousedao/todo-demo`, making its features available in your Powerhouse project.
+This command downloads and sets up the `@powerhousedao/todo-demo-package`, making its features available in your Powerhouse environment.
 
 <details>
 <summary>Expected CLI result</summary>
@@ -78,9 +73,9 @@ This command downloads and sets up the `@powerhousedao/todo-demo`, making its fe
 
 </details>
 
-You have now successfully installed `ph-cmd`, initalized a product project and added your first package!
+You have now successfully installed `ph-cmd` and added your first package!
 
-## Step 4: Run the connect app in studio mode
+## Step 3: Run the connect app in studio mode
 
 To run the package locally in Connect Studio (our collaboration and contributor app), run:
 
@@ -96,7 +91,7 @@ Click the returned localhost URL and you should see Connect Studio appear in you
 </figure>
 
 When you click the settings wheel in the bottom right corner, you'll get access to the **Package Manager**.
-Here, you'll see that you've installed the `@powerhousedao/todo-demo`, which contains not only a **Document Model** and its accompanying editor but also a **Drive App** specific to the to-do document model.
+Here, you'll see that you've installed the `@powerhousedao/todo-demo-package`, which contains not only a **Document Model** and its accompanying editor but also a **Drive App** specific to the to-do document model.
 
 <figure className="image-container">
   <img
@@ -108,13 +103,13 @@ Here, you'll see that you've installed the `@powerhousedao/todo-demo`, which con
   </figcaption>
 </figure>
 
-## Step 5: Create a todo list document
+## Step 4: Create a todo list document
 
 :::tip What is a 'drive' at Powerhouse?
 A **drive** is a folder to store and organize your documents in. Powerhouse offers the ability to build customized 'Drive Apps' for your documents. Think of a Drive App as a specialized lens—it offers **different ways to visualize, organize, and interact with** the data stored within a drive, making it more intuitive and efficient for specific use cases. To learn more, visit [Building A Drive App](/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer)
 :::
 
-### 5.1 Create a local todolist app drive
+### 4.1 Create a local todolist app drive
 
 First, let's create a dedicated drive for your to-do lists:
 
@@ -122,14 +117,14 @@ First, let's create a dedicated drive for your to-do lists:
 - In the **Drive App** field, select 'To-do Drive App'
 - This creates a specialized drive that's optimized for to-do list documents
 
-### 5.2 Create a todolist document
+### 4.2 Create a todolist document
 
 Now move into the drive you've just created:
 
 - Click the button at the bottom of the page to create a new to-do list document
 - This opens the to-do list editor where you can start managing your tasks
 
-### 5.3 Add a few todos and inspect the document history
+### 4.3 Add a few todos and inspect the document history
 
 - Add a few to-dos that are on your mind
 - You'll see a statistics widget that counts the open to-dos
@@ -139,6 +134,14 @@ This is an example of the **usefulness and impact of Drive Apps**.
 They offer a customized interface that works well with the different documents inside your drive.    
 Read more about drive apps in the Mastery Track: [Drive Apps and Drive Explorers](/academy/MasteryTrack/BuildingUserExperiences/BuildingADriveExplorer).
 
+<figure className="image-container">
+  <img
+    src={require("./images/TodoDriveApp.png").default}
+    alt="Todo Drive App"
+  />
+  <figcaption>A list of todos in the custom todo drive app.</figcaption>
+</figure>
+
 A key feature of Connect is the **Operations History**. Every change to a document is stored as an individual operation, creating an immutable and replayable history. This provides complete auditability and transparency, as you can inspect each revision, its details, and any associated signatures. For example, you can see a chronological list of all modifications, along with who made them and when.
 
 <figure className="image-container">
@@ -164,7 +167,7 @@ You can find the button to visit the operations history in the document model to
 
 Learn more about the [Operations History](../MasteryTrack/BuildingUserExperiences/DocumentTools/OperationHistory) and other document tools you get for free.
 
-## Step 6: Enable operation signing and verification through Renown
+## Step 5: Enable operation signing and verification through Renown
 
 Renown is Powerhouse's **decentralized identity and reputation system** designed to address the challenge of trust within open organizations, where contributors often operate under pseudonyms. In traditional organizations, personal identity and reputation are key to establishing trust and accountability. Renown replicates this dynamic in the digital space, allowing contributors to earn experience and build reputation without revealing their real-world identities.
 
@@ -172,7 +175,7 @@ Renown is Powerhouse's **decentralized identity and reputation system** designed
 When signing in with Renown, use an Ethereum or blockchain address that can function as your 'identity', as this address will accrue more experience and history over time.
 :::
 
-### 6.1 Click the renown icon and connect your Ethereum identity
+### 5.1 Click the renown icon and connect your Ethereum identity
 
 "**Log in with Renown**" is a decentralized authentication flow that enables you to log into applications by signing a credential with your Ethereum wallet. Upon signing in, a Decentralized Identifier (DID) is created based on your Ethereum key.
 
@@ -183,7 +186,7 @@ When signing in with Renown, use an Ethereum or blockchain address that can func
   </figcaption>
 </figure>
 
-### 6.2 Authorize Connect to sign document edits on your behalf
+### 5.2 Authorize Connect to sign document edits on your behalf
 
 This DID is then associated with a credential that authorizes a specific Connect instance to act on your behalf. That credential is stored securely on Ceramic, a decentralized data network. When you perform actions through the Powerhouse Connect interface, those operations are signed with the DID and transmitted to Switchboard, which serves as the verifier.
 
@@ -205,7 +208,7 @@ This DID is then associated with a credential that authorizes a specific Connect
   <figcaption>Confirmation of a successful login with Renown.</figcaption>
 </figure>
 
-### 6.3 Verify the signatures of new operations in the todo list
+### 5.3 Verify the signatures of new operations in the todo list
 
 By leveraging this system, every operation or modification made to a document is cryptographically signed by the contributor's Renown identity. This ensures that each change is verifiable, traceable, and attributable to a specific pseudonymous user, providing a robust audit trail for all document activity.
 
@@ -221,7 +224,7 @@ Now, return to your to-do list and make some additional changes. You'll notice t
   </figcaption>
 </figure>
 
-## Step 7: Export a document
+## Step 6: Export a document
 
 Export the document as a `.phd` (Powerhouse Document) file using the export button in the document toolbar at the top. In this toolbar, you will find all available functionality for your documents. The `.phd` file can be sent through any of your preferred channels to other users on your network.
 

package/docs/academy/01-GetStarted/01-CreateNewPowerhouseProject.md

@@ -1,100 +1,12 @@
 # Create a new to-do list document
 
-:::tip Tutorial Repository
-📦 **Reference Code**: [step-1-initialize-with-ph-init](https://github.com/powerhouse-inc/todo-tutorial/tree/step-1-initialize-with-ph-init)
-
-This tutorial step has a corresponding branch in the repository. You can:
-- View the complete code for this step
-- Clone and checkout the branch to see the result
-- Compare your implementation using `git diff`
-:::
-
-<details>
-<summary>📖 How to use this tutorial</summary>
-
-This tutorial is designed for you to **build your own project from scratch** while having access to reference code at each step.
-
-### Setup: Create your project and connect to tutorial repo
-
-1. **Create your project** following the tutorial:
-   ```bash
-   mkdir ph-projects
-   cd ph-projects
-   ph init
-   # When prompted, enter project name: todo-tutorial
-   cd todo-tutorial
-   ```
-
-2. **Add the tutorial repository as a remote** to access reference branches:
-   ```bash
-   git remote add tutorial https://github.com/powerhouse-inc/todo-tutorial.git
-   git fetch tutorial --prune
-   ```
-
-3. **Create your own branch** to keep your work organized:
-   ```bash
-   git checkout -b my-todo-project
-   ```
-
-Now you have access to all tutorial step branches while working on your own code!
-
-### Compare your work with reference steps
-
-At any point, compare what you've built with a tutorial step:
-
-```bash
-# Compare your current work with step-1
-git diff tutorial/step-1-initialize-with-ph-init
-
-# See what changed between tutorial steps
-git diff tutorial/step-1-initialize-with-ph-init..tutorial/step-2-generate-todo-list-document-model
-
-# Compare specific files
-git diff tutorial/step-1-initialize-with-ph-init -- package.json
-```
-
-### Visual diff with GitHub Desktop
-
-For a more visual comparison, use GitHub Desktop:
-
-1. **First, make your initial commit** (GitHub Desktop won't show your branch until you have at least one commit):
-   ```bash
-   git add .
-   git commit -m "Initial project setup"
-   ```
-
-2. **Open GitHub Desktop** and open your repository
-
-3. **Compare branches visually**:
-   - Click on **Branch** menu in the top menu bar
-   - Select **"Compare to Branch..."**
-   - Choose the tutorial branch you want to compare with (e.g., `tutorial/step-1-initialize-with-ph-init`)
-   - GitHub Desktop will show you all file differences in a visual interface
-
-4. **Review the differences**:
-   - Click on any file to see side-by-side or unified diff view
-   - See exactly what's different between your code and the reference
-
-**Tip**: You can also use VS Code's Git Graph extension or the command palette → "Git: Compare with Branch"
-
-### If you get stuck
-
-Reset your code to match a tutorial step:
-
-```bash
-# Reset to step-2 (WARNING: loses your changes)
-git reset --hard tutorial/step-2-generate-todo-list-document-model
-```
-
-</details>
-
 ## Overview
 
 This tutorial guides you through creating a simplified version of a 'Powerhouse project' for a **To-do List**.  
 A Powerhouse project primarily consists of a document model and its editor. 
 As your projects use-case expands you can add data-integrations or a specific drive-app as seen in the demo package. 
 
-For todays purpose, you'll be using Connect, our user-centric collaboration tool and Vetra Studio, the builder tooling through which developers can access and manage specifications of your project. 
+For todays purpose, you'll be using Connect, our user-centric collaboration tool and Vetra Studio, the builder tooling through which developers can access and manage specifications of their project. 
 
 ## Prerequisites
 
@@ -129,19 +41,19 @@ ph init
    ````bash
     you@yourmachine:~/ph-projects % ph init
 
-    ? What is the project name? ‣ todo-tutorial
+    ? What is the project name? ‣ getting-started
     ```
 
 
 Once the project is created, you will see the following output:
     ```bash
-    Initialized empty Git repository in /Users/you/ph-projects/todo-tutorial/.git/
+    Initialized empty Git repository in /Users/you/ph-projects/getting-started/.git/
     The installation is done!
     ```
 
 Navigate to the newly created project directory:
     ```bash
-    cd todo-tutorial
+    cd getting-started
     ```
 
 ## Develop a single document model in Connect
@@ -161,41 +73,20 @@ The Connect application will start and you will see the following output:
       ➜  press h + enter to show help
     ```
 
-A new browser window will open and you will see the Connect application. If it doesn't open automatically, you can open it manually by navigating to `http://localhost:3000/` in your browser. You will see your local drive and a button to create a new drive.
+A new browser window will open and you will see the Connect application. If it doesn't open automatically, you can open it manually by navigating to `http://localhost:3000/` in your browser.
 
-:::tip 
+You will see your local drive and a button to create a new drive.
 If you local drive is not present navigate into Settings in the bottom left corner. Settings > Danger Zone > Clear Storage.
 Clear the storage of your localhost application as it might has an old session cached.
-:::
 
 4. Move into your local drive.  
-   Create a new document model by clicking the `DocumentModel` button, found in the 'New Document' section at the bottom of the page. Name your document `TodoList` (PascalCase, no spaces or hyphens).
-
-If you've followed the steps correctly, you'll have an empty `TodoList` document where you can define the **'Document Specifications'**.
-
-## Verify your setup
+   Create a new document model by clicking the `DocumentModel` button, found in the 'New Document' section at the bottom of the page.
 
-At this point, your project structure should match the `step-1-initialize-with-ph-init` branch. You should have:
+If you've followed the steps correctly, you'll have an empty document where you can define the **'Document Specifications'**.
 
-- Empty `document-models/`, `editors/`, `processors/`, and `subgraphs/` directories
-- Configuration files: `powerhouse.config.json`, `powerhouse.manifest.json`
-- Package management files: `package.json`, `pnpm-lock.yaml`
-- Build configuration: `tsconfig.json`, `vite.config.ts`, `vitest.config.ts`
+## Develop a package in Vetra Studio
 
-### Compare with reference implementation
 
-Verify your initial setup matches the tutorial:
-
-```bash
-# Compare your project structure with step-1
-git diff tutorial/step-1-initialize-with-ph-init
-
-# List files in the tutorial's step-1
-git ls-tree -r --name-only tutorial/step-1-initialize-with-ph-init
-
-# View a specific config file from step-1
-git show tutorial/step-1-initialize-with-ph-init:package.json
-```
 
 ## Up next