From 6a6adb5fa2185a591b077aac132a71c22a2c075b Mon Sep 17 00:00:00 2001 From: Ralf Anton Beier Date: Fri, 7 Aug 2026 10:05:01 +0200 Subject: [PATCH] docs: stop advertising archived repos; refresh the tool roster MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit An org-wide repository reassessment found the site and the skills presenting repositories that are archived, and omitting ones that are live. agora was archived on 2026-08-07 but still appeared as a live component: - how-it-works: removed the agora node and its "coordination facts" edge from the pipeline diagram, and the reading note that described it as feeding rivet. This was the most visible inaccuracy we had — a dead component drawn on the front-door explainer. - how-it-works prose and the projects page now say what actually happened: a coordination substrate was spiked and archived, because the issue-driven loop proved sufficient and GitHub issues are already durable, signed and auditable. report-tool-friction's roster listed thrum (archived since 2026-03) and omitted ordeal and varve, so agents were told to file friction against a dead repo and did not know two live ones existed. Also drops mcp, which is being retired. report-tool-friction 0.2.0 -> 0.3.0; plugin 0.18.0 -> 0.19.0. Co-Authored-By: Claude Opus 4.8 (1M context) --- .../pulseengine-claude/.claude-plugin/plugin.json | 2 +- .../skills/report-tool-friction/SKILL.md | 4 ++-- content/how-it-works.md | 10 ++++------ templates/projects.html | 6 +----- 4 files changed, 8 insertions(+), 14 deletions(-) diff --git a/claude-tooling/plugins/pulseengine-claude/.claude-plugin/plugin.json b/claude-tooling/plugins/pulseengine-claude/.claude-plugin/plugin.json index 6efc9e8..bd3b53b 100644 --- a/claude-tooling/plugins/pulseengine-claude/.claude-plugin/plugin.json +++ b/claude-tooling/plugins/pulseengine-claude/.claude-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "pulseengine-claude", - "version": "0.18.0", + "version": "0.19.0", "description": "PulseEngine methodology as installable Claude Code tooling \u2014 philosophy + toolchain + repo-taxonomy + model-operating-contract memory, memory-persistence hooks (situational awareness at session start, working-context checkpoints across sessions/compaction), plus sixteen procedural skills (clean-room verification, release execution with a V-model traceability gate, oracle-gating, the full feature loop, the standardized release-artifact pipeline, tool-friction reporting, session-learning capture, STPA/STPA-Sec hazard-analysis audit, backend-agnostic proof synthesis, full bidirectional traceability audit across the V, greenfield verification bootstrap, release planning with an issue-driven delivery loop, an incremental issue-hunt loop, a quiesce-gated post-release repo-hygiene sweep, and a gate-potency audit that proves standing CI checks can still fail).", "author": { "name": "PulseEngine", diff --git a/claude-tooling/plugins/pulseengine-claude/skills/report-tool-friction/SKILL.md b/claude-tooling/plugins/pulseengine-claude/skills/report-tool-friction/SKILL.md index 870740d..689b84d 100644 --- a/claude-tooling/plugins/pulseengine-claude/skills/report-tool-friction/SKILL.md +++ b/claude-tooling/plugins/pulseengine-claude/skills/report-tool-friction/SKILL.md @@ -1,9 +1,9 @@ --- name: report-tool-friction -description: This skill should be used whenever a PulseEngine tool (rivet, spar, witness, sigil, meld, loom, synth, kiln, gale, scry, smithy, thrum, temper, mcp — the roster lives in the pulseengine-toolchain memory) produces friction during real work — it errors, crashes, produces wrong or surprising output, is missing a capability you needed, has confusing/undocumented behavior, or forced you into a workaround. ALWAYS use this skill the moment you notice yourself working *around* a tool instead of *with* it, or saying "this should just work but doesn't." The friction is the signal; capturing it as an issue in the tool's own repo is the action. Fires inside [`pulseengine-feature-loop`] and [`release-execution`] and any standalone tool use. +description: This skill should be used whenever a PulseEngine tool (rivet, spar, witness, sigil, meld, loom, synth, kiln, gale, scry, ordeal, varve, smithy, temper — the roster lives in the pulseengine-toolchain memory) produces friction during real work — it errors, crashes, produces wrong or surprising output, is missing a capability you needed, has confusing/undocumented behavior, or forced you into a workaround. ALWAYS use this skill the moment you notice yourself working *around* a tool instead of *with* it, or saying "this should just work but doesn't." The friction is the signal; capturing it as an issue in the tool's own repo is the action. Fires inside [`pulseengine-feature-loop`] and [`release-execution`] and any standalone tool use. metadata: author: pulseengine.eu - version: "0.2.0" + version: "0.3.0" --- # Report tool friction diff --git a/content/how-it-works.md b/content/how-it-works.md index 103d8a8..b0b37c7 100644 --- a/content/how-it-works.md +++ b/content/how-it-works.md @@ -37,7 +37,6 @@ flowchart TB apps["relay · wohl · jess"] verify{{"Verify gate
Verus · Rocq · Lean
scry · witness · ordeal"}} sigil["sigil
sign · attest"] - agora["agora
agent coordination"] rivet[("rivet
traceability spine")] spar ==>|WIT + skeletons| code ==> meld ==> loom @@ -51,7 +50,6 @@ flowchart TB synth -.-> sigil sigil -.->|signed evidence| rivet verify -.->|evidence| rivet - agora -.->|coordination facts| rivet spar -.->|typed artifacts| rivet classDef ours fill:#242836,stroke:#6c8cff,color:#e1e4ed; @@ -61,7 +59,6 @@ flowchart TB class spar,code,meld,loom,synth,kiln,gale,apps,sigil ours class verify gate class rivet spine - class agora agent {% end %} Reading it: @@ -190,9 +187,10 @@ the Phase-2 arc (its name is the falconry tether, on purpose). Today PulseEngine's agents coordinate the plain way — they synchronize through **GitHub issues and releases**, running in loops to hunt issues, implement features, and check whether a new release actually works. -[agora](https://github.com/pulseengine/agora) is the early substrate meant to make -that agent-to-agent chatter faster than round-tripping through GitHub (still a spike: -signing stubbed, transport in-memory). Around that, [rivet](https://github.com/pulseengine/rivet)'s +A dedicated coordination substrate ([agora](https://github.com/pulseengine/agora)) was +spiked to make that chatter faster than round-tripping through GitHub, and **archived** — +GitHub issues and releases turned out to be sufficient, and they are durable, signed and +auditable without new infrastructure. Around that, [rivet](https://github.com/pulseengine/rivet)'s MCP tools expose validate / add / link / coverage to agents, and [temper](https://github.com/pulseengine/temper) (a GitHub App) holds every repo to the same standards. The [mcp](https://github.com/pulseengine/mcp) framework was our diff --git a/templates/projects.html b/templates/projects.html index 10f7fb7..2abaf6b 100644 --- a/templates/projects.html +++ b/templates/projects.html @@ -192,10 +192,6 @@

{{ section.title }}

spar wasm in-browser analysis via WASM - - agora - real-time agent coordination -
@@ -275,7 +271,7 @@

Run — platforms & applications