Governance Dashboard

Live persistence + AI telemetry
QuestionWhat is the current architecture governance posture across the organization?

Real-time visibility into architecture reviews, compliance, and AI usage across your engineering organization.

Read-only demo
Public
PD

Effective Governance Decisions

Active Findings by Severity

Active Findings by Architecture Category

Review Volume Trend

✦ AI Usage & Cost Analytics

Token Usage by Component

Top Token Consumers (Users)

Cost by Repository

Prompt vs Completion Tokens

Daily Token & Cost Trend

Identity & access

Effective Governance Scope

Governance scope is resolved from the signed-in Entra identity.

Resolved governance persona

Authenticated Governance Persona

Enterprise identity is translated into governance authority, organizational scope, and product access.

Accessible product areas

Governance Surface Access

These areas and actions are resolved from the signed-in role and governed scope.

Visible Teams

Enterprise Users

Scoped Repositories

Repositories visible through governance authorization. A scoped repository may have no architecture-review activity yet.

Enterprise administration

Users, Teams, Repositories & Assignments

Administration requires Governance Admin permission.

Add / Update User

Add / Update Team

Add / Update Repository

Assign User to Team

Assign Repository to Team

Assign Governance Role

Organization posture

Governance Posture by Team

Compare governance coverage and current posture across accountable teams. This is an organizational view, not a repository risk ranking.

Recurring patterns

Recurring Finding Categories

Repeated findings reveal organization-wide architecture themes that may require standards, enablement, or platform action.

Coverage & activity

Portfolio Governance Activity

A compact view of how much of the engineering portfolio is represented in persisted governance evidence.

From posture to action

Explore the Next Governance Question

Portfolio explains the current organizational posture. Continue into the specialized view that matches the question you need to answer.

Portfolio exposure

Repository Architecture Risk

Risk scores are deterministic governance indicators, not predictions. Select a repository to see exactly what contributes to the score.
Low 0–24Medium 25–49High 50–74Critical 75–100

Historical posture

Repository Compliance Drift

Compare the earliest and latest persisted review evidence for each repository. Negative movement indicates governance drift; positive movement indicates recovery.

Debt pressure

Architecture Debt by Repository

Debt units combine unresolved finding severity, age, recurring categories, and governed exceptions. They prioritize remediation; they are not financial estimates.

Remediation backlog

Architecture Debt Backlog

Actionable debt grouped from current unresolved findings. Select an item to inspect the source governance finding.

Systemic patterns

Architecture Patterns Across Repositories

A pattern becomes systemic when the same active finding category appears in more than one repository. Select a pattern to inspect its evidence and blast radius.

Policy blast radius

Standards with Cross-Repository Exposure

Standards referenced across multiple repositories can reveal policy areas that need platform guidance, enablement, or coordinated remediation.

Repository relationships

Shared Architecture Signals

Repository pairs are connected when they share active architecture finding categories. Stronger overlap suggests a potentially systemic concern rather than isolated implementation debt.

Team comparison

Governance Posture by Team

Select a team to compare its repositories, findings and exceptions.

Architecture Review Explorer

Loading persisted reviews…

Human governance

Decision Queue

Loading persisted approval decisions…

Architecture Findings Explorer

Loading persisted findings…

Governance Exceptions

Loading persisted exceptions…

Proactive governance

Upcoming Exception Expirations

Time-bound exceptions already contain a known future governance obligation. ArkSentinel surfaces the next expiry and reminder window before the waiver becomes overdue.

Architecture debt signal

Exception Concentration

Repeated or concentrated deviations can reveal architecture debt that is becoming systemic.

By repository

By team

By finding category

Managed Enterprise Standards

Loading governed standards…
Governed standards are versioned enterprise policies. Published versions are immutable; editing a published standard creates a new Draft version.

Standards by Category

Loading category coverage…

Recent Policy Changes

Immutable governance audit trail

Architecture Standards Explorer

Loading persisted standards…
Associated findings are counted from reviews where the standard was selected. ArkSentinel does not yet persist a one-to-one finding-to-standard link, so this page avoids presenting that association as an exact violation count.

Decision registry

Enterprise ADR Registry

Loading architecture decisions…
ADR intelligence connects accepted ADRs to persisted repository review evidence, compliance trend, findings and architecture debt. Intelligence is deterministic and traceable; ArkSentinel does not infer implementation compliance from ADR prose alone.

Implementation evidence

ADR Adoption & Coverage

Accepted ADRs compared with persisted review evidence across their repository scope.

Architecture divergence

ADR Drift Watch

Scoped repositories with worsening compliance, current findings, or architecture debt.

Lifecycle posture

Decision Lifecycle

Current ADR distribution across governance states.

Decision assurance

Review & Renewal Risk

Accepted decisions that are overdue or approaching their next governance review.

Decision history

Recent ADR Changes

Immutable architecture decision and approval trail.

Repository Governance Portfolio

Loading persisted repositories…
Loading configurable AI rate card…

Spend concentration

Cost by Repository

Which codebases are consuming the most AI governance spend.

Workload economics

Cost by Component

AI spend across architecture-review and governance components.

Invocation source

Cost by Review Trigger

Understand which automated or human-triggered workflows generate AI spend.

Token economics

Prompt vs Completion Tokens

Input/output token mix behind the current filtered AI spend.

Traceable economics

AI Operations

Loading persisted AI usage…

Every row is persisted AI telemetry. Estimated cost uses the configured ArkSentinel rate card and remains traceable to repository, review trigger, component, model, tokens, and latency.

AttributionAttribution & Consumption AnalysisWho and what is driving AI governance consumption?

Organizational attribution

AI Cost by Team

Repository ownership maps AI consumption to accountable engineering teams.

Developer attribution

PR Author Attribution

Select a team to trace spend back to GitHub pull-request authors.

Model economics

Model Usage

Compare operations, tokens, cost, and latency across AI models.

Repository efficiency

Governance Unit Economics

AI cost normalized by reviews, findings, and approved exceptions.

Consumption outliers

High-Cost Operation Spotlight

Surface expensive, token-heavy, and slow AI operations for optimization.

Most expensive

Highest token usage

Highest latency

Financial governanceFinancial Governance & ValueIs AI governance spend controlled, predictable, and delivering useful coverage?

Budget governance

Team AI Budgets

Compare team-attributed AI spend with ArkSentinel planning budgets and escalation thresholds.

Planning budgets are deterministic guardrails for governance operations; they are not Azure billing limits.

Month-end outlook

AI Spend Forecast

Project month-end AI spend from the selected persisted telemetry window.

Spend trajectory

AI Cost Trend

Daily persisted AI spend and token consumption across the selected period.

Governance value

Cost vs Governance Posture

Compare repository AI spend with review coverage, compliance, findings, exceptions, and current architecture pressure.

FinOps guidance

Economics Efficiency Insights

Deterministic signals highlight where architects may investigate spend, coverage, or governance pressure. They do not make architecture decisions.

Step 1 · Establish context

Design & Remediation Context

Ask before coding, or open a GitHub violation here for standards-grounded remediation help.
Standards-grounded
No specific finding selected. Use this proactively before you code.
1

Choose governance scope

Identify the repository and optionally focus the guidance on a Standard or ADR.
2

Review resolved governance

ArkSentinel resolves the rules and decisions that apply to the selected repository.
Enter a repository to load applicable standards and ADRs.
Ready for standards-grounded guidance?Your selected context will carry into the AI workspace.

Active governance context

No governance context selected.

Standards-grounded conversation

Ask for design guidance, remediation steps, implementation patterns, or a pre-PR checklist.
Ask before you implement.ArkSentinel will ground the conversation in the active repository context and its applicable Standards and ADRs.

Recommendation inbox

Architecture Recommendations

Loading architecture recommendations…

Recommendations are generated from persisted ArkSentinel reviews, findings, repositories, standards, and ADR scope. Architects can create governed drafts, defer, dismiss, or reopen recommendations; every action is retained in the decision trail.

Architect decision trail

Recommendation Actions

Append-only history of draft creation, defer, dismiss, and reopen decisions.

Report builder

Evidence Scope

Select the organizational scope and evidence period, then generate a point-in-time governance report.

The report is generated from persisted reviews, findings, exceptions, approvals, ADRs, standards, audit events, and the current repository drift/debt posture. Audit-readiness checks flag missing rationale, approvers, expiry dates, review evidence, and decision history. Exported files contain no credentials or secrets.

Executive reporting

Portfolio Comparison & Change

Compare governed scopes, review compliance trend, and show what changed since the last saved evidence snapshot.
No executive summary yet.Generate an evidence report to calculate comparison and trend insights.

Comparative Governance Posture

Relative posture for repositories, teams, or architecture domains.

Compliance Trend

Average persisted review compliance over the selected period.

What Changed Since Last Snapshot

Compares this report with the latest saved snapshot for the same scope.

Report Snapshot History

Durable organizational history stored by ArkSentinel.

Generated evidence package

Compliance Evidence Report

Generate a report to create an evidence snapshot.
No evidence report generated yet.Choose a scope and date range above, then generate the report.

Health Checks

Loading runtime health…

Integration Readiness

Configuration readiness for the governance pipeline. These indicators do not replace external synthetic monitoring.

Support telemetry

Operational Diagnostics

Loading fast support diagnostics…

Failure evidence

Recent Runtime Failures

Process-local support evidence. Durable traces and dependencies remain in Application Insights.

Governance memory

Governance Audit Trail

Loading durable governance history…

Reconstruct why a governance decision happened by tracing the persisted review, exact policy versions, accountable approval, exception lifecycle, and delivery outcome.

Select an audit event to inspect its persisted evidence and open the related governance record.

Appearance

Choose how ArkSentinel looks. Your preference is applied instantly and remembered on this browser.

Enterprise Organization

Manage users, teams, repositories, memberships, ownership and scoped roles.

Open Enterprise Admin

Governance Policies

Manage versioned architecture standards and policy lifecycle.

Open Standards

Operations

Inspect runtime health, persistence and enterprise governance operations.

Open Operations

Safe configuration state

Protected Configuration Readiness

Operators can verify readiness for identity, AI, search, persistence, GitHub, and telemetry without exposing secret values.