Step 3 of 5 · What the live sources say
Checked live against npm, GitHub, PyPI and IP India
Aurexis checks your idea against live sources and shows you exactly what it found. You choose. Your choice is sealed.

Example check
npm
3 close matches
fetched 14:20 IST
Sealed · rec-8f2a41c9
Halt · condition set
Proceed if weekly downloads stay under 2k
Step 3 of 5 · What the live sources say
Every check reads live sources
You bring the idea. Live sources bring the evidence. You make the call, and the record keeps it honest.
We query live sources for your idea and show what each one supports, contradicts, or could not reach. Every finding carries its source and fetch time.
about a minuteProceed, Halt, or Wait until a date you pick. Your first choice is sealed and hashed the moment you confirm. It can never be edited.
sealed and hashedThe strongest case for your choice and the evidence against it. It never tells you that you chose well.
case for and againstAt day 30 and day 90 every source reruns. You see what moved, and you can change course with the reason recorded.
day 30 · day 90Every source answers in its own words, with the time we asked. Nothing is averaged into a score, and nothing is decided for you.
The idea
“An AI agent that triages and fixes GitHub issues for small teams.”
Whichever you pick, the report sets out the strongest case for it and the evidence against it. It never tells you that you chose well.
Build the smallest slice, with the conditions that would make you stop.
Your report includes
Stop here, and keep what would change your mind.
Your report includes
Not yet. Pick a date or an event to revisit on.
Your report includes
When you proceed, you write what would make you stop, in your own words. On each date we read the live source and mark it Held, Broke or Unknown. No rulebook, in any domain.
Your line was not crossed.
Your line was crossed. You decide what happens next.
Source unreachable after three retries. Never counted as held.
“If fewer than 20 teams sign up in the first 30 days, I stop.”
Held“If day 30 retention is below 40%, I stop.”
Broke“If a project in this space passes 5,000 GitHub stars before March, I stop.”
Watching“If fewer than 5 shops are paying by 31 March, I stop.”
“If weekly npm downloads fall below 2,000 for four weeks, I stop.”
“If the BIRAC call closes without a shortlist, I stop.”
Most tools merge two very different outcomes into one blank. We keep them apart on every check.
Every check, every source, every time. Nothing cached, nothing guessed.
Where other tools show a blankAbsent and Unreached look the same elsewhere. Here they never merge.
The source did not answer. Our gap, never your evidence. We retry three times, then say so plainly.
IP India no public feedThe source answered with nothing. That is a finding, and it counts as evidence.
PyPI exact name, 404A source supports some part of the idea.
A source shows the idea, or close to it, already exists.
Every state links to the source that produced it.
We rerun every source on a schedule, so you can see what changed since you decided.
Evidence frozen. First choice hashed and timestamped.
Every source reruns. Conditions due by now are read.
Everything reruns again. You see what moved, and what did not.
If a source will not answer, we say so. We never fill the gap with a guess.
The change sits next to your first choice, with the reason: new evidence, or none.
Totals only. No ideas, no names, no single records. Every number comes from a sealed first choice and the halt conditions founders wrote themselves.
No decisions yet. The first sealed choice starts the count.
Too few decisions for a rate to mean anything.
Most products promise what they will do. These are the promises that make a record worth keeping.
The sources speak. You decide.
Every finding stays in its own words.
Unreached is shown, every time.
Sealed and hashed the moment you confirm.
Your halt conditions are yours alone.
The Ledger shows totals only.
Every record is plain JSON. Canonicalise it, take the SHA-256, compare. No account, no network. If our servers disappear tomorrow, every record stays checkable.
$ jq -S -c . record.json | sha256sum
9f2a41c93e8b0c2d77f91b5e6a04c8d3f2e1b9a7c6d5ef4f30812a6b4cb7c14e
# same hash as the one printed on your record
Match. This record has not changed.Checked live against npm, GitHub, PyPI and IP India
Aurexis checks your idea against live sources and shows you exactly what it found. You choose. Your choice is sealed.

Example check
npm
3 close matches
fetched 14:20 IST
Sealed · rec-8f2a41c9
Halt · condition set
Proceed if weekly downloads stay under 2k
Step 3 of 5 · What the live sources say
Every check reads live sources
You bring the idea. Live sources bring the evidence. You make the call, and the record keeps it honest.
We query live sources for your idea and show what each one supports, contradicts, or could not reach. Every finding carries its source and fetch time.
about a minuteProceed, Halt, or Wait until a date you pick. Your first choice is sealed and hashed the moment you confirm. It can never be edited.
sealed and hashedThe strongest case for your choice and the evidence against it. It never tells you that you chose well.
case for and againstAt day 30 and day 90 every source reruns. You see what moved, and you can change course with the reason recorded.
day 30 · day 90Every source answers in its own words, with the time we asked. Nothing is averaged into a score, and nothing is decided for you.
The idea
“An AI agent that triages and fixes GitHub issues for small teams.”
Whichever you pick, the report sets out the strongest case for it and the evidence against it. It never tells you that you chose well.
Build the smallest slice, with the conditions that would make you stop.
Your report includes
Stop here, and keep what would change your mind.
Your report includes
Not yet. Pick a date or an event to revisit on.
Your report includes
When you proceed, you write what would make you stop, in your own words. On each date we read the live source and mark it Held, Broke or Unknown. No rulebook, in any domain.
Your line was not crossed.
Your line was crossed. You decide what happens next.
Source unreachable after three retries. Never counted as held.
“If fewer than 20 teams sign up in the first 30 days, I stop.”
Held“If day 30 retention is below 40%, I stop.”
Broke“If a project in this space passes 5,000 GitHub stars before March, I stop.”
Watching“If fewer than 5 shops are paying by 31 March, I stop.”
“If weekly npm downloads fall below 2,000 for four weeks, I stop.”
“If the BIRAC call closes without a shortlist, I stop.”
Most tools merge two very different outcomes into one blank. We keep them apart on every check.
Every check, every source, every time. Nothing cached, nothing guessed.
Where other tools show a blankAbsent and Unreached look the same elsewhere. Here they never merge.
The source did not answer. Our gap, never your evidence. We retry three times, then say so plainly.
IP India no public feedThe source answered with nothing. That is a finding, and it counts as evidence.
PyPI exact name, 404A source supports some part of the idea.
A source shows the idea, or close to it, already exists.
Every state links to the source that produced it.
We rerun every source on a schedule, so you can see what changed since you decided.
Evidence frozen. First choice hashed and timestamped.
Every source reruns. Conditions due by now are read.
Everything reruns again. You see what moved, and what did not.
If a source will not answer, we say so. We never fill the gap with a guess.
The change sits next to your first choice, with the reason: new evidence, or none.
Totals only. No ideas, no names, no single records. Every number comes from a sealed first choice and the halt conditions founders wrote themselves.
No decisions yet. The first sealed choice starts the count.
Too few decisions for a rate to mean anything.
Most products promise what they will do. These are the promises that make a record worth keeping.
The sources speak. You decide.
Every finding stays in its own words.
Unreached is shown, every time.
Sealed and hashed the moment you confirm.
Your halt conditions are yours alone.
The Ledger shows totals only.
Every record is plain JSON. Canonicalise it, take the SHA-256, compare. No account, no network. If our servers disappear tomorrow, every record stays checkable.
$ jq -S -c . record.json | sha256sum
9f2a41c93e8b0c2d77f91b5e6a04c8d3f2e1b9a7c6d5ef4f30812a6b4cb7c14e
# same hash as the one printed on your record
Match. This record has not changed.