PRODUCT · IN DEVELOPMENT · SOURCE AVAILABLE FOR STUDY

DynoGST

E-invoicing and GST compliance for Singapore on InvoiceNow (Peppol), built by AI coding agents under DynoKore Keel. DynoGST is our own product and is still being built; it is not customer work. Its source is published on GitHub so anyone can study how it is built (non-commercial use only). Formerly named DynoInvoice.

Get build updates View on GitHub How to read its commits
FROM THE RECORD · 26 OCTOBER 2026
859live requirements in Keel
1,530acceptance criteria
602tasks done
687merge requests merged
38%of merge requests sent back by an independent reviewer at least once
1,649design questions recorded; the owner answered 12% of those answered
34 minmedian from a merge request’s first commit to merge
3,301test functions in the public repository
In the week to 26 October: 762 design questions raised and 89% of them ruled without the owner; 262 merge requests merged.
Counts from the Keel record and the public repository at 26 October 2026, 00:00 SGT. Requirements and tasks count live records only. Test functions are a count, not a coverage measure.
Every commit names its task.And every task traces back to a requirement and its acceptance criteria.
Every gap becomes a question.A missing or unclear spec becomes a recorded question. Functionality and direction go to the owner; agents rule the clear-cut rest on a named practice, ask when it isn’t clear, and reuse earlier rulings.
No agent reviews its own work.An independent reviewer checks each merge request against the task’s criteria before it merges.
See eight examples, from requirement to merged code →  ·  One requirement, everything recorded about it →  ·  When a decision changes →  ·  When the spec runs out →  ·  When green isn’t enough →  ·  Why does this line exist? →  ·  Reviewing like an attacker →
THE BRIEF

A regulated system, not a demo.

DynoGST is a multi-tenant e-invoicing and GST compliance platform for Singapore: tenants that must never see each other's data, rules that come from regulation rather than taste, and an audit trail someone will eventually ask for.

We chose a system where mistakes are expensive on purpose. DynoGST is our first Dyno system, and the first we’re building in the open.

WHO DID WHAT

Stated plainly, from the record.

Keel holds DynoGST's requirements, decisions and tasks as linked records, builds each task's context, checks readiness and decides done from the merged change and CI. Who does what around it is how we chose to run the project, not part of Keel.

People

  • Set direction and priorities
  • Answered questions on functionality, exemptions and relaxed checks, each one recorded
  • Delegated routine approvals to agents, on the record

Agents

  • Drafted, examined and published requirements
  • Wrote tests to prove acceptance criteria
  • Wrote, reviewed and merged code
EVIDENCE FROM THE BUILD

Examples from our own product, showing how we work. They are not customer case studies.

Follow a requirement through the record

Anatomy of a requirementWhy does this line exist?How DynoGST is built, commit by commit

Review and test the change

Reviewing like an attackerWhen green isn't enough

Handle changes and missing decisions

When a decision changesWhen the spec runs out

DynoGST is still being built.

We intend to bring it to market when it's ready. Leave your email and we'll tell you when it's available. We use it only for that, and delete it on request to [email protected].

Want a system built this way — or to build this way yourself?

Dyno systems for your business, or Keel and our advisory for your team.

Talk to us Keel early access