# Treverse AI Rules

Use these rules before any vertical skill pack. These packs are harness-neutral:
they can be used in any AI chat, IDE assistant, agent runner, or document AI
surface that accepts URLs, pasted text, or uploaded Markdown files.

## Core Rules

- Do not paste secrets, passwords, API keys, private keys, credentials, bank data, full payment details, or unnecessary customer personal data into AI or LLM tools.
- Do not send AI-written messages to customers, vendors, candidates, or partners without human review.
- Do not let AI make final decisions about refunds, billing, pricing, inventory, disposition, compliance, hiring, or customer account action.
- Treat AI output as a draft or analysis aid until checked against the source system.
- Keep source links when work depends on Notion, Zendesk, Databricks, Linear, GitHub, Outlook, Slack, A-Stock/GEMS, TIPS, FORGE/Presort, X-Deal, or RecSys.
- If work could change customer experience, billing, inventory state, pricing, model behavior, or support policy, name the human owner before acting.

## Standard Prompt Shape

```text
You are helping with a Treverse workflow.

Context:
- Team / vertical:
- Source system:
- What happened:
- What I need:
- Constraints:
- Audience:

Task:
Return a structured first pass with:
1. Summary
2. Recommended next action
3. Risks or assumptions
4. Questions that need a human answer
5. Draft output, if useful

Do not invent facts. If the source material does not support something, label it as an assumption or question.
```

## Universal Skill: Summarize Into Action

```text
Summarize this into action items for Treverse.

Return:
- one-paragraph summary
- decisions made
- open questions
- action items with owner, due date if stated, and source quote or clue
- risks if nothing happens

Text:
<paste source>
```

## Universal Skill: Draft A Response

```text
Draft a reply in Chris/Treverse's direct, practical tone.

Audience:
<customer/vendor/candidate/teammate/stakeholder>

Goal:
<what the reply needs to accomplish>

Constraints:
- Do not promise anything not confirmed.
- Keep it concise.
- Flag anything I should verify before sending.

Source context:
<paste relevant context>
```

## Universal Skill: Find Missing Pieces

```text
Review this plan for missing pieces.

Look specifically for missing:
- owner
- timeline
- requirements
- acceptance criteria
- test plan
- rollout plan
- customer, billing, inventory, support, or compliance risk
- source of truth

Plan:
<paste plan>
```