Eclipse Feedforge runs on your own machine — the client starts it, so there is no endpoint to ping.
Messy catalog to agent-grade feed with per-attribute provenance. LOCAL/fixture only.
The linked repository no longer exists on GitHub — it was deleted or made private.
This one has been quiet for a while
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
Alternatives to Eclipse Feedforge
same job, measured the same wayBand-only age proofs over fixture attestations, sealed to one mandate; local only.
Failure-attribution recompute over hash-chained fixture records (local only): verdict + proof path.
Warranty witness for agent purchases: sealed, transferable claim packs. LOCAL/fixture only.
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1
Governed returns for agent purchases: sealed receipt+mandate binding. LOCAL/fixture only.
Fixture cyber-insurance evidence assembly with change receipts; local only, not underwriting.
kala memory over MCP: provenance-first agent memory with Datalog recall and as-of time travel.
Consent-bound lead work for real-estate agents — provenance on every lead, a Gate on every send, a
Eclipse Feedforge — questions
Answers built from our own checks of this server.