Repository navigation
Add Statewave to memory - #73
Conversation
Bugbot is paused — on-demand spend limit reachedBugbot uses usage-based billing for this team and has hit its on-demand spend limit. A team admin can raise the spend limit in the Cursor dashboard, or wait for the next billing cycle to continue. |
autogame-17
left a comment
There was a problem hiding this comment.
Reviewed the complete diff at 4f5e9fc516f728e49d852f3123ad19e9f9513dae and the canonical smaramwbc/statewave repository at upstream 6e2691cbcb5c565019805836056929ec348b0895.
The memory-category scope and description are supported by the README and implementation: event-derived context assembly, provenance back to source episodes, and self-hosted Postgres/pgvector storage. The repository is public, active, neither archived nor disabled, Apache-2.0 licensed, and above the inclusion threshold (368 stars when checked). No duplicate entry was found in either Awesome list.
Actual verification on this PR head with Node v24.19.0:
- Untouched and post-generation validation: 121 projects across 10 categories; passed.
- Two README generation passes: byte-identical to the committed README, with no generated diff.
- Whitespace check: passed.
- Full authenticated link scan: 121 OK, 0 failures, 0 warnings.
- GitHub Validate curated data and Check Links: completed successfully on this head.
GitHub reports the current head as mergeable with clean merge state; the active main ruleset's required validate check is satisfied. Bugbot's paused billing state was not treated as a passing review or used as evidence.
Approved for this catalog addition. No merge has been performed.
|
@autogame-17 thanks for the approval. Is there anything else needed from my side before this can be merged? |
|
Rechecked head There is now one author-side step before this can proceed: refresh the branch from current upstream main and resolve the conflicts in git merge-tree --write-tree 596c20ba06738d5d7fcb10afd9934e507b4b81bd 4f5e9fc516f728e49d852f3123ad19e9f9513daeKeep the current main catalog and star snapshots, add Statewave once (the proposed record is at After updating the branch, run: node scripts/generate-readme.js
node scripts/validate.js
git diff --check
node scripts/check-links.jsThe updated head also needs actual successful validation and link-check workflow runs. The current live check rollup is empty, so the previous successful run is not being treated as a current green integration gate. No merge or workflow approval has been performed. |
Resolve against current main and refresh the canonical star snapshot. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
autogame-17
left a comment
There was a problem hiding this comment.
Verified the refreshed catalog-only diff against current main. The Statewave entry is preserved with its current canonical star snapshot, and the generated README, validation, and link checks passed locally and in the two current GitHub Actions jobs.
Adds Statewave to the
memorycategory.What it is: an open-source memory runtime for AI agents. It records agent events and compiles them into structured memories, then assembles reproducible, provenance-tagged context bundles per subject, so it doesn't rely on query-time similarity retrieval. It is self-hosted on Postgres + pgvector and has Python and TypeScript SDKs plus an MCP server.
Why it belongs: it's a persistent memory system for long-running agents. Every recalled fact traces back to the episode it came from, which supports the auditability side of agent memory.
Criteria: Apache-2.0, 366★, active (v1.5.0, pushed this month), documented README with quickstart.
Followed CONTRIBUTING: edited
data/projects.jsonand regenerated the README withnode scripts/generate-readme.js.node scripts/validate.jsandnode scripts/check-links.jsboth pass (121 ok, 0 failures).