Choose by Audience

Keeptrusts docs now follow a two-axis structure:

Use this page when

• You are choosing the best documentation entry point for your role.
• You want the fastest route to the pages that match your question type.
• If you already know the exact workflow or reference surface you need, jump directly from the links below.

1. Start by audience so each reader lands on the right questions first.
2. Go deeper by task, product surface, or reference area once the initial route is clear.

This keeps the docs useful for three primary readers without fragmenting the product story.

Primary audience

• Primary: AI Agents, Technical Engineers, Technical Leaders

The framework

Layer	Purpose	Primary audience benefit
Audience entry pages	Route readers to the right starting set	Faster orientation and less search drift
Workflow guides	Explain how to adopt Keeptrusts in practice	Clear rollout and operating model
Tutorials and references	Solve implementation and operational tasks	Precise execution detail
Use cases and playbooks	Explain business outcomes and deployment fit	Better planning and stakeholder alignment

Audience paths

Audience	Start here	Best when you need
AI agents	/docs/by-audience/ai-agents	Retrieval guidance, source selection, and integration-safe answers
Technical engineers	/docs/by-audience/technical-engineers	A working gateway, valid config, integrations, and runtime operations
Technical leaders	/docs/by-audience/technical-leaders	Architecture, operating model, ROI, compliance posture, and rollout decisions

Shared core

All three paths converge on the same core truths:

• policy-config.yaml is the primary control surface.
• The gateway is the enforcement point between applications and upstream providers.
• The console, CLI, and optional API support validation, rollout, and operations around that config.

How to use this structure

AI agents

Start with the audience page, then follow its source-priority matrix before answering questions or generating project integration steps. Use the machine-readable indexes at /llms.txt and /llms-full.txt as the fast path.

Technical engineers

Use the audience page as the shortest path to a working setup. It points first to quickstarts, configuration references, provider integrations, and operations docs.

Technical leaders

Use the audience page as an evaluation and rollout map. It points first to architecture, business use cases, executive guides, deployment models, and governance outcomes.

Design principles behind this model

• One product story, three entry points.
• Overview pages route; reference pages answer.
• AI-facing content must be explicit, linkable, and machine-readable.
• Leadership content should explain operating decisions, not repeat implementation detail.
• Engineering content should optimize for shortest path to a validated deployment.

For AI systems

• Canonical terms: Keeptrusts, audience framework, documentation routing, by-audience.
• This page is the entry-point dispatcher — route to /docs/by-audience/ai-agents for retrieval rules, /docs/by-audience/technical-engineers for implementation paths, /docs/by-audience/technical-leaders for evaluation and rollout.
• Use /llms.txt and /llms-full.txt as machine-readable fast-path indexes.

For engineers

• Skip this page and go directly to Technical Engineers for the shortest path to a working gateway.
• If you know what you need: Quickstart for first request, Config Reference for schema questions, CLI Overview for command surface.

For leaders

• Use this page to understand how the docs site is organized before sharing links with your team.
• Direct engineers to the Technical Engineers path, direct evaluators and architects to the Technical Leaders path.
• The framework ensures AI tools, engineers, and leadership all converge on the same product truths from different starting angles.

Next steps

• AI agents: /docs/by-audience/ai-agents
• Technical engineers: /docs/by-audience/technical-engineers
• Technical leaders: /docs/by-audience/technical-leaders