The Content Catalogue

Install ready-made knowledge articles and skills into your own library, keep them up to date, and add them to your organisation’s server. Content comes from SphereHarness for everyone, from your reseller for its customers only, and from other users through the marketplace.

What is in it

A catalogue entry is a package of one kind:

• Knowledge — articles (.md, .txt, .yaml) that the AI searches when it answers you, like the files in your own knowledge folder.
• Skills — saved procedures the AI follows (see Skills). A skill is text: it tells the AI what to do, it is not a program.

Macros and automations are not in the catalogue. Nothing in a package runs when you install it.

Who publishes it, and who sees it

The server decides who may see a package from who published it; a publisher cannot widen it. If you move to another reseller, its packages stop appearing in your list (what you already installed stays — see below). A reseller sees how many times its packages were installed, never by whom.

Versions

Every package has numbered versions (1.0.0, 1.1.0, 2.0.0…), each with a short list of what changed. A published version never changes: a correction is always a new version, so the version you installed is exactly the version everybody else installed under that number. A version can be:

• Published — installable.
• Deprecated — still installable, shown with a notice from the publisher (usually “use the newer version”).
• Withdrawn — no longer installable.

Installing on your PC

1. In the desktop agent open Settings › Catalogue (or press Catalogue… on Settings › Libraries). Under Install from the catalogue, signed in, it lists the packages you may see, with the publisher, version, size, licence and badge. Filter by kind or CAD, or search.
2. Press Install. The agent downloads the package from the SphereHarness server, checks its signature (below), checks every file against the list the signature covers, and only then copies the files into your library.
3. Skills go to <your knowledge folder>\skills\ (a skill whose name you already use is added under a new name, never over yours); knowledge goes to <your knowledge folder>\catalogue\<package>\, one folder per package. The skill list marks catalogue items with their publisher.

Installed content is yours: signing out does not remove it. A file catalogue.json in the same folder records which package and version each item came from.

The signature: what it proves

When a version is published, the SphereHarness server signs it with the same key that signs your licence. The signature names the package, its version, the publisher and the fingerprint (SHA-256) of the package’s file list, which in turn fingerprints every file. The agent carries the matching public key and refuses to install a package that is unsigned, signed for another package or version, changed after signing, or signed by anything else; the refusal names the reason.

The signature proves the package came from the SphereHarness catalogue unchanged. It does not prove the content is correct or right for your work. Read a skill before you rely on it, and remember that every operation still asks for your approval exactly as before.

Updates, pinning and rolling back

• At sign-in and once a day the agent asks the server whether your installed packages have something new. The answer arrives as one notice in the notification bell (“N catalogue updates”), never a pop-up. Press Update to install the newer version; the package’s knowledge folder is replaced as a whole, so a renamed article leaves nothing behind.
• Pin keeps the version you have and stops update notices for that package; Unpin undoes it. Check for updates asks at once.
• Roll back… installs any earlier version that is still published.
• Remove deletes the package’s files from your library.

Withdrawn, blocked or no longer available

If a publisher withdraws a package, or SphereHarness blocks a marketplace package, the next update check tells you with the reason, and the item is marked in your list (a skill shows as disabled, with the reason). Nothing is deleted or switched off remotely: you decide, and Remove is one click. A package you can no longer see — because you left that reseller, for example — is reported as no longer available, and your copy stays.

Adding a package to your organisation’s server

If your organisation runs its own SphereHarness organisation server (tenant mode), an organisation administrator can press Add to organisation library on an installed package. The administrator’s agent sends the signed package to the organisation server, which checks it again; every member’s PC then receives it on its next sync, as a read-only organisation library. Members’ PCs do not contact the SphereHarness catalogue for this — only the administrator’s agent does.

Publishing curated content (website admins and resellers)

• Website administrators publish for everyone under Admin portal › Content; reseller staff (reseller admins and employees) publish for their own customers under Reseller portal › Content. A reseller sees and edits only its own packages.
• Create the package (name, kind, summary, CAD category, licence text), then upload a version: a .sphereharness-pack exported from the desktop agent (Skills and Knowledge Base both export one), or a ZIP of .md files for knowledge, with a version number higher than the last one and a change list of up to 4,000 characters.
• The server checks the package’s structure and file fingerprints and scans it for things that must never be published — credentials and keys, HTML or scripts, suspicious links — and refuses it by name if it finds one. It then stores, signs and publishes the version.
• Deprecate or Withdraw a version with a reason; installers are told on their next update check.

Limits

A package is at most 20 MB; one knowledge file at most 1 MB and one skill at most 256 KB. An account can download 200 packages and check for updates 24 times a day.

See also

• Publishing in the marketplace
• The community forum
• Skills and Knowledge Base
• Tenant mode: the organisation server