A
Alder Robotics
The maker
Hana (design lead), Kofi (test), Mei (production)
Owns the run. Sees the whole plan, every supplier's dates and what's holding up the line, in its own Taskivities.
Solutions · Manufacturing
Your whole supply chain on one plan.
You and every supplier keep your own Taskivities. The agent plans the run, sends each supplier its part, and follows up every day until the line starts.
Who's on the run
Each company runs its own Taskivities with its own people. The agent works across all of them.
P
Precision Parts
Machining supplier
Luis, Ana and Jon
Keeps its own Taskivities and its own shifts. Gets only its part of the run, with dates, and ticks it off from the shop floor.
+
Every other supplier
Finishing, electronics, logistics
Added as they're qualified
Connect their own Taskivities, or add their people to yours. The agent plans across all of them the same way.
What the agent takes off your plate
The follow-up that keeps a run on time: done every day, written down every time.
01
Plans the run
From the parts, the suppliers and the start date: tasks, owners, working days and what has to finish before what.
02
Gives each supplier its part
Every task lands in the right company's Taskivities, assigned to the right person, with its date and what it waits on.
03
Does the morning round
Reads every open task on every instance at the start of the shift and spots what's late, what's blocked and what's about to be.
04
Chases revisions and sign-offs
Drawing revisions, first-article reports, approvals: it asks whoever owns them, marks them urgent and tells the supplier that's waiting.
05
Re-plans when parts slip
It moves everything that depends on a late part and tells everyone whose date changed, before the line finds out.
06
Covers shifts
Someone's out? Their task goes to someone on the same run, with a note saying why, and the plan carries on.
Tell it what the run is
Write it the way you'd brief a program manager. The agent turns it into a plan and sends it out.
Taskivities agent
Connected to 2 instances
Plan the X2 pilot run for Nov 30. We freeze the design and release rev C drawings, build the test fixture, then run assembly and QA. Precision Parts does tooling, first articles and anodizing. No machining before rev C.
Done. The plan has 8 tasks over 11 working days, with the pilot run on Nov 30. I've sent Alder 5 tasks and Precision Parts 3, and I'll check in at the start of every shift.
- Scheduled 8 tasks back from Nov 30, working days only
- Made first articles wait on rev C and the tooling setup
- Assigned Hana, Kofi and Mei at Alder; Luis, Ana and Jon at Precision Parts
- Set a daily round at 7:30 and a Friday digest with machine hours
What your teams see
Nothing new to learn. The production lead sees the week on the board; the machinist sees today on their phone, with the agent's note on top.
Alder Robotics · Taskivities
A
Alder Robotics
Live
XP
X2 pilot run
2 done · 7 not finished · 1 late
TodayWeekBoard
This weekNov 16 – 20
AC
My day
3 open today · Precision Parts
TodayThu, Nov 19
Assigned to me
First-article parts2
CMM program check
Fixture plate
Shift handover notes
P
Precision PartsnowTaskivities agent on First-article partsRev C is released. Machining can start. New date: Nov 25.
A week with the agent
-
Mon · 7:30
Morning round
Reads every open task on both instances. The design freeze is done on time, so it tells Kofi the test fixture can start.
-
Tue · 9:40
Spots a blocker
Ana comments that the drawings are still at rev B. The agent marks Hana's release task urgent and asks Hana for a time.
-
Wed · 13:15
Re-plans the run
Rev C lands a day late. First articles and the assembly pilot each move a day, and Ana and Mei get their new dates straight away.
-
Thu · 6:55
Covers a shift
Jon is out. The anodizing batch goes to Luis, who's on the same run, with a note saying why.
-
Fri · 15:30
Posts the digest
What got done, what moved and what's next, with machine hours from the tasks, on the project for both companies.
It gets smarter every run
Taskivities keeps a history nobody can rewrite: when each task was planned, when it was done, who moved it and why. After every run the agent compares the plan with what happened and writes what it learned into a playbook on the project. The next plan starts from there.
Tasks finished on their planned day
61%
Run 1
68%
Run 2
77%
Run 3
83%
Run 4
88%
Run 5
93%
Run 6
Illustration: how a team's plans firm up as the agent learns from each job.
playbook.md
Attached to X2 pilot run · updated by the Taskivities agent
# What I learned
- -First articles from Precision Parts take 3 days, plus 1 for the report.
- -Revisions reach the supplier a day after release. Send them directly.
- -Anodizing runs on Tuesdays and Thursdays. Plan batches around them.
- -Fixture builds slip when parts arrive after Wednesday.
- -QA sign-off needs both Mei and Kofi. Book it a day early.
# Next plan starts from these.
Questions
Does every supplier need Taskivities?
No. A supplier can run its own Taskivities (it's free and open source), or you can add their people to yours. The agent works across both.
What can the agent see?
Only what it's given. It signs in to each company's Taskivities as its own account, sees just the projects it's on there, and every change it makes is in the task history, marked as made by the agent.
What do people on the team have to do?
Nothing new. They get their tasks on their phone, tick them off and comment when something's stuck. The agent does the chasing and the re-planning.
What if the agent gets something wrong?
Anyone on the project can change it back. Nothing is ever deleted: dates move back, handovers reverse, and the history shows what happened and why.
Put your next run on one plan.
Run Taskivities for your company, bring your suppliers in, and let the agent keep the line on time.
Also for Construction and Events & launches.