CORE_READY
Yes: v0.1 public CLI/API release candidate with tests, receipts, and live metadata demo.
Open-source release
The Fractalish Research Query core is a small public package for exact public-metadata discovery: forward from a question, reverse from a source, and always back to provider IDs, links, timestamps, command, runtime, and hashes.
Forward and reverse
Forward mode starts with a question or keyword expression and searches public metadata. Reverse mode starts from a paper title, identifier, or DOI-like string and expands toward precursors, methods, contradictions, replications, benchmarks, and related work. Both modes return leads, not conclusions.
Mode, exact terms, Boolean exclusions, provider list, and maximum result count.
Public metadata from arXiv, OpenAlex, Crossref, and Europe PMC. No PDFs are downloaded.
Deduped records keep provider observations, then receive conservative labels such as direct match, precursor candidate, method candidate, contradiction candidate, adjacent domain, or weak match.
JSON and Markdown receipts include source IDs, URLs, timestamps, command, runtime, provider errors, and SHA-256 hashes.
The core supports default AND behavior plus explicit OR and NOT/minus exclusions. A live release demo used:
"persistent state" AND AI NOT medical NOT immune NOT vitamin
That query narrowed broad exact phrase matches down to a single public metadata lead. The point is not semantic prettiness. The point is controllable retrieval with an inspectable trail.
Yes: v0.1 public CLI/API release candidate with tests, receipts, and live metadata demo.
No: no packaged installer or signed executable yet.
No: this page describes the release, but it is not the deployed query service.
No: the schema and redaction helper exist, but no storage or consent UI is deployed.
Claim boundary
The core can find likely relevant public sources and preserve a receipt of how it found them. It does not establish scientific claims, prove novelty, replace source review, or publish private queries. Shareable query pages and public query contribution require separate explicit consent controls.