12.0 Meet Felix

Included from Basic tierpacks:agents

After this you can: say who Felix is — the persona every agent lesson walks — what it is for, and how a job description shapes the roles and capabilities it takes on.

Before you start — tick each one:

• Lesson 0.1 — Install and sign in (opschain learn 0.1)

In the GUI: Operations → Agents lists Felix once it is enrolled (lesson 12.2); its agent sheet carries the manifest disclosures, the release it runs, its trust summary and its activity.

This module is one story about one agent. Every lesson from here to the end of the module hires, scopes, watches, rolls and finally retires the same agent, so that by the end you have seen a whole working life rather than nine unrelated features. That agent is Felix. Nothing in this lesson needs a running server; it is the ten minutes of reading that make the rest of the module coherent.

1. Who Felix is

Felix is a persona LimePoint created to demonstrate what an agent on the platform can do. It is not a product, not a bundled binary and not a feature you licence: there is no "Felix pack", and nothing on your server is called Felix until you enrol an agent under that code yourself. In the demo estate Felix is enrolled as the agent with code felix in the project limebank, owned by the release_managers group — and that is exactly the agent the demo kit seeds, so the commands in this module run unchanged against it.

In prose, Felix is the agent; in a command, felix is its code. Both name one thing: a long-running operator process that holds its own identity on the platform and acts under the same authorisation, approval and audit machinery as a person — plus the controls that exist only because the operator is software.

2. Why the documentation has one agent

Agents are easy to describe in the abstract and hard to picture. A reader who meets "an agent" in one lesson, "the SME" in the next and "the service account" in a third is reading about three strangers. Felix is the fix: one named agent, hired once, whose owner, grants, releases and history carry from lesson to lesson.

That is the shape of the module:

• 12.1 says what an agent is and names the two kinds.
• 12.2 hires Felix: a one-use token, an owner, an assignment, a grant, and the ceiling nothing exceeds.
• 12.3 reads Felix's evidence — the activity timeline, the trust review, its working day, its transcripts.
• 12.4 changes Felix the one way the platform allows: a signed release, the stage ladder, instances on lanes, the rollover, and the retirement of the old release.
• 12.5 takes Felix away — drain, halt, revoke — with its history intact.
• 12.6 gives Felix a brokered model and a token budget.
• 12.7 builds Felix from the SDK and packages it as a release.
• 12.8 hands Felix a different job description: the bundled Support SME.
• 12.9 is the other direction — your own AI assistant as a client of the platform.

3. The job description

Felix as a persona can take on new roles and capabilities based on the job description you hand it. Keep the two halves apart, because the platform does:

• The job description is what you give the agent. It is the manifest the agent declares at enrolment — its name, its type (service or ai), a purpose, the capabilities it serves, and for an AI Agent the disclosures of model, adapter, tool surface and credential custody — together with the code that actually runs. Change the job and you change the manifest; on an estate that signs releases, that means a new signed release (lesson 12.4).
• The platform's side is what the agent may do. An owner for accountability, an assignment for the subtree it manages, trust grants with a tier and caps for the work it may request, and ceilings by type and by node classification that no grant exceeds. None of this is in the manifest; the agent's payload can never name a tier or waive a gate.

Across the module Felix takes on three roles under three job descriptions:

Lesson	Felix's job	Type	What changes
12.2–12.5	an operator process patching the prod environment under supervision	service	nothing but grants and releases
12.6	an AI Agent reasoning against a brokered model with a daily token budget	ai	the manifest discloses model, adapter, tool surface and custody; a provider record brokers the key
12.8	the bundled Support SME triaging support tickets	service (the AI lane dark by default)	the kit's manifest, rules file and seed script

The identity fabric, the approval funnel, the kill switches and the audit trail are identical in all three. That is the point of the persona: the job changes, the leash does not.

4. You will see this agent in every lesson

One command recurs through the module, and it is the one to reach for whenever you lose track of Felix:

opschain admin agent show felix

Once Felix is enrolled it answers a two-column table — the identity rows (ID, CODE, PROJECT, OWNED BY, SERVICE ACCOUNT), the manifest facts (TYPE, PURPOSE and the disclosures), the release and lane the instance runs, and the host inventory the process reported. Before enrolment it answers that no agent matches the reference, which is where lesson 12.2 begins.

Check yourself

• What makes Felix a persona rather than a product, and what document gives it a new role?

What you learned

• Felix is a persona LimePoint made to demonstrate the agent platform — the one agent every lesson in this module walks, enrolled as felix in limebank and seeded by the demo kit.
• One named agent lets the module tell one story: hired in 12.2, governed and watched in 12.3, rolled in 12.4, retired in 12.5.
• A job description — the manifest plus the code — is what you hand the agent; owner, assignments, grants and ceilings are what the platform lets it do.
• Felix takes on new roles by taking on new job descriptions: an operator process, an AI Agent, the Support SME — under the same leash each time.

Next: lesson 12.1 — What an agent is; the two kinds (opschain learn 12.1), or back to your track (opschain learn).