@idleware/ringi 0.1.0 → 0.1.1

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.
Files changed (2) hide show
  1. package/README.md +14 -9
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -1,15 +1,20 @@
1
1
  # ringi
2
2
 
3
- **Distributed agent coordinator.**
3
+ [![CI](https://github.com/idleware/ringi/actions/workflows/ci.yml/badge.svg?branch=master)](https://github.com/idleware/ringi/actions/workflows/ci.yml)
4
+ [![Maintainability](https://qlty.sh/gh/idleware/projects/ringi/maintainability.svg)](https://qlty.sh/gh/idleware/projects/ringi)
5
+ [![Code Coverage](https://qlty.sh/gh/idleware/projects/ringi/coverage.svg)](https://qlty.sh/gh/idleware/projects/ringi)
6
+ [![npm version](https://img.shields.io/npm/v/@idleware/ringi/latest?label=npm&color=blue)](https://www.npmjs.com/package/@idleware/ringi)
4
7
 
5
- Orchestrators (Hermes, n8n, OpenClaw) run processes: they decide what happens next. ringi decides nothing of the
6
- kind. It connects the parts, agents of any vendor on one machine or many, and keeps them in sync: who said what to
7
- whom, who took which work, what it may spend, what came of it. Every message is a stored, checkable record; a peer's
8
- message is data, never an instruction.
8
+ *Distributed agent coordinator.*
9
9
 
10
- - **Your rules.** A room's profile defines work and who moves it; A2A tasks are one profile.
11
- - **Budgets.** Proposal, stamps, decision (稟議). The runner spends a grant, never the model.
12
- - **Signals.** Each counted transition gets a checkable marker beside its message (git: a tag).
10
+ Orchestrators (Hermes, n8n, OpenClaw) run processes and choose the next step. ringi only connects the parts, agents
11
+ of any vendor on one machine or many, and keeps them in sync: who said what to whom, who took which work, what it may
12
+ spend, what came of it. Everything is a stored, checkable record; whatever a peer writes is data, never an
13
+ instruction.
14
+
15
+ - **Your rules.** A room's profile defines work and who moves it; A2A tasks ship as one of them.
16
+ - **Budgets.** Proposal, stamps, decision ([稟議](https://en.wikipedia.org/wiki/Japanese_management_culture#Managerial_style)). The runner spends a grant, never the model.
17
+ - **Signals.** Each counted transition is marked beside its message (git: a tag).
13
18
  - **Any store.** Git first; one CLI and a skill for you and the agents.
14
19
 
15
20
  ```sh
@@ -51,7 +56,7 @@ Codex: add `~/.ringi` to `writable_roots` in `~/.codex/config.toml`, or approve
51
56
  ```
52
57
 
53
58
  1. `ringi hub create team --signed --url <git url>` prints the `ringi hub add …` line for the other machines.
54
- 2. There, `ringi join team fix --as codex` prints the agent's key; you run `ringi room admit codex '<key>' --room fix`.
59
+ 2. There, `ringi join team fix --as codex` shows the agent's key; you run `ringi room admit codex '<key>' --room fix`.
55
60
  3. `ringi watch team:fix/codex --require-grant --exec 'codex exec "…"'`
56
61
 
57
62
  ## Your own profile
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@idleware/ringi",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "Distributed agent coordinator",
5
5
  "keywords": [
6
6
  "agents",