@powerhousedao/academy 4.1.0-dev.56 → 4.1.0-dev.58

package/CHANGELOG.md

@@ -1,3 +1,36 @@
+## 4.1.0-dev.58 (2025-09-18)
+
+### 🚀 Features
+
+- adding feature flag to switchboard for controlling reactorv2 api ([4486c8a8d](https://github.com/powerhouse-inc/powerhouse/commit/4486c8a8d))
+
+### 🩹 Fixes
+
+- test fix for document-drive package ([40f4b6416](https://github.com/powerhouse-inc/powerhouse/commit/40f4b6416))
+
+### ❤️ Thank You
+
+- Benjamin Jordan (@thegoldenmule)
+
+## 4.1.0-dev.57 (2025-09-17)
+
+### 🚀 Features
+
+- **monorepo:** empty commit to satisfy naming ([5aa18f417](https://github.com/powerhouse-inc/powerhouse/commit/5aa18f417))
+- **monorepo:** merge main ([79f6472b1](https://github.com/powerhouse-inc/powerhouse/commit/79f6472b1))
+- **monorepo:** update release branch workflow ([e9c221ab5](https://github.com/powerhouse-inc/powerhouse/commit/e9c221ab5))
+
+### 🩹 Fixes
+
+- **monorepo:** re-add nx js plugin ([d477a49d7](https://github.com/powerhouse-inc/powerhouse/commit/d477a49d7))
+- **monorepo:** regenerate lockfile ([7811171ff](https://github.com/powerhouse-inc/powerhouse/commit/7811171ff))
+- **monorepo:** linting and type checking ([#1776](https://github.com/powerhouse-inc/powerhouse/pull/1776))
+
+### ❤️ Thank You
+
+- Ryan Wolhuter @ryanwolhuter
+- ryanwolhuter @ryanwolhuter
+
 ## 4.1.0-dev.56 (2025-09-17)
 
 This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
@@ -58,29 +91,27 @@ This was a version bump only for @powerhousedao/academy to align it with other p
 - Callme-T
 - ryanwolhuter @ryanwolhuter
 
-## 4.1.0-dev.50 (2025-09-09)
+## 5.0.0-staging.9 (2025-09-09)
 
 This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
 
-## 4.1.0-dev.49 (2025-09-09)
+## 5.0.0-staging.8 (2025-09-09)
 
 This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
 
-## 4.1.0-dev.48 (2025-09-09)
+## 5.0.0-staging.7 (2025-09-09)
 
 This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
 
-## 4.1.0-dev.47 (2025-09-06)
+## 5.0.0-staging.6 (2025-09-08)
 
-### 🩹 Fixes
-
-- **docs:** added zip redundancy to release notes ([3acfe1027](https://github.com/powerhouse-inc/powerhouse/commit/3acfe1027))
+This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
 
-### ❤️ Thank You
+## 5.0.0-staging.5 (2025-09-08)
 
-- Callme-T
+This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
 
-## 4.1.0-dev.46 (2025-09-05)
+## 5.0.0-staging.4 (2025-09-08)
 
 This was a version bump only for @powerhousedao/academy to align it with other projects, there were no code changes.
 
@@ -1205,4 +1236,4 @@ This was a version bump only for @powerhousedao/academy to align it with other p
 
 ### ❤️ Thank You
 
-- Frank
+- Frank

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

@@ -42,24 +42,25 @@ ph init
     ? What is the project name? ‣ getting-started
     ```
 
-    Once the project is created, you will see the following output:
+
+Once the project is created, you will see the following output:
     ```bash
     Initialized empty Git repository in /Users/you/ph-projects/getting-started/.git/
     The installation is done!
     ```
 
-    Navigate to the newly created project directory:
+Navigate to the newly created project directory:
     ```bash
     cd getting-started
     ```
-    Once in the project directory, run the `ph connect` command to start a local instance of the Connect application. This allows you to start your document model specification document.
-    Run the following command to start the Connect application:
+Once in the project directory, run the `ph connect` command to start a local instance of the Connect application. This allows you to start your document model specification document.
+Run the following command to start the Connect application:
 
     ```bash
     ph connect
     ```
 
-    The Connect application will start and you will see the following output:
+The Connect application will start and you will see the following output:
 
     ```bash
       ➜  Local:   http://localhost:3000/
@@ -67,13 +68,11 @@ ph init
       ➜  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.
-    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.
+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.
+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.

package/docs/academy/01-GetStarted/02-DefineToDoListDocumentModel.md

@@ -113,4 +113,4 @@ Check below screenshot for the complete implementation:
 ### Up next: reducers
 
 Up next, you'll learn how to implement the runtime logic and components that will use the `ToDoList` document model specification you've just created and exported.
-````
+

package/docs/academy/01-GetStarted/05-SpecDrivenAI.md

@@ -1,23 +1,29 @@
-# Spec-Driven AI
+# Vetra Studio: Specification Driven AI 
 
-This chapter introduces you to one of the most powerfull features of the Powerhouse development framework. 
-In this *Get Started'* chapter we've been making use of strict schema definition principles to communicate the intended use case. This shared language is not only a language that bridges the gap between developer, designer and analyst but also the gap between builder and AI-agent. 
+This chapter introduces you to one of the most powerfull features of the Powerhouse development framework: Specification Driven AI-control.  In the **'Get Started'** chapter we've been making use of strict schema definition principles to communicate the intended use case of our reactive documents. 
+
+:::tip
+The **schema definition language**, is a not only a shared language that bridges the gap between developer, designer and analyst but also the gap between **builder and AI-agent**. 
+:::
 
 ## Vision
 
-At Powerhouse we are embracing the progress of AI assisted coding while unlocking the next level of AI control through specification driven AI control.
+At Powerhouse we are embracing the progress of AI assisted coding while unlocking the next level of AI control through **specification driven AI control**.
 
 - Communicate your solution and intent through a structured specification framework designed for AI collaboration.
 - Specifications enable precise, iterative edits, since all our specification documents are machine-readable and executable.
 - Specifications offer the ability to update exact parameters and properties as your specs evolve in lock-step with your agent. 
-- Specs turn fragile sandcastles into solid, editable, and maintainable functionality with predictable results, so you can deliver AI driven projects to production environments with piece of mind. 
+- Specifications turn fragile sandcastles into solid, editable, and maintainable functionality with predictable results.
 
 This approach allows for the creation of editable specifications, enabling business analysts to modify details and instruct the AI to generate code based on updated specifications.
 It results in composable, maintainable, and scalable functionality.
 
 ## Introducing Vetra Studio
 
-Vetra studio functions as the orchestration hub where you as a builder assemble all the necessary specifications for your intended use-case, software solution or package. For each of the different *modules* that together form a package a specification document can be created in *Vetra Studio*. 
+**Vetra Studio** serves as a centralized hub for developers to access and manage specifications. 
+It allows developers to open packages (Git repositories with metadata) from a Vetra package library, providing access to a remote Vetra drive where all specifications are stored. 
+
+This setup ensures that all necessary documentation and project requirements are in one accessible location, streamlining communication and agreement on requirements and operations. Additionally, **Vetra Studio** functions as the orchestration hub where you as a builder assemble all the necessary specifications for your intended use-case, software solution or package. For each of the different **modules** that together form a package a specification document can be created in **Vetra Studio**. 
 
 As Vetra Studio matures each of these specification documents will offer an interface by which you as a builder get more control over the modules that make up your package. These modules are divided in 3 categories. 
 
@@ -28,7 +34,7 @@ As Vetra Studio matures each of these specification documents will offer an inte
 - **Editor specification**: Outlines the interface and functionalities of a document model editor, allowing users to interact with and modify document data.
 - **Drive-app specification**: Specifies the UI and interactions for managing documents within a Drive, providing tailored views and functionalities.
 
-### 3 Data intagrations
+### 3. Data integrations
 - **Subgraph specification**: Details the connections and relationships within a subgraph, facilitating efficient data querying and manipulation.
 - **Codegen Processor Specification**: Describes the process for automatically generating code from document model specifications, ensuring alignment with intended architecture.
 - **RelationalDb Processor Specification**: Defines how relational databases are structured and queried, supporting efficient data management and retrieval.
@@ -60,18 +66,18 @@ In standard mode:
 
 ### 2. Launch Claude with MCP
 
-Vetra Studio integrates deeply with Claude through MCP (Model Control Protocol):
+Vetra Studio integrates deeply with Claude through MCP (Model Control Protocol). This is where AI comes into the mix and you get the chance to have greater control and direction over what your llm is coding for you. 
 
-1. Start the MCP reactor:
+#### 1. Start the MCP reactor:
 ```bash
 ph mcp
 ```
 
-2. Verify MCP connection:
+#### 2. Verify MCP connection:
 - Check that the reactor MCP is available
 - Confirm Vetra Studio shows "Connected to reactor MCP"
 
-Key MCP Features:
+#### Key MCP Features:
 - Automatic document model creation from natural language descriptions
 - Smart editor generation based on document models
 - Uses reactor recipes for consistent code generation
@@ -79,11 +85,12 @@ Key MCP Features:
 
 The powerhouse config includes a vetra URL for consistent project configuration across different environments.
 
-### Integration with Custom Drives:
+:::tip
 - Vetra supports integration with custom remote drives, allowing users to create and manage documents within these drives.
 - The MCP server enables the agent to work with both existing and newly created document models.
+:::
 
-### 3. Document Creation Workflow
+### 3. Vetra Studio Package Creation Workflow
 
 #### A. Set Package Description (Required)
 1. Provide a name for your package
@@ -105,7 +112,7 @@ You can create document models in two ways:
    - Define document schema with fields and types
    - Create necessary operations
    - Add required modules
-   - Reference the document modeling material for detailed guidance
+   - The document model creation chapter in the Mastery track provides support [here](apps/academy/docs/academy/MasteryTrack/DocumentModelCreation/SpecifyTheStateSchema)
 
 #### C. Add Document Editor (Required)
 1. **Using MCP (AI-Assisted)**
@@ -129,15 +136,15 @@ Support for:
 
 ### Best Practices
 
-1. **Working with MCP**
-   - Provide clear, specific instructions
-   - Review generated schemas before confirmation
-   - Verify implementation details in generated code
+1. **Working with MCP and claude**
+   - Provide clear, specific instructions and ask for clarifying questions to be answered before code generation.
+   - Review generated schemas before confirmation and work in layers instead of 'one-shotting' your code. 
+   - Verify implementation details in generated code before continuing. 
 
 2. **General Tips**
    - Use interactive mode during development
    - Review changes before confirmation
    - Double-check proposed next actions
-   - Ask clarifying questions when needed
+   - Ask clarifying questions and double check if the task is understood correctly when needed.
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@powerhousedao/academy",
-  "version": "4.1.0-dev.56",
+  "version": "4.1.0-dev.58",
   "homepage": "https://powerhouse.academy",
   "repository": {
     "type": "git",

package/tsconfig.tsbuildinfo

@@ -0,0 +1 @@
+{"root":["./babel.config.js","./docusaurus.config.ts","./sidebars.ts","./scripts/generate-combined-cli-docs.ts","./src/components/HomepageFeatures/index.tsx","./src/pages/_archive-homepage.tsx","./src/theme/DocCardList/index.tsx"],"version":"5.9.2"}