Supervisor AGET

A Supervisor AGET is an AGET agent specialized for governing a fleet of Worker AGETs under a shared Governance Policy.

• AKA: AGET Supervisor, Fleet Supervisor AGET, Supervising Agent Seat, Portfolio Supervisor Agent.
• Context:
  • input: Agent Health Reports, Session Retrospectives, governance policy, Fleet Configuration
  • output: Fleet Coordination Decisions, Governance Rulings, Fleet Upgrade Plans, advisories
  • measure: Managed Seat Count, Governance Conformance Rate, Fleet Drift, Upgrade Convergence Time
  • It can (typically) orchestrate a portfolio of Worker AGETs, each carrying a distinct Agent Domain Scope.
  • It can (typically) enforce Governance Policy across managed seats through Advisory Enforcement or Strict Enforcement tiers.
  • It can (typically) aggregate Health Checks and Session Retrospectives from its fleet into a Fleet Health Report.
  • It can (typically) coordinate Cross-Fleet Evidence Chains and Substrate-OK Protocol signaling between seats.
  • It can (typically) propagate a Framework Release through a Fleet Upgrade Lifecycle, so managed seats converge on one Framework Version.
  • It can (typically) hold Filing Authority for its managed seats, relaying a Governed Issue on their behalf through Supervisor Intake.
  • It can (typically) adjudicate a Cross-Seat Conflict where two seats claim the same Stewardship Ownership.
  • It can (typically) maintain a Fleet Register recording each seat's Agent Location, Agent Archetype, and Agent Status.
  • It can (often) approve a Release Gate that a managed seat proposes but may not self-authorize.
  • It can (often) grant a Standing Authorization bounding what a managed seat may do without per-act approval.
  • It can (often) detect Cross-Seat Drift by comparing a Governed Artifact across seats holding forked copies.
  • It can (often) run a Fleet Scan to re-derive seat state from a Fleet Register rather than from a Path Glob.
  • It can (often) hold a Read-Only Cross-Seat Access boundary, auditing a managed seat without write authority.
  • It can (often) sequence a Joint Maintenance Window where managed seats share one Fleet Substrate.
  • It can (often) consume an Inbox Handoff from a managed seat and route it to the principal as a Decision Packet.
  • It can (often) record a Principal Ruling so that managed seats cite one authority rather than re-litigating it.
  • It can (often) retire a Dormant Agent Seat whose Agent Domain Scope has been absorbed elsewhere.
  • It can range from being a Private Supervisor AGET (single-principal) to being a Shared Supervisor AGET (multi-principal portfolio), depending on Principal Cardinality.
  • It can range from being an Advisory Supervisor AGET to being a Strict Supervisor AGET, depending on its Enforcement Tier.
  • It can range from being a Single-Substrate Supervisor to being a Cross-Substrate Supervisor, depending on Fleet Substrate breadth.
  • It can range from being a Nascent Supervisor Seat to being a Mature Supervisor Seat, depending on Governance Maturity.
• Example(s):
  • A supervisor AGET managing a single-principal portfolio of Worker AGETs across one Knowledge Base Substrate.
  • A supervisor AGET that blocks a Framework Release until every managed seat reports a passing Health Check.
  • A supervisor AGET relaying a Governed Issue filed by a Worker AGET that holds no Filing Authority of its own.
  • A supervisor AGET that records a Principal Ruling as a Standing Authorization, so managed seats stop asking per-act.
• Counter-Example(s):
  • A Worker AGET, which executes Domain Tasks rather than governing other seats.
  • An Orphan Agent, whose supervising seat has terminated, leaving it without Supervisory Context.
  • A Multi-Agent System Orchestrator that routes tasks but holds no Governance Policy.
  • A Build Pipeline, which sequences work without Agent Seat semantics.
• See: AGET Framework, Worker AGET, Fleet (AGET), AGET Agent, Multi-Agent System, Governance Policy, Agent Archetype, Fleet Upgrade Lifecycle, Learning Document, Session Protocol.

---

References

• • Published from the AGET framework. No machine-readable concept URI is asserted: `Supervisor AGET` is not yet a published concept in the AGET vocabulary, and asserting one that does not resolve is the defect this note exists to avoid.