How to use rkito
in your role.
Persona-specific playbooks for operating rkito day to day — what to check, when to act, and what each signal means for your specific responsibilities.
How rkito hooks into your PR workflow, what BLOCKED means, and how to govern AI coding agents.
Architecture health reporting, AI governance risk, and when to escalate.
Security architectural conformance, audit preparation, and agent risk.
Sprint conformance, team-level drift, and process health monitoring.
Lens authoring, conformance review, blocked PR triage, and governance depth.
Delivery predictability, sprint blocker root causes, and design approval timing.
Architectural risk monitoring, incident root cause tracing, and agent drift signals.
Connect your tools
Step-by-step integration setup — what to configure in each external system and what env vars rkito needs.
Connect rkito to GitHub for repo ingestion, Design Audit on PRs, and architecture manifest write-back.
Import Jira issues as Change Intentions and keep status in sync bidirectionally.
Sync architecture diagrams and extract Ledger entities — Systems, Components, Interfaces — via AI analysis.
rkito is connected to at least one repository and the CDA pipeline has run on at least one PR. If not yet set up, start with the getting started guide.
Every metric referenced in these guides has a full explainer in the metrics catalog — formula, thresholds, and coercion warnings included.
These guides are operational — what to do, not why to care. The blog covers why each role needs this in the first place.