How we work.
These are the rules we apply to ourselves before we apply them to the platform. We rewrite this page when the practice diverges from what's written here.
- 01
Speed as discipline.
Speed is a design constraint, not a slogan. We choose tools, release cadences, and team rituals that shorten the path from decision to shipped learning while preserving the reliability expected from infrastructure.
- 02
Bounded action over vague assistance.
Agents should complete narrowly approved work while merchants retain authority. Every workflow needs a visible scope, reviewable result, audit trail, and override path.
- 03
Bilingual rigor.
English and Turkish, written fresh from intent. We never ship phrase-by-phrase translation. Each language carries the full brand voice. Turkish is not a fallback for English; it's the home market. Native review on every release. Legal documents are Turkish-first; the courtesy English summary is clearly marked as such.
- 04
Benchmarks over hype.
We do not publish a performance claim until the method, test date, comparison scope, and result can be reviewed. If we cannot measure it, we do not say it. If a number stops being true, we remove or update it.
- 05
Compound systems over isolated features.
We are testing whether connected operating workflows can become more useful because they share context. That remains a product thesis until each layer is evidenced.