Human Identity
Users, roles, claims, department membership, delegated administration.
Govern what agents know, what they can do, and how long information should exist.
Governance in PRAXIS is intended to influence runtime behavior, not simply produce reports after the fact. Identity, knowledge, model access, tools, actions, approvals, retention, and lifecycle can all become governed decisions.
Identity Governance
Who is acting?
Human identity, agent identity, roles, claims, department membership, and delegated authority can affect access and execution.
Agent Identity
Named agents with distinct authority, audit trail, and ownership.
Cross-Department Access
Authorized access to shared knowledge and tools across boundaries.
Shared Corporate Identity
Single identity provider across departmental environments.
Knowledge Governance
What information may be used?
RAG scope, document access, classification, retention, expiration, and organizational relationships can influence retrieval.
Hierarchical RAG Structure
Corporate
Department
Team
Project
Workspace
Individual
Child scopes inherit authorized knowledge from parents. Permissions enforced at every level.
Agent Governance
What may the agent use and do?
Model access, tools, MCP, workflows, approvals, and action authority can be governed as part of the agent's operating environment.
Operational Governance
What happened?
Important access decisions, tool calls, approvals, policy actions, and lifecycle events should be auditable.
Access Decisions
Every authorization evaluation logged with context.
Tool Invocations
Complete record of tool calls, parameters, and results.
Policy Actions
Retention, deletion, and lifecycle enforcement events.
Approval Records
Human decisions on high-impact actions captured.
Policy Hierarchy
Governance at multiple levels.
Policy may exist at multiple levels of the organization, from corporate governance to department, project/RAG, agent, and resource-specific rules. The exact conflict and inheritance model will be defined as the platform architecture matures.
Governance Policy Hierarchy
Corporate Policy Organization-wide governance, compliance, standards
Department Policy Department-specific rules, tool access, procedures
Project / RAG Policy Project scope, model restrictions, retention, lifecycle
Agent / Resource Policy Agent-specific authority, tool permissions, approval rules
Document / Resource Policy Classification, access control, retention, disposition
Conceptual product direction. Exact conflict and inheritance rules will be defined as platform architecture matures.
Sensitive Project Governance
Temporary project environments carry their own permissions, model restrictions, tool restrictions, retention period, and disposition policy.
- PROJECT NORTHSTAR ACQUISITION Restricted
- Classification
- Restricted
- Authorized Scope
- Finance + Executive
- External AI
- Prohibited
- External MCP
- Prohibited
- Retention
- 180 days
- Disposition
- Delete
- Extension
- Approval required
- Audit
- Full
Lifecycle Management
Active → Review → Extend or Expire → Delete/Archive by Policy
Knowledge environments can carry retention and lifecycle rules aligned with the work they support. When a project reaches its configured boundary, PRAXIS is intended to enforce the appropriate policy unless an authorized governance rule changes the outcome.