Skip to content

WIP: Redis Agent Playbooks self-managed operator docs - #4256

Draft
tylerhutcherson wants to merge 19 commits into
iris-ga-docsfrom
MOD-19679-playbook-operator-docs
Draft

tylerhutcherson wants to merge 19 commits into
iris-ga-docsfrom
MOD-19679-playbook-operator-docs

Conversation

@tylerhutcherson

@tylerhutcherson tylerhutcherson commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

MOD-19679 — Self-managed Redis Agent Playbooks operator documentation.

Adds setup and administration guidance under /operate/iris/agent-playbook/. Operators can prepare dependencies, deploy the chart, provision playbooks and scoped application keys, configure identity-provider access, and optionally extract FAQ proposals from Redis Agent Memory.

Scope

  • Eleven pages: operator landing, self-managed overview, planning, prerequisites, configuration, deployment, authentication/access, API examples, background extraction, operations, and the generated control-plane reference.
  • Private embedding configuration through embedders_connection_details, a public model catalog, bootstrap credentials, scoped application keys, shared control-plane/data-plane OpenID Connect configuration, and optional Identity Service Control authentication.
  • Model discovery before provisioning, Secret/checksum rollouts, health/metrics, administrative clearing, suspension/deletion, backup responsibilities, and upgrades.
  • Opt-in Redis Agent Memory FAQ extraction with workload trust, persistent queueing, generation credentials, staged worker/binding activation, cleanup, and monitoring.
  • Developer handoffs for setup, authentication, retrieval configuration, clearing, and extraction. The shortened developer page is titled Proposals and still links directly to extraction setup.

Release boundary

The matching Helm chart remains unpublished. Guides intentionally use <chart-version> and individual control-plane, data-plane, and Identity Service image-tag placeholders.

The control-plane reference is locked to Iris revision 304467e3e3acf5ff9e6800e03055f0a7806bc14d, with a checked source hash and 13-operation inventory covering model listing, playbook administration, extraction store listing, and extraction binding administration.

Validation

  • Direct CLI examples: 17 CLI/reference checks passed on the combined stack, plus 5 developer-only reference checks. All 10 CLI programs pass Bash syntax checks; all five rendered guides show literal iris commands with the standard product environment variables. --json is used only where a response is saved or parsed.

  • Latest Proposals prose edit: 6 reference checks passed, with the title, 44 code panels, and 14 source links/anchors verified in the local Hugo preview. Existing examples and anchors are unchanged; earlier executable checks remain applicable.

  • Full combined Playbooks docs suite: 138 passed with redis-iris==0.1.0a4, its redis-agent-playbook==0.1.0a3 dependency, and @redis-iris/agent-playbook@0.1.0-alpha.3.

  • 12 live Python/CLI smoke tests passed against freshly built local Iris control/data planes, isolated Redis/Identity Service dependencies, and scoped author/reader keys. Temporary playbooks and keys were removed after each case.

  • Full Hugo 0.143 build passes: 19,928 pages, 665 non-page files, 2,116 static files, and 1,245 aliases. All 47 CLI panels and new source links/anchors were checked in rendered output.

  • Strict TypeScript compilation, Python/shell parsing, OpenAPI checks, source hashes, links, and git diff --check pass.

  • Earlier operator validation still applies to unchanged deployment content: Helm smoke/safety tests, lint, standard and extraction rendering, and all 41 Bash and 13 YAML fences passed.

  • This docs repository has no Taskfile; validation uses the dedicated Playbooks suite and supported Hugo version.

Remaining release work

  • Fill approved chart/image versions, platform support, and release-specific upgrade notes once the matching chart is published.
  • Qualify production sizing, high availability, minimum Redis access-control permissions, and backup/restore guarantees.
  • Correct stale upstream generated extraction descriptions before regenerating the reference; this PR preserves the locked generated contract.
  • CLI parity follow-up: redis/redis-iris#39.

Stack and publication

  • Parent: #4249 — WIP: Redis Agent Playbooks developer docs, targeting main, including unified Python examples and 47 CLI tabs, with direct executable invocations in c45109ecc.
  • This rebased PR: MOD-19679-playbook-operator-docs → MOD-19391-playbook-developer-docs, head 430c680a5. Review relative to the parent to see operator scope and handoffs.
  • Merge the developer PR first, then retarget/rebase this PR onto main and verify its remaining diff.

Both PRs remain draft/WIP and unmerged pending launch publication approval. Merging into main publishes the documentation.

@tylerhutcherson tylerhutcherson added documentation Improvements or additions to documentation op Operate docs iris Iris context engine docs labels Oct 13, 2026
@github-actions

github-actions Bot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

🧠 Redis Memory

Found 8 related items from repository history:

Memory updated at 430c680

@github-actions

github-actions Bot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Staging links:
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/develop/ai/context-engine/agent-playbook/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/develop/ai/context-engine/agent-playbook/concepts/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/develop/ai/context-engine/agent-playbook/limits/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/develop/ai/context-engine/agent-playbook/proposals/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/develop/ai/context-engine/agent-playbook/quickstart/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/develop/ai/context-engine/agent-playbook/retrieval/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/operate/iris/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/operate/iris/agent-playbook/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/operate/iris/agent-playbook/self-managed/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/operate/iris/agent-playbook/self-managed/api-examples/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/operate/iris/agent-playbook/self-managed/authentication/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/operate/iris/agent-playbook/self-managed/configuration/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/operate/iris/agent-playbook/self-managed/control-plane-api-reference/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/operate/iris/agent-playbook/self-managed/deploy/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/operate/iris/agent-playbook/self-managed/extraction/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/operate/iris/agent-playbook/self-managed/operations/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/operate/iris/agent-playbook/self-managed/plan-deployment/
https://redis.io/docs/staging/MOD-19679-playbook-operator-docs/operate/iris/agent-playbook/self-managed/prerequisites/

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@mich-elle-luna mich-elle-luna self-assigned this Oct 13, 2026
@mich-elle-luna
mich-elle-luna self-requested a review October 13, 2026 17:09
@mich-elle-luna

Copy link
Copy Markdown
Collaborator

Hi Tyler, this is looking good so far. But, I've merged in lots of changes since you branched, so here is the info to get this branch to appear with the new look/feel and nav menu from claude:

"Nothing in their pages needs to change. Their branches were cut on Sept 30, before the Iris work merged, and staging builds each branch as-is. Both branches are 133 commits behind main, so they don't have the new nav or dark theme.

What they need to do: Merge main into both branches (or rebase onto it) and push. Their new pages are under develop/ai/context-engine/agent-playbook/ and operate/iris/agent-playbook/. Everything under those two folders gets the Iris sidebar and dark theme automatically, with no frontmatter or extra setup.

What they'll run into:

Developer branch (MOD-19391-playbook-developer-docs): A dry-run merge with main is clean.
Operator branch (MOD-19679-playbook-operator-docs): One conflict, in content/operate/iris/_index.md. They added an Agent Playbooks tile and reworded the intro. Meanwhile main added a console screenshot, switched the tiles from color swatches to icons, and added lists of links. Resolving it means keeping main's version and re-adding their tile and wording.
Their new tile uses a color swatch (color="bg-blue-300"), while the other tiles now use icons. No playbook icon exists yet. They could use icon-redis-iris-64-duotone.png for now, or ask for a new icon."

thank you!

tylerhutcherson and others added 9 commits October 14, 2026 14:38
…amples

Adds three TCE pseudo-client keys, "Python (Iris)", "TypeScript (Iris)",
and "cURL (Iris)", so Iris examples can use the standard clients-example
system instead of multitabs. Each key is the visible tab title and is
shared across all Iris products, so names avoid any one SDK package.

- config.toml: keys in clientsExamples and clientsConfig, modeled on
  RedisVL. Own clientId (iris-python/-typescript/-curl), empty
  quickstartSlug and mappingClientId, so tabs don't carry redis-py or
  node-redis identity in the code-examples JSON metadata.
- build/local_examples.py: .ts/.mts -> typescript, .sh -> bash; a path
  containing 'iris' selects the Iris client (put sources under
  local_examples/iris/). .mts keeps top-level await working under tsx.
  Non-Iris .ts/.sh files resolve to no configured client.
- build/components/example.py: comment prefixes for typescript (//)
  and bash (#); without them Example() rejects the language.

Verified with a throwaway three-language set: the build tagged each file
with the right client and Hugo rendered the tabs with correct step
slices, lexers, full-file templates, and clientId/clientName. The test
set was removed; no pages are converted in this commit.

Gotcha: get_example_id_from_file reads only line 1, so .sh sources must
start with "# EXAMPLE:" and cannot carry a shebang.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Discover turn context through the SDK before running OpenAI Agents SDK or LangGraph. Keep standard MCP clients and tool guidance on the existing MCP page, and suppress drafts while tool failures remain unresolved.
@tylerhutcherson
tylerhutcherson force-pushed the MOD-19679-playbook-operator-docs branch from 0829b25 to efdbd73 Compare October 14, 2026 18:45
@tylerhutcherson
tylerhutcherson force-pushed the MOD-19391-playbook-developer-docs branch from c0ef4a2 to d7293c3 Compare October 14, 2026 18:45
@tylerhutcherson
tylerhutcherson force-pushed the MOD-19679-playbook-operator-docs branch from 14dcc3e to 85afad0 Compare October 18, 2026 00:59
@tylerhutcherson tylerhutcherson changed the title WIP: Playbook self-managed operator docs WIP: Redis Agent Playbooks self-managed operator docs Oct 18, 2026
@tylerhutcherson
tylerhutcherson force-pushed the MOD-19679-playbook-operator-docs branch from 85afad0 to eb6d8a6 Compare October 21, 2026 02:44
@tylerhutcherson
tylerhutcherson force-pushed the MOD-19679-playbook-operator-docs branch from eb6d8a6 to 2c70e92 Compare October 21, 2026 11:25
@tylerhutcherson
tylerhutcherson force-pushed the MOD-19679-playbook-operator-docs branch from 2c70e92 to 430c680 Compare October 21, 2026 11:38
@tylerhutcherson
tylerhutcherson force-pushed the MOD-19391-playbook-developer-docs branch from fafb18d to 7520513 Compare October 22, 2026 20:39
Base automatically changed from MOD-19391-playbook-developer-docs to iris-ga-docs October 22, 2026 22:33

@mich-elle-luna mich-elle-luna left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation iris Iris context engine docs op Operate docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants