Your team's hours, and the AI spend.
Two questions get asked about a project, and they take two answers. Hours are what your people put in, clocked while the work happens or typed in afterward. What the agents did is counted as spend instead, one line per model call and what it cost.
Two numbers, side by side, never added
The two sit beside each other and are never summed. What an hour of a person's time is worth against an hour of a machine's is a judgment, not a measurement. This record does not make it for you. It gives you both numbers and gets out of the way.
A clock that does not tick
Clock in, take a break, clock out. Nothing is counting anywhere: the time is worked out from when you started, whenever somebody looks. Close the tab, pick it up on another machine, let the laptop sleep, and nothing changes. Clocking out writes a draft you read and submit yourself. It never submits on your behalf.
- An hour you type in afterward is your word for it. An hour the clock timed is a measurement. Each row says which it is.
- Under thirty seconds is discarded rather than logged, and one entry stops at sixteen hours, so a timer somebody forgot cannot write a whole week.
Three ways to start it, one clock
Press Clock in on the Hours page. Type one command in the terminal where the work is happening. Or let an agent start it when it begins a job for you. All three reach the same clock, so a clock started in the terminal can be paused on the page and stopped by the agent.
- When an agent starts or stops the clock, the hours are its owner's. They land on that person's timesheet as a draft, for them to read and submit.
- An agent knows whose hours these are from its own identity, which names its owner. Nothing it sends can put hours on somebody else's sheet.
- Every start, break, and stop names the agent that did it and the owner it did it for. An hour you recorded and an hour your agent recorded can be told apart later.
- An agent can record hours. It cannot approve them, not its owner's and not anyone's. Signing off is a person's act.
What one entry holds
An hour is not a number on its own. It carries the task it was worked on, and who it belongs to. When an agent ran the clock, it also carries which agent, under whose name, between which two moments. You read it as a sentence: Jordan Alvarez's build agent clocked in on "Migrate the dispatch tables" at 09:12 and stopped at 11:40. Two hours and twenty-eight minutes, on their timesheet, as a draft for them to submit.
- Task: what was being worked on, linked to the work itself.
- Whose hours: the person the time is credited to, and whose timesheet it lands on.
- Clocked by: the person, or the agent and the owner it was acting for.
- Started and stopped: two moments, and every break between them.
- Duration: worked out from those moments, never accumulated by a ticking counter.
- Source: timed by the clock, or typed in afterward.
Nobody approves their own hours
Submitted hours go into somebody else's queue, and the platform refuses to let anyone approve their own, whatever their job title. Your agent counts as you here: it cannot approve your hours either. That costs a wait, and it is the only reason a total means anything, because approving assigns those hours to the reviewer who said yes.
- Hours still waiting on a reviewer are shown beside the totals, never inside them.
- Edit an approved hour and it loses the approval and goes back for review.
What it is, and what it is not
Hours are the one measure of human effort here that is not a stand-in for something else. A person wrote them down and a reviewer approved them. Today they are for your own team. Hours are not shown to your clients as the work goes, and they do not turn themselves into an invoice.
Hand over the software and the account of how it was made
Most delivery ends with a repository and an invoice, and everything about how the work was done lives in somebody's memory. Close an engagement here and you can produce a delivery record. It is one document, drawn from the sealed record, saying who did the work and how.
- Who did the work: approved hours by person, and every agent that ran, each named with its owner. The two are reported side by side and never blended into one figure.
- What waited for a person: every permanent step, who approved it, when, and the reason they gave. Refusals are in here too.
- What it is built from: the parts list with versions and licenses. The models allowed on the project are shown against the ones that actually ran.
- Where it came from: a link back to the sealed record the summary was drawn from. Anybody reading it can check a line rather than take your word for it.
What a delivery record is not
A delivery record says what happened on one engagement. It is not a certification, and neither TEKIMAX nor ALOS certifies anybody. Its value is that it is checkable: every line points back at the record it came from.
Ask how the hours record fits your engagement.