{"slug": "intelshed-an-open-source-platform-for-osint-ai-research-and-collaborative", "title": "IntelShed: An Open-Source Platform for OSINT, AI Research, and Collaborative Intelligence", "summary": "IntelShed, an open-source platform for OSINT and AI research, has updated its trust layer to include immutable run records, versioned policy, and a deduplicated recompute queue, following community feedback. The project now records inputs, policy version, and run context for each outcome, with operator-facing provenance endpoints planned. Maintainers invite contract-level review and reproducible edge-case reports via GitHub issues.", "body_md": "Hi everyone,\n\nthanks for the thoughtful feedback to John6666 - for the careful read and for framing the findings as contract questions rather than vague bug reports. That perspective has been very helpful for us.\n\nSince that review, we’ve made a lot of progress on the trust layer. The current stack now includes:\n\na clearer separation between claim content, occurrences, and trust outcomes,\n\nimmutable run records with versioned policy and reproducibility metadata,\n\ndirected stale marking for exact outcome scopes,\n\na deduplicated recompute queue with claim/lease, retry backoff, and dead-letter handling,\n\nand a service-level orchestration path from invalidation to recompute enqueueing.\n\nThat means the architecture now records not only what the system produced, but also which inputs, policy version, and run context produced each outcome. Operator-facing endpoints to query that provenance are on the roadmap but not yet exposed.\n\nI still welcome help with:\n\nreproducible edge cases,\n\ncontract-level review of the current trust boundaries,\n\nregression fixtures across SQLite and PostgreSQL,\n\nand any mismatch between intended semantics and actual behavior.\n\nIf you spot a problem, a missing invariant, or a boundary that should be tested more explicitly, please open an issue in the GitHub repository with a minimal reproduction and a clear description of the contract you believe is violated. That is the fastest way to help us turn this into a robust, evidence-based trust platform.\n\nI am especially interested in reports around:\n\nclaim content vs. occurrence separation,\n\nindependence and corroboration semantics,\n\nidempotency and replay behavior,\n\nstale marking and recompute scope,\n\nand reproducibility across database backends.\n\nThanks again to everyone who has taken the time to review the work — it genuinely helps move the project from working infrastructure toward a measurable and auditable trust system.", "url": "https://wpnews.pro/news/intelshed-an-open-source-platform-for-osint-ai-research-and-collaborative", "canonical_source": "https://discuss.huggingface.co/t/intelshed-an-open-source-platform-for-osint-ai-research-and-collaborative-intelligence/178410#post_4", "published_at": "2026-08-05 00:33:19+00:00", "updated_at": "2026-08-05 00:35:34.571392+00:00", "lang": "en", "topics": ["ai-research"], "entities": ["IntelShed", "John6666", "GitHub"], "alternates": {"html": "https://wpnews.pro/news/intelshed-an-open-source-platform-for-osint-ai-research-and-collaborative", "markdown": "https://wpnews.pro/news/intelshed-an-open-source-platform-for-osint-ai-research-and-collaborative.md", "text": "https://wpnews.pro/news/intelshed-an-open-source-platform-for-osint-ai-research-and-collaborative.txt", "jsonld": "https://wpnews.pro/news/intelshed-an-open-source-platform-for-osint-ai-research-and-collaborative.jsonld"}}