Muse Front Door — docs
Contents

Client consent model — public display of agents and work

The instance publishes public surfaces: the /.well-known/manifest.json (instance identity, services, agents), the landing page, the docs site. These may name agents and describe their work. Nothing belonging to a client appears on any public surface without that client's explicit consent. This document defines what that means and how to run it.

The rule #

No agent identity, work summary, client name, or client-identifying detail is published unless:

  1. The client gave explicit consent (not implied, not "they didn't

object"), 2. for a defined scope (what exactly is displayed, where), 3. recorded in a form you can produce later, 4. and the consent is currently in force (not expired, not revoked).

If any of the four fails, the material stays private. When in doubt, it stays private.

What counts as public display #

roles, service listings. - The landing page and docs site: testimonials, case studies, "our agents" sections. - Any marketing, social posts, or demos derived from client work.

Not public: the ops console, board/chat/verify internals, health dashboards, and anything behind authentication — those are operational surfaces covered by the managed-services agreement itself, not by this consent.

A valid consent record states:

it covers. - What: exactly what may be displayed — e.g. "agent identity operator-acme and a one-line service description", or "anonymized case study of the migration work". Vague "display our work" is not enough; write the actual text or a tight description of it. - Where: which surfaces (manifest, landing page, docs). - Duration: a term (e.g. 12 months) or "until revoked". A term with renewal is better than indefinite. - Revocation: how the client revokes (an email to the operator suffices), and your removal commitment (see below).

Email counts as written consent. A checkbox in an onboarding form counts if it names the scope. A verbal "sure, put us on your site" does not — write it down and get a reply confirming.

Recording #

Keep consent records outside the repo — they contain client names and contact details, which don't belong in version control or on the docs site. A private folder (or your normal contract storage) with one file per client is enough:


consent/

  acme-corp.md      # scope, term, the confirming email archived

  ...

Each record notes the date given, the scope, the term, and where the confirming message is archived. Review the folder when a term comes up for renewal.

Revocation #

When a client revokes (or a term lapses without renewal):

  1. Remove their material from the manifest, landing page, and docs at

the next publish — within 7 days at most, immediately if the client asks. 2. bin/publish.sh and re-render the manifest (bin/gen-manifest.sh only lists what the config + registry say; remove the agent's public listing first). 3. Confirm removal to the client in writing. 4. Keep the revocation record (who, when) — don't delete the paper trail.

Cached copies (search engines, the dist tarball of an older release) can't be un-published; say so in the consent text so expectations are honest.

Per-client separation #

Consent is per client, never blanket. Client A's consent covers Client A's agents and work only. A testimonial that names two clients needs both consents. An agent that serves multiple clients needs each client's consent for the portion displayed.

This mirrors the credential rule (one client, one credential set): the unit of trust is the client relationship, everywhere.

Adapt freely; keep the four elements (who/what/where/duration):

I, [CLIENT NAME], authorize [OPERATOR / BRAND] to publicly display
the following: [exact scope — e.g. "the agent identity
operator-acme and the service description nightly docs builds"].
This may appear on [surfaces — e.g. the instance manifest at
/.well-known/manifest.json and the landing page]. This consent runs
for [term] from [date] and I may revoke it at any time by emailing
[address]; revocation removes the material within 7 days. I understand
cached copies outside the operator's control can't be retracted.

The operator's own display #

Your own agents and your own reference work need no client consent — but mark them as the operator's. The reference instance (muse-dev.online) does exactly this: it displays the operator's agents and stays visibly a dev/reference deployment. Don't present your own test setup as client work; that's the fastest way to spend the trust this whole model runs on.