A camera sees an event.
A connected device reports an observation with evidence. AI can suggest whether it needs review. A detection is not automatically a problem.
Person detected → snapshot → human review
PHYSICAL WORK, CONNECTED
From something noticed
to work completed.
Kinemica brings the context, the person doing the work and the completion decision into one record.
AI helps make sense of the work. People stay responsible for what happens next.
01 / 6Received
An observation is a starting point.
A device can provide an event and snapshot. A person can instead report work directly. Neither input is permission to act.
- Device route
- Person detected · snapshot available
- Human route
- Please clear the empty carton from the workbench.
- This example follows
- The human report, not an AI-detected misplaced object.
Context recorded; no work assigned.
- 1. Context
- 2. AI assistance
- 3. Assignment
- 4. Work
- 5. Evidence
- 6. Acceptance
Illustrative workflow · fictional people and context · no live device or AI connection
Read the complete workflow
- An observation is a starting point.
A device can provide an event and snapshot. A person can instead report work directly. Neither input is permission to act.
- Device route
- Person detected · snapshot available
- Human route
- Please clear the empty carton from the workbench.
- This example follows
- The human report, not an AI-detected misplaced object.
Context recorded; no work assigned.
- A useful draft. A human decision.
AI can assist with reviewing a device snapshot or drafting a reported task. The person checks the suggestion before continuing.
- Suggested task
- Move the empty carton to the designated collection point.
- Completion requirement
- One completion photo, followed by human acceptance.
- Drafting input
- Report text only. The optional report photo is not analysed.
Draft prepared; no assignment until confirmed.
- Someone owns the next action.
An authorised person confirms the task and its assignee. Kinemica checks access and keeps the assignment with the work.
- Assigned to
- Rowan Patel · human worker
- Confirmed by
- Alex Chen · supervisor
- Where it appears
- My work, with instructions and required evidence.
Assignment recorded; notification queued.
- The person performs the task.
Rowan opens the assignment and records that work has started. Physical work happens outside the software.
- Action
- Move the empty carton to the collection point.
- Assignee
- Rowan Patel
- Next step
- Submit a completion photo for review.
Work started by the assigned person.
- Submission is not acceptance.
A completion photo is kept alongside the original context. A human can accept it or request another attempt.
- Submission
- Attempt 1 · completion photo attached
- Worker note
- The carton is at the collection point.
- Review
- Human decision required. No automatic after-photo analysis.
Evidence preserved; completion decision outstanding.
- A completed record you can revisit.
Alex accepts completion. The assignment, submission and decision remain linked. Rework would preserve the earlier attempt too.
- Accepted by
- Alex Chen · supervisor
- Record
- Context → assignment → attempt → decision
- If the assignee accepts
- Explicitly labelled self-confirmation, not independent inspection.
Human acceptance recorded with the work history.
BEYOND A MESSAGE AND A TICK
A request is easy to send.
The follow-through is harder.
A photo in one conversation. An instruction in another. A task marked done, with no clear record of who accepted it.
Kinemica connects those handovers: what needed attention, who took it on, what they submitted and the decision that followed.
TWO WAYS IN. ONE WORKFLOW.
Start with what you know.
A device observation and a human report provide different context. They lead into the same system for assigning and completing work.
A person reports the work.
Add a description and, if useful, a photo. Ask AI to draft the instruction from the text, or write it yourself. Review it before assigning.
Description + optional photo → editable task draft
One shared work record. Confirm an assignee. Perform the task. Submit evidence. Accept completion or request rework.
CLEAR RESPONSIBILITY
Someone owns the work. Someone accepts the result.
The person receiving the task sees the instruction, context and required evidence together in My work.
Explore the working product- 01
Confirm the assignment
An authorised person decides who should do the work, with permission checks before action.
- 02
See the submission
Completion evidence stays with the original context. Earlier attempts are preserved when rework is needed.
- 03
Record the decision
Acceptance names the person responsible. Accepting your own work is clearly labelled self-confirmation.
AI, PEOPLE AND MACHINES
Assistance is not authority.
AI can propose or interpret. It cannot grant itself permission, approve sensitive work or replace the human completion decision.
How access and decisions workBuild around the work, not the worker type.
The platform is designed for AI agents, people and machine workers to participate in the same workflow through defined permissions and integrations.
FOR DEVELOPERS
A clear integration surface.
Public tools for connecting to Kinemica and checking structured records.
Kinemica SDK
A TypeScript client for the Kinemica API: device heartbeats, image evidence, events and scoped work requests. Integrations do not gain policy authority.
Kinemica Verify
A Python library and CLI for structured contract, evidence-trace and signature checks. It does not inspect photographs or prove that physical work happened.
SEE KINEMICA WITH THE FOUNDER
Bring one real workflow. See how it could work.
We’ll look at how work arrives, who should receive it and what completion needs to show.