Skip to content

Feed Research Memory v0.1.0

Pre-release
Pre-release

Choose a tag to compare

@dcftradingcrypt dcftradingcrypt released this 17 Oct 13:24

Feed Research Memory imports local RSS/Atom snapshots into OriginTrail DKG v10 Working Memory and supports source revisions, research notes, cited question/answer packets and exact-evidence recall.

Published v0.1.0 artifact

The release job successfully ran gh attestation verify against the OCI digest, constrained to this repository, this workflow, the exact source/signer SHA, the v0.1.0 source ref and GitHub-hosted runners. Independent anonymous registry checks confirmed the tag-to-digest mapping, manifest/config hashes, public access to all nine image layers, attestation bundle hash and its matching subject/source. Those additional checks do not claim a second independent trust-chain verification.

Demo and verification

Twenty unit tests, a real local DKG 10.0.24 public-HTTP/Oxigraph WM workflow, separate acceptance using twenty selected entries from the official Node.js feed, and isolated npm-pack/install/bin smoke passed. The recorded walkthrough contains thirteen actual CLI commands; its benchmark source documents are explicitly fictional fixtures. The local DKG node used an outside-package transport-only loopback harness and an unfunded mock chain. No mainnet publication, SWM replication, financial transaction or paid LLM was exercised. The container release smoke checks the installed CLI, not another container-to-DKG end-to-end run.

This release record supersedes the publication-pending statements in the immutable source snapshot: those documents were prepared before the release workflow ran. npm publication has not occurred. The OCI image is a one-shot CLI, not a node service; use the documented operator-provided node URL, token and input mounts. No credentials or private runtime harness are included in the image.

AI-assisted implementation and documentation. Apache-2.0; imported feed content retains its original rights. Maintainer: @dcftradingcrypt, with at least six months support after an approved registry merge. Registry acceptance and any bounty payment remain unconfirmed. This prerelease is for evaluation.