Sinawy: Rethinking how software gets built.
An evolving AI-native software engineering operating model combining autonomous agents, structured workflows, quality gates, and human oversight.
1–30 October 2026
- 509
- work items delivered
- 16
- repositories
- 18 min
- median machine time per item
Observed operational results from Sinawy’s own ledger for 1–30 October 2026, not a controlled benchmark. Delivered means deployed and witnessed, not yet accepted by a person. Machine time includes failed attempts.
Explore an execution example
Sinawy is an operating model under development, not a product. Work starts as a card on a board. Each stage has to return a checked result before the next one runs. The stage that verifies never wrote the code, and the deployed commit is witnessed before anyone is told it shipped.
- 118
- items sent back by an independent stage before delivery. The gates catching faults.
- 39
- items returned for more work after delivery. A floor, because human checks can lag.
Where it stops. Browser checks run on a local build; after the deploy, Sinawy checks commit, health and pipeline. Verification is only as good as the criteria a person wrote.
| Stage | Model | Seconds |
|---|---|---|
| triage | haiku | 263 |
| spec | opus | 530 |
| plan | opus | 87 |
| implement | gpt-5.6-sol | 481 |
| review | sonnet | 19 |
| verify | opus | 452 |
| closeout | haiku | 24 |
| delivery | — | 4 |
| writeback | — | 0 |