Operate your AI-native estate
Learn to operate an AI-native estate safely and auditably: work the propose-only request lifecycle, run agentic operations, apply reliability and SRE practice, respond to incidents, and stand up Day 1 operations. By the end you'll be able to keep your estate running under least privilege with every action recorded as evidence. Cogitave's own estate is the worked example throughout.
Modules5
Duration132 min
Leveladvanced
Prerequisites
- Completion of the "Engineering standards for an AI-native org" and "Build on a single canonical model" paths is recommended.
Modules in this path
- Work the request lifecycle Move a change through the seven-stage request lifecycle, understand why the write tools only propose, and read the Definition of Done that decides when a request is actually done rather than merely worked on.
- 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.
- 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.
- 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.
Related
- Engineering standards for an AI-native org Learn the standards floor that governs every repository in an AI-native estate: the floor rules, naming, commits and versioning, testing and quality, API design, configuration, secure SDLC, CI/CD, and observability and reliability. By the end you'll be able to make changes that pass the org gates by default. Cogitave's own standards are the worked example throughout.
- Design and version an API Shape a clean, consistent API against a clear API design standard - resources, standard methods, typed errors, cursor pagination, idempotency - then version and deprecate it under a versioning policy so no consumer is ever broken without consent.
- Apply the naming standards Name a new identifier, file, repo, or branch the way an AI-native org does - keyword-first, no redundant prefix, cased by role - and tell a functional keyword apart from a product codename, so your first artifact passes the naming gate by default.