A directory that lists a host's plans is asked the next question at once:
how do I drive this thing from a terminal? Every provider answers it on a
page of its own, in its own words, and a reader that wants the install line
has to find and read that page for each host. nichedb.dev's hosting
collection just did exactly that for 46 providers, copying the commands
off each vendor's guide, and the exercise is the argument for putting the
facts in the descriptor.
`provider.developer` names the official CLI, its install commands keyed by
package manager and copied as the guide prints them, the install guide and
source, the API docs, the Terraform provider and the GitHub organisation. A
provider with no CLI says `"cli": null`, which is a fact, while a missing
block means unknown. Commands are copied, never composed: a reader that
invents `brew install <name>` sends a buyer to a formula that may not exist.
c0mpute.md gains the same block for the compute market, with the one
install line c0mpute.com prints, and the landing page says what 0.2 adds.
Claude-Session: https://claude.ai/code/session_01Khk1C6Ese6xjdHAWLVstca
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
* OpenServer 0.1: one file a hosting provider serves about what it sells
A new LogicSRC spec at /openserver and /docs/openserver. A provider puts
the table its order form already reads at /.well-known/openserver.json:
every offer with a kind, four axes, specs in fixed units, one price,
location and stock. A directory reads the provider instead of scraping
an aggregator whose terms forbid it, and the provider stays the author
of its own catalog. Only provider.name and each offer's name are
required; every other rule degrades.
Fifteen kinds cover what Anthony listed and the rest of the market:
cloud, vps, dedicated, bare-metal, colocation, on-prem, shared, managed,
paas, serverless, storage, gpu, edge, p2p and hybrid. Premises,
management, tenancy and model are their own keys rather than inferred
from the kind, because a managed VPS and an unmanaged one are the same
kind and different offers. A peer-to-peer market publishes one
descriptor whose offers are its current asks, with the operator pointing
at the market and not the peer; c0mpute is the compute case, OpenDisk
the storage case, OpenSwarm the settlement layer under both.
The first reader is nichedb.dev's hosting collection, being built
alongside this. findhost.app is named as the curated sibling.
Registered in DOC_SLUGS, NAV, STATIC_ROUTES and llms.txt, one line each.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Khk1C6Ese6xjdHAWLVstca
* OpenServer: name the resource blocks an offer may carry
OpenCPU, OpenMemory, OpenGPU and OpenBandwidth are being written as the
blocks that nest inside an offer's compute, compute.gpu and network, and
that stand alone as offers. Related standards now says so, with links at
/docs/<slug> where those specs will land. No subdomain is named anywhere
in this spec: every LogicSRC spec lives on logicsrc.com only.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Khk1C6Ese6xjdHAWLVstca
---------
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
