Reinforcement Learning

Reinforcement learning (RL) is an area of machine learning concerned with how intelligent agents ought to take actions in an environment in order to maximize the notion of cumulative reward. Reinforcement learning is one of three basic machine learning paradigms, alongside supervised learning and unsupervised learning.

General
Relese date1960

About Reinforcement Learning


Reinforcement Learning top builders

Explore the top contributors showcasing the highest number of Reinforcement Learning app submissions within our community.

Reinforcement Learning AI technology page Hackathon projects

Discover innovative solutions crafted with Reinforcement Learning, developed by our community members during our engaging hackathons.

SmartFlow

SmartFlow

SmartFlow is an intelligent trade execution and smart order routing platform designed to help traders execute large orders more efficiently while minimizing transaction costs, market impact, and execution risk. Traditional order execution can lead to unfavorable prices, excessive slippage, and poor liquidity utilization. SmartFlow addresses these challenges by combining quantitative finance principles, execution optimization models, and interactive market simulations to evaluate trading strategies and improve execution decisions. The platform incorporates the Almgren–Chriss optimal execution framework to analyze the trade-off between market impact and execution risk. It provides an interactive dashboard for exploring order book dynamics, simulating execution strategies, monitoring risk metrics, and evaluating strategy performance. SmartFlow is designed to demonstrate how intelligent routing decisions can adapt to changing market conditions and help balance execution speed, cost efficiency, and risk exposure. Through visual analytics and scenario-based simulations, users can better understand how different execution strategies affect trading outcomes. The platform combines a React-based frontend for interactive visualization with a backend API that coordinates execution logic, market simulations, and performance analytics. Its modular architecture supports future enhancements such as multi-venue routing, machine learning-based execution decisions, and more advanced liquidity analysis. Our goal is to make quantitative execution intelligence more accessible through an explainable, interactive platform that connects financial theory with practical trading simulations.

IBM Developer Change Intelligence

IBM Developer Change Intelligence

IBM Developer Change Intelligence (DCI) addresses a common software engineering problem: seemingly small code changes can create unexpected consequences across APIs, services, databases, tests, configuration, documentation, and deployment workflows. Developers often discover these dependencies manually by searching repositories, reading documentation, tracing code, reviewing history, creating tests, and validating behavior. This fragmented process increases investigation time, review effort, regressions, and rework. DCI transforms this workflow into a single repository-aware change intelligence process. A developer starts by submitting a natural-language change request such as a feature, bug fix, refactor, dependency upgrade, or security change, together with optional constraints and acceptance criteria. DCI first converts the request into structured intent and then analyzes the selected repository, including source code, tests, documentation, configuration, dependencies, and relevant history. IBM Bob 2.0 is used as the core AI development partner to understand repository context and coordinate multiple software-engineering tasks using Agent Mode, parallel tasks, subagents, and document understanding. Specialized analysis tasks identify direct and indirect dependencies, affected components, behavioral risks, missing tests, security concerns, and documentation impact. IBM watsonx.ai is used to reason over and synthesize these findings, prioritize risks, explain the evidence, and produce an actionable implementation and validation plan. After analysis, Bob assists with implementation, test generation, documentation updates, and validation. The system then performs regression and adversarial checks against the original intent and constraints. Instead of simply declaring that a change is complete, DCI produces a Proof-Carrying Change Report containing the requested change, affected components, risks, implementation evidence, tests, verification results, remaining unverified areas, and supporting evidence. The target users are software developers, engineering teams, technical leads, and organizations maintaining complex codebases. DCI is designed to move developers from “write code and discover consequences later” to “understand, analyze, change, and verify.” Its uniqueness comes from combining repository intelligence, multi-agent workflow execution, cross-agent reasoning, impact analysis, adversarial validation, and evidence-backed verification into one continuous developer workflow.

Fresno LUX: A Living City

Fresno LUX: A Living City

Fresno LUX is a prototype for a living intelligence layer across an entire city. Fresno already contains enormous amounts of intelligence: residents know where problems exist, nonprofits know where help is needed, businesses know where opportunities exist, educators understand gaps in learning, researchers generate knowledge, and government maintains critical infrastructure and data. The problem is that much of this intelligence is fragmented across disconnected systems. Fresno LUX connects those pieces. The platform creates a shared city graph where people, organizations, resources, needs, projects, observations, experiments, and outcomes become connected nodes. Instead of simply collecting data, LUX continuously asks: What is happening? What do we know? What is missing? What can we test? What changed? A community problem can become an observable signal. That signal can become an experiment. The experiment produces evidence. Evidence changes the system's understanding. That updated understanding informs the next action. Observe → Connect → Understand → Act → Measure → Learn → Converge. The goal is to move Fresno from disconnected information toward collective intelligence—a system where knowledge can travel across boundaries and successful solutions can be discovered, tested, measured, and replicated. LUX is designed to make the invisible connections visible: the relationship between a neighborhood and its resources, between a student and educational opportunity, between a business and workforce capacity, between environmental conditions and community health, and between an idea and measurable real-world impact. This hackathon prototype demonstrates the beginning of a Living Fresno Graph: a city that can observe itself, learn from evidence, and coordinate toward better outcomes.

Reinforcement Learning-First Live Options agent

Reinforcement Learning-First Live Options agent

OptionRelay is a RL-first options research and paper-trading workflow built around a practical deployment problem: an options model trained on historical data may select a contract that has expired by the time a live decision is made. The workflow begins with a ticker-specific end-of-day Deep Q-Network (DQN) trained on an options feature matrix. The inference service evaluates eligible candidates and emits a structured HOLD or ENTER decision. For ENTER, it records the intended long-call or long-put direction plus a reference profile: option type, days to expiration (DTE), moneyness, quantity, strike/expiration references, and modeled round-trip transaction costs. A live validation monitor consumes the DQN intent and uses Alpaca APIs to retrieve active contracts for the underlying. It maps the historical profile to live candidates by option type, DTE proximity, and moneyness proximity. The monitor subscribes to live quotes and applies execution-quality gates: valid bid/ask prices, quote freshness, minimum displayed size, maximum debit, and maximum round-trip spread cost. It produces a ranked shortlist of eligible contracts for review. Alpaca MCP was also integrated with VS Code Copilot for account- and contract-level research, including live contract inspection, paper-account review, and order/position reconciliation. The project runs as a reproducible local Python CLI application through the VS Code integrated terminal. The prototype is intentionally semi-autonomous: it automates DQN inference, intent generation, live-contract resolution, and quote-quality validation, while paper-order approval remains human-supervised. During paper deployment, a pending-order/position conflict caused a sell instruction to be rejected as potentially uncovered. The workflow did not retry automatically; state was reconciled manually to avoid duplicate or unintended exposure. This is documented as an execution exception, not a DQN-policy failure.