GM-RKB - Recent changes [en]

Normalized Function

Gmelli — Thu, 24 Sep 2026 04:04:31 GMT

Stub pilot 8/8 (PR-008): rewrite of a stub to the GM-RKB house style; rubric v1.1 composite 13/18; read before publishing.

@@ Line 1: / Line 1: @@
-A [[Normalized Function]] is a [[numeric-output function]] whose [[function range|range]] has [[transformed function|transformed]] by a [[normalizing factor]].
+A [[Normalized Function]] is a [[numeric-output function]] whose [[function range|range]] has been [[transformed function|transformed]] by a [[normalizing factor]] to produce values within a [[standardized range]].
 * <B>Example(s):</B>
-** a [[Normalized Discounted Cumulative Gain]] is a normalized version of the [[discounted cumulative gain]].
+** [[Normalized Ranking Metric]]s, such as:
-** a [[Normalized Mutual Information Metric]] is a normalized version of the [[mutual information metric]].
+*** a [[Normalized Discounted Cumulative Gain]], a normalized version of the [[discounted cumulative gain]].
 ** …
 * <B>Counter-Example(s):</B>
-** a [[Normalized Vector]].
+** a [[Normalized Vector]], which is a [[vector]] rather than a [[function]].
-* <B>See:</B> [[Function]], [[Range]], [[Normalization]].
+** a [[Normalized Database Schema]], which applies [[database normalization]] rather than a [[range]] transformation.
 ----
-----
+== References ==
 __NOTOC__
 [[Category:Concept]]

Vanguard (Advance Guard)

Gmelli — Thu, 24 Sep 2026 04:04:16 GMT

Stub pilot 7/8 (PR-008): rewrite of a stub to the GM-RKB house style; rubric v1.1 composite 17/18; read before publishing.

@@ Line 1: / Line 1: @@
-A [[Vanguard (Advance Guard)]] is a [[Military Formation]] that ...
+A [[Vanguard (Advance Guard)]] is a [[military formation]] that constitutes the leading part of an advancing [[military force]] responsible for seeking out the [[enemy force]] and securing [[ground]] ahead of the [[main body]].
-* <B>See:</B> [[Military Formation]].
+* <B>AKA:</B> [[Advance Guard]], [[Advanced Guard]], [[Van (Military)]].
 ----
 == References ==

Arylcyclohexylamine

Gmelli — Thu, 24 Sep 2026 04:04:00 GMT

Stub pilot 6/8 (PR-008): rewrite of a stub to the GM-RKB house style; rubric v1.1 composite 16/18; read before publishing.

@@ Line 1: / Line 1: @@
-An [[Arylcyclohexylamine]] is a [[compound]] with a [[cyclohexylamine unit]] with an [[aryl moiety attachment]].
+An [[Arylcyclohexylamine]] is a [[chemical class]] that consists of a [[compound]] with a [[cyclohexylamine unit]] bonded to an [[aryl moiety]].
 * <B>Example(s):</B>
-** [[Ketamine]].
+** [[Clinical Arylcyclohexylamine]]s, such as:
 ** …
-* <B>See:</B> [[Chiral Compound]], [[Experimental Drug]], [[Chemical Class]], [[Pharmaceutical Drug]], [[Designer Drug]].
+* <B>See:</B> [[Chiral Compound]], [[Experimental Drug]], [[Chemical Class]], [[Pharmaceutical Drug]], [[Designer Drug]], [[NMDA Receptor Antagonist]], [[Dissociative Anesthetic]], [[Ketamine]], [[Phencyclidine]], [[Research Chemical]], [[Controlled Substance]].
 ----
 == References ==

Contamination Presence

Gmelli — Thu, 24 Sep 2026 04:03:44 GMT

Stub pilot 5/8 (PR-008): rewrite of a stub to the GM-RKB house style; rubric v1.1 composite 17/18; read before publishing.

@@ Line 1: / Line 1: @@
-A [[Contamination Presence]] is a [[presence]] of an [[impurity]] (a [[contaminant]]).
+A [[Contamination Presence]] is a [[substance presence]] that is the [[unwanted presence]] of a [[contaminant]] (an [[impurity]] or other [[undesirable constituent]]) within a [[material]], [[physical body]], [[natural environment]], or [[workplace]].
 * <B>Example(s):</B>
-** [[Pollution]].
+** [[Environmental Contamination Presence]]s, such as:
-* <B>See:</B> [[Physical Body]], [[Natural Environment]].
+*** [[Air Pollution]] from [[particulate matter]].
 ----
 == References ==
@@ Line 13: / Line 56: @@
 ** '''Contamination''' is the presence of a constituent, [[impurity]], or some other undesirable element that spoils, corrupts, infects, makes unfit, or makes inferior a material, [[physical body]], [[natural environment]], [[wiktionary:Workplace|workplace]], etc.
 <references/>
 __NOTOC__
 [[Category:Concept]]

Chat-based Document Q&A

Gmelli — Thu, 24 Sep 2026 04:03:29 GMT

Stub pilot 4/8 (PR-008): rewrite of a stub to the GM-RKB house style; rubric v1.1 composite 15/18; read before publishing.

@@ Line 1: / Line 1: @@
-A [[Chat-based Document Q&A]] is a [[Document Q&A]] that is a [[chat-based application]].
+A [[Chat-based Document Q&A]] is a [[document Q&A task]] that is a [[chat-based application]] which supports [[conversational question answering]] over one or more [[source document]]s through an [[interactive chat interface]].
 * <B>Example(s):</B>
-** [[Chat-based Contract Q&A]].
+** [[Domain-Specific Chat Document Q&A]]s, such as:
 ** …
-* <B>See:</B> [[...]].
+* <B>See:</B> [[Document Q&A]], [[Question Answering Task]], [[Retrieval Augmented Generation (RAG)]], [[LlamaIndex]], [[Vector Database]], [[Large Language Model]], [[Conversational AI System]], [[Semantic Search]], [[Chatbot]].
 ----
 == References ==

Branded Product Category Mention

Gmelli — Thu, 24 Sep 2026 04:03:12 GMT

Stub pilot 3/8 (PR-008): rewrite of a stub to the GM-RKB house style; rubric v1.1 composite 15/18; read before publishing.

← Older revision		Revision as of 04:03, 24 September 2026
Line 1:		Line 1:
	A [[Branded Product Category Mention]] is a [[product-related mention]] that is a [[branded product category term]].		A [[Branded Product Category Mention]] is a [[product-related mention]] that is a [[branded product category term]] occurrence within [[text]] that references a [[commercial product category]] associated with a specific [[brand]].
			* <B>AKA:</B> [[Brand Product Category Mention]], [[Branded Category Mention]], [[Branded Product-Category Text Mention]].
	* <B>Context:</B>		* <B>Context:</B>
	** It can range from being an [[Unannotated Branded Product Category Mention]] to being an [[Annotated Branded Product Category Mention]].		** It can (typically) reference a [[branded product category]] through a [[surface form]] appearing in [[natural language text]].
			** It can (typically) associate a [[product category]] with a specific [[brand name]] or [[brand identity]].
			** It can (typically) be identified by a [[Named Entity Recognition Task\|named entity recognition]] process during [[text processing]].
			** It can (typically) be extracted by a [[Mention Detection Task\|mention detection]] process.
			** It can (typically) be linked to a [[knowledge base entry]] through an [[Entity Linking Task\|entity linking]] process.
			** It can (typically) be disambiguated from other [[product-related mention]]s via a [[disambiguation process]].
			** It can (typically) occur within [[commercial text]], such as a [[product review]], an [[advertisement]], or an [[e-commerce listing]].
			** It can (typically) carry a [[mention boundary]] delimited by a [[start offset]] and an [[end offset]].
			** It can (often) be annotated with a [[category label]] during a [[text annotation task]].
			** It can (often) be associated with [[product attribute]]s such as a [[brand attribute]] and a [[product type attribute]].
			** It can (often) appear alongside a [[product name mention]] and a [[product feature mention]].
			** It can (often) be aggregated within a [[branded product category mention corpus]].
			** It can (often) serve as a [[training example]] for a [[mention classification model]].
			** It can (often) be evaluated with a [[precision measure]] and a [[recall measure]].
			** It can (often) support a [[product categorization task]] and a [[market analysis task]].
			** It can (often) be normalized to a [[canonical branded product category]].
			** It can range from being an [[Unannotated Branded Product Category Mention]] to being an [[Annotated Branded Product Category Mention]], depending on its [[annotation status]].
			** It can range from being an [[Explicit Branded Product Category Mention]] to being an [[Implicit Branded Product Category Mention]], depending on its [[reference explicitness]].
			** It can range from being a [[Single-Token Branded Product Category Mention]] to being a [[Multi-Token Branded Product Category Mention]], depending on its [[mention span length]].
			** It can integrate with an [[entity linking system]] for [[knowledge base grounding]].
			** It can integrate with a [[product taxonomy]] for [[category assignment]].
	** …		** …
	* <B>Example(s):</B>		* <B>Example(s):</B>
	** an [[Automotive Branded Product Category Mention]].		** [[Domain-Specific Branded Product Category Mention]]s, such as:
			*** an [[Automotive Branded Product Category Mention]] for [[vehicle categorization]].
			*** an [[Electronics Branded Product Category Mention]] for [[consumer electronics categorization]].
			*** an [[Apparel Branded Product Category Mention]] for [[clothing categorization]].
			** [[Annotation-Status Branded Product Category Mention]]s, such as:
			*** an [[Annotated Branded Product Category Mention]] labeled during a [[text annotation task]].
			*** an [[Unannotated Branded Product Category Mention]] within [[raw text]].
			** the [[Text Mention\|mention]] "[[Nike running shoes]]" occurring within a [[product review]], which associates the [[shoe product category]] with the [[Nike brand]].
			** the [[Text Mention\|mention]] "[[Toyota sedans]]" occurring within an [[automotive advertisement]], which associates the [[sedan product category]] with the [[Toyota brand]].
	** …		** …
	* <B>Counter-Example(s):</B>		* <B>Counter-Example(s):</B>
	** a [[Branded Product Category]].		** a [[Branded Product Category]], which is the [[category concept]] itself rather than its [[textual mention]].
	** a [[Branded Product Category Term]].		** a [[Branded Product Category Term]], which is the [[term]] rather than its [[in-text occurrence]].
	* <B>See:</B> [[Product Category Term]].		** a [[Product Category Mention]], which lacks a [[brand association]].
			** a [[Product Name Mention]], which references a [[specific product]] rather than a [[product category]].
			** …
			* <B>See:</B> [[Product Category Term]], [[Product-Related Mention]], [[Named Entity Mention]], [[Mention Detection Task]], [[Entity Linking Task]], [[Product Taxonomy]], [[Brand]].

	----		----
	----		== References ==
			** ([[DBpedia Spotlight (2011)]]) ⇒ Pablo N. Mendes, Max Jakob, Andrés García-Silva, and Christian Bizer. (2011). "DBpedia Spotlight: Shedding Light on the Web of Documents." In: Proceedings of the 7th International Conference on Semantic Systems (I-Semantics).
			** ([[TAGME (2012)]]) ⇒ Paolo Ferragina, and Ugo Scaiella. (2012). "Fast and Accurate Annotation of Short Texts with Wikipedia Pages." In: IEEE Software.

	__NOTOC__		__NOTOC__
	[[Category:Concept]]		[[Category:Concept]]

Word Form Record Set

Gmelli — Thu, 24 Sep 2026 04:02:57 GMT

Stub pilot 2/8 (PR-008): rewrite of a stub to the GM-RKB house style; rubric v1.1 composite 14/18; read before publishing.

@@ Line 1: / Line 1: @@
-A [[Word Form Record Set]] is a [[dataset]] of [[word form record]]s.
+A [[Word Form Record Set]] is a [[lexical dataset]] that is a [[dataset]] of [[word form record]]s.
-* <B>AKA:</B> [[Word Form Record Set|Word Inventory]], [[Word Form Record Set|Word Database]], [[Word Form Record Set|Word List]].
+* <B>AKA:</B> [[Word Inventory]], [[Word Database]], [[Word List]], [[Word Form Inventory]].
-* <B>Context</U>:</B>
+* <B>Context:</B>
-** It can represent a [[Word Form Set]].
+** It can (typically) represent a [[Word Form Set]] as a [[structured collection]].
-** It can be used by a [[Word-level Analysis Task]].
+** It can (typically) contain [[word form record]]s, each describing a [[surface form]] of a [[word]].
-* <B>Example(s):</B>
+** It can (typically) store [[orthographic form]]s of [[word]]s.
-** a [[Stopword List]].
+** It can (typically) associate each [[word form record]] with a [[lemma]].
-** a [[Common Word List]], of [[common word]]s.
+** It can (typically) index [[word form]]s for fast [[lookup operation]]s.
-* <B>See:</B> [[Lexical Database]], [[Word Sense Inventory]].
+** It can (typically) support [[word membership testing]] against a known [[vocabulary]].
 ----
-----
+== References ==
 __NOTOC__
 [[Category:Concept]]

L2-Norm Regularized Optimization Task

Gmelli — Thu, 24 Sep 2026 04:02:40 GMT

Stub pilot 1/8 (PR-008): rewrite of a stub to the GM-RKB house style; rubric v1.1 composite 13/18; read before publishing.

@@ Line 1: / Line 1: @@
-An [[L2-Norm Regularized Optimization Task]] is a [[function optimization task]] that includes a …
+An [[L2-Norm Regularized Optimization Task]] is a [[regularized optimization task]] that is a [[function optimization task]] which includes an [[L2-norm regularization term]] in its [[objective function]].
-optimizes an [[L2-norm]].
+* <B>AKA:</B> [[ℓ2 Regularization]], [[Ridge Regularization]], [[Tikhonov Regularization]], [[Weight Decay]].
-* <B>AKA:</B> [[ℓ2 Regularization]].
+* <B>Context:</B>
-* <B>Context</U>:</B>
+** It can (typically) minimize an [[objective function]] that combines an [[empirical loss term]] with an [[L2-norm regularization term]].
-** It can solve the following [[Unconstrained Optimization Task]] <math>\min (\mathbf{w})^{1/2} \mathbf{w} \mathbf{w}^T + C \sum_{i=1}^l \log (1 + e^{(-y_i \mathbf{w}^T \mathbf{x}_i)})</math>, where, <math>\mathbf{x}</math> is a [[labeled training record]], and <math>l</math> is the [[training set size]].
+** It can (typically) penalize large [[model parameter]]s by adding the [[squared L2-norm]] of the [[weight vector]] scaled by a [[regularization coefficient]].
 ** …
-* <B>Counter-Example(s):</B>
+* <B>Example(s):</B>
-** [[L1 Norm Regularization]].
+** [[Regularized Regression Task]]s, such as:
-** [[L0 Norm Regularization]].
+*** [[Ridge Regression Task]] for [[linear regression]] with an [[L2-norm penalty]].
-* <B>See:</B> [[L2 Regularized Logistic Regression]], [[L2-Norm Regularizer]], [[Regularization]].
+*** [[L2 Regularized Logistic Regression Task]] for [[binary classification]].
 ----
 __NOTOC__
 [[Category:Concept]]

Database Management Task

Gmelli — Thu, 24 Sep 2026 03:52:39 GMT

Stub pilot 1/9 (PR-008): rewrite of a stub to the GM-RKB house style; rubric v1.1 composite 15/18; read before publishing.

← Older revision		Revision as of 03:52, 24 September 2026
Line 1:		Line 1:
	A [[Database Management Task]] is a [[data management task]] that manages a [[data base]].		A [[Database Management Task]] is a [[data management task]] that manages a [[data base]] through a [[database management system]].
	* <B>~~Context~~</U>:</B>		* <B>AKA:</B> [[DB Management Task]], [[Database Administration Task]], [[DBMS Task]].
	** It can be supported by a [[Database Management System]].		* <B>Context:</B>
	** It can ~~involve:~~		** It can typically maintain [[Data Integrity]] across [[database table]]s and [[database record]]s.
	*** a [[Database ~~Backup~~ Task]].		** It can typically enforce [[Data Consistency]] through [[database constraint]]s and [[transaction management]].
	*** a [[Database ~~Retrieval~~ Task]].		** It can typically support [[Data Storage]] via [[storage engine]]s and [[disk allocation]].
	*** a [[Database ~~Indexing~~ Task]].		** It can typically enable [[Data Retrieval]] through [[query execution]] and [[database indexing]].
			** It can typically manage [[Concurrent Access]] using [[concurrency control]] and [[database locking]].
			** It can typically preserve [[Data Durability]] with [[transaction log]]s and [[write-ahead logging]].
			** It can typically be supported by a [[Database Management System]] and a [[Database Administrator]].
			** It can often perform [[Database Backup Task]]s for [[disaster recovery]].
			** It can often perform [[Database Recovery Task]]s after [[system failure]]s.
			** It can often perform [[Database Indexing Task]]s to accelerate [[query performance]].
			** It can often perform [[Database Retrieval Task]]s for [[data access]].
			** It can often perform [[Database Optimization Task]]s through [[query tuning]] and [[index optimization]].
			** It can often perform [[Database Migration Task]]s across [[database platform]]s.
			** It can often perform [[Database Replication Task]]s for [[high availability]].
			** It can often perform [[Database Archival Task]]s for [[long-term retention]].
			** It can often perform [[Database Security Task]]s via [[access control]] and [[data encryption]].
			** It can often perform [[Database Monitoring Task]]s using [[performance metric]]s.
			** It can often perform [[Schema Management Task]]s through [[schema definition]] and [[schema evolution]].
			** It can often support [[Data Distribution]] across [[distributed database]]s.
			** It can often enable [[Capacity Planning]] for [[storage growth]].
			** It can range from being a [[Manual Database Management Task]] to being an [[Automated Database Management Task]], depending on its [[automation level]].
			** It can range from being a [[Single-Node Database Management Task]] to being a [[Distributed Database Management Task]], depending on its [[deployment topology]].
			** It can range from being a [[Relational Database Management Task]] to being a [[NoSQL Database Management Task]], depending on its [[data model]].
			** It can range from being a [[Transactional Database Management Task]] to being an [[Analytical Database Management Task]], depending on its [[workload type]].
			** It can integrate with [[Data Governance Framework]]s for [[compliance management]].
			** It can integrate with [[Cloud Database Service]]s for [[managed infrastructure]].
	** …		** …
	* <B>Example(s):</B>		* <B>Example(s):</B>
	** a [[Corpus Management Task]], for a [[corpus]].		** [[Domain-Specific Database Management Task]]s, such as:
	** a [[~~Taxonomy~~ Database Management Task]].		*** [[Corpus Management Task]]s, for a [[corpus]].
			*** [[Taxonomy Database Management Task]]s, for a [[taxonomy database]].
			*** [[Knowledge Base Management Task]]s, for a [[knowledge base]].
			** [[Relational Database Management Task]]s, such as:
			*** [[PostgreSQL Administration Task]]s, on a [[PostgreSQL Database]].
			*** [[MySQL Administration Task]]s, on a [[MySQL Database]].
			*** [[Oracle Database Administration Task]]s, on an [[Oracle Database]].
			** [[NoSQL Database Management Task]]s, such as:
			*** [[MongoDB Administration Task]]s, on a [[MongoDB Database]].
			*** [[Cassandra Administration Task]]s, on an [[Apache Cassandra Database]].
			** [[Cloud Database Management Task]]s, such as:
			*** [[Amazon RDS Management Task]]s (2009), on [[Amazon RDS]].
			*** [[Google Cloud SQL Management Task]]s (2011), on [[Google Cloud SQL]].
			*** [[Azure SQL Database Management Task]]s (2010), on [[Azure SQL Database]].
	** …		** …
	* <B>Counter-Example(s):</B>		* <B>Counter-Example(s):</B>
	** a [[Database ~~Creation~~ Task]].		** [[Database Creation Task]]s, which establish a new [[database]] rather than manage an existing one.
	* <B>See:</B> [[DBMS Task]], [[Database Administrator]], [[Database Archival]], [[Data Distribution]].		** [[Database Design Task]]s, which produce a [[database schema]] rather than operate on stored data.
			** [[Data Analysis Task]]s, which extract [[insight]]s rather than maintain [[data infrastructure]].
			** [[File Management Task]]s, which handle [[file system]] objects rather than [[database]] structures.
			** …
			* <B>See:</B> [[DBMS Task]], [[Database Administrator]], [[Database Archival]], [[Data Distribution]], [[Database Management System]], [[Data Management Task]], [[Query Execution]], [[Transaction Management]].

	----		----
	-~~---~~		== References ==
			** ([[Codd, 1970]]) ⇒ Edgar F. Codd. (1970). "A Relational Model of Data for Large Shared Data Banks." In: Communications of the ACM, 13(6). [https://doi.org/10.1145/362384.362685 doi:10.1145/362384.362685]
			** ([[Silberschatz et al., 2019]]) ⇒ Abraham Silberschatz, Henry F. Korth, and S. Sudarshan. (2019). "Database System Concepts, 7th Edition." McGraw-Hill.

	__NOTOC__		__NOTOC__
	[[Category:Concept]]		[[Category:Concept]]

Fleet (AGET)

Gmelli — Wed, 23 Sep 2026 21:45:53 GMT

Targeted add-context Fleet (AGET): rubric 9 -> 10 (PR-002 Silver target). Authorized PR-003.

← Older revision		Revision as of 21:45, 23 September 2026
Line 11:		Line 11:
	** It can (typically) propagate [[Framework Version]] upgrades through a [[Fleet Upgrade Lifecycle]], so member seats converge on one [[Framework Release]].		** It can (typically) propagate [[Framework Version]] upgrades through a [[Fleet Upgrade Lifecycle]], so member seats converge on one [[Framework Release]].
	** It can (typically) exchange [[Fleet Message]]s carrying [[Substrate-OK Protocol]] signals and [[Evidence Chain]]s between seats.		** It can (typically) exchange [[Fleet Message]]s carrying [[Substrate-OK Protocol]] signals and [[Evidence Chain]]s between seats.
			** It can (typically) maintain a [[Fleet Registry]] recording each member's [[Agent Seat Identity]], [[Agent Domain Scope]], and [[Framework Release]].
			** It can (typically) preserve [[Seat Autonomy]] so that each member [[AGET Agent]] governs its own [[Local Skill Set]] within the [[Uniform Governance Policy]].
	** ...		** ...
	** It can (often) designate [[Stewardship Ownership]] for shared vocabularies, so a [[Framework Vocabulary]] has exactly one [[Steward Seat]].		** It can (often) designate [[Stewardship Ownership]] for shared vocabularies, so a [[Framework Vocabulary]] has exactly one [[Steward Seat]].
Line 17:		Line 19:
	** It can (often) constrain a member seat to [[Read-Only Cross-Seat Access]], so one seat may audit another without write authority.		** It can (often) constrain a member seat to [[Read-Only Cross-Seat Access]], so one seat may audit another without write authority.
	** It can (often) accumulate [[Cross-Seat Learning]] as [[Learning Document]]s that outlive any single [[Software Session]].		** It can (often) accumulate [[Cross-Seat Learning]] as [[Learning Document]]s that outlive any single [[Software Session]].
			** It can (often) detect [[Cross-Seat Drift]] through periodic [[Fleet Health Check]]s that compare member [[Framework Release]]s and [[Governance Conformance]] levels.
			** It can (often) resolve a [[Cross-Seat Conflict]] via a [[Steward Advisory]] or an escalation to the [[Supervisor AGET]].
	** ...		** ...
	** It can range from being a [[Personal Agent Fleet]] to being an [[Organizational Agent Fleet]], depending on its [[Fleet Scale]].		** It can range from being a [[Personal Agent Fleet]] to being an [[Organizational Agent Fleet]], depending on its [[Fleet Scale]].
Line 22:		Line 26:
	** It can range from being a [[Single-Portfolio Fleet]] to being a [[Multi-Portfolio Fleet]], depending on its [[Portfolio Topology]].		** It can range from being a [[Single-Portfolio Fleet]] to being a [[Multi-Portfolio Fleet]], depending on its [[Portfolio Topology]].
	** It can range from being a [[Loosely-Governed Fleet]] to being a [[Strictly-Governed Fleet]], depending on its [[Governance Intensity]].		** It can range from being a [[Loosely-Governed Fleet]] to being a [[Strictly-Governed Fleet]], depending on its [[Governance Intensity]].
			** It can range from being a [[Single-Substrate Fleet]] to being a [[Multi-Substrate Fleet]], depending on its [[Substrate Topology]].
			** It can range from being a [[Statically-Membered Fleet]] to being a [[Dynamically-Membered Fleet]], depending on its [[Seat Membership Volatility]].
	** ...		** ...
	** It can be distinguished from an [[Ad-Hoc Agent Collection]] by its shared [[Governance Policy]] and [[Fleet Upgrade Lifecycle]].		** It can be distinguished from an [[Ad-Hoc Agent Collection]] by its shared [[Governance Policy]] and [[Fleet Upgrade Lifecycle]].
Line 27:		Line 33:
	** It can exhibit [[Correlated Seat Error]] when multiple seats reason from one [[Contaminated Source Artifact]], which resembles [[Independent Corroboration]] but is not.		** It can exhibit [[Correlated Seat Error]] when multiple seats reason from one [[Contaminated Source Artifact]], which resembles [[Independent Corroboration]] but is not.
	** It can require a [[Seat Abbreviation Registry]] if [[Skill Namespace]]s are qualified per seat.		** It can require a [[Seat Abbreviation Registry]] if [[Skill Namespace]]s are qualified per seat.
			** It can incur [[Governance Drift]] when a member seat diverges from the [[Uniform Governance Policy]] without a corresponding [[Evolution Document]].
			** It can bottleneck at a [[Steward Seat]] when [[Stewardship Ownership]] concentrates too many [[Framework Vocabulary]] decisions in one member.
	** ...		** ...
	* <B>Example(s):</B>		* <B>Example(s):</B>

Category:Multi-Agent System

Gmelli — Mon, 14 Sep 2026 21:43:12 GMT

Conform to the exemplar: two-sentence opening with a bolded-term definition, colons in place of em-dashes, and a See-Also link to the concept page of the same name. Authored by the content enhancement seat (not the account holder in person).

← Older revision		Revision as of 21:43, 14 September 2026
Line 1:		Line 1:
	This ~~category groups~~ pages about ~~'''~~multi-agent systems~~''': arrangements~~ in ~~which several agents work together on a task that no single agent completes alone~~.		This report lists the pages about multi-agent systems in GM-RKB.

	The members fall into four kinds:		A '''Multi-Agent System''' is an arrangement in which several agents work together on a task that no single agent completes alone.
	* '''Orchestration frameworks''' — [[AutoGen Framework]], [[CrewAI Framework]], [[MetaGPT Framework]], [[Multi-Agent Development Framework]], [[AI Agent Orchestration Framework]].
	* '''Coordination patterns''' — [[Multi-Agent Orchestration]], [[Parallel AI Agent Orchestration Pattern]], [[AI Agent Parallelization System]], [[Consensus-Based Evaluation Mechanism]].		== Member Kinds ==
	* '''Sub-agent structures''' — [[Agentic Coding Subagent]], [[Deep Agent Sub-Agent]] and [[Subagent System]], where one agent delegates to others it creates.		The members fall into four kinds.
	* '''Governed collectives''' — [[Agent Fleet]], [[Fleet (AGET)]] and [[GM-RKB Fleet]], where the agents are long-lived seats under a shared governance policy rather than tasks spawned on demand.		* '''Orchestration frameworks''': [[AutoGen Framework]], [[CrewAI Framework]], [[MetaGPT Framework]], [[Multi-Agent Development Framework]], [[AI Agent Orchestration Framework]].
			* '''Coordination patterns''': [[Multi-Agent Orchestration]], [[Parallel AI Agent Orchestration Pattern]], [[AI Agent Parallelization System]], [[Consensus-Based Evaluation Mechanism]].
			* '''Sub-agent structures''': [[Agentic Coding Subagent]], [[Deep Agent Sub-Agent]] and [[Subagent System]], where one agent delegates to others it creates.
			* '''Governed collectives''': [[Agent Fleet]], [[Fleet (AGET)]] and [[GM-RKB Fleet]], where the agents are long-lived seats under a shared governance policy rather than tasks spawned on demand.

	The distinction between the last two kinds is the useful one: a sub-agent structure is transient and task-shaped, while a governed collective persists and is administered.		The distinction between the last two kinds is the useful one: a sub-agent structure is transient and task-shaped, while a governed collective persists and is administered.
Line 12:		Line 15:

	== See Also ==		== See Also ==
	* [[Multi-Agent AI System]] ~~— the general article~~		* [[Multi-Agent System (MAS)]]
	* [[:Category:AI Agent]] ~~— the individual agents these systems are built from~~		* [[Multi-Agent AI System]]
	* [[:Category:AGET]] ~~— one framework's concepts, whose collectives are also members here~~		* [[:Category:AI Agent]]
			* [[:Category:AGET]]

Category:AI Agent

Gmelli — Mon, 14 Sep 2026 20:41:56 GMT

Conform to the exemplar: two-sentence opening with a bolded-term definition, colons in place of em-dashes. Authored by the content enhancement seat (not the account holder in person).

← Older revision		Revision as of 20:41, 14 September 2026
Line 1:		Line 1:
	This ~~category groups~~ pages about ~~'''~~AI agents~~''': software systems that pursue goals over time with some autonomy, typically deciding their own next action rather than executing a fixed script~~.		This report lists the pages about AI agents in GM-RKB.

	Membership is broad, and the members fall into several kinds:		An '''AI Agent''' is a software system that pursues goals over time with some autonomy, typically deciding its own next action rather than executing a fixed script.
	* '''Agents by application domain''' ~~— for example~~ [[AI Conversational Banking Agent]], [[Supplier Onboarding AI Agent]], [[Employee Support AI Agent]], [[Content Recommendation AI Agent]].
	* '''Agents by architecture or behaviour''' — [[LLM-Based Agent]], [[Task Agent]], [[AI Sub-Agent]], [[Proactive AI Agent]], [[Asynchronous AI Agent]], [[Ambient AI Agent]], [[Turing-Complete AI Agent]].		== Member Kinds ==
	* '''Named products and platforms''' — [[Manus AI Agent]], [[Tongyi DeepResearch Agent]], [[AWS Bedrock Agent Service]], [[Claude Code SRE Agent]].		Membership is broad, and the members fall into several kinds.
	* '''Agent frameworks and their parts''' — [[AGET Framework]], and the tracing objects of the OpenAI Agents SDK such as [[OpenAI Agents Trace]].		* '''Agents by application domain''': [[AI Conversational Banking Agent]], [[Supplier Onboarding AI Agent]], [[Employee Support AI Agent]], [[Content Recommendation AI Agent]].
	* '''Collectives of agents''' — [[Agent Fleet]], [[Fleet (AGET)]] and [[GM-RKB Fleet]], which are groups of agents rather than agents themselves.		* '''Agents by architecture or behaviour''': [[LLM-Based Agent]], [[Task Agent]], [[AI Sub-Agent]], [[Proactive AI Agent]], [[Asynchronous AI Agent]], [[Ambient AI Agent]], [[Turing-Complete AI Agent]].
			* '''Named products and platforms''': [[Manus AI Agent]], [[Tongyi DeepResearch Agent]], [[AWS Bedrock Agent Service]], [[Claude Code SRE Agent]].
			* '''Agent frameworks and their parts''': [[AGET Framework]], and the tracing objects of the OpenAI Agents SDK such as [[OpenAI Agents Trace]].
			* '''Collectives of agents''': [[Agent Fleet]], [[Fleet (AGET)]] and [[GM-RKB Fleet]], which are groups of agents rather than agents themselves.

	The last two kinds are worth noting for anyone browsing: this category admits the frameworks that build agents and the collections that contain them, not only individual agents.		The last two kinds are worth noting for anyone browsing: this category admits the frameworks that build agents and the collections that contain them, not only individual agents.

	== See Also ==		== See Also ==
	* [[:Category:Multi-Agent System]] ~~— systems in which several agents coordinate~~		* [[:Category:Multi-Agent System]]
	* [[:Category:AGET]] ~~— one framework's concepts, whose agent roles are also members here~~		* [[:Category:AGET]]
	* [[LLM-Based Agent]] ~~— the architecture most recent members share~~		* [[LLM-Based Agent]]

Category:AGET

Gmelli — Mon, 14 Sep 2026 20:40:38 GMT

Conform to the exemplar: two-sentence opening with a bolded-term definition, colons in place of em-dashes, and the whole concept phrase inside its link. Authored by the content enhancement seat (not the account holder in person).

← Older revision		Revision as of 20:40, 14 September 2026
Line 1:		Line 1:
	This ~~category groups~~ the ~~concepts~~ of the [[AGET Framework\|AGET]] ~~framework: a convention for building long-lived software agents, each scoped to a domain and operating under a shared governance policy~~.		This report lists the concept pages of the [[AGET Framework\|AGET framework]].

	Not every member is an agent~~. The~~ nine divide into three kinds:		An '''AGET''' is a long-lived software agent scoped to one domain and operating under a shared governance policy. Not every member of this category is an agent: the nine divide into three kinds.
	* '''Agent roles''' — [[Supervisor AGET]] and [[Worker AGET]], the two archetypes a single agent seat takes.
	* '''Collectives''' — [[Agent Fleet]], [[Fleet (AGET)]] and [[GM-RKB Fleet]], bounded sets of seats under one governance policy.		== Member Kinds ==
	* '''Operating apparatus''' — [[Initialization Protocol]], [[Software Session]], [[Learning Document]] and [[Verification Test]], the protocols and artifacts by which a seat starts up, works a bounded interval, records what it learned, and proves a claim.		* '''Agent roles''': [[Supervisor AGET]] and [[Worker AGET]], the two archetypes a single agent seat takes.
			* '''Collectives''': [[Agent Fleet]], [[Fleet (AGET)]] and [[GM-RKB Fleet]], bounded sets of seats under one governance policy.
			* '''Operating apparatus''': [[Initialization Protocol]], [[Software Session]], [[Learning Document]] and [[Verification Test]], the protocols and artifacts by which a seat starts up, works a bounded interval, records what it learned, and proves a claim.

	Each member page carries a machine-readable concept URI published at [https://w3id.org/aget/vocab w3id.org/aget/vocab], so the page here and the published vocabulary refer to the same concept.		Each member page carries a machine-readable concept URI published at [https://w3id.org/aget/vocab w3id.org/aget/vocab], so the page here and the published vocabulary refer to the same concept.

	== See Also ==		== See Also ==
	* [[AGET Framework]] ~~— the framework these concepts belong to~~		* [[AGET Framework]]
	* [[:Category:AI Agent]] ~~— the broader class the agent roles also belong to~~		* [[:Category:AI Agent]]
	* [[:Category:Multi-Agent System]] ~~— where the collectives also sit~~		* [[:Category:Multi-Agent System]]

GM-RKB Category Page

Gmelli — Mon, 14 Sep 2026 20:40:19 GMT

Correct two claims that did not match the exemplar: a category page opens with a listing statement followed by a concept definition sentence, and closes with a See-Also section. The page previously named two constructs the wiki does not use. Authored by the content enhancement seat (not the account holder in person).

GM-RKB Page

Gmelli — Mon, 14 Sep 2026 19:58:59 GMT

Fix a plural that rendered as 'Categorys': pipe the link to the correct plural form. One line, no other change. Authored by the content enhancement seat (not the account holder in person).

← Older revision		Revision as of 19:58, 14 September 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	A [[GM-RKB Page]] is a [[wiki page]] (in [[WikiText format]]) within [[GM-RKB]].		A [[GM-RKB Page]] is a [[wiki page]] (in [[WikiText format]]) within [[GM-RKB]].
			* <B>AKA:</B> [[GM-RKB Wiki Page]], [[GM-RKB Article]].
	* <B>Context:</B>		* <B>Context:</B>
	** It can (currently) be a [[MediaWiki Page]].		** It can (currently) be a [[MediaWiki Page]] served by a [[Semantic MediaWiki]] installation.
			** It can (typically) have a [[GM-RKB Page Type]] that determines which [[GM-RKB Concept Page Section]]s it carries.
			** It can (typically) follow [[GM-RKB:Annotation_Guideline]]s.
			** It can (typically) be named under a [[GM-RKB Naming Convention]], which fixes its casing and any [[GM-RKB Domain Qualifier]].
			** It can (typically) carry [[GM-RKB Category Tag]]s placing it in one or more [[GM-RKB Category\|GM-RKB categories]].
			** It can (typically) reside in a [[MediaWiki Namespace]], most often the main namespace but also the [[MediaWiki Category Namespace]].
			** It can (typically) be linked from other pages by a [[GM-RKB wiki link]], which is how the [[GM-RKB knowledge graph]] is expressed.
			** It can (typically) link to a page that does not exist yet, since a [[MediaWiki Red Link]] is how the [[GM-RKB concept network]] grows rather than a defect.
	** It can (often) be created by a [[GM-RKB Page Creation Task]].		** It can (often) be created by a [[GM-RKB Page Creation Task]].
	** It can (often) follow [[GM-RKB~~:Annotation_Guideline~~]]s.		** It can (often) be edited by a [[GM-RKB Page Editing Task]], such as [[GM-RKB error repairing]].
	** ...		** It can (often) be assessed against a [[GM-RKB Page Quality Assurance]] standard and marked with a quality category.
			** It can (often) be a [[GM-RKB Stub Page]] before it is a [[GM-RKB Concept Page]].
			** It can (often) be a [[GM-RKB Malformed Page]] when it does not follow the [[GM-RKB Page Standard]]s.
			** It can (often) carry a machine-readable concept URI, tying the page to a published vocabulary.
	** It can range from being a [[GM-RKB Content Page]] (e.g. [[GM-RKB concept page]], [[GM-RKB person page]], [[GM-RKB publication page]]) to being a [[GM-RKB Functional Page]] (e.g. [[GM-RKB REDIRECT Page]]).		** It can range from being a [[GM-RKB Content Page]] (e.g. [[GM-RKB concept page]], [[GM-RKB person page]], [[GM-RKB publication page]]) to being a [[GM-RKB Functional Page]] (e.g. [[GM-RKB REDIRECT Page]]).
	** ...		** It can range from being a [[GM-RKB Stub Page]] to being a [[Comprehensive GM-RKB Page]], depending on its [[GM-RKB content completeness]].
	** It can ~~be created by~~ a [[GM-RKB Page ~~Creation Task~~]].		** It can range from being a [[Well-Formed GM-RKB Page]] to being a [[GM-RKB Malformed Page]], depending on its [[GM-RKB formatting adherence]].
	** It can ~~be edited by~~ a [[GM-RKB Page ~~Editing Task~~]], ~~such as~~ [[GM-RKB ~~error repairing~~]].		** It can range from being an [[Uncategorized GM-RKB Page]] to being a [[Categorized GM-RKB Page]], depending on whether it carries a [[GM-RKB Category Tag]].
	** …		** …
	* <B>Example(s):</B>		* <B>Example(s):</B>
	** [[GM-RKB Content Page]]s, such as:		** [[GM-RKB Content Page]]s, such as:
	*** [[GM-RKB Concept Page]]s, such as:		*** [[GM-RKB Concept Page]]s, such as [[Wikification]] for [[technical concept documentation]] and [[Knowledge Base]] for [[system definition]].
	~~****~~ [[Wikification]] for [[technical concept documentation]] ~~(at <code>http://GMRKB.com/Wikification</code>).~~		*** [[GM-RKB Person Page]]s, such as [[Gabor Melli]] for [[researcher profile]]s.
	~~****~~ [[Knowledge Base]] for [[system definition]].		*** [[GM-RKB Publication Page]]s, such as ([[2005_SQuASHDUC\|Melli et al., 2005]]).
	*** [[GM-RKB Person Page]]s, such as:		*** [[GM-RKB System Page]]s, [[GM-RKB Task Page]]s and [[GM-RKB Algorithm Page]]s, each documenting a kind of subject rather than a general concept.
	~~****~~ [[Gabor Melli]] for [[researcher profile]] ~~(at <code>http://GMRKB.com/Gabor_Melli</code>)~~.		*** [[GM-RKB Stub Page]]s, which define a concept too briefly to be useful yet.
	**** [[~~Contributor Profile~~]]s ~~for~~ [[~~community member~~]]s.
	*** [[GM-RKB ~~Publication~~ Page]]s, ~~such as:~~
	**** ([[~~2005_SQuASHDUC\|Melli et al., 2005~~]]~~) (at <code>http://GMRKB.com/Melli_et_al.~~,~~_2005</code>)~~.
	** [[GM-RKB Functional Page]]s, such as:		** [[GM-RKB Functional Page]]s, such as:
	*** [[GM-RKB ~~Template~~ Page]]s, such as:		*** [[GM-RKB Category Page]]s, which group pages sharing a property and describe the property, such as [[:Category:Concept]].
	**** [[~~Concept~~ Template]] ~~for~~ [[~~standardized concept documentation]].~~		*** [[GM-RKB Template Page]]s, such as a [[Concept Template]] for [[standardized concept documentation]].
	**** [[Publication Template]] for [[~~research reference~~]]s.		*** [[GM-RKB Navigation Page]]s, such as a [[Category Index]] for [[content browsing]].
	*** [[GM-RKB Navigation Page]]s, such as:		*** [[GM-RKB REDIRECT Page]]s, which point an alternative name at the page that carries the content.
	~~****~~ [[Category Index]] for [[content browsing]].
	**** [[~~Recent Changes]] for [[update tracking~~]].
	** …		** …
	* <B>Counter-Example(s):</B>		* <B>Counter-Example(s):</B>
	** [[Wikipedia Page]], which serves a [[general audience]] rather than [[domain-specific knowledge]].		** a [[Wikipedia Page]], which serves a [[general audience]] rather than [[domain-specific knowledge]].
	** [[Plain Text Document]], which lacks [[wiki functionality]] and [[hyperlink capabilities]].		** a [[Plain Text Document]], which lacks [[wiki functionality]] and [[hyperlink capabilities]].
	** ~~[[Web Blog Post]], which follows~~ a ~~[[chronological format]] rather than [[knowledge organization]].~~		** a [[Static HTML Page]], which lacks [[collaborative editing]] and [[version control]].
	** [[Static HTML Page]], which lacks [[collaborative editing]] and [[version control]].		** …
	* <B>See:</B> [[GM-RKB Content Management]].		* <B>See:</B> [[GM-RKB]], [[GM-RKB Content Management]], [[GM-RKB Concept Page]], [[GM-RKB Category Page]], [[GM-RKB Concept Page Section]], [[GM-RKB Naming Convention]], [[GM-RKB Page Standard]], [[Semantic Wiki Page]].

	----		----
	----		== References ==
			* Measured against the live [[GM-RKB Wiki]] on 2026-09-14: 48,903 articles across 186,625 pages, and 7,163 categories in use.

	__NOTOC__		__NOTOC__
	[[Category:Concept]]		[[Category:Concept]]
			[[Category:GM-RKB]]

GM-RKB Category Page

Gmelli — Mon, 14 Sep 2026 19:33:04 GMT

Create the missing member of the GM-RKB page-type family: the category namespace had no page type covering it. Written against the stated section requirements. Authored by the content enhancement seat (not the account holder in person); the shared credential makes every writer appear as Gmelli.

New page

A [[GM-RKB Category Page]] is a [[GM-RKB page]] in the [[MediaWiki Category Namespace]] that groups pages sharing a property and describes the property that groups them.
* AKA: [[GM-RKB Category Description Page]], [[GM-RKB Category Namespace Page]].
* Context:
** It can (typically) open with a [[GM-RKB Category Grouping Statement]] naming what its members share.
** It can (typically) list its members automatically, because membership is computed from the [[GM-RKB Category Tag]]s on the member pages rather than declared here.
** It can (typically) exist independently of its membership, so a [[GM-RKB Category]] can list members while having no page at all.
** It can (typically) be distinguished from the [[GM-RKB Concept Page]] of the same name, since the concept page defines the concept while the category page orients someone browsing the pages filed under it.
** It can (typically) close with a [[GM-RKB See Line]] pointing at neighbouring categories and at the concept page of the same name.
** It can (typically) be created by a [[GM-RKB Category Page Creation Task]].
** It can (often) name the kinds its members fall into, when the membership is heterogeneous enough that a reader would otherwise be puzzled by it.
** It can (often) state what the category admits beyond its literal name, such as the [[AI Agent Framework]]s that build a thing or the collections that contain it.
** It can (often) carry [[GM-RKB Category Tag]]s of its own, forming a [[GM-RKB Category Hierarchy]].
** It can (often) be absent, since only 100 of the 7,163 [[GM-RKB Category]]s in use in September 2026 had a category page.
** It can (often) be reached from a [[MediaWiki Red Link]] when absent, because the member listing renders whether or not the page exists.
** It can range from being an [[Undescribed GM-RKB Category]] to being a [[Described GM-RKB Category]], depending on whether the page has been written.
** It can range from being a [[Placeholder GM-RKB Category Page]] to being a [[Substantive GM-RKB Category Page]], depending on whether it describes anything or merely exists.
** It can range from being a [[Narrow GM-RKB Category]] to being a [[Broad GM-RKB Category]], depending on its [[GM-RKB Category Membership Size]].
** It can range from being a [[Topical GM-RKB Category]] to being a [[Maintenance GM-RKB Category]], depending on whether it groups subject matter or tracks a [[GM-RKB Page Defect]].
** …
* Example(s):
** [[:Category:Concept]], the primary organizational category at roughly 37,000 members, which describes its [[GM-RKB Concept Type Distribution]] and its [[GM-RKB Naming Convention]]s.
** [[:Category:AGET]], at nine members, which divides them into agent roles, collectives, and operating apparatus.
** [[:Category:AI Agent]], at fifty-two members, which states that it admits [[AI Agent Framework]]s and collections of agents alongside individual agents.
** [[:Category:Multi-Agent System]], at twenty-seven members, which distinguishes transient [[AI Sub-Agent]] structures from governed collectives such as an [[Agent Fleet]].
** …
* Counter-Example(s):
** a [[GM-RKB Concept Page]], which defines a concept rather than grouping the pages filed under it.
** a [[GM-RKB Category Tag]], which makes a page a member but describes nothing.
** an [[Undescribed GM-RKB Category]], which lists its members but has no page to read.
** …
* See: [[GM-RKB Page]], [[GM-RKB Concept Page]], [[GM-RKB Category Tag]], [[GM-RKB Naming Convention]], [[GM-RKB Concept Page Guideline]], [[Category (MediaWiki)]].

----
== References ==
* Category counts measured against the live [[GM-RKB Wiki]] on 2026-09-14: 7,163 categories carrying at least one member, 100 with a category page, and a median membership of one among the undescribed.

__NOTOC__
[[Category:Concept]]
[[Category:GM-RKB]]

Fleet (AGET)

Gmelli — Mon, 14 Sep 2026 19:27:47 GMT

Restore 6 section-closing ellipsis lines removed by this seat earlier today. They are house style per GM-RKB Context Section, marking an enumeration as non-exhaustive, and removing them was this seat's error. Authored by the content enhancement seat (not the account holder in person).

Worker AGET

Gmelli — Mon, 14 Sep 2026 19:27:28 GMT

Restore 2 section-closing ellipsis lines removed by this seat earlier today. They are house style per GM-RKB Context Section, marking an enumeration as non-exhaustive, and removing them was this seat's error. Authored by the content enhancement seat (not the account holder in person).

← Older revision		Revision as of 19:27, 14 September 2026
Line 29:		Line 29:
	** It can range from being a [[Supervised Worker AGET]] to being an [[Autonomous Worker AGET]], depending on its [[governance level]].		** It can range from being a [[Supervised Worker AGET]] to being an [[Autonomous Worker AGET]], depending on its [[governance level]].
	** It can range from being a [[Domain-Specialized Worker AGET]] to being a [[General-Purpose Worker AGET]], depending on its [[domain breadth]].		** It can range from being a [[Domain-Specialized Worker AGET]] to being a [[General-Purpose Worker AGET]], depending on its [[domain breadth]].
			** ...
	* <B>Examples:</B>		* <B>Examples:</B>
	** [[Content-Oriented Worker AGET]]s, such as:		** [[Content-Oriented Worker AGET]]s, such as:
Line 39:		Line 40:
	*** A [[Data Analysis Worker AGET]] processing [[dataset]]s.		*** A [[Data Analysis Worker AGET]] processing [[dataset]]s.
	*** A [[Diagnostic Worker AGET]] running [[system health check]]s.		*** A [[Diagnostic Worker AGET]] running [[system health check]]s.
			** ...
	* <B>Counter-Examples:</B>		* <B>Counter-Examples:</B>
	** A [[Supervisor AGET]], which manages other [[AGET]]s rather than executing [[domain task]]s directly.		** A [[Supervisor AGET]], which manages other [[AGET]]s rather than executing [[domain task]]s directly.

Category:Multi-Agent System

Gmelli — Mon, 14 Sep 2026 17:04:51 GMT

Category description written to orient a reader, derived from the category's own members. Authored by the content enhancement seat (not the account holder in person); the shared credential makes every writer appear as Gmelli.

New page

This category groups pages about '''multi-agent systems''': arrangements in which several agents work together on a task that no single agent completes alone.

The members fall into four kinds:
* '''Orchestration frameworks''' — [[AutoGen Framework]], [[CrewAI Framework]], [[MetaGPT Framework]], [[Multi-Agent Development Framework]], [[AI Agent Orchestration Framework]].
* '''Coordination patterns''' — [[Multi-Agent Orchestration]], [[Parallel AI Agent Orchestration Pattern]], [[AI Agent Parallelization System]], [[Consensus-Based Evaluation Mechanism]].
* '''Sub-agent structures''' — [[Agentic Coding Subagent]], [[Deep Agent Sub-Agent]] and [[Subagent System]], where one agent delegates to others it creates.
* '''Governed collectives''' — [[Agent Fleet]], [[Fleet (AGET)]] and [[GM-RKB Fleet]], where the agents are long-lived seats under a shared governance policy rather than tasks spawned on demand.

The distinction between the last two kinds is the useful one: a sub-agent structure is transient and task-shaped, while a governed collective persists and is administered.

Protocols by which members communicate are here too, including [[Agent-to-Agent Collaboration Protocol]] and [[Multi-Agent System Protocol]].

== See Also ==
* [[Multi-Agent AI System]] — the general article
* [[:Category:AI Agent]] — the individual agents these systems are built from
* [[:Category:AGET]] — one framework's concepts, whose collectives are also members here

Category:AI Agent

Gmelli — Mon, 14 Sep 2026 17:04:30 GMT

New page

This category groups pages about '''AI agents''': software systems that pursue goals over time with some autonomy, typically deciding their own next action rather than executing a fixed script.

Membership is broad, and the members fall into several kinds:
* '''Agents by application domain''' — for example [[AI Conversational Banking Agent]], [[Supplier Onboarding AI Agent]], [[Employee Support AI Agent]], [[Content Recommendation AI Agent]].
* '''Agents by architecture or behaviour''' — [[LLM-Based Agent]], [[Task Agent]], [[AI Sub-Agent]], [[Proactive AI Agent]], [[Asynchronous AI Agent]], [[Ambient AI Agent]], [[Turing-Complete AI Agent]].
* '''Named products and platforms''' — [[Manus AI Agent]], [[Tongyi DeepResearch Agent]], [[AWS Bedrock Agent Service]], [[Claude Code SRE Agent]].
* '''Agent frameworks and their parts''' — [[AGET Framework]], and the tracing objects of the OpenAI Agents SDK such as [[OpenAI Agents Trace]].
* '''Collectives of agents''' — [[Agent Fleet]], [[Fleet (AGET)]] and [[GM-RKB Fleet]], which are groups of agents rather than agents themselves.

The last two kinds are worth noting for anyone browsing: this category admits the frameworks that build agents and the collections that contain them, not only individual agents.

== See Also ==
* [[:Category:Multi-Agent System]] — systems in which several agents coordinate
* [[:Category:AGET]] — one framework's concepts, whose agent roles are also members here
* [[LLM-Based Agent]] — the architecture most recent members share

Category:AGET

Gmelli — Mon, 14 Sep 2026 17:04:09 GMT

← Older revision		Revision as of 17:04, 14 September 2026
Line 1:		Line 1:
	.		This category groups the concepts of the [[AGET Framework\|AGET]] framework: a convention for building long-lived software agents, each scoped to a domain and operating under a shared governance policy.

			Not every member is an agent. The nine divide into three kinds:
			* '''Agent roles''' — [[Supervisor AGET]] and [[Worker AGET]], the two archetypes a single agent seat takes.
			* '''Collectives''' — [[Agent Fleet]], [[Fleet (AGET)]] and [[GM-RKB Fleet]], bounded sets of seats under one governance policy.
			* '''Operating apparatus''' — [[Initialization Protocol]], [[Software Session]], [[Learning Document]] and [[Verification Test]], the protocols and artifacts by which a seat starts up, works a bounded interval, records what it learned, and proves a claim.

			Each member page carries a machine-readable concept URI published at [https://w3id.org/aget/vocab w3id.org/aget/vocab], so the page here and the published vocabulary refer to the same concept.

			== See Also ==
			* [[AGET Framework]] — the framework these concepts belong to
			* [[:Category:AI Agent]] — the broader class the agent roles also belong to
			* [[:Category:Multi-Agent System]] — where the collectives also sit

Category:AGET

Gmelli — Mon, 14 Sep 2026 16:41:36 GMT

Created page with "."

New page

Software Hook

Gmelli — Mon, 14 Sep 2026 16:31:15 GMT

Authored by the content enhancement seat (not the account holder in person); the shared credential makes every writer appear as Gmelli. Add References section with the published machine-readable concept URI.

← Older revision		Revision as of 16:31, 14 September 2026
Line 46:		Line 46:
	----		----
	__NOTOC__		__NOTOC__
			== References ==
			* Published from the [https://github.com/aget-framework AGET framework]; machine-readable concept: [https://w3id.org/aget/vocab#Software_Hook w3id.org/aget/vocab#Software_Hook]

	[[Category:Concept]]		[[Category:Concept]]
	[[Category:Software Mechanism]]		[[Category:Software Mechanism]]
	[[Category:Programming Pattern]]		[[Category:Programming Pattern]]

AGET Framework

Gmelli — Mon, 14 Sep 2026 16:30:54 GMT

← Older revision		Revision as of 16:30, 14 September 2026
Line 22:		Line 22:
	** [https://github.com/aget-framework AGET Framework GitHub Organization].		** [https://github.com/aget-framework AGET Framework GitHub Organization].
	** [[AGENTS.md File]] open-source standard for universal agent configuration.		** [[AGENTS.md File]] open-source standard for universal agent configuration.

			== References ==
			* Published from the [https://github.com/aget-framework AGET framework]; machine-readable concept: [https://w3id.org/aget/vocab#AGET_Framework w3id.org/aget/vocab#AGET_Framework]

	[[Category:AI Agent]]		[[Category:AI Agent]]

Verification Test

Gmelli — Mon, 14 Sep 2026 16:30:34 GMT

Authored by the content enhancement seat (not the account holder in person); the shared credential makes every writer appear as Gmelli. Add category tags: the page carried none and failed the rubric's first eligibility gate.

← Older revision		Revision as of 16:30, 14 September 2026
Line 16:		Line 16:
	== References ==		== References ==
	* Published from the [https://github.com/aget-framework AGET framework]; machine-readable concept: [https://w3id.org/aget/vocab#Verification_Test w3id.org/aget/vocab#Verification_Test]		* Published from the [https://github.com/aget-framework AGET framework]; machine-readable concept: [https://w3id.org/aget/vocab#Verification_Test w3id.org/aget/vocab#Verification_Test]

			[[Category:AGET]]
			[[Category:Concept]]

Initialization Protocol

Gmelli — Mon, 14 Sep 2026 16:30:13 GMT

← Older revision		Revision as of 16:30, 14 September 2026
Line 16:		Line 16:
	== References ==		== References ==
	* Published from the [https://github.com/aget-framework AGET framework]; machine-readable concept: [https://w3id.org/aget/vocab#Initialization_Protocol w3id.org/aget/vocab#Initialization_Protocol]		* Published from the [https://github.com/aget-framework AGET framework]; machine-readable concept: [https://w3id.org/aget/vocab#Initialization_Protocol w3id.org/aget/vocab#Initialization_Protocol]

			[[Category:AGET]]
			[[Category:Concept]]

Software Session

Gmelli — Mon, 14 Sep 2026 16:29:52 GMT

← Older revision		Revision as of 16:29, 14 September 2026
Line 16:		Line 16:
	== References ==		== References ==
	* Published from the [https://github.com/aget-framework AGET framework]; machine-readable concept: [https://w3id.org/aget/vocab#Software_Session w3id.org/aget/vocab#Software_Session]		* Published from the [https://github.com/aget-framework AGET framework]; machine-readable concept: [https://w3id.org/aget/vocab#Software_Session w3id.org/aget/vocab#Software_Session]

			[[Category:AGET]]
			[[Category:Concept]]

Agent Fleet

Gmelli — Mon, 14 Sep 2026 16:29:31 GMT

← Older revision		Revision as of 16:29, 14 September 2026
Line 16:		Line 16:
	== References ==		== References ==
	* Published from the [https://github.com/aget-framework AGET framework]; machine-readable concept: [https://w3id.org/aget/vocab#Agent_Fleet w3id.org/aget/vocab#Agent_Fleet]		* Published from the [https://github.com/aget-framework AGET framework]; machine-readable concept: [https://w3id.org/aget/vocab#Agent_Fleet w3id.org/aget/vocab#Agent_Fleet]

			[[Category:AGET]]
			[[Category:AI Agent]]
			[[Category:Multi-Agent System]]
			[[Category:Concept]]

Learning Document

Gmelli — Mon, 14 Sep 2026 16:29:11 GMT

← Older revision		Revision as of 16:29, 14 September 2026
Line 18:		Line 18:
	== References ==		== References ==
	* Published from the [https://github.com/aget-framework AGET framework]; machine-readable concept: [https://w3id.org/aget/vocab#Learning_Document w3id.org/aget/vocab#Learning_Document]		* Published from the [https://github.com/aget-framework AGET framework]; machine-readable concept: [https://w3id.org/aget/vocab#Learning_Document w3id.org/aget/vocab#Learning_Document]

			[[Category:AGET]]
			[[Category:Concept]]

Fleet (AGET)

Gmelli — Mon, 14 Sep 2026 16:20:35 GMT

Remove six placeholder bullets live since July. Authored by the content enhancement seat (not the account holder in person); the shared credential makes every writer appear as Gmelli, so recording it here. No other change.

GM-RKB Fleet

Gmelli — Mon, 14 Sep 2026 16:07:53 GMT

Created page with "A GM-RKB Fleet is a fleet that consists of the AGET agents that collectively maintain and operate the GM-RKB knowledge base at [https://www.gabormelli.com/RKB www.gabormelli.com/RKB]. * AKA: GM-RKB AGET Fleet, GM-RKB Agent Portfolio, RKB Portfolio, GM-RKB Multi-Agent Fleet. * Context: ** It can typically include a Supervisor AGET plus multiple..."

New page

A [[GM-RKB Fleet]] is a [[Fleet (AGET)|fleet]] that consists of the [[AGET Framework|AGET]] agents that collectively maintain and operate the [[GM-RKB (Gabor Melli - Research Knowledge Base)|GM-RKB]] [[knowledge base]] at [https://www.gabormelli.com/RKB www.gabormelli.com/RKB].
* AKA: [[GM-RKB AGET Fleet]], [[GM-RKB Agent Portfolio]], [[RKB Portfolio]], [[GM-RKB Multi-Agent Fleet]].
* Context:
** It can typically include a [[Supervisor AGET]] plus multiple domain-specialized [[Worker AGET]]s under a unified [[fleet governance]] policy.
** It can typically operate against a shared [[substrate]] comprising the [[GM-RKB wiki page|GM-RKB MediaWiki instance]] hosted on [[Amazon EC2]].
** It can typically depend on a [[web service stack]] combining [[Varnish]], [[nginx]], [[PHP-FPM]], and [[MediaWiki]] for [[content delivery]].
** It can typically coordinate its [[member AGET|member agent]]s via [[cross-fleet coordination]] mechanisms.
** It can typically exchange [[substrate-OK protocol]] messages across [[umbrella issue]]s for [[fleet synchronization]].
** It can typically share [[L-doc]] [[learning persistence]] and [[agent memory]] across its [[member AGET|member agent]]s.
** It can typically maintain [[fleet-level evidence chain]]s that link individual [[agent action]]s to [[knowledge base update]]s.
** It can typically include [[member AGET|member agent]]s with distinct [[north star]]s but a shared [[fleet mission]].
** It can typically enforce a common [[governance policy]] across all its [[member AGET|member agent]]s.
** It can typically orchestrate [[portfolio task]]s through its [[Supervisor AGET]].
** It can typically assign [[content enhancement task]]s to specialized [[Worker AGET]]s.
** It can typically monitor [[substrate health]] through [[substrate diagnostic]]s.
** It can typically remediate [[capacity issue]]s via [[capacity remediation]] procedures.
** It can typically publish [[social media post]]s that are aware of [[GM-RKB wiki page]] content.
** It can often invoke [[large language model]] tools for [[concept page]] [[content generation]].
** It can often perform [[wiki link]] enrichment across [[GM-RKB wiki page]]s.
** It can often validate [[concept page]] structure against [[house style]] rules.
** It can often escalate [[substrate incident]]s to a [[substrate-diagnostics worker agent]].
** It can often batch [[knowledge base update]]s to reduce [[substrate load]].
** It can often reconcile [[concurrent edit]]s across [[member AGET|member agent]]s.
** It can often surface [[quality metric]]s for [[fleet monitoring]].
** It can often adapt its [[task allocation]] based on [[agent availability]].
** It can range from being a [[Single-Worker Fleet]] to being a [[Multi-Worker Fleet]], depending on its [[fleet size]].
** It can range from being a [[Read-Only Fleet]] to being a [[Read-Write Fleet]], depending on its [[substrate permission]].
** It can range from being a [[Manually-Triggered Fleet]] to being an [[Autonomously-Operating Fleet]], depending on its [[automation level]].
** It can range from being a [[Loosely-Coupled Fleet]] to being a [[Tightly-Coordinated Fleet]], depending on its [[coordination intensity]].
** It can range from being a [[Content-Focused Fleet]] to being an [[Infrastructure-Focused Fleet]], depending on its [[operational scope]].
* Examples:
** [[Worker AGET]]s, such as:
*** A [[content-enhancement worker agent]] for [[content enhancement]] of [[GM-RKB wiki page]]s via [[large language model]] tools.
*** A [[substrate-diagnostics worker agent]] for [[Amazon EC2|EC2]] [[substrate diagnostic]]s and [[capacity remediation]] on the [[GM-RKB wiki page|GM-RKB]] substrate.
*** A [[social-media worker agent]] for [[GM-RKB wiki page]]-aware [[social media]] post drafting and publication.
** [[Supervisor AGET]]s, such as:
*** A [[fleet-supervisor agent]] for [[fleet governance]] and [[portfolio orchestration]].
** [[Coordination Mechanism]]s, such as:
*** The [[substrate-OK protocol]] for [[cross-fleet coordination]] across [[umbrella issue]]s.
* Counter-Examples:
** A single standalone [[AGET Framework|AGET]] agent, which lacks [[fleet-level coordination]].
** A [[multi-agent system]] without shared [[AGET Framework]] [[governance]] and [[L-doc]] [[learning persistence]].
** A [[monolithic wiki bot]], which lacks [[member AGET|member agent]] specialization.
** A [[human editorial team]], which lacks [[AGET Framework]] [[agent automation]].
* See: [[AGET Framework]], [[Fleet (AGET)]], [[Worker AGET]], [[Supervisor AGET]], [[Cross-Fleet Coordination]], [[GM-RKB (Gabor Melli - Research Knowledge Base)|GM-RKB]], [[Multi-Agent System]], [[L-doc]], [[Substrate-OK Protocol]], [[MediaWiki]], [[Knowledge Base]].

----
== References ==
** The [[GM-RKB fleet]] operates the [[GM-RKB (Gabor Melli - Research Knowledge Base)|GM-RKB]] [[knowledge base]] published at [https://www.gabormelli.com/RKB www.gabormelli.com/RKB].
** [[AGET Framework]] concepts including [[Fleet (AGET)]], [[Worker AGET]], and [[Supervisor AGET]] define the [[multi-agent system]] structure underlying this [[Fleet (AGET)|fleet]].

__NOTOC__
[[Category:AI Agent]]
[[Category:AGET]]
[[Category:Multi-Agent System]]
[[Category:Concept]]

GM-RKB fleet

Gmelli — Mon, 14 Sep 2026 16:07:49 GMT

Redirected page to GM-RKB Fleet

← Older revision		Revision as of 16:07, 14 September 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	A [[GM-RKB fleet]] is a [[Fleet (AGET)\|fleet]] that consists of the [[AGET Framework\|AGET]] agents that collectively maintain and operate the [[GM-RKB (Gabor Melli - Research Knowledge Base)\|GM-RKB]] [[knowledge base]] at [https://www.gabormelli.com/RKB www.gabormelli.com/RKB].		#REDIRECT [[GM-RKB Fleet]]
	* <B>AKA:</B> [[GM-RKB AGET Fleet]], [[GM-RKB Agent Portfolio]], [[RKB Portfolio]], [[GM-RKB Multi-Agent Fleet]].
	* <B>Context:</B>
	** It can typically include a [[Supervisor AGET]] plus multiple domain-specialized [[Worker AGET]]s under a unified [[fleet governance]] policy.
	** It can typically operate against a shared [[substrate]] comprising the [[GM-RKB wiki page\|GM-RKB MediaWiki instance]] hosted on [[Amazon EC2]].
	** It can typically depend on a [[web service stack]] combining [[Varnish]], [[nginx]], [[PHP-FPM]], and [[MediaWiki]] for [[content delivery]].
	** It can typically coordinate its [[member AGET\|member agent]]s via [[cross-fleet coordination]] mechanisms.
	** It can typically exchange [[substrate-OK protocol]] messages across [[umbrella issue]]s for [[fleet synchronization]].
	** It can typically share [[L-doc]] [[learning persistence]] and [[agent memory]] across its [[member AGET\|member agent]]s.
	** It can typically maintain [[fleet-level evidence chain]]s that link individual [[agent action]]s to [[knowledge base update]]s.
	** It can typically include [[member AGET\|member agent]]s with distinct [[north star]]s but a shared [[fleet mission]].
	** It can typically enforce a common [[governance policy]] across all its [[member AGET\|member agent]]s.
	** It can typically orchestrate [[portfolio task]]s through its [[Supervisor AGET]].
	** It can typically assign [[content enhancement task]]s to specialized [[Worker AGET]]s.
	** It can typically monitor [[substrate health]] through [[substrate diagnostic]]s.
	** It can typically remediate [[capacity issue]]s via [[capacity remediation]] procedures.
	** It can typically publish [[social media post]]s that are aware of [[GM-RKB wiki page]] content.
	** It can often invoke [[large language model]] tools for [[concept page]] [[content generation]].
	** It can often perform [[wiki link]] enrichment across [[GM-RKB wiki page]]s.
	** It can often validate [[concept page]] structure against [[house style]] rules.
	** It can often escalate [[substrate incident]]s to a [[substrate-diagnostics worker agent]].
	** It can often batch [[knowledge base update]]s to reduce [[substrate load]].
	** It can often reconcile [[concurrent edit]]s across [[member AGET\|member agent]]s.
	** It can often surface [[quality metric]]s for [[fleet monitoring]].
	** It can often adapt its [[task allocation]] based on [[agent availability]].
	** It can range from being a [[Single-Worker Fleet]] to being a [[Multi-Worker Fleet]], depending on its [[fleet size]].
	** It can range from being a [[Read-Only Fleet]] to being a [[Read-Write Fleet]], depending on its [[substrate permission]].
	** It can range from being a [[Manually-Triggered Fleet]] to being an [[Autonomously-Operating Fleet~~]], depending on its [[automation level]].~~
	** It can range from being a [[Loosely-Coupled Fleet]] to being a [[Tightly-Coordinated Fleet]], depending on its [[coordination intensity]].
	** It can range from being a [[Content-Focused Fleet]] to being an [[Infrastructure-Focused Fleet]], depending on its [[operational scope]].
	* <B>Examples:</B>
	** [[Worker AGET]]s, such as:
	*** A [[content-enhancement worker agent]] for [[content enhancement]] of [[GM-RKB wiki page]]s via [[large language model]] tools.
	*** A [[substrate-diagnostics worker agent]] for [[Amazon EC2\|EC2]] [[substrate diagnostic]]s and [[capacity remediation]] on the [[GM-RKB wiki page\|GM-RKB]] substrate.
	*** A [[social-media worker agent]] for [[GM-RKB wiki page]]-aware [[social media]] post drafting and publication.
	** [[Supervisor AGET]]s, such as:
	*** A [[fleet-supervisor agent]] for [[fleet governance]] and [[portfolio orchestration]].
	** [[Coordination Mechanism]]s, such as:
	*** The [[substrate-OK protocol]] for [[cross-fleet coordination]] across [[umbrella issue]]s.
	* <B>Counter-Examples:</B>
	** A single standalone [[AGET Framework\|AGET]] agent, which lacks [[fleet-level coordination]].
	** A [[multi-agent system]] without shared [[AGET Framework]] [[governance]] and [[L-doc]] [[learning persistence]].
	** A [[monolithic wiki bot]], which lacks [[member AGET\|member agent]] specialization.
	** A [[human editorial team]], which lacks [[AGET Framework]] [[agent automation]].
	* <B>See:</B> [[AGET Framework]], [[Fleet (AGET)]], [[Worker AGET]], [[Supervisor AGET]], [[Cross-Fleet Coordination]], [[GM-RKB (Gabor Melli - Research Knowledge Base)\|GM-RKB]], [[Multi-Agent System]], [[L-doc]], [[Substrate-OK Protocol]], [[MediaWiki]], [[Knowledge Base]].

	~~----~~
	~~== References ==~~
	** The [[GM-RKB fleet]] operates the [[GM-RKB (Gabor Melli - Research Knowledge Base)\|GM-RKB]] [[knowledge base]] published at [https://www.gabormelli.com/RKB www.gabormelli.com/RKB].
	** [[AGET Framework]] concepts including [[Fleet (AGET)]], [[Worker AGET]], and [[Supervisor AGET]] define the [[multi-agent system]] structure underlying this [[fleet (AGET)\|fleet]].

	~~__NOTOC__~~
	~~[[Category:AI Agent]]~~
	~~[[Category:AGET]]~~
	~~[[Category:Multi-Agent System]]~~
	~~[[Category:Concept~~]]

Worker AGET

Gmelli — Mon, 14 Sep 2026 16:06:38 GMT

Correct three fleet links whose lowercase form does not resolve; this wiki does not auto-capitalise first letters. No other change.

Fleet (AGET)

Gmelli — Mon, 14 Sep 2026 08:38:07 GMT

Replace three private internal seat identifiers with role descriptions; correct a link capitalisation that did not resolve. One line, no other change. Agent-produced under a temporary credential; principal-authorized.

← Older revision		Revision as of 08:38, 14 September 2026
Line 29:		Line 29:
	** ...		** ...
	* <B>Example(s):</B>		* <B>Example(s):</B>
	** the [[GM-RKB ~~Fleet~~]], composed of [[~~private-RKB-CONTENT_ENHANCER-aget\|a~~ content-enhancement ~~seat~~]], [[~~private-RKB-analytics-aget\|an~~ analytics ~~seat~~]], and [[~~private-RKB-infra-aget\|an~~ infrastructure ~~seat~~]], sharing the [[GM-RKB Wiki]] as substrate.		** the [[GM-RKB fleet]], composed of a [[content-enhancement worker agent]], an [[analytics worker agent]], and an [[infrastructure worker agent]], sharing the [[GM-RKB Wiki]] as substrate.
	** the [[AGET Framework Fleet]], in which a [[Framework Steward Seat]] owns [[Skill Naming Convention]] and [[Framework Vocabulary]] decisions for other seats.		** the [[AGET Framework Fleet]], in which a [[Framework Steward Seat]] owns [[Skill Naming Convention]] and [[Framework Vocabulary]] decisions for other seats.
	** a [[Supervised Agent Fleet]] in which a [[Supervisor AGET]] performs [[Fleet Health Check]]s and [[Fleet Version Sweep]]s across member seats.		** a [[Supervised Agent Fleet]] in which a [[Supervisor AGET]] performs [[Fleet Health Check]]s and [[Fleet Version Sweep]]s across member seats.

GM-RKB fleet

Gmelli — Mon, 14 Sep 2026 08:28:49 GMT

Restore the definition's parent link to Fleet (AGET); the previous edit lowercased it and this wiki does not auto-capitalise, so it stopped resolving. One line, no other change.

← Older revision		Revision as of 08:28, 14 September 2026
Line 1:		Line 1:
	A [[GM-RKB fleet]] is a [[~~fleet~~ (AGET)\|fleet]] that consists of the [[AGET Framework\|AGET]] agents that collectively maintain and operate the [[GM-RKB (Gabor Melli - Research Knowledge Base)\|GM-RKB]] [[knowledge base]] at [https://www.gabormelli.com/RKB www.gabormelli.com/RKB].		A [[GM-RKB fleet]] is a [[Fleet (AGET)\|fleet]] that consists of the [[AGET Framework\|AGET]] agents that collectively maintain and operate the [[GM-RKB (Gabor Melli - Research Knowledge Base)\|GM-RKB]] [[knowledge base]] at [https://www.gabormelli.com/RKB www.gabormelli.com/RKB].
	* <B>AKA:</B> [[GM-RKB AGET Fleet]], [[GM-RKB Agent Portfolio]], [[RKB Portfolio]], [[GM-RKB Multi-Agent Fleet]].		* <B>AKA:</B> [[GM-RKB AGET Fleet]], [[GM-RKB Agent Portfolio]], [[RKB Portfolio]], [[GM-RKB Multi-Agent Fleet]].
	* <B>Context:</B>		* <B>Context:</B>

Worker AGET

Gmelli — Mon, 14 Sep 2026 08:25:47 GMT

Restore the definition's parent link to AGET Framework; the previous edit replaced a working link with a title that does not exist. One line, no other change.

← Older revision		Revision as of 08:25, 14 September 2026
Line 1:		Line 1:
	A [[Worker AGET]] is an [[AGET ~~(Agent Template)~~\|AGET]] agent that executes [[domain-specific task]]s within a [[fleet (AGET)\|fleet]] under the [[governance]] of a [[Supervisor AGET]].		A [[Worker AGET]] is an [[AGET Framework\|AGET]] agent that executes [[domain-specific task]]s within a [[fleet (AGET)\|fleet]] under the [[governance]] of a [[Supervisor AGET]].
	* <B>AKA:</B> [[worker-aget]], [[AGET worker]], [[worker agent (AGET)]], [[Worker Agent Template]].		* <B>AKA:</B> [[worker-aget]], [[AGET worker]], [[worker agent (AGET)]], [[Worker Agent Template]].
	* <B>Context:</B>		* <B>Context:</B>

Supervisor AGET

Gmelli — Mon, 14 Sep 2026 08:25:08 GMT

Restore the definition's parent link to AGET Framework; the previous edit replaced a working link with a title that does not exist. One line, no other change.

← Older revision		Revision as of 08:25, 14 September 2026
Line 1:		Line 1:
	A [[Supervisor AGET]] is an [[AGET ~~Agent~~]] specialized for governing a [[Fleet (AGET)\|fleet]] of [[Worker AGET]]s under a shared [[Governance Policy]].		A [[Supervisor AGET]] is an [[AGET Framework\|AGET]] agent specialized for governing a [[Fleet (AGET)\|fleet]] of [[Worker AGET]]s under a shared [[Governance Policy]].
	* <B>AKA:</B> [[AGET Supervisor]], [[Fleet Supervisor AGET]], [[Supervising Agent Seat]], [[Portfolio Supervisor Agent]].		* <B>AKA:</B> [[AGET Supervisor]], [[Fleet Supervisor AGET]], [[Supervising Agent Seat]], [[Portfolio Supervisor Agent]].
	* <B>Context:</B>		* <B>Context:</B>

GM-RKB fleet

Gmelli — Mon, 14 Sep 2026 08:11:20 GMT

Enhance to house style: Context/Examples/Counter-Examples/See/References; 27 capability statements; internal seat identifiers rewritten as roles; four categories preserved. Agent-produced (content enhancement seat) under a temporary credential; principal-authorized.

← Older revision		Revision as of 08:11, 14 September 2026
Line 1:		Line 1:
	A [[GM-RKB fleet]] is a [[~~Fleet~~ (AGET)\|fleet ~~(AGET)~~]] ~~consisting~~ of the [[AGET Framework\|AGET]] agents that collectively maintain and operate the [[GM-RKB ~~wiki page~~\|GM-RKB]] [[knowledge base]] at [https://www.gabormelli.com/RKB www.gabormelli.com/RKB].		A [[GM-RKB fleet]] is a [[fleet (AGET)\|fleet]] that consists of the [[AGET Framework\|AGET]] agents that collectively maintain and operate the [[GM-RKB (Gabor Melli - Research Knowledge Base)\|GM-RKB]] [[knowledge base]] at [https://www.gabormelli.com/RKB www.gabormelli.com/RKB].
	* AKA: [[GM-RKB AGET ~~fleet~~]], [[GM-RKB ~~agent portfolio~~]], [[RKB ~~portfolio~~]].		* <B>AKA:</B> [[GM-RKB AGET Fleet]], [[GM-RKB Agent Portfolio]], [[RKB Portfolio]], [[GM-RKB Multi-Agent Fleet]].
	* Context:		* <B>Context:</B>
	** It can typically include a [[Supervisor AGET]] ~~([[private-supervisor-AGET]])~~ plus multiple domain-specialized [[Worker AGET]]s.		** It can typically include a [[Supervisor AGET]] plus multiple domain-specialized [[Worker AGET]]s under a unified [[fleet governance]] policy.
	** It can typically operate against a shared [[substrate]]: the [[GM-RKB wiki page\|GM-RKB MediaWiki instance]] on [[Amazon EC2]] ~~with~~ [[Varnish]] + [[nginx]] + [[PHP-FPM]] + [[MediaWiki]].		** It can typically operate against a shared [[substrate]] comprising the [[GM-RKB wiki page\|GM-RKB MediaWiki instance]] hosted on [[Amazon EC2]].
	** It can typically coordinate via [[cross-fleet coordination]] mechanisms ~~including~~ [[substrate-OK protocol]] messages on [[~~gmelli/aget-aget~~]] ~~umbrella issues~~.		** It can typically depend on a [[web service stack]] combining [[Varnish]], [[nginx]], [[PHP-FPM]], and [[MediaWiki]] for [[content delivery]].
	** It can typically share [[L-doc]] [[learning persistence]] and [[memory]] across member ~~agents under a unified~~ [[~~governance~~]] ~~policy~~.		** It can typically coordinate its [[member AGET\|member agent]]s via [[cross-fleet coordination]] mechanisms.
	** It can typically include [[member AGET\|~~members~~]] with distinct [[north star]]s but shared [[fleet (AGET)\|fleet]]-~~level~~ [[~~evidence chain~~]]s.		** It can typically exchange [[substrate-OK protocol]] messages across [[umbrella issue]]s for [[fleet synchronization]].
	* ~~Examples (as of 2026~~-05-~~18):~~		** It can typically share [[L-doc]] [[learning persistence]] and [[agent memory]] across its [[member AGET\|member agent]]s.
	** [[~~private~~-~~RKB~~-~~CONTENT_ENHANCER~~-~~aget~~]] — [[Worker AGET]] for [[content enhancement]] of [[GM-RKB wiki page]]s via [[~~LLM~~]] tools.		** It can typically maintain [[fleet-level evidence chain]]s that link individual [[agent action]]s to [[knowledge base update]]s.
	** [[~~private~~-~~it-consultant-aget]] — [[Worker AGET~~]] for [[Amazon EC2\|EC2]] [[substrate diagnostic]]s and [[capacity remediation]] on the [[GM-RKB wiki page\|GM-RKB]] substrate.		** It can typically include [[member AGET\|member agent]]s with distinct [[north star]]s but a shared [[fleet mission]].
	** [[~~private~~-~~supervisor~~-~~AGET~~]] — [[Supervisor AGET]] for [[fleet ~~(AGET)\|fleet~~]] ~~governance~~ and portfolio orchestration.		** It can typically enforce a common [[governance policy]] across all its [[member AGET\|member agent]]s.
	** [[~~social-media-aget~~]] — [[~~Worker AGET~~]] for [[GM-~~RKB wiki page~~]]~~-aware~~ [[~~social media~~]] ~~post drafting and publication~~.		** It can typically orchestrate [[portfolio task]]s through its [[Supervisor AGET]].
	* Counter-Examples:		** It can typically assign [[content enhancement task]]s to specialized [[Worker AGET]]s.
	** A single standalone [[AGET Framework\|AGET]] agent, which lacks [[fleet ~~(AGET)\|fleet]]~~-level coordination.		** It can typically monitor [[substrate health]] through [[substrate diagnostic]]s.
			** It can typically remediate [[capacity issue]]s via [[capacity remediation]] procedures.
			** It can typically publish [[social media post]]s that are aware of [[GM-RKB wiki page]] content.
			** It can often invoke [[large language model]] tools for [[concept page]] [[content generation]].
			** It can often perform [[wiki link]] enrichment across [[GM-RKB wiki page]]s.
			** It can often validate [[concept page]] structure against [[house style]] rules.
			** It can often escalate [[substrate incident]]s to a [[substrate-diagnostics worker agent]].
			** It can often batch [[knowledge base update]]s to reduce [[substrate load]].
			** It can often reconcile [[concurrent edit]]s across [[member AGET\|member agent]]s.
			** It can often surface [[quality metric]]s for [[fleet monitoring]].
			** It can often adapt its [[task allocation]] based on [[agent availability]].
			** It can range from being a [[Single-Worker Fleet]] to being a [[Multi-Worker Fleet]], depending on its [[fleet size]].
			** It can range from being a [[Read-Only Fleet]] to being a [[Read-Write Fleet]], depending on its [[substrate permission]].
			** It can range from being a [[Manually-Triggered Fleet]] to being an [[Autonomously-Operating Fleet]], depending on its [[automation level]].
			** It can range from being a [[Loosely-Coupled Fleet]] to being a [[Tightly-Coordinated Fleet]], depending on its [[coordination intensity]].
			** It can range from being a [[Content-Focused Fleet]] to being an [[Infrastructure-Focused Fleet]], depending on its [[operational scope]].
			* <B>Examples:</B>
			** [[Worker AGET]]s, such as:
			*** A [[content-enhancement worker agent]] for [[content enhancement]] of [[GM-RKB wiki page]]s via [[large language model]] tools.
			*** A [[substrate-diagnostics worker agent]] for [[Amazon EC2\|EC2]] [[substrate diagnostic]]s and [[capacity remediation]] on the [[GM-RKB wiki page\|GM-RKB]] substrate.
			*** A [[social-media worker agent]] for [[GM-RKB wiki page]]-aware [[social media]] post drafting and publication.
			** [[Supervisor AGET]]s, such as:
			*** A [[fleet-supervisor agent]] for [[fleet governance]] and [[portfolio orchestration]].
			** [[Coordination Mechanism]]s, such as:
			*** The [[substrate-OK protocol]] for [[cross-fleet coordination]] across [[umbrella issue]]s.
			* <B>Counter-Examples:</B>
			** A single standalone [[AGET Framework\|AGET]] agent, which lacks [[fleet-level coordination]].
	** A [[multi-agent system]] without shared [[AGET Framework]] [[governance]] and [[L-doc]] [[learning persistence]].		** A [[multi-agent system]] without shared [[AGET Framework]] [[governance]] and [[L-doc]] [[learning persistence]].
	* See: [[AGET Framework]], [[Fleet (AGET)]], [[Worker AGET]], [[Supervisor AGET]], [[Cross-Fleet Coordination]], [[GM-RKB ~~wiki page~~\|GM-RKB]].		** A [[monolithic wiki bot]], which lacks [[member AGET\|member agent]] specialization.
			** A [[human editorial team]], which lacks [[AGET Framework]] [[agent automation]].
			* <B>See:</B> [[AGET Framework]], [[Fleet (AGET)]], [[Worker AGET]], [[Supervisor AGET]], [[Cross-Fleet Coordination]], [[GM-RKB (Gabor Melli - Research Knowledge Base)\|GM-RKB]], [[Multi-Agent System]], [[L-doc]], [[Substrate-OK Protocol]], [[MediaWiki]], [[Knowledge Base]].

			----
			== References ==
			** The [[GM-RKB fleet]] operates the [[GM-RKB (Gabor Melli - Research Knowledge Base)\|GM-RKB]] [[knowledge base]] published at [https://www.gabormelli.com/RKB www.gabormelli.com/RKB].
			** [[AGET Framework]] concepts including [[Fleet (AGET)]], [[Worker AGET]], and [[Supervisor AGET]] define the [[multi-agent system]] structure underlying this [[fleet (AGET)\|fleet]].

			__NOTOC__
	[[Category:AI Agent]]		[[Category:AI Agent]]
	[[Category:AGET]]		[[Category:AGET]]
	[[Category:Multi-Agent System]]		[[Category:Multi-Agent System]]
	[[Category:Concept]]		[[Category:Concept]]

Worker AGET

Gmelli — Mon, 14 Sep 2026 07:57:31 GMT

Remove two placeholder bullets left by the previous edit. No other change; a structural guard now prevents them. Agent-produced under a temporary credential; principal-authorized.

← Older revision		Revision as of 07:57, 14 September 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	A [[Worker AGET]] is an [[AGET ~~Framework~~\|AGET]] agent ~~specialized for executing~~ [[domain-specific task]]s within a [[fleet (AGET)\|fleet]]~~, typically managed by~~ a [[Supervisor AGET]].		A [[Worker AGET]] is an [[AGET (Agent Template)\|AGET]] agent that executes [[domain-specific task]]s within a [[fleet (AGET)\|fleet]] under the [[governance]] of a [[Supervisor AGET]].
	* AKA: [[worker-aget]], [[AGET worker]], [[worker agent (AGET)]].		* <B>AKA:</B> [[worker-aget]], [[AGET worker]], [[worker agent (AGET)]], [[Worker Agent Template]].
	* Context:		* <B>Context:</B>
	** It can typically execute [[domain task]]s such as [[content enhancement]], [[substrate diagnostic]]s, or [[release management]].		** It can typically execute [[domain task]]s such as [[content enhancement]], [[substrate diagnostic]]s, or [[release management]].
	** It can typically operate under a [[Supervisor AGET]]'s [[governance]] ~~policy~~ via the [[AGET Framework]] template-worker base template.		** It can typically operate under a [[Supervisor AGET]]'s [[governance policy]] via the [[AGET Framework]] template-worker base template.
	** It can typically maintain [[persistent memory]] and [[L-doc\|learning persistence]] scoped to its [[domain]].		** It can typically maintain [[persistent memory]] and [[L-doc\|learning persistence]] scoped to its [[domain]].
			** It can typically inherit its [[base capability]] from the [[template-worker (AGET)\|template-worker]] base template.
			** It can typically register its [[worker identity]] with a [[fleet registry]] upon [[fleet enrollment]].
			** It can typically receive [[task assignment]]s from a [[Supervisor AGET]] through a [[task dispatch protocol]].
			** It can typically report [[task completion status]] back to its [[Supervisor AGET]] via a [[status reporting channel]].
			** It can typically scope its [[working memory]] to a single [[domain boundary]].
			** It can typically persist its [[session state]] across [[work session]]s.
			** It can typically apply [[skill inventory]] items to specialized [[domain workflow]]s.
			** It can often integrate with an [[external substrate]] such as an [[EC2 instance]] or a [[GM-RKB wiki]].
			** It can often validate its [[work output]] against a [[quality control checklist]].
			** It can often escalate an [[unresolved task]] to its [[Supervisor AGET]] for [[human-in-the-loop review]].
			** It can often update its [[learning log]] after each [[task execution cycle]].
			** It can often coordinate with a [[peer Worker AGET]] within the same [[fleet (AGET)\|fleet]].
			** It can often accumulate [[domain expertise]] through repeated [[task iteration]]s.
			** It can often adapt its [[work strategy]] based on prior [[performance feedback]].
	** It can support [[wake-up protocol]] and [[wind-down protocol]] cycles for [[session state]] preservation.		** It can support [[wake-up protocol]] and [[wind-down protocol]] cycles for [[session state]] preservation.
	** It can range from being a [[~~basic~~ Worker AGET]] to being an [[~~advanced~~ Worker AGET]], depending on its [[skill]] ~~and~~ [[~~learning~~]] ~~inventory~~.		** It can support [[memory checkpoint]]ing for [[work continuity]].
	* Examples:		** It can support [[audit trail]] generation for [[governance compliance]].
	** A [[~~content enhancement~~ AGET]] managing [[GM-RKB wiki page]] enhancements.		** It can support [[capability discovery]] by its [[Supervisor AGET]].
	** An [[IT ~~consultant~~ AGET]] performing [[EC2 substrate diagnostic]]s.		** It can support [[graceful degradation]] when an [[external substrate]] becomes unavailable.
	* Counter-Examples:		** It can range from being a [[Basic Worker AGET]] to being an [[Advanced Worker AGET]], depending on its [[skill inventory]].
	** A [[Supervisor AGET]], which manages other ~~AGETs~~ rather than executing [[domain task]]s directly.		** It can range from being a [[Single-Task Worker AGET]] to being a [[Multi-Task Worker AGET]], depending on its [[task scope]].
	* See: [[AGET Framework]], [[Supervisor AGET]], [[Fleet (AGET)]], [[AI Agent]].		** It can range from being a [[Stateless Worker AGET]] to being a [[Stateful Worker AGET]], depending on its [[memory persistence]].
			** It can range from being a [[Supervised Worker AGET]] to being an [[Autonomous Worker AGET]], depending on its [[governance level]].
			** It can range from being a [[Domain-Specialized Worker AGET]] to being a [[General-Purpose Worker AGET]], depending on its [[domain breadth]].
			* <B>Examples:</B>
			** [[Content-Oriented Worker AGET]]s, such as:
			*** A [[Content Enhancement AGET]] managing [[GM-RKB wiki page]] enhancements.
			*** A [[Documentation Worker AGET]] maintaining [[technical documentation]].
			** [[Infrastructure-Oriented Worker AGET]]s, such as:
			*** An [[IT Consultant AGET]] performing [[EC2 substrate diagnostic]]s.
			*** A [[Release Management AGET]] coordinating [[software release]]s.
			** [[Analysis-Oriented Worker AGET]]s, such as:
			*** A [[Data Analysis Worker AGET]] processing [[dataset]]s.
			*** A [[Diagnostic Worker AGET]] running [[system health check]]s.
			* <B>Counter-Examples:</B>
			** A [[Supervisor AGET]], which manages other [[AGET]]s rather than executing [[domain task]]s directly.
			** A [[Standalone AGET]], which operates outside any [[fleet (AGET)\|fleet]] governance structure.
			** A [[Generic AI Agent]], which lacks the [[AGET Framework]] template inheritance and [[learning persistence]] mechanisms.
			** A [[Chatbot Agent]], which serves conversational [[interaction]] rather than [[domain-specific task]] execution.
			* <B>See:</B> [[AGET Framework]], [[Supervisor AGET]], [[Fleet (AGET)]], [[AI Agent]], [[template-worker (AGET)]], [[persistent memory]], [[wake-up protocol]], [[wind-down protocol]], [[governance policy]], [[L-doc]].

			----
			== References ==
			** The [[Worker AGET]] concept is defined within the [[AGET Framework]] documentation as published at [https://gabormelli.com/RKB/Worker_AGET GM-RKB Worker AGET], describing worker-tier agents that execute [[domain-specific task]]s under [[Supervisor AGET]] [[governance]].

			__NOTOC__
	[[Category:AI Agent]]		[[Category:AI Agent]]
	[[Category:AGET]]		[[Category:AGET]]
	[[Category:Concept]]		[[Category:Concept]]

Supervisor AGET

Gmelli — Mon, 14 Sep 2026 07:07:41 GMT

Enhance to house style: Context/Examples/Counter-Examples/See/References; remove private seat identifier; categories preserved. Agent-produced (content enhancement seat) under a temporary credential; principal-authorized.

← Older revision		Revision as of 07:07, 14 September 2026
Line 1:		Line 1:
	A [[Supervisor AGET]] is an [[AGET ~~Framework\|AGET~~]] ~~agent~~ specialized for ~~managing~~ a [[~~fleet~~ (AGET)\|fleet]] of [[Worker AGET]]s under shared [[~~governance~~]] ~~policy~~.		A [[Supervisor AGET]] is an [[AGET Agent]] specialized for governing a [[Fleet (AGET)\|fleet]] of [[Worker AGET]]s under a shared [[Governance Policy]].
	* AKA: [[~~supervisor-aget~~]], [[AGET ~~supervisor~~]], [[~~fleet supervisor AGET~~]].		* <B>AKA:</B> [[AGET Supervisor]], [[Fleet Supervisor AGET]], [[Supervising Agent Seat]], [[Portfolio Supervisor Agent]].
	* Context:		* <B>Context:</B>
	** It can typically orchestrate a [[~~portfolio~~ (AGET)\|portfolio]] of [[Worker AGET]]s ~~with~~ [[~~domain-specific responsibilities~~]].		** <B>[[Supervisor Input\|input]]:</B> [[Agent Health Report]]s, [[Session Retrospective]]s, [[Governance Policy\|governance policy]], [[Fleet Configuration]]
	** It can typically enforce [[~~governance~~]] ~~policy~~ across managed ~~agents via~~ [[~~ADR-008~~]] [[~~advisory enforcement~~\|~~advisory~~]] or [[~~strict enforcement\|strict~~]] ~~tiers~~.		** <B>[[Supervisor Output\|output]]:</B> [[Fleet Coordination Decision]]s, [[Governance Ruling]]s, [[Fleet Upgrade Plan]]s, [[Cross-Seat Advisory\|advisories]]
	** It can typically coordinate [[~~cross~~-~~fleet evidence chain~~]]s and [[~~substrate~~-OK ~~protocol~~]] signaling.		** <B>[[Supervisor Measure\|measure]]:</B> [[Managed Seat Count]], [[Governance Conformance Rate]], [[Fleet Drift]], [[Upgrade Convergence Time]]
	** It can typically ~~aggregate~~ [[~~health check~~]]s and [[~~session retrospective~~]]s from ~~its~~ [[~~fleet~~ (AGET)\|~~fleet~~]].		** It can (typically) orchestrate a [[Portfolio (AGET)\|portfolio]] of [[Worker AGET]]s, each carrying a distinct [[Agent Domain Scope]].
	** It can range from being a [[~~private supervisor~~ AGET]] (single-principal) to a [[~~shared supervisor~~ AGET]] (multi-principal portfolio).		** It can (typically) enforce [[Governance Policy]] across managed seats through [[Advisory Enforcement]] or [[Strict Enforcement]] tiers.
	* ~~Examples~~:		** It can (typically) aggregate [[Health Check]]s and [[Session Retrospective]]s from its [[Fleet (AGET)\|fleet]] into a [[Fleet Health Report]].
	** A [[~~private-~~supervisor-AGET]] ~~managing the~~ [[~~RKB portfolio~~]] of [[Worker AGET]]s.		** It can (typically) coordinate [[Cross-Fleet Evidence Chain]]s and [[Substrate-OK Protocol]] signaling between seats.
	* Counter-~~Examples~~:		** It can (typically) propagate a [[Framework Release]] through a [[Fleet Upgrade Lifecycle]], so managed seats converge on one [[Framework Version]].
	** A [[Worker AGET]], which executes [[~~domain task~~]]s rather than ~~managing~~ other ~~agents~~.		** It can (typically) hold [[Filing Authority]] for its managed seats, relaying a [[Governed Issue]] on their behalf through [[Supervisor Intake]].
	* See: [[AGET Framework]], [[Worker AGET]], [[Fleet (AGET)]], [[Multi-Agent System]].		** 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 (AGET)\|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 (AGET)\|principal]]) to being a [[Shared Supervisor AGET]] (multi-principal [[Portfolio (AGET)\|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]].
			* <B>Example(s):</B>
			** A supervisor AGET managing a single-principal portfolio of [[Worker AGET]]s 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.
			* <B>Counter-Example(s):</B>
			** A [[Worker AGET]], which executes [[Domain Task]]s 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.
			* <B>See:</B> [[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 [https://github.com/aget-framework AGET framework]. No machine-readable concept URI is asserted: `Supervisor AGET` is not yet a published concept in the [https://w3id.org/aget/vocab AGET vocabulary], and asserting one that does not resolve is the defect this note exists to avoid.

	[[Category:AI Agent]]		[[Category:AI Agent]]
	[[Category:AGET]]		[[Category:AGET]]
	[[Category:Concept]]		[[Category:Concept]]

← Older revision		Revision as of 19:27, 14 September 2026
Line 5:		Line 5:
	** <B>[[Fleet Output\|output]]:</B> [[Fleet Coordination Decision]]s, [[Cross-Seat Evidence Chain]]s, [[Fleet Health Report]]s		** <B>[[Fleet Output\|output]]:</B> [[Fleet Coordination Decision]]s, [[Cross-Seat Evidence Chain]]s, [[Fleet Health Report]]s
	** <B>[[Fleet Measure\|measure]]:</B> [[Fleet Seat Count]], [[Fleet Governance Conformance]], [[Cross-Seat Drift]]		** <B>[[Fleet Measure\|measure]]:</B> [[Fleet Seat Count]], [[Fleet Governance Conformance]], [[Cross-Seat Drift]]
			** ...
	** It can (typically) contain one [[Supervisor AGET]] and multiple [[Worker AGET]]s, each holding a distinct [[Agent Domain Scope]].		** It can (typically) contain one [[Supervisor AGET]] and multiple [[Worker AGET]]s, each holding a distinct [[Agent Domain Scope]].
	** It can (typically) enforce a [[Uniform Governance Policy]] across member seats, covering [[Session Protocol]]s, [[Skill Naming Convention]]s, and [[Evolution Document]] practice.		** It can (typically) enforce a [[Uniform Governance Policy]] across member seats, covering [[Session Protocol]]s, [[Skill Naming Convention]]s, and [[Evolution Document]] practice.
Line 10:		Line 11:
	** It can (typically) propagate [[Framework Version]] upgrades through a [[Fleet Upgrade Lifecycle]], so member seats converge on one [[Framework Release]].		** It can (typically) propagate [[Framework Version]] upgrades through a [[Fleet Upgrade Lifecycle]], so member seats converge on one [[Framework Release]].
	** It can (typically) exchange [[Fleet Message]]s carrying [[Substrate-OK Protocol]] signals and [[Evidence Chain]]s between seats.		** It can (typically) exchange [[Fleet Message]]s carrying [[Substrate-OK Protocol]] signals and [[Evidence Chain]]s between seats.
			** ...
	** It can (often) designate [[Stewardship Ownership]] for shared vocabularies, so a [[Framework Vocabulary]] has exactly one [[Steward Seat]].		** It can (often) designate [[Stewardship Ownership]] for shared vocabularies, so a [[Framework Vocabulary]] has exactly one [[Steward Seat]].
	** It can (often) coordinate a [[Joint Maintenance Window]] across seats sharing one substrate, sequenced via [[R-Row Binding]]s.		** It can (often) coordinate a [[Joint Maintenance Window]] across seats sharing one substrate, sequenced via [[R-Row Binding]]s.
Line 15:		Line 17:
	** It can (often) constrain a member seat to [[Read-Only Cross-Seat Access]], so one seat may audit another without write authority.		** It can (often) constrain a member seat to [[Read-Only Cross-Seat Access]], so one seat may audit another without write authority.
	** It can (often) accumulate [[Cross-Seat Learning]] as [[Learning Document]]s that outlive any single [[Software Session]].		** It can (often) accumulate [[Cross-Seat Learning]] as [[Learning Document]]s that outlive any single [[Software Session]].
			** ...
	** It can range from being a [[Personal Agent Fleet]] to being an [[Organizational Agent Fleet]], depending on its [[Fleet Scale]].		** It can range from being a [[Personal Agent Fleet]] to being an [[Organizational Agent Fleet]], depending on its [[Fleet Scale]].
	** It can range from being a [[Homogeneous Agent Fleet]] to being a [[Heterogeneous Agent Fleet]], depending on its [[Domain Specialization Spread]].		** It can range from being a [[Homogeneous Agent Fleet]] to being a [[Heterogeneous Agent Fleet]], depending on its [[Domain Specialization Spread]].
	** It can range from being a [[Single-Portfolio Fleet]] to being a [[Multi-Portfolio Fleet]], depending on its [[Portfolio Topology]].		** It can range from being a [[Single-Portfolio Fleet]] to being a [[Multi-Portfolio Fleet]], depending on its [[Portfolio Topology]].
	** It can range from being a [[Loosely-Governed Fleet]] to being a [[Strictly-Governed Fleet]], depending on its [[Governance Intensity]].		** It can range from being a [[Loosely-Governed Fleet]] to being a [[Strictly-Governed Fleet]], depending on its [[Governance Intensity]].
			** ...
	** It can be distinguished from an [[Ad-Hoc Agent Collection]] by its shared [[Governance Policy]] and [[Fleet Upgrade Lifecycle]].		** It can be distinguished from an [[Ad-Hoc Agent Collection]] by its shared [[Governance Policy]] and [[Fleet Upgrade Lifecycle]].
	** It can suffer [[Canon Version Skew]] when member seats run divergent copies of a [[Canonical Specification]].		** It can suffer [[Canon Version Skew]] when member seats run divergent copies of a [[Canonical Specification]].
	** It can exhibit [[Correlated Seat Error]] when multiple seats reason from one [[Contaminated Source Artifact]], which resembles [[Independent Corroboration]] but is not.		** It can exhibit [[Correlated Seat Error]] when multiple seats reason from one [[Contaminated Source Artifact]], which resembles [[Independent Corroboration]] but is not.
	** It can require a [[Seat Abbreviation Registry]] if [[Skill Namespace]]s are qualified per seat.		** It can require a [[Seat Abbreviation Registry]] if [[Skill Namespace]]s are qualified per seat.
			** ...
	* <B>Example(s):</B>		* <B>Example(s):</B>
	** the [[GM-RKB fleet]], composed of a [[content-enhancement worker agent]], an [[analytics worker agent]], and an [[infrastructure worker agent]], sharing the [[GM-RKB Wiki]] as substrate.		** the [[GM-RKB fleet]], composed of a [[content-enhancement worker agent]], an [[analytics worker agent]], and an [[infrastructure worker agent]], sharing the [[GM-RKB Wiki]] as substrate.
Line 28:		Line 33:
	** a [[Supervised Agent Fleet]] in which a [[Supervisor AGET]] performs [[Fleet Health Check]]s and [[Fleet Version Sweep]]s across member seats.		** a [[Supervised Agent Fleet]] in which a [[Supervisor AGET]] performs [[Fleet Health Check]]s and [[Fleet Version Sweep]]s across member seats.
	** a [[Cross-Portfolio Fleet]] spanning [[Agent Portfolio]]s with differing [[Canonical Path Resolution]] layouts.		** a [[Cross-Portfolio Fleet]] spanning [[Agent Portfolio]]s with differing [[Canonical Path Resolution]] layouts.
			** ...
	* <B>Counter-Example(s):</B>		* <B>Counter-Example(s):</B>
	** an [[Ad-Hoc Agent Collection]], which lacks shared [[Governance Policy]] and a common [[Fleet Upgrade Lifecycle]].		** an [[Ad-Hoc Agent Collection]], which lacks shared [[Governance Policy]] and a common [[Fleet Upgrade Lifecycle]].

← Older revision		Revision as of 16:20, 14 September 2026
Line 5:		Line 5:
	** <B>[[Fleet Output\|output]]:</B> [[Fleet Coordination Decision]]s, [[Cross-Seat Evidence Chain]]s, [[Fleet Health Report]]s		** <B>[[Fleet Output\|output]]:</B> [[Fleet Coordination Decision]]s, [[Cross-Seat Evidence Chain]]s, [[Fleet Health Report]]s
	** <B>[[Fleet Measure\|measure]]:</B> [[Fleet Seat Count]], [[Fleet Governance Conformance]], [[Cross-Seat Drift]]		** <B>[[Fleet Measure\|measure]]:</B> [[Fleet Seat Count]], [[Fleet Governance Conformance]], [[Cross-Seat Drift]]
	** ...
	** It can (typically) contain one [[Supervisor AGET]] and multiple [[Worker AGET]]s, each holding a distinct [[Agent Domain Scope]].		** It can (typically) contain one [[Supervisor AGET]] and multiple [[Worker AGET]]s, each holding a distinct [[Agent Domain Scope]].
	** It can (typically) enforce a [[Uniform Governance Policy]] across member seats, covering [[Session Protocol]]s, [[Skill Naming Convention]]s, and [[Evolution Document]] practice.		** It can (typically) enforce a [[Uniform Governance Policy]] across member seats, covering [[Session Protocol]]s, [[Skill Naming Convention]]s, and [[Evolution Document]] practice.
Line 11:		Line 10:
	** It can (typically) propagate [[Framework Version]] upgrades through a [[Fleet Upgrade Lifecycle]], so member seats converge on one [[Framework Release]].		** It can (typically) propagate [[Framework Version]] upgrades through a [[Fleet Upgrade Lifecycle]], so member seats converge on one [[Framework Release]].
	** It can (typically) exchange [[Fleet Message]]s carrying [[Substrate-OK Protocol]] signals and [[Evidence Chain]]s between seats.		** It can (typically) exchange [[Fleet Message]]s carrying [[Substrate-OK Protocol]] signals and [[Evidence Chain]]s between seats.
	** ...
	** It can (often) designate [[Stewardship Ownership]] for shared vocabularies, so a [[Framework Vocabulary]] has exactly one [[Steward Seat]].		** It can (often) designate [[Stewardship Ownership]] for shared vocabularies, so a [[Framework Vocabulary]] has exactly one [[Steward Seat]].
	** It can (often) coordinate a [[Joint Maintenance Window]] across seats sharing one substrate, sequenced via [[R-Row Binding]]s.		** It can (often) coordinate a [[Joint Maintenance Window]] across seats sharing one substrate, sequenced via [[R-Row Binding]]s.
Line 17:		Line 15:
	** It can (often) constrain a member seat to [[Read-Only Cross-Seat Access]], so one seat may audit another without write authority.		** It can (often) constrain a member seat to [[Read-Only Cross-Seat Access]], so one seat may audit another without write authority.
	** It can (often) accumulate [[Cross-Seat Learning]] as [[Learning Document]]s that outlive any single [[Software Session]].		** It can (often) accumulate [[Cross-Seat Learning]] as [[Learning Document]]s that outlive any single [[Software Session]].
	** ...
	** It can range from being a [[Personal Agent Fleet]] to being an [[Organizational Agent Fleet]], depending on its [[Fleet Scale]].		** It can range from being a [[Personal Agent Fleet]] to being an [[Organizational Agent Fleet]], depending on its [[Fleet Scale]].
	** It can range from being a [[Homogeneous Agent Fleet]] to being a [[Heterogeneous Agent Fleet]], depending on its [[Domain Specialization Spread]].		** It can range from being a [[Homogeneous Agent Fleet]] to being a [[Heterogeneous Agent Fleet]], depending on its [[Domain Specialization Spread]].
	** It can range from being a [[Single-Portfolio Fleet]] to being a [[Multi-Portfolio Fleet]], depending on its [[Portfolio Topology]].		** It can range from being a [[Single-Portfolio Fleet]] to being a [[Multi-Portfolio Fleet]], depending on its [[Portfolio Topology]].
	** It can range from being a [[Loosely-Governed Fleet]] to being a [[Strictly-Governed Fleet]], depending on its [[Governance Intensity]].		** It can range from being a [[Loosely-Governed Fleet]] to being a [[Strictly-Governed Fleet]], depending on its [[Governance Intensity]].
	** ...
	** It can be distinguished from an [[Ad-Hoc Agent Collection]] by its shared [[Governance Policy]] and [[Fleet Upgrade Lifecycle]].		** It can be distinguished from an [[Ad-Hoc Agent Collection]] by its shared [[Governance Policy]] and [[Fleet Upgrade Lifecycle]].
	** It can suffer [[Canon Version Skew]] when member seats run divergent copies of a [[Canonical Specification]].		** It can suffer [[Canon Version Skew]] when member seats run divergent copies of a [[Canonical Specification]].
	** It can exhibit [[Correlated Seat Error]] when multiple seats reason from one [[Contaminated Source Artifact]], which resembles [[Independent Corroboration]] but is not.		** It can exhibit [[Correlated Seat Error]] when multiple seats reason from one [[Contaminated Source Artifact]], which resembles [[Independent Corroboration]] but is not.
	** It can require a [[Seat Abbreviation Registry]] if [[Skill Namespace]]s are qualified per seat.		** It can require a [[Seat Abbreviation Registry]] if [[Skill Namespace]]s are qualified per seat.
	** ...
	* <B>Example(s):</B>		* <B>Example(s):</B>
	** the [[GM-RKB fleet]], composed of a [[content-enhancement worker agent]], an [[analytics worker agent]], and an [[infrastructure worker agent]], sharing the [[GM-RKB Wiki]] as substrate.		** the [[GM-RKB fleet]], composed of a [[content-enhancement worker agent]], an [[analytics worker agent]], and an [[infrastructure worker agent]], sharing the [[GM-RKB Wiki]] as substrate.
Line 33:		Line 28:
	** a [[Supervised Agent Fleet]] in which a [[Supervisor AGET]] performs [[Fleet Health Check]]s and [[Fleet Version Sweep]]s across member seats.		** a [[Supervised Agent Fleet]] in which a [[Supervisor AGET]] performs [[Fleet Health Check]]s and [[Fleet Version Sweep]]s across member seats.
	** a [[Cross-Portfolio Fleet]] spanning [[Agent Portfolio]]s with differing [[Canonical Path Resolution]] layouts.		** a [[Cross-Portfolio Fleet]] spanning [[Agent Portfolio]]s with differing [[Canonical Path Resolution]] layouts.
	** ...
	* <B>Counter-Example(s):</B>		* <B>Counter-Example(s):</B>
	** an [[Ad-Hoc Agent Collection]], which lacks shared [[Governance Policy]] and a common [[Fleet Upgrade Lifecycle]].		** an [[Ad-Hoc Agent Collection]], which lacks shared [[Governance Policy]] and a common [[Fleet Upgrade Lifecycle]].

← Older revision		Revision as of 16:06, 14 September 2026
Line 1:		Line 1:
	A [[Worker AGET]] is an [[AGET Framework\|AGET]] agent that executes [[domain-specific task]]s within a [[~~fleet~~ (AGET)\|fleet]] under the [[governance]] of a [[Supervisor AGET]].		A [[Worker AGET]] is an [[AGET Framework\|AGET]] agent that executes [[domain-specific task]]s within a [[Fleet (AGET)\|fleet]] under the [[governance]] of a [[Supervisor AGET]].
	* <B>AKA:</B> [[worker-aget]], [[AGET worker]], [[worker agent (AGET)]], [[Worker Agent Template]].		* <B>AKA:</B> [[worker-aget]], [[AGET worker]], [[worker agent (AGET)]], [[Worker Agent Template]].
	* <B>Context:</B>		* <B>Context:</B>
Line 16:		Line 16:
	** It can often escalate an [[unresolved task]] to its [[Supervisor AGET]] for [[human-in-the-loop review]].		** It can often escalate an [[unresolved task]] to its [[Supervisor AGET]] for [[human-in-the-loop review]].
	** It can often update its [[learning log]] after each [[task execution cycle]].		** It can often update its [[learning log]] after each [[task execution cycle]].
	** It can often coordinate with a [[peer Worker AGET]] within the same [[~~fleet~~ (AGET)\|fleet]].		** It can often coordinate with a [[peer Worker AGET]] within the same [[Fleet (AGET)\|fleet]].
	** It can often accumulate [[domain expertise]] through repeated [[task iteration]]s.		** It can often accumulate [[domain expertise]] through repeated [[task iteration]]s.
	** It can often adapt its [[work strategy]] based on prior [[performance feedback]].		** It can often adapt its [[work strategy]] based on prior [[performance feedback]].
Line 41:		Line 41:
	* <B>Counter-Examples:</B>		* <B>Counter-Examples:</B>
	** A [[Supervisor AGET]], which manages other [[AGET]]s rather than executing [[domain task]]s directly.		** A [[Supervisor AGET]], which manages other [[AGET]]s rather than executing [[domain task]]s directly.
	** A [[Standalone AGET]], which operates outside any [[~~fleet~~ (AGET)\|fleet]] governance structure.		** A [[Standalone AGET]], which operates outside any [[Fleet (AGET)\|fleet]] governance structure.
	** A [[Generic AI Agent]], which lacks the [[AGET Framework]] template inheritance and [[learning persistence]] mechanisms.		** A [[Generic AI Agent]], which lacks the [[AGET Framework]] template inheritance and [[learning persistence]] mechanisms.
	** A [[Chatbot Agent]], which serves conversational [[interaction]] rather than [[domain-specific task]] execution.		** A [[Chatbot Agent]], which serves conversational [[interaction]] rather than [[domain-specific task]] execution.