---
name: entity-profile
description: "One-time org/business profile referenced on every document. Use when a person asks to install or apply \"Entity / Organization Profile\" (FTR-17) in a project, or when working in a project that has it installed."
---

# Entity / Organization Profile (FTR-17, version 1.0)

> Generated from library record FTR-17 version 1.0, publish 20261102a. Review status: unreviewed. The complete specification is in references/spec.md and is the authority; this file is the operating procedure drawn from it.

## What this does

One-time org/business profile referenced on every document

## When to use this skill

- A person asks to install, apply or update "Entity / Organization Profile" (FTR-17) in a project.
- A project's agent instructions list entity-profile as installed and the task touches what it covers.
- No other feature is required first.

## Install procedure

Steps run in order. Assess comes first, every question in the Ask step is answered by the person before anything is written, and every write merges additively into the existing project files (read the file first, update an existing section in place, never overwrite).

### Assess first
- Ask whether the project is for a business or organization at all; if not, skip this feature.
- Check for an existing profile: `admin\[Entity]_Profile.md` on the filesystem and a sanitized copy in Project Files. Read and carry forward whatever exists.
- If the user drops a document (letterhead, about page, registration record): read it, extract fields only — do not analyze content or store the document.

### Ask, only if needed
- "Is this project for a business or organization?" If no, skip.
- Qualify the type: "Is this a formal nonprofit or incorporated organization (501(c)(3), charitable corp, foundation)? Or a business entity (LLC, S-Corp, sole proprietorship, partnership)? This decides which profile template we use."
- Collect the minimum viable field set (below) — offer the document-drop shortcut. Do not ask for bank account numbers, passwords, or SSNs in chat. EIN is fine (public identifier).

### Write

The full Write payload is in references/write-payload.md. It is applied exactly as written, with the merge rule above.

### Confirm
Confirm: your entity profile is built and saved (full copy in admin\, sanitized copy in Project Files) — the agent will auto-fill your org info on every document and run the entity/logo pre-flight before branded output. Want to install another, or is that everything for now?

## Files in this skill

- references/spec.md: the complete specification, unabridged.
- references/write-payload.md: the Write step on its own.