<!-- source: openspec/_root/public-mirror-README-template.md -->

# Rapoport Studio — OpenSpec public mirror

This is an auto-synced public mirror of Rapoport Studio's internal `openspec/` directory. We use OpenSpec to plan and ship our own platform — the same way we'd use it on a client engagement. The mirror updates within 60 seconds of a merge to our private monorepo.

---

## Navigate

**Want to see how we plan a new feature?**
→ Browse [`openspec/changes/`](./openspec/changes/) — every active and in-flight change has a `proposal.md` / `design.md` / `tasks.md` triplet.

**Want to see how we describe current capabilities?**
→ Browse [`openspec/current/`](./openspec/current/) — one file per live capability, each naming the spec contract it satisfies.

**Want to read how we work?**
→ Read [`openspec/AGENTS.md`](./openspec/AGENTS.md) — the operating rules every collaborator (human or AI) follows in this repo.

**Want to browse completed work?**
→ Browse [`openspec/archive/`](./openspec/archive/) — retired changes with full triplets, including the research and design decisions that shaped them.

---

## What is OpenSpec?

OpenSpec is the studio's planning methodology. Every change — whether it's a new feature, a methodology amendment, or a dependency upgrade — ships as three short markdown files:

- **`proposal.md`** — Why this change? What changes? Decisions captured.
- **`design.md`** — Surface contracts, implementation approach, edge cases, acceptance checks.
- **`tasks.md`** — Atomic checklist, owner-tagged, checkboxes live during implementation.

The triplet is the atomic unit of studio delivery. It lives in the client's own git repository from day one — not in studio infrastructure.

---

*Synced from the private monorepo at `rapoport-studio/rapoport.studio`. Source of truth for methodology: [`openspec/_methodology/`](./openspec/_methodology/).*
