feat: add the AI Transformation playbook to the docs - #11
Open
gokulasok-klarityintelligence wants to merge 1 commit into
Open
feat: add the AI Transformation playbook to the docs#11gokulasok-klarityintelligence wants to merge 1 commit into
gokulasok-klarityintelligence wants to merge 1 commit into
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Adds a nine-page "Drive AI transformation" group covering the layer the portal was missing: what to build, where to build it, and how to run the motion from a business objective through to a deployed agent. Sits between Concepts and How-to guides. The hub page introduces "Company Brain" once and bridges it to the Process Index and Artifacts layers, since the term did not appear anywhere on the site before now. The technical track documents the ADK as a methodology rather than something you install. It is served from the MCP at runtime via get_agent_builder_instructions, so there is nothing separate to set up and no plugin version to track. Also fixes a dead link on the landing page. The "Build agents and skills" card pointed at /guides/code-and-agents, which does not exist. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
gokulasok-klarityintelligence
force-pushed
the
add-transformation-playbook
branch
from
July 29, 2026 16:03
a680e61 to
182a26d
Compare
This was referenced Sep 10, 2026
rs07-within
added a commit
that referenced
this pull request
Sep 10, 2026
Bring the docs/transformation pages from PR #11 (add-transformation-playbook) forward onto current main, and sweep Klarity -> Within in prose so they match the rebranded site. Nav wiring and the new pages (readouts, opportunity loops) follow in later commits. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
rs07-within
added a commit
that referenced
this pull request
Sep 10, 2026
Bring the docs/transformation pages from PR #11 (add-transformation-playbook) forward onto current main, and sweep Klarity -> Within in prose so they match the rebranded site. Nav wiring and the new pages (readouts, opportunity loops) follow in later commits. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Sep 10, 2026
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
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.
Adds a nine-page Drive AI transformation group, sitting between Concepts and How-to guides. It covers the layer the portal was missing: what to build, where to build it, and how to run the motion from a business objective through to a deployed agent.
Pages
/transformationobjectivecompany-brainuse-case-selectionwhat-you-can-buildwhere-you-buildnon-technical-tracktechnical-trackmaintain-agentsHow the ADK is documented
The technical track documents the ADK as a methodology rather than something you install. It is served from the MCP at runtime through
get_agent_builder_instructions, so there is nothing separate to set up and no plugin version to track, and improvements reach builders the next time they build. A mermaid diagram on that page shows how the coding harness, the MCP, and the Company Brain fit together.The sequence is documented as eight steps: Objective, Companion, Analyze, Recommend and select, Design, Build, Test, Deploy.
Terminology
"Company Brain" appeared zero times on the site before this. It is introduced once on the hub page, tied to the Process Index and Artifacts layers, then used freely across the group.
Integration Flow,Managed AgentandADKwere also new to the portal and are each defined on first use.Also in this PR
The landing page card "Build agents and skills" pointed at
/guides/code-and-agents, which does not exist and 404s on the live site today. Repointed at/guides/agent-builder. Came in with #8.concepts/discover-structure-improveandguides/agent-buildereach gained a cross-link into the new group.Checks
All 41 internal links across the site resolve,
docs.jsonparses, and every nav entry has a file.Known gaps
Advisor has no page on the portal, so its mentions in the non-technical track and the Structure section are plain text.
🤖 Generated with Claude Code