Run agentic operations
Explain what agentic operations means - agents running an estate unattended inside rails - state the draft-vs-act rule that decides when an agent acts unattended versus when it stops for a human, and study Cogitave's own fleet of scheduled and operations agents as the worked example of the fleet you would build.
Units5
Duration27 min
Levelintermediate
By the end of this module, you'll be able to:
- Explain what "agentic operations" means: agents running your estate under least privilege, inside the request lifecycle, traced as evidence - with Cogitave's own agent fleet as the worked example.
- State the draft-vs-act rule and read the loop-placement table that decides when an agent acts unattended and when it stops for a human.
- Name Cogitave's real fleet - five scheduled engineering agents and six operations business agents - and say what each proposes and who holds its human gate, as a model for the fleet you would build.
- Read an agentic-operations standard as the source, and trace any specific agent claim to its paired spec - in Cogitave's estate, under
agents/scheduled/oragents/operations/.
Prerequisites
- Completion of "Apply the AGENTS floor" and "Work the request lifecycle" is recommended.
- Familiarity with the agent identity and capability model helps but is not required.
Units
- 01Introduction4 min
- 02What agentic operations is8 min
- 03The agent fleet8 min
- 04Knowledge check4 min
- 05Summary3 min
Related
- Operate from Day 1 Describe the Day 1 operating model - the pinned inner loop and the flow-based outer loop - state the parity contract that keeps the inner loop honest, read Cogitave's flow-based ways of working and its ADR-0025 choice of flow over Scrum as one org's answer, and explain why the human gate stays an exception inside the flow.
- Reliability and SRE Reason about a service's reliability targets the way an SRE discipline does - set an SLO from the user's journey, compute the error budget it buys, and operate the service against that budget with burn-rate alerts, sustainable on-call, a toil cap, and the freeze that stops shipping when the budget runs out.
- Respond to incidents Walk the incident-response flow end to end - detection, severity declaration, single-commander roles, containment through a runbook, communication, recovery, and the blameless postmortem - and see how business continuity and disaster recovery extend the same discipline to a region loss or a destructive event.