Retire the two roles whose subjects the platform does not run - #79
Merged
Conversation
kagent-curator and agentgateway-curator stewarded products this org does not deploy. The operator emits a Deployment per agent and renders a ModelGateway into Envoy AI Gateway resources; no manifest anywhere applies kagent.dev or agentgateway.dev, and no chart in eks-gitops or kx installs either. Deleted rather than renamed, and that is a change of mind worth stating. The first read was that the function survived the products and the roles should follow it. Reading the briefs settled it the other way: the function is already housed. eks-agent-platform-curation covers AgentFleet and ModelGateway, so renaming would have kept two roles whose every line had to be rewritten into what a third role already said. ─── The briefs were not stale, they were invented ─── kagent-curation documented Agent, AgentTool and AgentSkill CRDs, a spec.runtime block with concurrency and queue-depth knobs, an advisor escalation field, kagent_* metrics and a dashboard path. None of it exists. The real AgentSpec is a name, a system prompt, a model route, an image, and optional replicas and resources. A role brief is an instruction manual an agent is handed as fact. One that teaches an API the cluster will reject is worse than no role at all — it produces confident work that cannot apply. ─── What moved to the surviving role ─── The model plane. eks-agent-platform-curator's brief gains the route as the unit of the contract: an agent is an image plus the name of a route, the operator resolves the route to a base URL and a wire format, and which model answers is the gateway's business — which is what lets a model change without touching a fleet. Two errors in that brief went with it: an agent carried a tools[] field that does not exist, and omitted image, which is required. FACTORY_PREAMBLE carried the same description of the AgentFleet artifact, which made it the bar every build is read against rather than a stale note. The roster is 78, and the count is restated in five places plus a test. The test is what caught it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
kagent-curatorandagentgateway-curatorstewarded products this org does not deploy. The operator emits a Deployment per agent and renders aModelGatewayinto Envoy AI Gateway resources; no manifest anywhere applieskagent.devoragentgateway.dev, and no chart in eks-gitops or kx installs either.Deleted rather than renamed, and that's a change of mind worth stating. The first read was that the function survives the products, so the roles should follow it to their new subjects. Reading the briefs settled it the other way: the function is already housed.
eks-agent-platform-curationcovers AgentFleet and ModelGateway, so renaming would have kept two roles whose every line had to be rewritten into what a third role already said.The briefs weren't stale, they were invented
kagent-curationdocumentedAgent,AgentToolandAgentSkillCRDs, aspec.runtimeblock with concurrency and queue-depth knobs, an advisor escalation field,kagent_*metrics and a dashboard path. None of it exists. The realAgentSpecis a name, a system prompt, a model route, an image, and optional replicas and resources.A role brief is an instruction manual an agent is handed as fact. One that teaches an API the cluster will reject is worse than no role at all — it produces confident work that cannot apply. This is the same failure that once taught an invalid Platform, at full scale.
What moved to the surviving role
The model plane.
eks-agent-platform-curatorgains the route as the unit of the contract: an agent is an image plus the name of a route, the operator resolves that route to a base URL and a wire format, and which model answers is the gateway's business — which is what lets a model change without touching a fleet.Two errors in that brief went with it: an agent carried a
tools[]field that doesn't exist, and omittedimage, which is required.FACTORY_PREAMBLEinsrc/standards.tscarried the same description of the AgentFleet artifact — making it the bar every build is read against rather than a stale note.The count
The roster is 78. It's restated in
README.md,CLAUDE.md,AGENTS.md,docs/roster.mdand the roster tree's group total, plus__tests__/team.test.ts— which is what caught it. The same count appears innanohype/docs/platform-reference.mdand the docs site; those follow in the docs-side change.Checks
pnpm typecheck,pnpm lint,pnpm test— 502 tests, 33 files, all pass.