{"acceptanceLead":"I am authorised to act for this organisation, confirm the selected revenue band for our whole group in the prior tax year, and accept the Entitlement terms and the refund policy in the ","acceptanceLink":"Terms & purchase details","attKitVersion":"att-1","confirmations":[{"id":"authority","text":"I am authorised to make this purchase for my organisation. I certify that the selected revenue band is correct for our whole consolidated group in the prior tax year. There is no audit right or inspection clause under these terms.","title":"Authority and revenue band"},{"id":"group","text":"I confirm that the band above was assessed across my whole consolidated group as the licence defines it. Quoting Purpose Source License 1.0, §2: “An organization's group is that organization plus all organizations that control it, that it controls, or that are under common control with it. Control means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise. Control can be direct or indirect.” A small subsidiary of a large parent is inside the parent's group.","title":"The whole consolidated group"},{"id":"terms","text":"I accept the Entitlement terms identified below, including the selected coverage, annual term, fee, renewal and vesting rules, the respective roles of the Association and the project stewards, and the rules for using official badges and logos. Selecting coverage does not opt my organisation into public naming.","title":"Terms and responsibilities"}],"optional":[{"id":"declaration","label":"Optional, the Pass only: I may name up to fifty repositories we use; each active one is attributed 1%, and the list is never published per purchaser.","lanes":["pass"],"max":50,"min":0,"n":6,"optional":true,"text":"Optional, and for the Pass only. I may name up to fifty registered repositories my organisation uses, or none. Each named repository that is active at a month's lock is attributed 1% of what is passed on from this fee for that month, so fifty names take at most 50%. The rest, and all of it when I name none, is split equally across every registered repository active at the lock, the named ones included. A named repository that is not active at the lock drops out and its 1% returns to the equal split. Naming changes neither what the Pass covers nor its price, is advisory like every attribution, and is never published as a per-purchaser list. Every named repository is checked against the registry when the purchase is recorded.","title":"Credit your favourite repositories (optional)"},{"id":"listing","label":"Optional: list our organisation's name publicly. Unticked, we are listed as “Unlisted organisation”, which is not anonymous.","lanes":["project","pass"],"n":7,"optional":true,"text":"Optional, in every lane. Ticked, I ask that my organisation's registered legal name be shown publicly: on the list of covered organisations, in the signed entitlement record, on the public record of its certificate and beside the ledger rows of its purchases. Unticked, my organisation is listed as “Unlisted organisation” under its reference code and is named in none of those places. The reference code does not itself display your name. Anonymity is not guaranteed: the reference code, the lane, what the Entitlement covers, its term dates, its status and the fee amount of each purchase stay public, and a domain my organisation verifies resolves publicly to that identifier. If our registered legal name is a person's name, ticking publishes that name. I may later ask to be unlisted; from then on the name is removed from the list, the signed entitlement record, the public certificate records and the ledger pages — the ledger rows themselves never carry it — and a signed certificate already published stays in copies others made.","title":"Public listing (optional)"}],"permalink":"/legal/attestations/v1","publicationPromise":"your coverage record is published within 2 business days","responsibilitySummary":"Project stewards are responsible for maintaining and publishing their code. Purpose Source manages your Entitlement and its coverage record.","schemaVersion":4,"scope":{"id":"scope","label":"I choose the lane and what it covers; what is passed on from this fee is attributed by lane, advisory, the board deciding finally.","lanes":["project","pass"],"n":1,"text":"I choose the lane and what it covers. A Project covers the one registered repository I select; the Pass, every registered repository. What is passed on from this fee after the published, capped costs is attributed under the published allocation rule: for a Project, all of it to the selected repository; for the Pass, as the optional declaration below sets out. A selected repository that is not active at a lock drops out for that month: a Project's part is split equally across every registered repository active at the lock. Nothing is ever given to a project, contributor, owner or administrator: the money reaches only listed recipient organisations, by the category or listed recipient organisation designated for each repository, and otherwise under the allocation key the board publishes before each month. Attribution is advisory under the statutes and the board decides finally.","title":"Lane and coverage"},"termsPermalink":"/legal/entitlement-terms/v1","termsPublished":true,"termsVersion":"ent-terms-1","version":"att-1"}