@fugood/bricks-project 2.23.0-beta.60 → 2.23.0-beta.62

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "@fugood/bricks-project",
-  "version": "2.23.0-beta.60",
+  "version": "2.23.0-beta.62",
   "main": "index.ts",
   "scripts": {
     "build": "bun scripts/build.js"
   },
   "dependencies": {
-    "@fugood/bricks-cli": "^2.23.0-beta.60",
+    "@fugood/bricks-cli": "^2.23.0-beta.61",
     "@huggingface/gguf": "^0.3.2",
     "@modelcontextprotocol/sdk": "^1.15.0",
     "@toon-format/toon": "^2.1.0",
@@ -18,5 +18,5 @@
     "lodash": "^4.17.4",
     "uuid": "^8.3.1"
   },
-  "gitHead": "99b9d959ed3ef67a04780c58c8a4d39cb0796313"
+  "gitHead": "aaa3df5305420b5250f4ba1d6500ba07b799b116"
 }

package/skills/bricks-project/SKILL.md

@@ -11,6 +11,7 @@ This skill covers advanced BRICKS features not in the main project instructions.
 
 | Rule | Description |
 |------|-------------|
+| [Architecture Patterns](rules/architecture-patterns.md) | **Read first** — decompose flows and select patterns |
 | [Animation](rules/animation.md) | Animation system for brick transforms and opacity |
 | [Standby Transition](rules/standby-transition.md) | Canvas enter/exit animations |
 | [Automations](rules/automations.md) | E2E testing and scheduled tasks |
@@ -22,6 +23,7 @@ This skill covers advanced BRICKS features not in the main project instructions.
 
 ## Quick Reference
 
+- **Complex flows**: See [Architecture Patterns](rules/architecture-patterns.md) for decomposing multi-step workflows
 - **Multi-device**: See [Local Sync](rules/local-sync.md) for LAN coordination
 - **Cloud data**: See [Remote Data Bank](rules/remote-data-bank.md) for sync and API access
 - **Media assets**: See [Media Flow](rules/media-flow.md) for centralized asset management

package/skills/bricks-project/rules/architecture-patterns.md

@@ -0,0 +1,62 @@
+# Architecture Patterns
+
+How to decompose complex flows into the right combination of BRICKS patterns.
+
+## Pattern Selection Priority
+
+Prefer higher-priority patterns; only fall to lower when they genuinely can't solve the sub-problem:
+
+| Priority | Pattern | Use For |
+|----------|---------|---------|
+| 1 | Generator + Events | I/O, AI inference, external data |
+| 2 | Event Action Chains | Orchestration, sequential steps |
+| 3 | System Actions | State changes, navigation, UI triggers |
+| 4 | Data Calculation | Pure data transformation ONLY |
+
+### Generators (Priority 1)
+For all external I/O and AI inference. Each generator emits events that naturally chain into actions.
+- **GeneratorAssistant**: multi-turn LLM conversations, function calling, built-in message history
+- **GeneratorLLM**: single-shot local inference (GGML)
+- **GeneratorHttp**: REST API calls
+- **GeneratorMqtt / GeneratorWebSocket**: real-time messaging
+
+### Event Action Chains (Priority 2)
+The primary way to orchestrate multi-step flows. A single event can contain an array of EventActions executed sequentially.
+- Use `waitAsync: true` to await async actions before the next step
+- Use `dataParams` + `mapping` to pass event data downstream
+- This is the "glue" that wires generators, state, and UI together
+
+### System Actions (Priority 3)
+Built-in commands for direct state and UI changes.
+- **PROPERTY_BANK**: set data value
+- **PROPERTY_BANK_EXPRESSION**: inline JS expression for simple compute
+- **CHANGE_CANVAS**: navigate to another canvas
+- **DYNAMIC_ANIMATION**: trigger animation
+- **ALERT / MESSAGE**: system feedback
+
+### Data Calculation (Priority 4)
+ONLY for deriving, formatting, or aggregating values from other data. Not for orchestration, side effects, or flow control.
+
+## Flow Decomposition
+
+When the user describes a complex flow, decompose it BEFORE writing code:
+
+### Step 1: Extract I/O boundaries
+Every external interaction maps to a Generator:
+- "call LLM" → GeneratorAssistant or GeneratorLLM
+- "fetch API" → GeneratorHttp
+- "speech to text" → GeneratorSpeechInference
+
+### Step 2: Extract state transitions
+Every UI change maps to a System Action in an event chain:
+- "show loading" → PROPERTY_BANK on a boolean data
+- "go to result screen" → CHANGE_CANVAS
+- "animate in" → DYNAMIC_ANIMATION
+
+### Step 3: Extract pure transformations
+Only actual data derivation maps to Data Calculation:
+- "format the response" → DataCalculationScript
+- "compute a score" → DataCalculationScript or DataCalculationMap
+
+### Step 4: Wire with Event Action Chains
+Connect the pieces through events on generators and bricks.

package/skills/bricks-project/rules/data-calculation.md

@@ -49,7 +49,7 @@ Use `manual` to prevent circular dependencies or for explicit control.
 
 ## Script Sandbox Features
 
-Scripts run in `use strict` mode. In sync mode, `fetch`, `XMLHttpRequest`, `setTimeout`, `setInterval`, `Promise` are **not available**.
+Scripts run in `use strict` mode with a sandboxed set of globals and libraries.
 
 ### Built-in Globals
 
@@ -140,9 +140,10 @@ Enable `enableAsync: true` to unlock additional capabilities:
 
 ```typescript
 code: `
-  const response = await fetch(inputs.apiUrl)
-  const data = await response.json()
-  return data.result
+  const result = await new Promise((resolve) => {
+    setTimeout(() => resolve(inputs.value * 2), 100)
+  })
+  return result
 `,
 enableAsync: true,
 ```
@@ -186,3 +187,22 @@ const triggerCalc: EventAction = {
 2. **Error handling**: Always set `error` output for scripts that might fail
 3. **Keep scripts pure**: Avoid side effects, return computed values
 4. **Debounce rapid updates**: Use `manual` mode + timer for high-frequency inputs
+
+## Anti-Patterns (AVOID)
+
+See [Architecture Patterns](architecture-patterns.md) for the full pattern selection guide.
+
+### Using Data Calc as an orchestrator
+Scripts that manage state machines, control UI flow, or coordinate multi-step processes belong in Event Action Chains, not here.
+
+**Symptom**: Script has if/else branches deciding "what happens next" or tracks "current step".
+
+### Quick reference
+
+| If you need to... | Use instead |
+|---|---|
+| Call an LLM / AI model | Generator (Assistant, LLM, HTTP) |
+| Sequence multiple actions | Event Action Chain |
+| Set a data value directly | PROPERTY_BANK system action |
+| Compute a simple expression | PROPERTY_BANK_EXPRESSION |
+| Transform/format/parse data | Data Calculation (correct use) |

package/types/system.ts

@@ -642,6 +642,11 @@ export type SystemActionThrowException = ActionWithParams & {
   >
 }
 
+/* Restart the foundation (React Native bundle) */
+export type SystemActionRestartFoundation = Action & {
+  __actionName: 'RESTART_FOUNDATION'
+}
+
 /* Dismiss keyboard */
 export type SystemActionDismissKeyboard = Action & {
   __actionName: 'DISMISS_KEYBOARD'