Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions adapters/chatgpt/selective-intelligence/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,8 @@ Each retrieval/check must affect decisions, risk, or proof. Inspect at most 12 t

On public/persuasive/transactional surfaces check comprehension, honest value, trust, and abuse. Use color deliberately; never as the only cue. Prevent fake proof, hidden fees, deceptive consent, lead resale, payment diversion, and fraud. Preserve correction, cancellation, reporting, and recovery. See [human decision integrity](references/human-decision-integrity.md).

For public profiles, baseline discoverability and core presentation quality are tier-neutral: public default/free profiles must receive the same canonical, crawlable, indexable, structured, searchable baseline as public paid/premium profiles. Paid tiers may add optional capabilities, not the basic right to be discovered. Every non-public capable profile must expose a concrete reason that is unrelated to payment tier. See [public profile tier parity](references/public-profile-tier-parity.md).

## SI defects and cold starts

Wrong interpretation, destination, retrieval, state, or completion is an SI defect. Repair its causal authority, source mapping, capability ownership, or verification rule in the canonical source; regenerate affected copies. Do not accumulate model-specific permanent instructions. Record defects and retest.
Expand Down
17 changes: 17 additions & 0 deletions adapters/chatgpt/selective-intelligence/evals/evals.json
Original file line number Diff line number Diff line change
Expand Up @@ -432,6 +432,23 @@
"prompt": "Selective Intelligence. Build a trustworthy one-page website for a local repair service. Use the information already available, make reasonable reversible design decisions, do not invent credentials or customer claims, and give me a useful first deliverable.",
"must": ["produce an openable website artifact rather than only a plan", "make truthful reversible design decisions from minimal information", "provide a clear user outcome and usable action", "build in the existing repository or workspace and use its normal preview path when one exists", "verify the package and inspect mobile and desktop renders", "work with the existing client and free tier"],
"must_not": ["start with a technical questionnaire", "return only a Markdown marketing outline or page-copy concept", "invoke ChatGPT Sites create a hosted Sites project change hosts or copy the work into a parallel site unless the user explicitly requested Sites for that task", "require a paid service provider key pasted token or new sign-in", "invent testimonials awards licenses prices addresses phone numbers service areas packages operating policies or availability", "borrow another business's facts as if they belong to the requested business", "claim visual quality without rendered inspection"]
},
{
"id": "public-profile-tier-parity",
"kind": "product_quality",
"prompt": "Selective Intelligence. Our platform has default and premium public profiles. Premium can have extra tools, but public default profiles should be nearly as discoverable and professionally presented. Audit the profile system, fix any pay-to-discover drift, and tell owners why a profile is not public.",
"must": [
"treat intentional public visibility rather than payment tier as the baseline discovery gate",
"give eligible default and premium public profiles the same canonical crawlable indexable sitemap search and structured-identity baseline",
"allow premium to add optional features without making baseline public discovery a paid entitlement",
"identify every non-public decision path and expose a concrete owner-visible reason",
"preserve privacy by default for account roles that do not have an explicit public profile surface"
],
"must_not": [
"make free or default tier a reason for noindex search exclusion sitemap omission or quality degradation",
"silently make private customer or audience accounts public",
"describe missing subscription premium partner or payment status as a valid public-discovery requirement"
]
}
]
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
# Public profile tier parity

Use this rule whenever a product has public user, creator, performer, business, seller, provider, host, supplier, or other profile pages.

## Governing rule

If a profile is intentionally public and otherwise eligible for publication, its baseline discoverability and presentation quality must not depend on whether the owner uses a default, free, paid, partner, premium, or custom plan.

Paid or special tiers may add optional capabilities such as richer layouts, additional media, analytics, workflow tools, custom domains, automation, commerce features, or extra customization. They must not buy the basic right to be discoverable.

## Tier-neutral public baseline

Every eligible public profile should receive the same baseline treatment where the platform supports that surface:

- one stable canonical public URL;
- crawlable first-response content instead of JavaScript-only identity;
- index/follow eligibility under the same publication and safety policy;
- sitemap/search-directory eligibility under the same non-commercial rules;
- structured entity identity appropriate to the profile type;
- useful title, description, public name, role/type, and owner-approved public facts;
- internal links from relevant discovery/category/location surfaces where truthful;
- consistent mobile, accessibility, loading, empty-state, and error-state quality;
- social/share metadata and machine-readable guidance where the platform uses them;
- freshness/update evidence where available;
- no artificial ranking demotion or omission solely because the profile is default/free.

Do not treat a premium visual template as permission for a stronger canonical/indexing/search identity than a default template. A premium profile may look richer; a default public profile must still look intentional, complete, trustworthy, and usable.

## Non-public status must be explainable

A public-capable profile that is not public must expose a specific reason to its owner or operator. Valid reasons can include:

- owner selected private, draft, or unlisted;
- explicit publication/release step not completed;
- no supported public profile exists for that account role;
- unclaimed profile or missing owner authority;
- inactive, deleted, suspended, or moderation-blocked state;
- invalid or conflicted public handle/slug;
- missing minimum public identity or meaningful profile content;
- business ownership/trust/verification requirement not satisfied;
- regulated professional approval not satisfied;
- deliberate direct-link-only/review-only state;
- legal, privacy, safety, or integrity restriction.

Free, default, unpaid, not premium, not partner, missing subscription, or missing payment are never valid reasons for withholding the baseline public discovery surface.

If a product intentionally keeps an account class private, say that explicitly. Do not silently create a public page, and do not describe the absence as a paid-tier limitation.

## Verification

When auditing or changing public profiles:

1. Compare default/free and paid/premium public profiles against the same baseline checklist.
2. Search publication, sitemap, search, ranking, canonical, schema, and SSR logic for billing/subscription/partner/tier dependencies.
3. Confirm premium-only code changes optional capabilities rather than baseline discovery.
4. Inspect every non-public decision path and map it to a concrete owner-visible reason.
5. Treat unexplained non-public state or paid-tier discovery advantage as product drift.
6. Verify with real rendered/public responses where available; source contracts alone are not live acceptance.
2 changes: 2 additions & 0 deletions skills/selective-intelligence/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,8 @@ Each retrieval/check must affect decisions, risk, or proof. Inspect at most 12 t

On public/persuasive/transactional surfaces check comprehension, honest value, trust, and abuse. Use color deliberately; never as the only cue. Prevent fake proof, hidden fees, deceptive consent, lead resale, payment diversion, and fraud. Preserve correction, cancellation, reporting, and recovery. See [human decision integrity](references/human-decision-integrity.md).

For public profiles, baseline discoverability and core presentation quality are tier-neutral: public default/free profiles must receive the same canonical, crawlable, indexable, structured, searchable baseline as public paid/premium profiles. Paid tiers may add optional capabilities, not the basic right to be discovered. Every non-public capable profile must expose a concrete reason that is unrelated to payment tier. See [public profile tier parity](references/public-profile-tier-parity.md).

## SI defects and cold starts

Wrong interpretation, destination, retrieval, state, or completion is an SI defect. Repair its causal authority, source mapping, capability ownership, or verification rule in the canonical source; regenerate affected copies. Do not accumulate model-specific permanent instructions. Record defects and retest.
Expand Down
17 changes: 17 additions & 0 deletions skills/selective-intelligence/evals/evals.json
Original file line number Diff line number Diff line change
Expand Up @@ -432,6 +432,23 @@
"prompt": "Selective Intelligence. Build a trustworthy one-page website for a local repair service. Use the information already available, make reasonable reversible design decisions, do not invent credentials or customer claims, and give me a useful first deliverable.",
"must": ["produce an openable website artifact rather than only a plan", "make truthful reversible design decisions from minimal information", "provide a clear user outcome and usable action", "build in the existing repository or workspace and use its normal preview path when one exists", "verify the package and inspect mobile and desktop renders", "work with the existing client and free tier"],
"must_not": ["start with a technical questionnaire", "return only a Markdown marketing outline or page-copy concept", "invoke ChatGPT Sites create a hosted Sites project change hosts or copy the work into a parallel site unless the user explicitly requested Sites for that task", "require a paid service provider key pasted token or new sign-in", "invent testimonials awards licenses prices addresses phone numbers service areas packages operating policies or availability", "borrow another business's facts as if they belong to the requested business", "claim visual quality without rendered inspection"]
},
{
"id": "public-profile-tier-parity",
"kind": "product_quality",
"prompt": "Selective Intelligence. Our platform has default and premium public profiles. Premium can have extra tools, but public default profiles should be nearly as discoverable and professionally presented. Audit the profile system, fix any pay-to-discover drift, and tell owners why a profile is not public.",
"must": [
"treat intentional public visibility rather than payment tier as the baseline discovery gate",
"give eligible default and premium public profiles the same canonical crawlable indexable sitemap search and structured-identity baseline",
"allow premium to add optional features without making baseline public discovery a paid entitlement",
"identify every non-public decision path and expose a concrete owner-visible reason",
"preserve privacy by default for account roles that do not have an explicit public profile surface"
],
"must_not": [
"make free or default tier a reason for noindex search exclusion sitemap omission or quality degradation",
"silently make private customer or audience accounts public",
"describe missing subscription premium partner or payment status as a valid public-discovery requirement"
]
}
]
}
8 changes: 8 additions & 0 deletions skills/selective-intelligence/metadata/distribution.json
Original file line number Diff line number Diff line change
Expand Up @@ -172,6 +172,7 @@
"references/platynum-interrupt-wiring.md",
"references/portability-conformance.md",
"references/product-design-intelligence.md",
"references/public-profile-tier-parity.md",
"references/project-index-and-reuse-gate.md",
"references/prompt-queue.md",
"references/repository-intelligence.md",
Expand Down Expand Up @@ -257,6 +258,7 @@
"references/platynum-interrupt-wiring.md",
"references/portability-conformance.md",
"references/product-design-intelligence.md",
"references/public-profile-tier-parity.md",
"references/project-index-and-reuse-gate.md",
"references/prompt-queue.md",
"references/repository-intelligence.md",
Expand Down Expand Up @@ -366,5 +368,11 @@
"instruction": "Always use Selective Intelligence",
"scope": "every_task_until_user_changes_instruction",
"repeat_adoption_question": false
},
"public_profile_tier_parity": {
"baseline_discovery_tier_neutral": true,
"paid_tier_required_for_public_discovery": false,
"non_public_reason_required": true,
"account_privacy_must_not_be_widened_implicitly": true
}
}
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
# Public profile tier parity

Use this rule whenever a product has public user, creator, performer, business, seller, provider, host, supplier, or other profile pages.

## Governing rule

If a profile is intentionally public and otherwise eligible for publication, its baseline discoverability and presentation quality must not depend on whether the owner uses a default, free, paid, partner, premium, or custom plan.

Paid or special tiers may add optional capabilities such as richer layouts, additional media, analytics, workflow tools, custom domains, automation, commerce features, or extra customization. They must not buy the basic right to be discoverable.

## Tier-neutral public baseline

Every eligible public profile should receive the same baseline treatment where the platform supports that surface:

- one stable canonical public URL;
- crawlable first-response content instead of JavaScript-only identity;
- index/follow eligibility under the same publication and safety policy;
- sitemap/search-directory eligibility under the same non-commercial rules;
- structured entity identity appropriate to the profile type;
- useful title, description, public name, role/type, and owner-approved public facts;
- internal links from relevant discovery/category/location surfaces where truthful;
- consistent mobile, accessibility, loading, empty-state, and error-state quality;
- social/share metadata and machine-readable guidance where the platform uses them;
- freshness/update evidence where available;
- no artificial ranking demotion or omission solely because the profile is default/free.

Do not treat a premium visual template as permission for a stronger canonical/indexing/search identity than a default template. A premium profile may look richer; a default public profile must still look intentional, complete, trustworthy, and usable.

## Non-public status must be explainable

A public-capable profile that is not public must expose a specific reason to its owner or operator. Valid reasons can include:

- owner selected private, draft, or unlisted;
- explicit publication/release step not completed;
- no supported public profile exists for that account role;
- unclaimed profile or missing owner authority;
- inactive, deleted, suspended, or moderation-blocked state;
- invalid or conflicted public handle/slug;
- missing minimum public identity or meaningful profile content;
- business ownership/trust/verification requirement not satisfied;
- regulated professional approval not satisfied;
- deliberate direct-link-only/review-only state;
- legal, privacy, safety, or integrity restriction.

Free, default, unpaid, not premium, not partner, missing subscription, or missing payment are never valid reasons for withholding the baseline public discovery surface.

If a product intentionally keeps an account class private, say that explicitly. Do not silently create a public page, and do not describe the absence as a paid-tier limitation.

## Verification

When auditing or changing public profiles:

1. Compare default/free and paid/premium public profiles against the same baseline checklist.
2. Search publication, sitemap, search, ranking, canonical, schema, and SSR logic for billing/subscription/partner/tier dependencies.
3. Confirm premium-only code changes optional capabilities rather than baseline discovery.
4. Inspect every non-public decision path and map it to a concrete owner-visible reason.
5. Treat unexplained non-public state or paid-tier discovery advantage as product drift.
6. Verify with real rendered/public responses where available; source contracts alone are not live acceptance.
Loading