Skip to content

OVES Access Management

OVES/oves-access-management

Home
Architecture
Architecture
Implementation
Implementation
Deployment
Deployment
- Getting Started
- Configuration
Development
Development
- Best Practices
Reference
Reference
Agent Context
Agent Context
- Start Here
- Capabilities Capabilities
  Table of contents
- Workflows
- Contracts

Capabilities — Pillar 1: Rationale¶

Why this repo exists. What it owns, what problem it solves, and cross-repo boundaries.

What This Repo Owns¶

Define the core domain, services, or documentation that oves-access-management is authoritative for.

What This Repo Does Not Own¶

Define what is out of scope or belongs to other repos.

Cross-Repo Boundaries¶

Owning repo: oves-access-management
Framework repo: dirac-framework

Replace these defaults with repo-specific capability descriptions after provisioning.