Lindy asks what should trigger what.Byte already knows what affects what.

A room change should not need a flowchart.

An agent platform needs the trigger, steps, conditions and tools. Byte begins with an understanding of what the change means for the student.

With LindyBuild the workflow
Room change workflow Active
TRIGGERNew Canvas announcement

When a post arrives

•••
AGENT STEPRead the change

Extract room, time and module

•••
CONDITIONIs the event today?

Branch on date

•••
ACTIONUpdate calendar

Move the event

•••
ACTIONSend message

Post the new room

•••
Last run Today at 08:125 steps · 3 integrations

Describe the process, then assemble it.

The workflow defines how an agent should react, branch and act across connected tools.

With ByteLet the consequence carry through
Tuesday in motion Live
CANVAS · POLS0045 · 08:12Seminar moved to G14

Today at 10:00

new

This changes when you leave, not what you need to finish.

ROUTELeave for campus

G14 adds six minutes

moved
SEMINARPOLS0045 in G14

Main Building

updated
PREPEssay block protected

45 minutes remains

kept
1 signal3 consequences understood0 workflows built

Let the change move through the student’s day.

Byte already knows which parts should move, which should stay and where the student needs a choice.

A student should not need an agent org chart.

Splitting work between specialised agents is useful for a process. Personal context should not be handed off like a ticket.

Agent teamOne request split across four workers4 agents
NEW TASK

Handle the seminar room change and everything around it.

CoordinatorDelegating the taskrouting
Calendar agentMove the eventdone
Message agentTell the course groupwaiting
Research agentFind the new roomdone
Task agentMove the preparation taskrunning
4 task runs3 handoffs1 approval
One ByteOne continuous understanding of the studentnow
STUDENTSamMODULEPOLS0045TODAYEssay + seminar
BYTE NOTICEDSeminar moved to G14

I moved the route and kept the essay block. Want me to tell Maya the room changed?

ROUTELeave at 09:20updated
45WORKEssay block untouchedkept
PEOPLEMaya waits for youask first

If this, then that. Until life does something else.

Conditions handle the cases you name in advance. Byte reads the tradeoffs that make this decision belong to this student.

Decision workflowConditions defined in advance
GOAL

Decide whether to add a student event tonight.

IF

calendar is free after 17:00

continue
IF

ticket price is under £10

continue
IF

travel time is under 30 minutes

continue
THEN

create calendar event

action
Trigger3 conditions1 action
Student judgementContext interpreted in the moment
TUE14POLICY FUTURES LAB · 17:30Who gets to shape the city?

Gordon Square · £4 student

Maya is goingmatters
Essay block is safematters
Last useful train at 20:12matters
Application due tomorrowmatters more

Go, but leave at 19:42. The application stays tomorrow’s first block.

The student is the integration.

University, people, place, money, travel and what comes next only become useful when one system understands the person between them.

Sam’s Tuesdaysix kinds of context, one life
BYTE UNDERSTANDSThe student between the systems

Not just the data moving through them.

Leave for G14Campus route updatedready
Essay blockApplication still protectedkept
Policy Futures LabMaya · £4 · Gordon Squarefits
Train homeLeave the event at 19:42safe
University People Place TravelOne continuous context

Do not build a workflow around student life. Build for student life.