See exactly where every task stands. Live.
Task trackers show what people say. Actmark reads every push and shows what is actually in the code, checked against each task, with nobody updating anything.
Sign-in
Due 2026-11-28 · 0 of 1 task done
Founder's words (fixed once saved)
Let people log in with their Google account.
Technical version
Clause 1 Sign-in page renders a Continue with Google button
Anchored to
Done. Matched automatically to commit on Nov 10 (components/SignInButton.tsx).
Clause 2 GET /auth/callback exchanges the Google code for a session
Anchored to
Done. Matched automatically to commit on Nov 11 (app/auth/callback/route.ts).
Clause 3 users table has a unique google_id column
Anchored to
Done. Matched automatically to commit on Nov 12 (db/schema.ts).
Clause 4 Session cookie is set on callback and read on return visits
Anchored to
Waiting for a commit that does this.
Three steps. Then it runs itself.
Setup is one GitHub App install, on the repositories you choose. After that, your only job is saying what you want next.
Step 01
Say what you want.
In your own words: “Let people log in with their Google account.” Actmark turns it into a short list of what has to be in the code.
Step 02
Your engineer signs off on what done means.
They read the list, fix anything it got wrong and approve it. Nobody argues about it later.
Step 03
Every push moves the bar.
When a commit builds one of the items, Actmark ticks it and names the file. If nothing was pushed, the bar doesn’t move.
You ask how it’s going. You get a guess.
A status is something a person typed, or a ticket someone dragged. It’s usually honest. It’s still a guess, and “80% there” doesn’t tell you what’s left.
Actmark shows you exactly where each task stands: which parts are in the code, which aren’t yet, and the commit behind each one. Nobody has to say a word.
| Week | What you were told | What Actmark shows |
|---|---|---|
| “Going well. About 80% there.” | 1 of 4 in the code In the code: sign-in button. Not yet: google callback, users table, session cookie. | |
| “Nearly done. Maybe 85%.” | 1 of 4 in the code In the code: sign-in button. Not yet: google callback, users table, session cookie. | |
| “Almost there. 90%.” | 2 of 4 in the code In the code: sign-in button, google callback. Not yet: users table, session cookie. |
Status is what someone said.Progress is what was pushed.
Engineers: done is written down before you start.
You can veto a tool like this, and you should if it’s unfair to you. Here is what Actmark does and doesn’t do.
You sign off on what done means.
Each task arrives with a short list of what has to be in the code. Edit it or approve it. Nothing is counted until you do, and the person running the project can’t approve it for you. Nobody argues about it later.
It can read. It can’t write.
The GitHub App has read-only access to code and pull requests, on the repositories your team chooses. It can’t push, merge or comment.
It is not surveillance.
Actmark tracks tasks, not people. There are no productivity scores and no rankings of who did how much.
You work the way you already do.
Nothing to install, no status to fill in, no extra meeting. You write code and push it. Free for engineers.
Sign-in
Due 2026-11-28 · 0 of 1 task done
Founder's words (fixed once saved)
Let people log in with their Google account.
Technical version
Clause 1 Sign-in page renders a Continue with Google button v1
Anchored to
Waiting for a commit that does this.
Clause 2 GET /auth/callback exchanges the Google code for a session v1
Anchored to
Waiting for a commit that does this.