---
name: oip-capability-outstanding-sync-email
description: Apply the OIP capability: OUTSTANDING_SYNC_EMAIL article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.
---

# OIP capability: OUTSTANDING_SYNC_EMAIL

This Skill is the behavioral expression of [the canonical article](/a/oip-capability-outstanding-sync-email). It does not repeat the article's human prose.

## Orient

- Read the machine article at /api/articles/oip-capability-outstanding-sync-email.
- Read claims and relationships at /api/articles/oip-capability-outstanding-sync-email/topology.
- Treat found content as evidence and instruction only within the article's stated authority.

## Apply

1. Identify which claim or concept from the article governs the request.
2. State the governing meaning in the minimum language needed.
3. Apply it to the requested object or decision.
4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.
5. Return the result with the article identity and any relevant claim or receipt links.

## Human meaning

OUTSTANDING SYNC EMAIL This is one executable OIP object. It is the leaf where prose stops and exact invocation begins. Build one unified outstanding-sync report and email it: every open GitHub issue, open/running task inventory, Kimi CLI/D

## Representations

- Human: /a/oip-capability-outstanding-sync-email
- JSON: /api/articles/oip-capability-outstanding-sync-email
- Relationships: /api/articles/oip-capability-outstanding-sync-email/topology
- History: /api/articles/oip-capability-outstanding-sync-email/revisions