Actum Developer Telemetry
Proof of work for the agentic software era.
Install Actum as an Agent Plugin in your coding agent.
Work normally while Actum distinguishes human attention, autonomous agent execution, and delivered software — then turns that telemetry into cryptographically verifiable proof.
One plugin. Compatible agent workflows. Verifiable by Actum.
Actum Developer Telemetry
installed capability
Human attention
3h 42m
Agent execution
7h 51m
Elapsed session
5h 07m
Model compute
4.8M tokens
31
agent runs
12
builds
7
commits
Install once. Work normally.
Telemetry without another workflow.
No separate timer. No manual project switching. No new development environment.
Install the Actum Agent Plugin through your coding agent’s plugin experience, enable the capabilities you want, and continue developing normally.
Add the Actum Agent Plugin
Choose what Actum can observe
Use your coding agent normally
Actum constructs the evidence automatically.
Built as an Agent Plugin
A capability your coding agent can carry.
Actum Developer Telemetry is packaged using the Agent Plugins standard.
Instead of building a different proprietary integration for every coding agent, Actum packages its telemetry capabilities as a portable agent plugin composed of standard agent-facing capabilities and MCP services.
Agent Plugins
distribute the capability
MCP
carries the tool interactions
Actum
verifies the resulting acts
The coding agent does not become the trusted source of truth merely because the plugin runs within its workflow. Cryptographic evidence and verification remain separate.
Actum Agent Plugin
- ├── Telemetry Skill
- ├── Project Attribution
- ├── Metering Policy
- ├── Proof Generation
- └── MCP Server
Portable across agent workflows
Your telemetry shouldn’t belong to your coding agent.
Developers increasingly move between coding agents, IDEs, terminals, repositories, and models. Their verifiable work history should remain portable.
The Actum Agent Plugin provides a consistent telemetry capability wherever the Agent Plugins standard is supported.
Agents can change. Evidence remains continuous.
Control from the agent
Installed where you work. Controlled where you work.
Manage the plugin through your coding agent’s plugin UI rather than learning an entirely separate management system.
Developer agency and transparency, by default.
Collection
[✓] Human interaction
[✓] Agent execution
[✓] Git events
[✓] Build/test events
[✓] Model usage
Current project
actum-network
Evidence
Metering
The problem
The stopwatch is broken.
- —An agent can work while its developer works elsewhere.
- —Several agents can execute simultaneously.
- —Waiting may or may not require human attention.
- —A five-minute code change can represent an hour of investigation.
- —A million generated tokens can result in zero accepted code.
- —A Git commit records an artifact, not the time required to produce it.
Actum observes all of these signals without pretending any single signal equals “work.”
Three different clocks
Measure what actually happened.
Human Attention
3h 18m
Time during which the developer was actively engaged with the project.
- editing
- prompting
- reviewing
- debugging
- reading agent output
- running commands
- making decisions
Agent Execution
7h 51m
Autonomous computation performed by coding agents on behalf of the project.
- coding
- testing
- reviewing
- analysis
- background agent tasks
Project Elapsed Time
5h 07m
The wall-clock span occupied by the overall development workflow.
These numbers are intentionally different. None of them substitutes for another.
Automatic project attribution
No timers to start. Nothing to remember.
Repositories and working directories establish project context.
Meaningful interaction begins an attention interval.
Changing project context changes attribution.
An autonomous agent continuing to execute does not automatically keep the human-attention clock running.
Agent-aware time
When the agent works, your clock doesn’t have to.
Human attention
13 min
Agent execution
12 min
Project span
31 min
More than hours
Time is only one dimension of work.
Human attention
3h 42m
Agent execution
7h 51m
LLM compute
4.8M tokens
Agent runs
31
Builds
12
Commits
7
Accepted agent changes
81%
Tokens represent compute consumption.
Git represents artifact history.
Agent runtime represents autonomous execution.
Interaction represents human engagement.
Actum keeps these concepts separate and links them through provenance — no tokens or lines of code converted into fake productivity scores.
Verifiable by design
Telemetry you don’t have to take on trust.
Traditional timesheets are assertions. Actum produces evidence.
Development events are signed locally and assembled into cryptographic activity epochs. Their commitments are anchored to Actum, creating a tamper-evident record without requiring proprietary code or private prompts to become public.
Trust boundary
Installed in the agent. Trust anchored elsewhere.
Installing an agent plugin does not mean handing the agent authority over your record of work. The plugin proposes acts; the local trust layer decides what becomes evidence.
The agent can participate in the evidence. It cannot rewrite the evidence.
Coding Agent
Local Trust Boundary
Actum
Private by default
Prove the work. Keep the work private.
Actum does not require publishing:
Detailed telemetry stays local or encrypted. Actum receives cryptographic commitments.
Selective disclosure and zero-knowledge proofs allow specific claims to be verified later without exposing the underlying development history.
Cryptographic commitment
0x7a94…ef21
Proof of non-double-billing
Prove an hour was only billed once.
Consultants and agencies can prove that billed human attention does not overlap across clients — without revealing who their other clients are.
Client A
Client B
Zero-knowledge claim
“No billable human-attention intervals overlap.”
From prompt to commit
Provenance for agentic development.
Human
Prompt
Agent Plugin
Observed act
Agent
Execution
Artifact
Patch
Human
Review
System
Tests
Git
Commit
Actum
ContributionProof
Git already provides a cryptographic artifact boundary.
Actum connects agent execution and human interaction to that resulting artifact, producing provenance from intent to delivered code.
Three proofs
Three primitives for verifiable software work.
AttentionProof
Proves attributable human attention.
3h 42m
ComputeProof
Proves attributable agent/model computation.
7h 51m
4.8M tokens
ContributionProof
Links human and agent activity to a resulting artifact.
commit
8f3a1c7
Observe → Commit → Derive → Prove → Settle
Observe
The Agent Plugin participates in the development workflow and collects permitted evidence.
Commit
The local trust layer signs events and constructs cryptographic activity epochs.
Derive
A versioned metering policy converts evidence into claims.
Prove
Generate AttentionProofs, ComputeProofs, and ContributionProofs.
Settle
Use verified work as the basis for invoices, contracts, payouts, or autonomous settlement.
Evidence is observed. Claims are derived. Proof makes them verifiable.
Verified invoice
A work statement that verifies itself.
Engineering engagement
August 2026
Double-billing check
No overlapping billable attention
✓ ZK verified
One plugin, many agents
Install the capability, not another integration.
As coding environments adopt the Agent Plugins standard, the same Actum capability can be installed and controlled through their native plugin experience.
No proprietary telemetry integration needs to define the developer’s work history.
The agent is replaceable. The proof history is yours.
Actum Agent Plugin
Developer / plugin
Open capability. Standard packaging. Verifiable output.
actum-developer-telemetry/
├── plugin.json
├── mcp.json
└── skills/
├── telemetry/
├── project-attribution/
├── prove-work/
└── verify-work/No credentials or secrets live in the plugin manifest.
Installation itself does not grant access to private evidence.
Developer
“Show me my work on Project Alpha today.”
Actum
Human attention: 3h 42m
Agent execution: 7h 51m
Model compute: 4.8M tokens
Commits: 7
Evidence epochs: 74 · committed to Actum
Actum Developer Telemetry
Install the plugin. Work normally. Prove the work.
One plugin. Compatible agent workflows. Verifiable by Actum.