Skip to content
Preview — registry, ledger and certificate data on this host are sample data.
Registry

Registry / sample-commons/brasswork

sample-commons/brasswork

Sample data

This repository does not exist. It is part of the preview's fictional dataset, present so this page's every state — badge, waivers, allocations, coverage — can be seen and tested before a real project adopts. A production build refuses this data outright.

Delisted

Delisted 2026-09-25 · reason class: marks misuse. This page stays at its URL as a neutral record so citations and audit trails keep resolving. The badge is neutral and asserts nothing; vested coverage is unaffected, and the ledger rows this repository produced are not withdrawn.

A build tool for brass-instrument fingering charts. Delisted for misuse of the movement's marks.

Registration

purpose source · status: see registry

Repository
https://github.com/sample-commons/brasswork
Node id
R_kgDOSMPL0009
State
delisted · marks misuse
Verification state
unverified — no current administrator claim stands for this listing.
Weight class
Standard — chosen from the published menu by the administrators, reviewable by the steward. Administrators never set prices; the weight class is the only pricing input they touch.
Adopted
2026-09-07
Registered
2026-09-07
Licence version
PurposeSource-1.0 — the published text of this version is a draft under counsel review.
Per-project manifest
defaults apply — no manifest, none needed PURPOSE.yml is optional overrides only (D23) and is not parsed at v0; the published defaults apply.
Administrators on record
1

Conversion to Apache-2.0

Every released version converts on its own fourth anniversary — the licence is not a single clock, and a project that keeps releasing keeps a rolling four-year window rather than reaching one cliff.

Per-release-year conversion dates for this repository

Versions released in Convert to Apache-2.0 during
2026 2030

The licence version itself (PurposeSource-1.0) converts on 2030-09-01, computed from its publication date rather than stored.

Computed at 2026-09-03T16:17:53Z · evaluated as of 2026-11-20T09:00:00Z · updated within minutes

This project's numbers

Contributors claimed
2
Organisations covered for this repository
1 — Tessellate Cloud Inc (yes-via-project)

Impact Shares

2 holders. Largest share 67% · median 67%. Algorithm version: pp-v0 (sample)

below the published floor — points and percentiles only, no currency figure. Impact Shares direct a pool towards cause categories; they never pay a contributor. The share figures are coarse on purpose — the display gate exists so a small share is never dressed up as an income, and the algorithm version is printed because the shares mean nothing without it.

Public benefit produced

Allocated to this repository's pool, read from the append-only ledger. Every figure carries the row it came from.

Period Amount Ledger row
Lifetime CHF 293 1 row(s) through 2026-09
Last quarter (2026-Q3) CHF 293 the rows falling inside that quarter
2026-09 CHF 293 led_tj6q5a14w6typm3vac96kr1db6

"Produced" means allocated to this repository's pool and routed onward to category funds — never received by this repository or by anyone working on it. Contributors direct the pool; they are not paid from it.

Where this project's pool routes

  • Health steward-default
  • Education steward-default
  • Environment steward-default

Categories come from the published menu, never from free text. A project that sets none inherits the steward default; either way the routing is visible here and in the ledger rows.

Fee waivers

No waiver stands for this repository. Waivers are granted by a verified administrator from the claim flow, are public, gratis and repository-scoped, and are listed here with their grant and revocation dates. An empty list is the correct state rather than a missing feature.

Full registry and the rules: waiver registry. Machine access: /v1/waivers/R_kgDOSMPL0009.json.

Proving coverage for this repository

There is no live coverage endpoint at this phase. The proof of coverage is the published, signed entitlement record plus this site's verification page: fetch /v1/entitlements/{companyId}.jws, check its ES256 signature against /jwks.json, and read the lane, scope and period. The computed endpoint activates later with no schema change, so a client written against those documents today keeps working.

How the coverage answer is computed · verify a certificate

verify only at purposesource.org/verify

Badge embed kit

This badge currently renders neutral

The repository's state is delisted, so the endpoint answers the neutral form (status: see registry, grey) rather than asserting registration. A stale badge never keeps claiming a status the registry no longer records.

Sample data

This repository is part of the sample dataset, so the snippets below point at a node id that no real repository holds. They are here to show the exact shape of what a real administrator copies.

The badge reads a published artifact through the shields.io endpoint protocol, so it reflects the registry within the published propagation bound and needs no build step in your repository.

Markdown

[![Purpose Source](https://img.shields.io/endpoint?url=https%3A%2F%2Fapi.purposesource.org%2Fbadge%2FR_kgDOSMPL0009.json)](https://purposesource.org/registry/repo/R_kgDOSMPL0009)

HTML

<a href="https://purposesource.org/registry/repo/R_kgDOSMPL0009"><img src="https://img.shields.io/endpoint?url=https%3A%2F%2Fapi.purposesource.org%2Fbadge%2FR_kgDOSMPL0009.json" alt="Purpose Source: registered" /></a>

The endpoint itself

https://api.purposesource.org/badge/R_kgDOSMPL0009.json

verify only at purposesource.org/verify — the badge asserts registration, and a certificate proves it. Any other address offering to verify a Purpose Source certificate is not ours, and the one above is the only address printed on any artifact we issue.

Contributors: claim your impact. A merged contribution to sample-commons/brasswork can carry an attributed, verifiable record once the claim flow exists. The only channels that will ever invite you are this page, the badge, and links in the repository itself — no email campaigns, no unsolicited messages.