Skip to content

docs: stop advertising archived repos; refresh the tool roster #158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
avrabe merged 1 commit into from
Aug 7, 2026
Merged

docs: stop advertising archived repos; refresh the tool roster #158

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion claude-tooling/plugins/pulseengine-claude/.claude-plugin/plugin.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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",
Expand Down
4 changes: 2 additions & 2 deletions claude-tooling/plugins/pulseengine-claude/skills/report-tool-friction/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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
Expand Down
10 changes: 4 additions & 6 deletions content/how-it-works.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,6 @@ flowchart TB
apps["relay · wohl · jess"]
verify{{"Verify gate<br/>Verus · Rocq · Lean<br/>scry · witness · ordeal"}}
sigil["sigil<br/>sign · attest"]
agora["agora<br/>agent coordination"]
rivet[("rivet<br/>traceability spine")]

spar ==>|WIT + skeletons| code ==> meld ==> loom
Expand All @@ -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;
Expand All @@ -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:
Expand Down Expand Up @@ -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
Expand Down
6 changes: 1 addition & 5 deletions templates/projects.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,10 +192,6 @@ <h1 class="section-heading">{{ section.title }}</h1>
<span class="face-tool__name">spar wasm</span>
<span class="face-tool__desc">in-browser analysis via WASM</span>
</a>
<a href="https://github.com/pulseengine/agora" class="face-tool" rel="noopener">
<span class="face-tool__name">agora</span>
<span class="face-tool__desc">real-time agent coordination</span>
</a>
</div>
<div class="face-edge">
<span class="face-edge__dot" style="background:#fbbf24"></span>
Expand Down Expand Up @@ -275,7 +271,7 @@ <h3 style="color:#f87171">Run — platforms &amp; applications</h3>
<div class="cube-detail__panel" data-detail="agent" style="display:none">
<h3 style="color:#c084fc">Agent — AI-native development</h3>
<p><strong>rivet mcp</strong> exposes a full tool suite to AI agents — validate, add artifacts, link, check coverage, stamp provenance. Agents write code AND maintain traceability as part of their workflow.</p>
<p><strong>rivet stamp</strong> records AI session provenance. <strong>mcp</strong> is the Rust framework for building MCP servers. <strong>spar wasm</strong> runs architecture analysis in-browser at 1.3 MB. <strong>agora</strong> is the real-time coordination substrate — named agents subscribe to channels and coordinate on a durable, signed, traceable fact log, augmenting the issue-driven loop.</p>
<p><strong>rivet stamp</strong> records AI session provenance. <strong>mcp</strong> is the Rust framework for building MCP servers. <strong>spar wasm</strong> runs architecture analysis in-browser at 1.3 MB. A dedicated coordination substrate (<strong>agora</strong>) was spiked and archived — the issue-driven loop proved sufficient, and GitHub issues are already durable, signed and auditable.</p>
<div class="cube-detail__links">
<a href="https://github.com/pulseengine/rivet" rel="noopener">rivet</a>
<a href="https://github.com/pulseengine/mcp" rel="noopener">mcp framework</a>
Expand Down