میثاق misaghio — home
Building in public فا نسخهٔ فارسی

Work log, live edition

I build ideas, then find out if they work.

I'm Misagh. I like taking ideas, building them with AI tools, and turning them into products that actually work.

This is my work log: what I've built, what's half-finished, and what still only exists on paper.

Work log / 01

Three projects,
three stages.

Each project is at a different point. For every one I've written down what exists, what doesn't yet, and why I made the choices I did.

The 3D scenes on this page are conceptual models, not product screenshots. Each project gets its own scene; the text carries its real stage.

Web product, panel and infrastructure

Matisco

In development

Matisco is an attempt to build a web product with AI assistance: a panel and sign-in, an API, a database. The goal was never to ship it all at once — it's that each layer works and can be tested once it's built.

Most of the work so far is foundation: sessions, part of the security layer, and the connection between the panel and the API. The core features aren't finished, so I don't present this as a finished product or a public demo.

Built

  • First web panel
  • Sign-in and session handling
  • Part of the security layer, and its testing
  • API and PostgreSQL infrastructure

Next

  • Core product features
  • Testing real user flows
  • Hardening the security layer

Conceptual illustration

A 3D architecture model, not a product screenshot. Four layers are built and tested one at a time.

  • web panelinterface, sign-in, sessions
  • APIpanel to server logic
  • dataPostgreSQL
  • securitystill being hardened

The panel is private for now. I've left its address off this page rather than linking something a visitor can't open.

View 02Layered architecture

Telegram bot, running service

The Aster AI bot

Running

A Telegram bot running on an AWS server. It receives messages, keeps a conversation going, and answers with a language model — with a fallback path for when a model stops responding.

What's actually built and tested: the Python service, conversation handling, model failover on errors, pause and resume commands for the admin, and running it under systemd. That's a list of finished work, not a wishlist.

Built

  • Python service and conversation handling
  • Model failover on errors
  • Pause and resume commands
  • Running under systemd

Next

  • Better answer quality
  • Error and latency monitoring
  • A clear path to public use

Conceptual diagram

The message path through the service; not a screenshot or a real bot transcript. Each node is part of the architecture, not a marketing claim.

  • Telegrammessages in and out
  • conversationkeeps the thread
  • primary modelanswers the message
  • fallback modelwhen the first fails
  • systemdkeeps it running

The bot isn't publicly advertised, and I make no claims about user numbers or scale. If you want to ask about it, message me on Telegram.

View 03Signal network

Game, world design

Mortad بازی مرتد

Design and prototyping

Worlds, progression, and building an empire

Mortad started with a question: how do you build a world that changes shape in response to how the player progresses? Right now it's design work and small prototypes, not a game anyone can play.

Core idea
The world reacts to the player's decisions, not only to progression numbers.
Still open
The core loop: what meaningful decision exists on each turn.
Next step
Build one small, complete cycle: a goal, a decision, a result.
Status
Design and prototyping. There's no playable build to show.

Conceptual illustration

A territory network and a supply line: a picture of the design direction, not the game's actual state.

  • Your territory
  • Rival territory
  • Contested

There are no screenshots of the game here because there's nothing to show yet. This panel is deliberately a design notebook, not a store page.

View 04Territory and route

Behind the desk / 02

About

This isn't a CV. It's an explanation of why I make these things and how I move through them.

I'm Misagh. I like building ideas with AI tools and turning them into real products.

An idea is only a guess until it's built. AI tools let me prototype faster than I could before, test things, and find out which part actually works. But speed of building doesn't replace making decisions.

This site is a work log, not a portfolio of claims. Each project is described at its real stage: what's finished and what isn't. If something here doesn't match reality, tell me and I'll fix it.

A small tool / 03

Workshop

A small tool that applies the same method to your idea. Pick two options and get one concrete next step — no predictions, no promises.

From idea to next step

Choose what kind of idea it is and where you are. The output is one practical step and a copyable summary you can drop into your notes.

Kind of idea
Current stage

First step

Get the problem into one sentence

Before writing any code, decide who this product makes something easier for. If your sentence says "everyone", it isn't specific yet.

  • Choose one specific group of users.
  • Review three similar products and write down your difference.
  • Sketch a single core user path on paper.

Copyable summary

Idea: a web product. Stage: just an idea. Next step: write the problem statement for one specific group, review three similar products, and sketch a single core user path.

Contact / 04

Let's talk.

For a collaboration, a question about one of these projects, or just an idea worth trading, send a message. Both routes below are real, and I answer them myself.