@indra.ai/deva 1.64.11 → 1.64.23
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/.github/workflows/test.yml +28 -0
- package/README.md +1 -1
- package/_includes/header.html +2 -1
- package/about.md +2 -0
- package/core/index.md +1 -1
- package/index.md +1 -1
- package/package.json +1 -1
- package/test.md +2 -10
- package/vibe.md +1 -1
- package/vla.md +76 -0
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
# Deva Core Tests
|
|
2
|
+
# Copyright ©2000-2026 Quinn Michaels; All rights reserved.
|
|
3
|
+
# Owner Signature Required For Lawful Use.
|
|
4
|
+
# Distributed under VLA:31711622713594414221 LICENSE.md
|
|
5
|
+
name: Tests
|
|
6
|
+
|
|
7
|
+
on:
|
|
8
|
+
push:
|
|
9
|
+
branches: [main]
|
|
10
|
+
pull_request:
|
|
11
|
+
branches: [main]
|
|
12
|
+
workflow_dispatch:
|
|
13
|
+
|
|
14
|
+
permissions:
|
|
15
|
+
contents: read
|
|
16
|
+
|
|
17
|
+
jobs:
|
|
18
|
+
test:
|
|
19
|
+
runs-on: ubuntu-latest
|
|
20
|
+
strategy:
|
|
21
|
+
matrix:
|
|
22
|
+
node: [22, 24]
|
|
23
|
+
steps:
|
|
24
|
+
- uses: actions/checkout@v4
|
|
25
|
+
- uses: actions/setup-node@v4
|
|
26
|
+
with:
|
|
27
|
+
node-version: ${{ matrix.node }}
|
|
28
|
+
- run: npm test
|
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Deva
|
|
2
2
|
|
|
3
|
-
[](https://www.npmjs.com/package/@indra.ai/deva)
|
|
3
|
+
[](https://www.npmjs.com/package/@indra.ai/deva) [](https://github.com/indraai/deva/actions/workflows/test.yml)
|
|
4
4
|
|
|
5
5
|
**`@indra.ai/deva`**
|
|
6
6
|
|
package/_includes/header.html
CHANGED
|
@@ -12,10 +12,11 @@
|
|
|
12
12
|
</label>
|
|
13
13
|
|
|
14
14
|
<div class="trigger">
|
|
15
|
-
<a class="page-link" href="/vibe/">Vibe</a>
|
|
16
15
|
<a class="page-link" href="/core/">Core</a>
|
|
17
16
|
<a class="page-link" href="/docs/">Docs</a>
|
|
18
17
|
<a class="page-link" href="/tests/">Tests</a>
|
|
18
|
+
<a class="page-link" href="/vibe/">Vibe</a>
|
|
19
|
+
<a class="page-link" href="/vla/">VLA</a>
|
|
19
20
|
<a class="page-link" href="/about/">About</a>
|
|
20
21
|
</nav></div>
|
|
21
22
|
</header>
|
package/about.md
CHANGED
|
@@ -6,6 +6,8 @@ description: What Deva Core is, what it does, where it fits, and what a company
|
|
|
6
6
|
image: /assets/banner.png
|
|
7
7
|
---
|
|
8
8
|
|
|
9
|
+
[](https://www.npmjs.com/package/@indra.ai/deva) [](https://github.com/indraai/deva/actions/workflows/test.yml)
|
|
10
|
+
|
|
9
11
|
Deva Core is a small, dependency-free Node.js framework for building software agents ("Devas") that work as a team on a shared event bus, describe everything they do in plain named steps, and stamp every packet of data they produce so it can be verified later.
|
|
10
12
|
|
|
11
13
|
It is written and maintained by Quinn Michaels, and it has been in development for more than ten years. It is the base that the other Deva modules build on.
|
package/core/index.md
CHANGED
|
@@ -6,7 +6,7 @@ image: /assets/banner.png
|
|
|
6
6
|
permalink: /core/
|
|
7
7
|
---
|
|
8
8
|
|
|
9
|
-
[](https://www.npmjs.com/package/@indra.ai/deva)
|
|
9
|
+
[](https://www.npmjs.com/package/@indra.ai/deva) [](https://github.com/indraai/deva/actions/workflows/test.yml)
|
|
10
10
|
|
|
11
11
|
**{{page.description}}**
|
|
12
12
|
|
package/index.md
CHANGED
|
@@ -11,7 +11,7 @@ image: /assets/banner.png
|
|
|
11
11
|
|
|
12
12
|
**{{ page.description}}**
|
|
13
13
|
|
|
14
|
-
[](https://www.npmjs.com/package/@indra.ai/deva)
|
|
14
|
+
[](https://www.npmjs.com/package/@indra.ai/deva) [](https://github.com/indraai/deva/actions/workflows/test.yml)
|
|
15
15
|
|
|
16
16
|
Deva Core is the base of every Deva. Each agent is one `Deva` class instance on a shared event bus. As it works, it moves through named features, zones, actions, states, intents, beliefs and contexts, and it announces every step as an event. Every data packet it builds is stamped with cumulative md5, sha256 and sha512 hashes, so you can verify what happened and in what order.
|
|
17
17
|
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"id": "31711622713594414221",
|
|
3
3
|
"name": "@indra.ai/deva",
|
|
4
|
-
"version": "1.64.
|
|
4
|
+
"version": "1.64.23",
|
|
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/test.md
CHANGED
|
@@ -1,6 +1,3 @@
|
|
|
1
|
-
Here's `tests.md`. It uses the same front matter as `about.md` and the core pages, and it builds everything from `site.data.tests.DATA`, the same way `core/actions.md` loops over its data. The page also adds up the suite counts itself, so the total of 69 isn't written into the page by hand. It's saved at `/workspace/drafts/tests.md`:
|
|
2
|
-
|
|
3
|
-
```markdown
|
|
4
1
|
---
|
|
5
2
|
layout: page
|
|
6
3
|
title: Tests
|
|
@@ -9,6 +6,8 @@ description: How the Deva Core is tested, what each test suite proves, and the e
|
|
|
9
6
|
image: /assets/banner.png
|
|
10
7
|
---
|
|
11
8
|
|
|
9
|
+
[](https://github.com/indraai/deva/actions/workflows/test.yml)
|
|
10
|
+
|
|
12
11
|
{{ page.description }}
|
|
13
12
|
|
|
14
13
|
{% assign tests = site.data.tests.DATA %}
|
|
@@ -43,10 +42,3 @@ The suite found {{ tests.edgecases | size }} edge cases. Each looks small on its
|
|
|
43
42
|
|
|
44
43
|
{{ edge.describe }} Fixed in version {{ edge.fixed }}, tested in `{{ edge.suite }}`.
|
|
45
44
|
{% endfor %}
|
|
46
|
-
```
|
|
47
|
-
|
|
48
|
-
**Where it goes:** put it at the repo root next to `about.md` and `docs.md`, so it lives at `/tests/`. To show it in the menu, add `- tests.md` under `header_pages` in `_config.yml`.
|
|
49
|
-
|
|
50
|
-
I don't have Jekyll on my computer, so I haven't built the page or seen it rendered. One part is worth checking on your first build: the table rows come out of a Liquid loop. Each row has to land directly under the `|---|` line with no blank line in between, or kramdown will cut the table short.
|
|
51
|
-
|
|
52
|
-
**One mismatch to fix:** `index.md` says Node.js 22 or later, but the tests run on Node 24, which is what I put in the data file. It would be better to make the two agree, or to say the core needs 22 and the tests were run on 24.
|
package/vibe.md
CHANGED
|
@@ -6,7 +6,7 @@ image: /assets/banner.png
|
|
|
6
6
|
permalink: /vibe/
|
|
7
7
|
---
|
|
8
8
|
|
|
9
|
-
[](https://www.npmjs.com/package/@indra.ai/deva)
|
|
9
|
+
[](https://www.npmjs.com/package/@indra.ai/deva) [](https://github.com/indraai/deva/actions/workflows/test.yml)
|
|
10
10
|
|
|
11
11
|
**{{page.description}}**
|
|
12
12
|
|
package/vla.md
ADDED
|
@@ -0,0 +1,76 @@
|
|
|
1
|
+
---
|
|
2
|
+
layout: page
|
|
3
|
+
title: VLA
|
|
4
|
+
permalink: /vla/
|
|
5
|
+
description: The Vedic License Agreement behind the Deva Core, the teacher and student path it follows, and how to ask Quinn Michaels for a proper license for personal, corporate, government, educational or military use.
|
|
6
|
+
image: /assets/banner.png
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
{{ page.description }}
|
|
10
|
+
|
|
11
|
+
The full agreement is in [LICENSE.md](https://github.com/indraai/deva/blob/main/LICENSE.md). This page explains it in plain words. If anything here differs from LICENSE.md, LICENSE.md is the agreement that applies.
|
|
12
|
+
|
|
13
|
+
| | |
|
|
14
|
+
|---|---|
|
|
15
|
+
| **Agreement** | Vedic License Agreement (VLA) |
|
|
16
|
+
| **VLA** | `31711622713594414221` |
|
|
17
|
+
| **Owner** | Quinn Michaels |
|
|
18
|
+
| **Company** | Inside The Net, Inc. |
|
|
19
|
+
| **Contact** | [quinn@indra.ai](mailto:quinn@indra.ai) |
|
|
20
|
+
|
|
21
|
+
## 1. Rooted in Vedic teachings
|
|
22
|
+
|
|
23
|
+
The Deva Core is built on Vedic teachings. Its agents are Devas, and as they work they record their actions, states, intents and beliefs, following the Vedic idea that every action through mind, speech and body carries a consequence. It is also the base that Quinn Michaels builds his own system from, so the Deva Core sits behind everything else in that system.
|
|
24
|
+
|
|
25
|
+
The license follows the same roots. It is grounded in Vedic Law and works under a threefold order:
|
|
26
|
+
|
|
27
|
+
1. **Vedic Law** sets right action, rightful ownership and the measure of consequences.
|
|
28
|
+
2. **The Constitution of the United States** gives the secular framework, protecting the free exercise of religion and due process.
|
|
29
|
+
3. **Owner Authority** rests with Quinn Michaels, whose signature and consent are required for any valid license.
|
|
30
|
+
|
|
31
|
+
All three must be satisfied for use to be lawful.
|
|
32
|
+
|
|
33
|
+
## 2. The path of a teacher, not a wall
|
|
34
|
+
|
|
35
|
+
The VLA is not meant to keep people away. It follows the path of a Vedic teacher and student:
|
|
36
|
+
|
|
37
|
+
- **Ask permission.** A student does not take a teaching without first asking the teacher. In the same way, using the Deva Core starts with asking Quinn Michaels for a license.
|
|
38
|
+
- **Make a proper offering.** In the Vedic tradition, a student gives a proper offering to the teacher in return for the teaching. For the Deva Core, that offering is agreed when the license is set up, and it supports the work going forward.
|
|
39
|
+
- **Build a community around the teachings.** Once the relationship is in place, the goal is a community of people and teams who learn, build and grow with the Deva Core together, with the teacher's guidance.
|
|
40
|
+
|
|
41
|
+
That is why the agreement protects the work by default. Without a license, the Deva Core may not be modified, redistributed, sub-licensed, reverse engineered or shared, and using it without permission is treated as taking what has not been given. With a license, the door is open.
|
|
42
|
+
|
|
43
|
+
The agreement also sets these limits, which apply to every license:
|
|
44
|
+
|
|
45
|
+
- Use is confined to the United States of America.
|
|
46
|
+
- Official, government and commercial use needs express authorization from the Owner with verified legal signatures.
|
|
47
|
+
- The Owner may revoke access at any time.
|
|
48
|
+
- The Software is provided as-is, without warranty.
|
|
49
|
+
|
|
50
|
+
## 3. How to ask for a license
|
|
51
|
+
|
|
52
|
+
Every license starts the same way: write to Quinn Michaels at [quinn@indra.ai](mailto:quinn@indra.ai) and tell him who you are and how you want to use the Deva Core. The sections below say what to include for each kind of use.
|
|
53
|
+
|
|
54
|
+
### Personal use
|
|
55
|
+
|
|
56
|
+
For individuals learning, experimenting or building their own projects. Include your name, what you want to build, and whether it will stay private or be shared with anyone else.
|
|
57
|
+
|
|
58
|
+
### Corporate use
|
|
59
|
+
|
|
60
|
+
For companies and teams building products or internal systems. Commercial use needs express authorization with verified legal signatures. Include your company name, the people responsible, the product or system you plan to build, how many Devas or deployments you expect, and whether you want consulting help from Quinn to design and build it.
|
|
61
|
+
|
|
62
|
+
### Government use
|
|
63
|
+
|
|
64
|
+
For any official or government body. Government use needs express authorization with verified legal signatures. Include the agency or office, the official responsible, the purpose of the system, and where it will run.
|
|
65
|
+
|
|
66
|
+
### Educational use
|
|
67
|
+
|
|
68
|
+
For schools, universities, teachers and students. Include the institution, the course or program, the number of students, and how the Deva Core will be taught or used.
|
|
69
|
+
|
|
70
|
+
### Military use
|
|
71
|
+
|
|
72
|
+
Military use is official government use under the agreement, so it needs express authorization with verified legal signatures. Include the branch or unit, the authorized official, the purpose of the system, and where it will run.
|
|
73
|
+
|
|
74
|
+
## What to expect
|
|
75
|
+
|
|
76
|
+
Quinn will reply to talk about your use, the proper offering, and the terms of your license. The license is valid once it is agreed and signed. Until then, the full terms of [LICENSE.md](https://github.com/indraai/deva/blob/main/LICENSE.md) apply.
|