Verify the witness chain, a linked record of evidence, for a Cognitum Seed device. Check for missing recording periods and broken hash links, report an integrity score, and save detected gaps for auditing.
Verify witness chain integrity and detect provenance gaps
Run score Not tested
See how to installiot-witness-verify checks the witness chain of a Cognitum Seed device: the continuous links between its evidence records. You specify a device ID and run the verification command. The check looks for missing recording periods, called epochs, and breaks in the hash chain that connects records. It reports an integrity score from 0.0 to 1.0.
Use it when you need to examine a device's evidence records and identify which recording periods are missing. Alongside reviewing the integrity score, you can keep the detected gaps as an audit record. The device ID determines which device's chain is checked.
You need an environment that can run @claude-flow/plugin-iot-cognitum@1.0.0 through npx. To save gaps, the skill uses Ruflo's memory storage tool. It records the device ID and missing periods in the iot-audit namespace.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Verify the witness chain integrity for a Cognitum Seed device.
Steps:
npx -y -p @claude-flow/plugin-iot-cognitum@1.0.0 cognitum-iot witness verify DEVICE_IDmcp__plugin_ruflo-core_ruflo__memory_store({ key: "iot-witness-gap-DEVICEID", value: "Gap from EPOCH to EPOCH", namespace: "iot-audit" })No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.