DEV Community: Rasika Chavan

OBLIGATION-ZERO

Rasika Chavan — Mon, 26 Oct 2026 06:01:47 +0000

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady.

What I Built

Have you ever opened a long document just to find one important deadline buried somewhere in the text?

That is the problem I wanted to tackle with Obligation Zero — an AI-powered document analysis application that helps turn document content into actionable tasks.

Instead of manually scanning documents for every obligation, users can upload supported files and let the application identify important tasks, deadlines, and relevant evidence.

What can it do?

📄 Upload documents in PDF, DOCX, TXT, Markdown, CSV, and EML formats.
🔍 Extract obligations, tasks, and deadlines from document content.
🤖 Analyse document text using an Ollama-hosted AI model.
✍️ Generate draft replies to help users respond to obligations.
✅ Review extracted information and use it to plan their next steps.

The goal is simple: spend less time searching through documents and more time acting on what matters.

Demo

🌐 Live Application: https://obligation-zero.onrender.com/

🎥 Video Demo: https://youtu.be/51GEAb_vmmQ

Try the live application and see how a document can become a more actionable set of tasks.

Code

💻 GitHub Repository: https://github.com/rasikachavan13/Obligation-Zero.git

The project is built as a full-stack application, with a frontend, an Express backend, and AI-powered document analysis.

Note: Replace the GitHub profile link above with your exact Obligation Zero repository URL if the repository has a different name.

How I Built It

I built Obligation Zero as a full-stack web application, combining document processing, backend APIs, and open-source AI.

Technology stack

Frontend: Vite-based web application
Backend: Node.js and Express
AI inference: Ollama Cloud
AI model: Gemma, configured through Ollama
Document processing: Text extraction for supported file formats
Deployment: Render

How the workflow works

Upload: The user uploads a supported document.
Extract: The backend extracts available text from the document.
Analyse: The application sends the extracted content for AI-powered analysis.
Identify: The analysis identifies obligations, tasks, deadlines, and supporting evidence.
Draft: Users can generate draft replies to help them respond.
Review: Users review the results before deciding what action to take.

I also worked on fallback behaviour so that the application can provide rule-based suggestions when AI analysis fails. This is important because a useful application should handle failures instead of leaving users with a broken screen.

Scanned documents requiring OCR are not currently supported by the text-extraction workflow.

Why Does Open Innovation Matter?

Open innovation matters because it makes AI experimentation more accessible to developers who are still learning and building.

For Obligation Zero, using Gemma through Ollama gave me a way to explore AI-powered document analysis without making the entire application dependent on a proprietary, paid model API.

It also helped me understand more than just prompting a model. I had to work with backend integration, API authentication, document extraction, error handling, deployment, and the difference between a model being reachable and a model actually producing useful results.

Open tools make it easier to experiment, inspect workflows, adapt implementations, and learn by building. They help individual developers turn ideas into working applications without needing to build every component from scratch.

For me, open innovation is about having the freedom to experiment, learn, and build something useful while sharing that work with the developer community.

My Agent Session

I developed and debugged the application through an iterative workflow, testing document extraction, task and deadline identification, evidence references, saved draft replies, and persistence after refreshing the application.

I don't have a verified DevRelay agent-session link to share, so I'm leaving this optional section without an invented link.

The Lazy Payoff

The intended payoff is reducing the manual effort involved in reading lengthy documents and locating important obligations and deadlines.

Instead of searching through a document repeatedly, users can start with extracted tasks and deadlines, then review the relevant evidence.

I have built and deployed the application, but I haven't measured a reliable time-saving figure yet. I would like to test it with real users and compare the time spent reviewing documents manually against the time spent using Obligation Zero.

The goal isn't to remove human judgement. It's to reduce repetitive searching so people can focus on decisions and action.

Prize Categories

My submission is focused on the open-source AI theme, using Gemma through Ollama as part of the application.

I'll include any additional partner categories only where the project meets the challenge's eligibility requirements.

Thanks for checking out Obligation Zero! 🚀

If you have suggestions for improving document analysis, deadline extraction, or the overall workflow, I'd love to hear them in the comments.

Build steadily. Make useful things. Keep learning.

Build For a Friend

Rasika Chavan — Sat, 17 Oct 2026 16:44:23 +0000

This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend

What I Built

Demo

Code

How I Built It

Why Does Open Innovation Matter?

My Agent Session

Prize Categories

TouchGrass AI 🌿 — Less Screen. More World!

Rasika Chavan — Sat, 10 Oct 2026 20:07:11 +0000

This is a submission for the Hacktoberfest Open-Source AI Challenge. Week 1: Touch Grass

What I Built

What if AI encouraged us to spend less time online and more time experiencing the real world?

That question inspired me to build TouchGrass AI — an AI-powered outdoor mission generator designed to help people take breaks from their screens and reconnect with the world around them.

As students and developers, we can easily spend hours sitting in front of our laptops. Between coding, studying, debugging, and scrolling, sometimes we need a little push to step outside.

Instead of building another AI tool that keeps users engaged with a screen, I wanted to explore a different idea: using AI to help people step away from technology.

TouchGrass AI turns the simple intention of going outside into a personalised, achievable mission.

Users can customise their experience based on:

⏱️ Time: How long they want to spend outdoors.
⚡ Energy: How energetic they feel.
🌿 Interests: What kind of activities they enjoy.
🧍 Company: Whether they want to go solo or spend time with others.

The application uses these preferences to generate an outdoor mission. Users can then complete the activity and track their progress through the app's gamified experience.

The idea is simple: make taking a break feel less like another task and more like a small adventure.

Who is it for?

TouchGrass AI is for students, developers, remote workers, and anyone who spends a lot of time online and wants a gentle reminder to move, explore, and experience life beyond a screen.

My guiding philosophy:

Less screen. More world. 🍃

Demo

🌐 Live application:

touchgrass-ai-fq0a.onrender.com

🎥 Video demonstration:

Code

💻 GitHub repository:

rasikachavan13 / -TouchGrass-AI

TouchGrass AI — AI that gives you a reason to leave the screen. A local-first AI companion that creates personalized, screen-free outdoor missions based on your time, energy, interests, and company. Built with React, Express, Ollama, Gemma 3, Backboard, and Tinker.

🌱 TouchGrass AI

AI that gives you a reason to leave the screen.

TouchGrass AI is a local-first outdoor activity companion that uses AI to generate personalized, real-world missions based on your available time, energy, interests, and company.

Instead of keeping users inside another chatbot, TouchGrass AI encourages them to go outside, move, observe, explore, and interact with the physical world.

🌐 Live Demo: https://touchgrass-ai-fq0a.onrender.com

✨ What It Does

Tell TouchGrass AI:

⏱️ How much time you have
⚡ Your current energy level
🌿 What interests you
👥 Whether you're going alone or with others

The AI generates an outdoor mission tailored to your preferences.

Each mission includes:

A memorable title
A short description

Three practical steps

Suggested items to bring

A real-world observation challenge

Example Mission

Quiet Campus Explorer

Turn an ordinary walk into a deliberate exploration by observing environmental details, noticing patterns in nature, and experiencing your surroundings…

View on GitHub

The project is publicly available, and the repository contains the application code and project documentation.

How I Built It

TouchGrass AI evolved from a simple concept into a full-stack application involving frontend development, backend APIs, AI integration, memory experiments, local inference, and cloud deployment.

The Technology Stack

React & Vite: Building the interactive frontend and build tooling.
CSS: Styling the application and its responsive, nature-inspired interface.
Node.js & Express.js: Building the backend and API endpoints.
Gemma 3 4B & Ollama: An open-weight language model used in local AI experimentation, run locally.
Backboard: Experimenting with AI memory and saving user preferences.

Gemini API: Exploring hosted AI generation for the production integration.
Tinker: Exploring the model fine-tuning and evaluation workflow separately from the main application.

Render: Deploying the web application and backend.

localStorage: Persisting supported user progress in the browser.

1. Frontend: Making the experience approachable

I used React and Vite to build the user interface, with CSS to create a minimal, nature-inspired visual identity. The interface lets users select their preferences, request a mission, and interact with their progress without demanding constant attention like a productivity dashboard.

2. Backend: Connecting the application to AI

The Node.js and Express backend handles requests from the frontend and provides the API layer for mission generation.

The intended workflow is:

The user selects their preferences.
The frontend sends these preferences to the backend.
The backend communicates with the configured model provider.
The generated mission is returned to the frontend.

Building this flow taught me that an AI application is not just a single prompt; the frontend, backend, model runtime, API configuration, and error handling must all work together.

3. Open-weight AI: Gemma 3 4B and Ollama

One of the most educational parts of this project was experimenting with Gemma 3 4B through Ollama. Running the model locally helped me understand how open-weight models can be integrated without relying exclusively on a hosted inference API.

Debugging local model configuration and backend integration errors helped me understand the deeper connection between model runtimes and Express APIs.

4. Backboard: Exploring AI memory

I also experimented with Backboard to explore how an AI application could retain useful context about a user. In the backend, I implemented preference-saving functionality that records details such as selected time, energy, interests, and company preferences.

5. Tinker & Gemini API

Alongside local Gemma and Ollama experiments, I worked on a Gemini API integration for hosted AI generation and explored Tinker separately for model fine-tuning and evaluation workflows.

6. Render Deployment

I deployed the application using Render, making the project accessible through a public URL. Deployment introduced a great lesson: a site loading successfully doesn't mean every backend integration works out-of-the-box; AI generation must always be tested end-to-end in production.

Why Does Open Innovation Matter?

For me, open innovation is about having the freedom to experiment, learn, adapt, and build beyond the boundaries of a single closed service. Working with open-source tools and open-weight models provides:

Learning through implementation: Seeing how runtimes, backends, and frontends communicate.
Flexibility: Choosing between local inference and hosted APIs based on the problem.
Accessibility: Creating opportunities for students and independent developers to build practical AI projects.

✨ What It Does

Tell TouchGrass AI:

⏱️ How much time do you have?
⚡ Your current energy level
🌿 What interests you
👥 Whether you're going alone or with others

The AI generates an outdoor mission tailored to your preferences.

Each mission includes:

A memorable title
A short description

Three practical steps

Suggested items to bring

A real-world observation challenge

Example Mission

Quiet Campus Explorer

Turn an ordinary walk into a deliberate exploration by observing environmental details, noticing patterns in nature, and experiencing your surroundings without digital distractions.

🌿 Core Features

Feature	Description
Personalised missions	Generate outdoor activities from user-selected preferences.
Local AI inference	Run missions locally using Ollama and Gemma 3 4B.
Cloud AI generation	Use Gemini through the deployed backend.
Memory-powered personalisation	Backboard stores and retrieves outdoor preference memories.
Outside Mode	A distraction-free experience designed around completing the mission.
Mission history	Review previously generated missions.
TouchGrass Score	Earn points for completing missions.
Streaks and milestones	Track progress and encourage consistent outdoor activity.
Local persistence	Save progress in the browser using `localStorage`.

🧠 AI Architecture

Local Development

The local setup supports inference on the user's machine after the required model has been downloaded. Mission history and score are stored separately in browser localStorage.

Production Deployment

The deployed application uses Gemini for cloud-based mission generation. The local Ollama setup is used for local development and testing; it is not automatically available to the cloud deployment.

🛠️ Tech Stack

Component	Technology
Frontend	React, Vite, CSS
Backend	Node.js, Express
Local inference	Ollama
Local model	Gemma 3 4B
Cloud inference	Gemini API
Preference memory	Backboard
Fine-tuning experiment	Tinker, LoRA
Deployment	Render
Browser persistence	localStorage

🧠 Tinker Fine-Tuning Experiment

TouchGrass AI also includes a domain-specific fine-tuning experiment using Tinker.

Fine-Tuning Setup

Base model: Qwen/Qwen3.5-4B
Fine-tuning method: LoRA
LoRA rank: 16
Training examples: 8
Training steps: 10
Checkpoint: touchgrass-v1
Checkpoint type: Sampler weights

The training examples were designed to encourage the behavior required by TouchGrass AI:

Screen-free outdoor activities
Safe, practical real-world experiences
Minimal equipment requirements
Specific, actionable instructions
Physical-world observation challenges
No unnecessary dependence on apps, internet access, photos, or digital navigation

Why Fine-Tune?

A general-purpose model can suggest outdoor activities, but TouchGrass AI has a more specific goal: generate practical missions that encourage users to disconnect from their screens.

The experiment explored whether a small, domain-specific dataset could encourage more consistent adherence to these requirements.

AI should create a reason to leave the screen, not another reason to stay on it.

Evaluation and Limitations

The fine-tuned model was compared with base-model generations using the same prompts.

In the observed examples, the fine-tuned model showed stronger adherence to some screen-free and outdoor-activity constraints. However, the results were not consistently better across every dimension, including creativity and specificity.

The experiment is preliminary. With only eight training examples and ten training steps, it does not establish a general performance improvement. A larger dataset, repeatable evaluation set, and quantitative measurements would be needed to support stronger conclusions.

The fine-tuned checkpoint is a separate experiment and is not the model currently serving missions in the live application.

🔓 Why Local-First and Open Innovation?

TouchGrass AI explores how locally run AI can support a more privacy-conscious, accessible experience.

Local inference: Run the local version without sending mission prompts to a cloud AI provider.
Privacy-conscious design: Keep local mission history and score in browser storage.
Reduced API dependence: Local generation does not require a paid cloud inference request once the model is available.
Model experimentation: Explore different models and specialized fine-tuning approaches.
Practical AI: Use AI to encourage real-world activity rather than maximize screen time.

Ollama provides the local inference tooling, while Gemma 3 is an open-weight model distributed under its applicable license. These are distinct from the separate cloud Gemini integration.

Run Locally

Prerequisites

Node.js and npm
Ollama
Git

1. Clone the repository

git clone https://github.com/rasikachavan13/-TouchGrass-AI.git
cd -TouchGrass-AI

2. Download the local model

ollama pull gemma3:4b

Make sure Ollama is running before generating missions locally.

3. Configure the backend

cd backend
npm install

Create a .env file using .env.example as a reference.

Configure the local model and, if desired, your Backboard credentials:

PORT=5000
FRONTEND_URL=http://localhost:5173

OLLAMA_HOST=http://127.0.0.1:11434
OLLAMA_MODEL=gemma3:4b

BACKBOARD_API_KEY=
BACKBOARD_ASSISTANT_ID=

GEMINI_API_KEY=
GEMINI_MODEL=gemini-3.8-flash

Start the backend:

npm start

4. Configure the frontend

Open a second terminal:

cd frontend
npm install

Create frontend/.env with:

VITE_API_URL=http://localhost:5000

Start the frontend:

npm run dev

Open the local URL printed by Vite, usually http://localhost:5173.

Prize Categories

My project explored open-weight AI through Gemma 3 4B and Ollama, and I used Render to host the application. I will only claim specific partner prize categories if the implementation meets their official requirements.

Final Thoughts

TouchGrass AI began with a small question: could technology help us become more intentional about using technology itself?

Not every experiment became part of the production application, and not every integration worked on the first try, but those challenges formed the core of the learning process.

What would you build if AI's purpose were to help people reconnect with the real world? Let me know in the comments below! 👇

Starting my developer journey — one commit at a time.

Rasika Chavan — Sun, 04 Oct 2026 06:49:34 +0000

I’m a CSE student exploring DSA, AI/ML, Web Development & Open Source.

Currently:
→ Learning DSA with C++
→ Building projects with AI/ML + Web
→ Improving my GitHub every day
→ Exploring hackathons & open source
→ Learning by building, breaking, and rebuilding.

DEV Community: Rasika Chavan

OBLIGATION-ZERO

What I Built

What can it do?

Demo

Code

How I Built It

Technology stack

How the workflow works

Why Does Open Innovation Matter?

My Agent Session

The Lazy Payoff

Prize Categories

Build For a Friend

What I Built

Demo

Code

How I Built It

Why Does Open Innovation Matter?

My Agent Session

Prize Categories

TouchGrass AI 🌿 — Less Screen. More World!

What I Built

Who is it for?

Demo

Code

rasikachavan13 / -TouchGrass-AI

**TouchGrass AI — AI that gives you a reason to leave the screen.** A local-first AI companion that creates personalized, screen-free outdoor missions based on your time, energy, interests, and company. Built with React, Express, Ollama, Gemma 3, Backboard, and Tinker.

🌱 TouchGrass AI

✨ What It Does

Example Mission

How I Built It

The Technology Stack

1. Frontend: Making the experience approachable

2. Backend: Connecting the application to AI

3. Open-weight AI: Gemma 3 4B and Ollama

4. Backboard: Exploring AI memory

5. Tinker & Gemini API

6. Render Deployment

Why Does Open Innovation Matter?

✨ What It Does

Example Mission

🌿 Core Features

🧠 AI Architecture

Local Development

Production Deployment

🛠️ Tech Stack

🧠 Tinker Fine-Tuning Experiment

Fine-Tuning Setup

Why Fine-Tune?

Evaluation and Limitations

🔓 Why Local-First and Open Innovation?

Run Locally

Prerequisites

1. Clone the repository

2. Download the local model

3. Configure the backend

4. Configure the frontend

Prize Categories

Final Thoughts

Starting my developer journey — one commit at a time.

TouchGrass AI — AI that gives you a reason to leave the screen. A local-first AI companion that creates personalized, screen-free outdoor missions based on your time, energy, interests, and company. Built with React, Express, Ollama, Gemma 3, Backboard, and Tinker.