Creator-voice fine-tunes, attested by Planisphere. Every delivery includes a sha-pinned, Merkle-rooted bundle that resolves which adapters in the batch are doing distinct work, which are redundant, and which fail. The measurement is part of the product.
Backstaff is a vertical product on the Planisphere substrate. The customer brings a set of source corpora — one per target voice — and receives back a batch of LoRA-style fine-tuned adapters, each evaluated against a standard three-category battery, packaged inside a Planisphere attestation bundle.
| Spec | Value |
|---|---|
| Subject | Creator-voice corpus → LoRA-style adapter |
| Categories evaluated | cat_beats_base · cat_beats_system · cat_voice_coherence |
| Grading | PASS / PARTIAL / FAIL per category, trinary |
| Deliverable | Per-adapter weights + Planisphere attestation bundle |
| Attestation format | Same as PSP-002 — sha-pinned, Merkle-rooted, NIST AI RMF-mapped |
| Validated scale | 28-creator batch · 7 distinct profiles · 1 catastrophic outlier identified · 17 saturated |
| Reference bundle | PSP-005 — verified, root 408a536d…b964e9a |
Past-performance evidence — the creators in the v0.2 reference batch. Twenty-eight corpora in, twenty-eight adapters out, one attestation bundle binding them. Outliers shown in signal red; saturated-bucket members at low contrast. For the cluster math behind the labels, see PSP-005 §03.
PSP-003 frames a portfolio of verticals — Vendor Lattice, Drift Witness, Backstaff, others — sharing one measurement substrate and one attestation format. Backstaff is the first vertical actually shipped. Its existence is the working demonstration of the substrate's product strategy.
The customer never has to know the substrate exists. They commission a batch of voice fine-tunes. They receive weights plus an attestation bundle. The bundle's value lands on second read: the deliverable carries its own proof. Two months later, when the customer wants to know whether their re-trained creator-vN+1 is actually distinct from creator-vN, the attestation is the citable answer.
verify <bundle> on customer infrastructureFor the worked example — what 28 deliverables look like in practice — see PSP-005. Same product, prior batch, real numbers.