Can a compact state preserve what matters?
EILER explores how evolving state and selective memory updates might work together in sequence models. The value of that design has to be measured against strong baselines.
INDEPENDENT AI RESEARCH & ENGINEERING
Ideactivate is a founder-operated AI research and engineering lab. We build developer infrastructure for AI-assisted software work and investigate how systems retain useful state, expose structure, and verify outcomes.
We turn technical questions into working systems, then make the assumptions and limits visible.
The current work spans structured context for coding agents, recurrent sequence-model research, and the architecture of complex creative software. These projects are at different stages; each page distinguishes implementation from hypothesis and future work.
EILER explores how evolving state and selective memory updates might work together in sequence models. The value of that design has to be measured against strong baselines.
Atrium explores repository structure, local memory, and verification tools for AI coding workflows. The goal is better task outcomes—not a smaller prompt at any cost.
FluxCut explores a modular foundation for a timeline-based media editor, where commands, project state, and rendering can evolve without becoming tangled.
The projects are independent, but share one standard: explain the mechanism, test what can be tested, and let evidence—not presentation—carry the claim.
Give coding agents structured repository context and a path to engineering feedback.
Test how evolving state and selective memory might work together in sequence models.
Build a modular media workspace with explicit timeline state, command flow, and a rendering path.
✳ Projects are developed independently and may be at different stages. Descriptions reflect design intent and current exploration, not independent validation of performance.
Atrium is the most immediately practical expression of Ideactivate’s work on AI systems: give a coding agent structured repository context and a route to observable engineering feedback.
Through an MCP-facing tool interface, Atrium is intended to work with Claude Code and other compatible coding clients. The model remains responsible for reasoning; Atrium supplies repository-specific tools and local checks. The open question is whether this structure improves real task outcomes once overhead and failure cases are counted.
Expose symbols and relationships that help a coding client navigate a repository without treating every file as an undifferentiated text block.
Keep selected project facts local and inspectable, with the repository—not cached notes—remaining the source of truth.
Return local build or test outcomes to the workflow, while being explicit that passing checks are evidence—not a guarantee of correctness.
Ideactivate is founded and operated by Shreshth Banjare. It is an independent, founder-operated lab—not a claim of a large team, institutional funding, or completed frontier-scale research.
The work is built in public where possible. Implemented behavior, research hypotheses, known limitations, and planned milestones are kept distinct so a reader can judge the work for themselves.
The aim is straightforward: make difficult ideas concrete, create useful engineering artifacts, and improve them through evaluation and feedback.
Find the work on GitHub ↗OPEN TO GOOD QUESTIONS
Open-source issues, research questions, and engineering collaborations are welcome. A clear problem statement is the best place to start.
shreshthbanjare@ideactivate.cloud ↗