> ## Documentation Index
> Fetch the complete documentation index at: https://docs.grantex.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# OACP Policy And Governance

> Policy, freshness, source, revocation, and adapter governance for Grantex OACP authority.

# OACP Policy And Governance

Canonical end-to-end flow: [OACP authority overview](./overview).

Grantex governs the policy envelope around OACP artifacts: source lineage, TTL, freshness, revocation snapshot age, risk tier, blocked capabilities, and adapter lineage.

## Governance Controls

| Control | Grantex requirement |
| - | - |
| Source lineage | Every artifact needs source refs and observed timestamps. |
| Freshness | TTL is capped by artifact family and risk tier. |
| Revocation | Cache consumers need current enough revocation posture for the action class. |
| Risk tier | Low-risk discovery can use valid cache; commitment-bound actions require stronger evidence. |
| Adapter lineage | Adapter payloads must cite canonical OACP artifact families. |
| Non-enablement | Artifacts must not imply checkout, payment, order, mandate, refund, return, shipment, or stock-hold execution. |

## Policy Diagram

```mermaid theme={null}
flowchart TD
  input[Authority request] --> source{Source refs present?}
  source -->|No| refuse1[Refuse: missing source]
  source -->|Yes| ttl{Fresh within TTL?}
  ttl -->|No| refuse2[Refuse: stale]
  ttl -->|Yes| scope{Scope allowed?}
  scope -->|No| refuse3[Refuse: private or executable scope]
  scope -->|Yes| issue[Issue internal OACP artifacts]
```

## Publication And Approval

External public claims require documented evidence, product approval, security review, partner review, and release notes. Until then, docs must use "compatibility mapping" and "internal OACP artifact authority."

## Ownership

Grantex is owned by Orchestrum Technologies LLP. Inventor and owner: Sanjeev Kumar. Ownership contact: [sanjeev@orchestrum.in](mailto:sanjeev@orchestrum.in) or [mishra.sanjeev@gmail.com](mailto:mishra.sanjeev@gmail.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.