@indra.ai/deva 1.63.0 → 1.63.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/package.json +1 -1
- package/vibe.md +0 -6
package/README.md
CHANGED
|
@@ -83,7 +83,7 @@ Run it with `node examples/hello-world.js` and it prints `hello world`.
|
|
|
83
83
|
|
|
84
84
|
Three things to know from this example:
|
|
85
85
|
|
|
86
|
-
- **Do your work from `onReady`, not after `await init()`.** The `init()` promise currently resolves with
|
|
86
|
+
- **Do your work from `onReady`, not after `await init()`.** The `init()` promise currently resolves with client data as soon as the client step finishes, before `start`, `enter`, `done` and `ready` have run. `onReady` is the reliable point where the Deva is fully up.
|
|
87
87
|
- **`info`, `config: {hash: {}}` and `vars.context` are effectively required.** Without them `ready()` or `context()` throws. The error handler then calls `context()` again, and the process ends in a stack overflow.
|
|
88
88
|
- **Methods must return a Promise.** `answer()` calls `this.methods[method](packet).then(...)`.
|
|
89
89
|
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"id": "31711622713594414221",
|
|
3
3
|
"name": "@indra.ai/deva",
|
|
4
|
-
"version": "1.63.
|
|
4
|
+
"version": "1.63.2",
|
|
5
5
|
"description": "Deva Core a Vedic-inspired Event Based Context Aware Feature, Zone, Action, and State Machine integrated Artificial Intelligence Framework",
|
|
6
6
|
"main": "index.js",
|
|
7
7
|
"license": "VLA:31711622713594414221 LICENSE.md",
|
package/vibe.md
CHANGED
|
@@ -129,8 +129,6 @@ After `init`, the Deva walks through named steps. Each step does the same things
|
|
|
129
129
|
|
|
130
130
|
`ready` also seals your `vars`, `utils`, `listeners`, `modules`, `func` and `methods` into `config.hash[agent.key]` (a snapshot of how the office was set up) and starts each child Deva.
|
|
131
131
|
|
|
132
|
-
**`onReady` is the moment the office is open.** Do your work from there, or after hearing `devacore:ready`. Don't do it right after `await init()`. The section on limits explains why.
|
|
133
|
-
|
|
134
132
|
## Talking on the intercom: messaging
|
|
135
133
|
|
|
136
134
|
### Asking a specialist a question
|
|
@@ -278,7 +276,6 @@ stopped: shutdown | after: ⭕️ OFFLINE
|
|
|
278
276
|
|
|
279
277
|
Why it's "safe":
|
|
280
278
|
|
|
281
|
-
- the work happens inside `onReady`, not after `await init()`;
|
|
282
279
|
- every method returns a Promise;
|
|
283
280
|
- `info`, `config: {hash: {}}` and `vars: {context: {}}` are all present;
|
|
284
281
|
- there's a `devacore:error` listener, so errors are visible;
|
|
@@ -311,8 +308,6 @@ Why it's "safe":
|
|
|
311
308
|
|
|
312
309
|
### Current limits (true at version 1.62.92)
|
|
313
310
|
|
|
314
|
-
- **`init()` resolves too early. A fix is planned for 1.63.** Right now the `init()` promise resolves with `undefined` as soon as the client step finishes, before `start`, `enter`, `done` and `ready` have run. In our recipe, `init resolved with: undefined` printed before `onReady` had done any work. Until the fix ships, wait for `onReady` or `devacore:ready`, and don't trust the `init` promise as a "ready" signal.
|
|
315
|
-
- **Errors during the client feature chain don't stop start-up.** Because of the same early resolve, if the client object is missing feature settings, each feature step announces a `devacore:error` (in our test: `Cannot read properties of undefined (reading 'license')`, and the same for the others), but `init` has already resolved and the Deva still reaches `onReady`. Listen for `devacore:error` so you notice.
|
|
316
311
|
- **Unknown names are silent.** A name that isn't in `_data` (or your agent's additions) makes `feature`, `zone`, `action`, `state`, `intent` and `belief` do nothing at all. That keeps the vocabulary strict, but a typo, or a name removed from `_data` in a later version, can quietly drop logbook lines. Check the lists after upgrading.
|
|
317
312
|
- **`npm test` has no assertions yet.** It runs a Deva through its lifecycle and passes as long as nothing throws. Assertion tests are planned. Until then, "tests pass" means "it didn't crash," not "it did the right thing."
|
|
318
313
|
- **The license-failure prompt isn't heard.** `init` calls `prompt()` with the license failure message, but the Deva isn't active yet, so no `devacore:prompt` is announced (we counted zero). Check the value `init` resolves with instead.
|
|
@@ -332,7 +327,6 @@ Ask these yourself, or paste them to your AI assistant:
|
|
|
332
327
|
|
|
333
328
|
- [ ] Have I read `LICENSE.md`, and is my use allowed under it (location, commercial use, modification)?
|
|
334
329
|
- [ ] Does my client object carry the VLA that matches the Core's `package.json`, and an entry for every client feature?
|
|
335
|
-
- [ ] Is all my real work inside `onReady` (or after `devacore:ready`), not after `await init()`?
|
|
336
330
|
- [ ] Does every method return a Promise, and does every hook call the next step or `resolve`?
|
|
337
331
|
- [ ] Is every feature, zone, action, state, intent and belief name I use actually on its list?
|
|
338
332
|
- [ ] Do I have a `devacore:error` listener, and does my `onError` (if any) call `reject`?
|