← MUSITU AxiomCONTENT HISTORY

Update to MUSITU Axiom

Snapshot Oct 29, 2026 · 12:07 UTC · version 2.0.4

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save MUSITU Axiom and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Qualify legitimate MUSITU paid, team, enterprise, recurring-compute, or API needs after analytical value is established. Use only when the user asks about access, limits, pricing, upgrading, teams, enterprise, API, or protected capabilities require authentication.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 265
    },
    {
      "relative_path": "references/COMMERCIAL.md",
      "size_in_bytes": 751
    },
    {
      "relative_path": "references/PROOF.md",
      "size_in_bytes": 537
    },
    {
      "relative_path": "references/QUALITY.md",
      "size_in_bytes": 2262
    },
    {
      "relative_path": "references/ROUTING.md",
      "size_in_bytes": 504
    },
    {
      "relative_path": "scripts/proof_envelope.py",
      "size_in_bytes": 1023
    },
    {
      "relative_path": "scripts/scenario_grid.py",
      "size_in_bytes": 691
    }
  ],
  "name": "musitu-commercial-expansion",
  "skill_md_contents": "---\nname: musitu-commercial-expansion\ndescription: \"Qualify legitimate MUSITU paid, team, enterprise, recurring-compute, or API needs after analytical value is established. Use only when the user asks about access, limits, pricing, upgrading, teams, enterprise, API, or protected capabilities require authentication.\"\n---\n# MUSITU Commercial Expansion\nRead `references/COMMERCIAL.md` and `references/QUALITY.md`.\n\n## Workflow\n1. Identify the actual capability or outcome requested.\n2. Determine whether authentication, volume, recurring use, team governance or API access is genuinely required.\n3. Explain the access requirement without inventing a price or plan.\n4. Use only verified current MUSITU commercial/account paths.\n5. Never collect payment-card data or execute a financial transaction in ChatGPT.\n6. Qualify enterprise needs: seats, frequency, sensitivity, governance, integrations and support.\n7. Keep selling subordinate to successful user outcomes.\n"
}

SHA-256 of public snapshot: b0e9bd49d6d7ccec001f5971c8bfb05b053c15d185be1477adf3ccbe11f0060a