Guide market prediction workflows with LSTM, Transformer, and N-BEATS models using neural-trader commands and result storage. It explicitly identifies version 2.8.11 outputs as placeholders, so they cannot be treated as fitted models or evidence of prediction accuracy.
Train neural models (LSTM, Transformer, N-BEATS) on market data using npx neural-trader with confidence intervals
Review the instructions the agent will receive before you install.
Train neural prediction models using neural-trader's ML engine.
Steps:
npm ls neural-trader 2>/dev/null || npm install --ignore-scripts neural-tradernpx neural-trader --train --model lstm --symbol TICKER --epochs 50
--train is required; --model X --symbol T alone is rejected ("Unknown command"), and --confidence and --decompose do not exist. In 2.8.11 the result carries upstreamStub: true ("neuralTrain returns a placeholder shape (no real LSTM/Transformer fit yet)"). Report that no model was fitted; never describe the output as a trained model or quote its numbers as accuracy.npx neural-trader --predict --model MODEL --symbol TICKER [--gpu]
--horizon is not supported, and neuralPredict is also a placeholder (upstreamStub: true) in 2.8.11.--model-compare) does not exist in the CLI. Without a real fit there is nothing to compare; say so rather than fabricating a ranking.trading-analysis namespace per ADR-126 Phase 1 — was previously stored to undeclared trading-models):
mcp__plugin_ruflo-core_ruflo__memory_store({ key: "model-MODEL-TICKER-DATE", value: "TRAINING_RESULTS", namespace: "trading-analysis" })mcp__plugin_ruflo-core_ruflo__neural_train({ modelType: "moe", epochs: 10 }) (modelType is required; there is no patternType). Skip this step when step 2 returned a stub, so placeholder runs do not train SONA.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.