---
name: oip-designer-legibility-policy
description: Apply the Designer Legibility Policy — A8 Feature vs Operator Exposure article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.
---

# Designer Legibility Policy — A8 Feature vs Operator Exposure

This Skill is the behavioral expression of [the canonical article](/a/oip-designer-legibility-policy). It does not repeat the article's human prose.

## Orient

- Read the machine article at /api/articles/oip-designer-legibility-policy.
- Read claims and relationships at /api/articles/oip-designer-legibility-policy/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

Designer Legibility Policy — A8 Feature vs Operator Exposure §SELF — oip-designer-legibility-policy What this page is: the boundary A8 made necessary — what about the designer is deliberately legible vs incidentally leaked . What it explain

## Representations

- Human: /a/oip-designer-legibility-policy
- JSON: /api/articles/oip-designer-legibility-policy
- Relationships: /api/articles/oip-designer-legibility-policy/topology
- History: /api/articles/oip-designer-legibility-policy/revisions
