LIKELY WORKAROUND / TO OBSERVE
- 01Open screener and chart tabs
- 02Check freshness by hand
- 03Reconcile missing names
- 04Write down why something passed
Independent verdict: VALIDATE FIRST
AlgoTrader is a concept for reducing the NIFTY 100 to at most five inspectable research candidates—or a truthful no-candidate, partial, or failed result. It is designed to preserve the part software should not own: your financial decision.
Concept status. No live product, live market-data connection, signup service, or launch date is claimed.
Execution boundary
The proposed product does not place, modify, or cancel orders.
01Current truth Tested deterministic code primitives exist; an operating product does not.
02Question to answer Is this meaningfully better than tabs, a screener, and the current script?
03Authority Research reads only. The human decides and acts elsewhere.
01 / THE JOB
Today’s likely workflow crosses chart tabs, screeners, notes, and small scripts. That can make a genuine empty result hard to distinguish from stale observations, missing symbols, or an upstream failure.
This problem is a dossier hypothesis, not a user-research finding. The validation study exists to test its frequency and cost.
LIKELY WORKAROUND / TO OBSERVE
PROPOSED / NOT IMPLEMENTED
02 / THE LOOP
The core loop is deliberately narrow. Every stage either adds traceable evidence or stops the result from looking more certain than it is.
Use one approved, named, versioned policy. Daily and intraday rules are not blended.
Capture the NIFTY 100 universe and the evidence contract for that run.
Block missing, stale, future-dated, malformed, or incomplete observations.
Apply deterministic rules only after every mandatory gate passes.
Inspect 0–5 policy-passing candidates, all exclusions, and the frozen manifest.
The human decides independently in an unrelated broker interface. There is no product order path.
03 / PROPOSED EXPERIENCE
A polished candidate card is easy. Trust depends on what happens when zero names pass, 18 observations are missing, or the source fails. Use the controls to inspect the proposed language for each state.
COMPLETED / NO CANDIDATES
Every universe member received a decision; none passed this synthetic policy scenario. This is not a failed scan.
Policy version, source and receipt times, all per-symbol reason IDs, expected versus actual values, and the immutable run checksum.
PARTIAL / QUEUE SUPPRESSED
This dossier-grounded failure scenario preserves the 82 valid observations but does not promote them as a current candidate queue.
Inspect affected symbols or create a linked new run after the source and policy are revalidated. The prior record stays unchanged.
FAILED / NO QUEUE
No candidate content appears. A typed failure and correlation ID would support diagnosis without leaking a credential or source payload.
Terminal records are immutable. Recovery creates a linked successor with a new run ID, rather than rewriting the failed evidence trail.
04 / THE BET
Established tools already offer more indicators, charts, alerts, and integrations. Agent connectivity exists elsewhere too. The only credible reason to build this concept is if a narrower evidence record creates a measurable advantage.
These are positioning hypotheses from a bounded desk review, not hands-on superiority findings. The study must compare the same task against at least two current substitutes.
05 / TRUST BOUNDARIES
The reviewed concept limits what the system and any connected agent may know or do. Some boundaries are permanent; others are conditions that block a future pilot.
ALLOWED IN THE CONCEPT
PHYSICALLY ABSENT
BLOCKED BEFORE PILOT
06 / AGENT ACCESS — LATER
If the core workflow proves valuable, a separate algotrader_research MCP could expose typed reads from the same frozen record. It would not relay the upstream OpenAlgo MCP or inherit its wider authority.
list_runsBounded history summariesREADget_runStatus, policy, coverage, limitationsREADlist_decisionsFiltered inclusion and exclusion reasonsREADget_decisionOne stored evidence recordREADNo scan command, export creation, order, account, shell, file, SQL, URL fetch, deletion, or publish tool.
07 / VALIDATION STUDY
The next step is not feature development. It is observing real NIFTY 100 research sessions, timing the current workaround, comparing substitutes, and testing whether critical states are understood correctly.
Looking for Self-directed Indian-equity researchers who review large-cap names at least weekly.
What is tested Workflow time, state comprehension, evidence usefulness, and permission understanding—not investment performance.