Ask for the outcome. Keep the work.
Public experience · Studio · Product requirements · Deployment
verb — to reduce by removing what is unnecessary.
PARÉ applies that rule to the product itself.
A person can arrive with an outcome:
Build the brand.
Turn this brief into three real directions.
Audit this page and fix the largest gap.
PARÉ handles project context, creation, critique, evidence, approvals, and delivery underneath the request.
The interface reveals machinery only when it helps the work.
+---------------------------------------------------------------+
| PARÉ Company / Project |
+------------------------+--------------------------------------+
| CONVERSATION | LIVE CANVAS |
| request / history | HTML / SVG / deck / visual output |
| files / context | responsive preview |
| progress / approvals | inspect / compare / refine |
+------------------------+--------------------------------------+
| Project · Strategy · Assets · Proof · Approvals · Export |
+---------------------------------------------------------------+
On a phone:
Chat · Canvas · Project
The Studio is one door into the project. Machines use semantic interfaces against the same files and receipts.
PARÉ can route work through supported local, hosted, or external execution engines without changing the product experience.
PARÉ is the product. The runtime is replaceable.
Runtime names appear only where someone is actually selecting, installing, diagnosing, or configuring that runtime.
Your projects.
Your files.
Your agents.
Your infrastructure.
Projects are folder-backed and portable. Strategy, assets, approvals, and evidence do not have to exist only inside a proprietary database.
Hosted infrastructure may make PARÉ easier to operate. It does not become the only copy of the work.
project/
├── AGENTS.md
├── CONTEXT.md
├── 00_intake/
├── 10_strategy/
├── 20_design/
├── 30_validate/
├── 40_deliver/
├── 50_publish/
├── _shared/
└── _ledger/
Rules:
- one fact has one canonical home;
- one folder has one job;
- strategy explains why;
- design files explain how the selected visual system behaves;
- approvals and evaluations leave receipts;
- generated indexes are not project truth.
intake
↓
strategy
↓
governing idea
↓
creative directions
↓
human selection
↓
design
↓
application stress test
↓
independent critique
↓
validation
↓
proof
↓
delivery / publish
PARÉ can create, inspect, critique, repair, validate, and prepare. It does not silently promote its own work to official status.
| State | Meaning |
|---|---|
| Draft | Generated, not approved |
| Candidate | Creator checks passed |
| Verified | Evidence checks passed |
| Approved | Required human/gate accepted it |
| Canonical | Approved project truth |
| Official | Canonical, validated package |
| Preview | Non-production external view |
| Published | Externally released |
| Production | Live authoritative system |
PARÉ Studio
│
├── CLI
├── MCP
├── authenticated runtime API
└── authorized filesystem access
│
▼
SAME PROJECT
SAME FILES
SAME RECEIPTS
Legacy package namespaces, storage keys, protocol contracts, and CLI compatibility identifiers remain internally where changing them would break existing behavior. They are implementation details, not product branding.
The browser and privileged runtime are separate responsibilities.
browser / desktop
│
▼
PARÉ Studio
│
authenticated HTTPS
│
▼
persistent runtime
│
┌─────┼──────────────┐
│ │ │
files agent CLIs runtime state
│ │ │
└──── same project ──┘
Netlify, Vercel, or another host can serve the browser surface. Long-running sessions, process spawning, privileged filesystem access, exports, and server credentials belong on a persistent owner-controlled machine or managed runtime.
The landing page performs the product idea.
A field of letters contains PARÉ. Scrolling removes what does not belong until the word resolves. Definition, Saint-Exupéry, interface noise, and the Studio continue the same subtraction language.
Motion communicates change. If it only decorates the page, remove it.
Start with:
The monorepo retains compatibility paths required by the underlying runtime.
Do not expose the privileged runtime publicly without authentication.
PARÉ is derived from an Apache-2.0 upstream project. Attribution, notices, and technical compatibility names remain where required; they are not presented as PARÉ product branding.
See LICENSE and the repository history for upstream attribution and notices.