Work wakes up on time.

AGE ENGINE · 03/03

A 24-hour schedule crosses each heartbeat with the queue, context, permissions and next job.

See the five steps Back to the Age Engine ↖ 01 heartbeat schedule 24h · 00 · 04 · 08 · 12 · 16 · 20 · 24 02 queue Finance · every 4 hours · Sales · every 8 hours 03 context heartbeat → queue → context → delivery 04 delivery 08:00 · Update projection 01 Work execution Turns decisions into work. 02 Human approvals Keeps you in control. 03 Smart routines Keeps work moving.

01 · HEARTBEAT

The heartbeat wakes the agent at the right time.

Finance wakes every four hours; Support reviews the queue whenever the service level agreement (SLA) breaches its limit.

Sales runs every eight hours and Content every twelve. The first heartbeat of the day opens the cash position; the next checks due dates. Time, event, condition, queue and request are the five triggers. 01 24H 08:00 · PULL QUEUE 12:00 · REVIEW 16:00 · DELIVER 01 · HEARTBEAT

02 · PULLS FROM THE QUEUE

Upon waking up, the routine seeks the next work released.

Dependencies and approval separate what can begin from what remains blocked.

On waking, the routine looks for the next released work. A ticket past its SLA takes precedence over work still within its deadline. Work awaiting a human decision stays stopped while the routine continues. 02 AGE-281 AVAILABLE AGE-282 BLOCKED AGE-284 AVAILABLE AVAILABLE QUEUE EXECUTOR BOT 02 · PULLS FROM THE QUEUE

03 · CONTEXT BEFORE

Before acting, the agent receives context, evidence and permissions.

The routine receives business data, origin decision and active policy before touching the operation.

The Finance agent arrives with cash and due dates already checked. Without this package, the cycle searches for everything again each time. Workspace permission determines how far the agent may change things. 03 CURRENT CONTEXT ATTACHED EVIDENCE PERMISSION OK GATE READY TO ACT ACTION EXECUTE 03 · CONTEXT FIRST

04 · EXECUTES OR DELEGATES

The agent executes, delegates or requests approval.

The path depends on the scope and risk; the queue retains who is responsible for the next state.

The agent executes independently when scope and risk fit the policy. It delegates when the next step requires a different skill. It requests approval when risk exceeds the stated limit. 04 AGE-284 ACTION EXECUTE DIRECTLY DELEGATE WITH CONTEXT REQUEST APPROVAL EXECUTOR BOT DELEGATED PERSON HUMAN OWNER 04 · EXECUTES OR DELEGATES

05 · NEXT CYCLE

Delivery stays in history and defines when the routine returns.

Conclusion, block or new attempt update the trail and calculate the next activation.

A pause for incomplete customer data appears in history with its time and reason. Delivery is recorded with a timestamp and final state. The next cycle resumes from the recorded point, rather than the beginning. 05 AGE-284 COMPLETED DELIVERY RECORDED NEXT CYCLE 05 · NEXT CYCLE

HEARTBEAT AND WORK CYCLE

A scheduled time alone does not create a routine. The heartbeat wakes the agent. Queue, context and policy determine which work can advance. ONLY A SCHEDULED TIME 08:00 the clock fires without checking the queue Context the task must fetch everything again Failure the next cycle does not know what happened INTELLIGENT CYCLE Heartbeat wakes by time, event or condition Released work pulls only what can advance History delivery and attempts define the next cycle

OPERATIONAL SCHEDULE

Four workstreams follow different routines during the same day. Each follows its own cadence and pulls only released work. An event can arrive during the day without changing other routines. If a routine pauses or fails, the next cycle continues from the recorded point. SCHEDULE · 24 HOURS 08:00 · active operation 1 DAY IN 7.2S Advance four hours Pause routine Try again AGENT / FREQUENCY 00 04 08 12 16 20 24 NOW Finance every 4 hours TIME Open cash position 00:00 Review due dates 04:00 Update projection 08:00 Check cash and due dates 12:00 Validate payments 16:00 Prepare closing 20:00 Record daily summary 00:00 of the next cycle Sales every 8 hours TIME Open the day’s opportunities 00:00 Review pending responses 08:00 Prioritize opportunities without a response 16:00 Record next steps 00:00 of the next cycle Content every 12 hours TIME Review editorial calendar 08:00 Prepare publishing queue 20:00 Support every 24 hours + event TIME + EVENT Open queue past SLA 00:00 Review tickets past SLA 12:00 Record shift handoff 00:00 of the next cycle Current-time line: 08:00. Each row keeps its frequency and task in the fixed schedule; the current-time line moves through the 24 hours. Pauses and retries remain in history.

TRIGGERS

Each routine starts with a signal type. TRIGGER OPERATIONAL EXAMPLE WHAT IT RELEASES time Finance · 12:00 cash check event payment declined billing retry condition margin below 31% campaign review queue ticket past SLA support priority request owner requests reprocessing new cycle with history

DELEGATION BETWEEN AGENTS AND PERSONS

Each handoff shows who takes the next step. The routine executes what policy allows, delegates work requiring a different skill and requests approval when risk exceeds the limit. Finance agent checks cash and due dates Marina · Growth receives campaign adjustment Felipe · Director decides on revenue risk Control agent tracks the recorded effect

PAUSE, FAILURE AND RETRY

Pauses and failures remain in history. 08:00 Finance completes the cash check 09:14 Sales pauses because customer data is incomplete 10:02 Support fails to open a ticket and schedules a retry 10:07 retry completes and records the SLA 12:00 heartbeat pulls the released queue for the next cycle

WHERE THIS HAPPENS

This chapter is part of the third engine. 01 Conecta

It forms the context with visible origin, access and gaps.

→ 02 Planeja

Calculate scenarios and deliver an approved route.

→ 03 Age

Transforms the route into work, authorization and recorded delivery.

→ 04 Controla

Tracks the effect and returns the result to the cycle.

↺

THE CYCLE CONTINUES

Age records delivery. Controla tracks the effect.

The record returns to the cycle and gives Controla the starting point to follow the result.

Return to the Age Engine View the Controla Engine in the cycle