NOTES

Decisions, experiments and lessons from building.

Notes captures first-hand product decisions, AI fieldwork, market observations and lessons behind the portfolio. It is not a generic technology news feed; its job is to document knowledge earned through building.

What belongs here

Every note should have a clear first-hand angle, publication date, sources for external facts and an explicit connection to a thesis or product when relevant.

01

Product decisions

Why a capability was built, removed or delayed, and what that decision taught us.

02

AI and technology field notes

First-hand observations from tools, models, architectures and constraints encountered while building real products.

03

Market and user behavior

Hypotheses and observations about markets, distribution, pricing, trust and Persian-speaking user behavior.

04

Experiments and learning

Results from experiments, failures and changes of direction that can improve the next decision.

Published notes

Only notes that pass through the canonical content model with Published status appear here.

No first-hand notes have been published yet.

This state is intentionally empty. The page will not be filled with fabricated articles, rewritten news or placeholder content.

What happens to the legacy news archive?

Legacy content remains available for historical and search continuity, but it is editorially distinct from Notes. Old technology posts are an archive; Notes is the new first-hand publishing layer.

Notes should grow from real operating experience.

Every new note needs a first-hand angle, content owner, date, product or thesis relationship, and sources for external facts.