iiRecord
Agentic AI Atlas · Curriculum Update Cycle
workflow:curriculum-update-cyclea5c.ai
II.
Workflow JSON

workflow:curriculum-update-cycle

Structured · live

Curriculum Update Cycle json

Inspect the normalized record payload exactly as the atlas UI reads it.

File · workflows/workflows/workflows-education.yamlCluster · workflows
Record JSON
{
  "id": "workflow:curriculum-update-cycle",
  "_kind": "Workflow",
  "_file": "workflows/workflows/workflows-education.yaml",
  "_cluster": "workflows",
  "attributes": {
    "displayName": "Curriculum Update Cycle",
    "workflowKind": "governance",
    "triggerType": "scheduled",
    "typicalCadence": "semi-annually",
    "complexity": "cross-team",
    "description": "Coordinates the periodic revision of educational curricula -- gathering\ninstructor feedback and learner outcome data, benchmarking against\nindustry competency frameworks and accreditation requirements, reviewing\ncontent currency against evolving technology stacks, prioritizing module\nadditions and deprecations, and routing updated syllabi through academic\ngovernance approval. Produces updated curriculum maps, change-impact\nassessments, and accreditation alignment matrices. Excludes content\nauthoring.\n"
  },
  "outgoingEdges": [
    {
      "from": "workflow:curriculum-update-cycle",
      "to": "role:planner",
      "kind": "involves_role",
      "attributes": {}
    },
    {
      "from": "workflow:curriculum-update-cycle",
      "to": "role:technical-writer",
      "kind": "involves_role",
      "attributes": {}
    },
    {
      "from": "workflow:curriculum-update-cycle",
      "to": "role:engineering-manager",
      "kind": "involves_role",
      "attributes": {}
    },
    {
      "from": "workflow:curriculum-update-cycle",
      "to": "skill-area:domain-driven-design",
      "kind": "requires_skill_area",
      "attributes": {}
    },
    {
      "from": "workflow:curriculum-update-cycle",
      "to": "domain:education",
      "kind": "applies_to_domain",
      "attributes": {}
    },
    {
      "from": "workflow:curriculum-update-cycle",
      "to": "domain:knowledge-management",
      "kind": "applies_to_domain",
      "attributes": {}
    },
    {
      "from": "workflow:curriculum-update-cycle",
      "to": "responsibility:review-architecture-changes",
      "kind": "triggers_responsibility",
      "attributes": {}
    },
    {
      "from": "workflow:curriculum-update-cycle",
      "to": "responsibility:write-user-docs",
      "kind": "triggers_responsibility",
      "attributes": {}
    },
    {
      "from": "workflow:curriculum-update-cycle",
      "to": "org-unit:content-team",
      "kind": "performed_by_org_unit",
      "attributes": {}
    },
    {
      "from": "workflow:curriculum-update-cycle",
      "to": "org-unit:product-team",
      "kind": "performed_by_org_unit",
      "attributes": {}
    }
  ],
  "incomingEdges": [
    {
      "from": "tool:fireflies-ai",
      "to": "workflow:curriculum-update-cycle",
      "kind": "supports_work",
      "attributes": {
        "confidence": "medium",
        "evidence": "Lecture and seminar transcripts can surface course-content updates and student questions."
      }
    }
  ]
}