Ordu Genç İş İnsanları Derneği needed a private member app, not a public social network. ~180 invite only members, six roles (root → üye), and board approvals that must survive presidency transfers without orphaning queues. Shares, sector purchase requests, and dues all needed different feeds, notification rules, and audit trails on a mobile only surface with unreliable push delivery and Turkish calendar billing.

Role based approvals, not person based queues. Post and purchase requests are approved by yk_baskan / yk_vekili roles so a presidency transfer does not break pending work.

Separate share vs purchase feeds. Event style posts and sector buying announcements never merge in the API. Different schemas, paths, and notification targets.

Deno + Yelix/Hono + MongoDB. OpenAPI first REST for a Flutter client, Zod validation end to end, Coolify self hosting, R2 for media, FCM with retry cron, Istanbul aware dues jobs.

Root Admin Ask with read only Mongo. OpenRouter chat can query association data only through a readonly URI, so ops Q&A cannot mutate production state.

• Member directory & companies. Invite only accounts, company profiles, sector tags
• Share feed. Moderated posts with media, comments, redflag filtering
• Purchase requests. Sector buying pipeline → separate announcement feed
• Dues (aidat). Monthly rows, role multipliers, partial payments, reminder cron
• Notifications. In app inbox + FCM device tokens, event level push prefs
• Governance. Soft archive for members, hard delete + audit for companies
• Admin Ask. Root only AI over read only aggregates

A small fine-tuned adapter on top of Kara Kumru (AlicanKiraz0/Kara-Kumru-v1.0-2B). Trained on a curated subset of an internal benchmark for tool routing: deciding when a query needs an external tool versus a direct model reply. Metrics below are after applying the adapter; the base weights stay unchanged.

Binary labels only: TOOL if an external tool is required, DIRECT if the model can answer without tools. Dataset language: Turkish (mixed domain). Each sample is decision-only — not tool name or arguments.

{
  "instruction": "User query here",
  "output": "TOOL"
}

Load the base checkpoint, apply this adapter for routing, then handle tool schemas and full fine-tuning elsewhere. Next step: extend the adapter so that after TOOL, the model also picks which tool to call.

A location-based chat application and information platform specifically designed for the Ordu province in Turkey. The project provides local services including transportation, news, places search, and regional information through an AI-powered chat interface. Built as a full-stack application with separate backend and frontend components.

Backend (Deno + Hono) — API server with chat functionality and data crawling capabilities.

Frontend (Astro) — Web interface with mobile app capabilities through Capacitor.

Database — MongoDB with Mongoose ODM for flexible data storage.

AI Integration — OpenRouter for chat functionality with tool-based pipeline.

• AI Chat Interface — Core functionality with tool-based pipeline
• Local Transportation — Public transport routes (Kentkart integration)
• Places Search — Mapping and location services
• Local News — Aggregated regional news
• Inter-district Transport — OrduBirlik integration
• Parking Availability — Real-time parking information
• Tourist Attractions — Curated local points of interest
• Bus Routes — Comprehensive transportation information
• Pharmacy Services — On-duty pharmacy schedules
• Restaurant Recommendations — Curated local dining options

The system includes a comprehensive data pipeline with web crawling for local information, scheduled data updates, and MongoDB storage with various data models. This ensures real-time and accurate information for all local services.

Native Android and iOS applications through Capacitor with geolocation services and native app distribution. The mobile apps provide the full functionality of the web platform with optimized mobile experience.