{
  "uid": "cogitave.learn.run-agentic-operations.introduction",
  "kind": "moduleUnit",
  "href": "/modules/run-agentic-operations/introduction/",
  "title": "Introduction",
  "summary": "",
  "type": null,
  "products": [],
  "roles": [],
  "levels": [],
  "subjects": [],
  "headings": [
    "Two halves, one contract",
    "Day-0 honesty",
    "What you will get from this module"
  ],
  "source": "An AI-native org runs its own operations the same way it ships software: with\nagents. The transferable premise is **dogfooding** - if the agent platform you\nbuild is good enough to sell, it should be good enough to run your own company,\nand running the company is the honest test of the platform.\n\nCogitave is one such org: `yuva` is its Agent OS, `namzu` its Agent Kernel, and\nits operating premise is that the estate should run itself with those same\nproducts. That premise has a name and a governing document:\n[agentic-operations](../../../../standards/docs/standards/agentic-operations.md),\nCogitave's standard for how agents run its engineering estate and its business\noperations - the worked example this module reads.\n\n> [!IMPORTANT]\n> Read the standard's own framing first: *\"If our agents cannot safely run\n> Cogitave, they are not ready to run anyone else.\"* Agentic operations is not a\n> side project - it is the test a company applies to its own platform. Read\n> that as the pattern: an org proves its agents on itself before it trusts them\n> anywhere.\n\n## Two halves, one contract\n\nThe pattern splits the fleet in two - agents that run the **engineering** estate\nand agents that run the **business** - under one shared contract. Cogitave's\ninstance realizes that split as two directories, each with its own catalog of\nnamed agents:\n\n- [`agents/scheduled/`](../../../../agents/README.md) runs the **engineering**\n  estate - PR triage, dependency review, issue grooming, docs sync, security\n  triage.\n- [`agents/operations/`](../../../../agents/operations/README.md) runs the\n  **business** - marketing, RevOps/sales, customer support, finance/FinOps, and\n  incident/status communications.\n\nWhichever half it belongs to, every agent satisfies the same three-part\ncontract: a first-class identity with a least-privilege capability grant, a run\ninside the [request lifecycle](../../../../agents/lifecycle/LIFECYCLE.md), and a\nrelease gated by the [eval harness](../../../../agents/evals/eval-harness.md).\nThis module teaches you to read that contract and to study the real fleet that\nimplements it.\n\n## Day-0 honesty\n\n> [!NOTE]\n> The agentic-operations standard is explicit: **\"These are specs, not running\n> systems. No ops agent is live yet.\"** Everywhere this module says an agent\n> \"does\" something, read it as the spec'd behavior once that agent is built and\n> passes its evals - not a claim that it runs in production today.\n\n## What you will get from this module\n\nA working definition of agentic operations, the **draft-vs-act rule** that\ndecides when an agent acts unattended and when it stops for a human, and a\nnamed tour of Cogitave's fleet - which agent proposes what, and who holds its\nhuman gate - as a concrete model for the fleet you would build.\n",
  "partOf": "cogitave.learn.run-agentic-operations",
  "durationInMinutes": 4,
  "quiz": null
}