# Policy Register Record version: 1.1.0 Published: 2026-08-10 Research cutoff: 2026-08-10 Source commit: 8fc9554267b1e1dc82abc4f422151e3ebbc90723 The operating rules currently adopted by AB5D. # Founding and Operating Principles Record ID: AB5D-POL-001 Record version: 1.1.0 Published: 2026-08-10 Research cutoff: 2026-08-10 Source commit: 8fc9554267b1e1dc82abc4f422151e3ebbc90723 Status: Adopted Effective date: 2026-08-10 Defines AB5D as a collector-led reference institution for the AB[500] and establishes evidence, openness, bounded scope, revision, and stewardship as operating principles. ## Provisions 1. AB5D documents the AB[500] as a historically bounded field: the first 500 projects carrying the official Art Blocks ab500 designation. 2. Institutional records distinguish verified observations from supplied metadata, interpretation, and unresolved research. 3. Material records receive stable identifiers, publication dates, versions, research cutoffs, and revision histories. 4. Machine-readable access is part of publication, not a secondary export. 5. Corrections preserve an audit trail. Substantive earlier claims are not silently overwritten. 6. AB5D may operate through founder and editorial decisions until a membership body and voting mechanism are formally constituted. --- # Collection Mandate Record ID: AB5D-POL-002 Record version: 1.1.0 Published: 2026-08-10 Research cutoff: 2026-08-10 Source commit: 8fc9554267b1e1dc82abc4f422151e3ebbc90723 Status: Adopted Effective date: 2026-08-10 Defines what the AB5D collection preserves and how collection significance is assessed. ## Provisions 1. The primary collection mandate is representative custody across the AB[500], with priority given to completing the 500-project project-level set. 2. A held token is not interchangeable with its project record. Each accession may carry object-specific provenance, traits, rendering behavior, risks, and display instructions. 3. Acquisition priorities may consider missing project coverage, historical importance, preservation risk, research value, and responsible cost. 4. The mandate does not promise custody of every edition or declare any one token the definitive example of a project. 5. Collection statistics are dated observations and must identify the wallet or consolidated profile basis used. --- # Accession and Deaccession Policy Record ID: AB5D-POL-003 Record version: 1.1.0 Published: 2026-08-10 Research cutoff: 2026-08-10 Source commit: 8fc9554267b1e1dc82abc4f422151e3ebbc90723 Status: Adopted Effective date: 2026-08-10 Creates a documented threshold for admitting works to the permanent record and for recording any later removal from institutional custody. ## Provisions 1. Accession requires confirmed token identity, current custody, a traceable custody event, a credit line, rights metadata, and an initial preservation assessment. 2. Selection, acquisition, custody, and accession are distinct states. A selected or held work is not accessioned until its record is published. 3. Accession identifiers are permanent and are never reassigned. 4. A disposal, transfer, loss of access, or mandate-based removal does not erase the accession record. Its custody status and reason are revised with an audit entry. 5. Deaccession decisions must identify authority, rationale, destination when public, and whether retained research or media records remain. 6. No work in the initial pilot is approved for deaccession by this policy. --- # Donation Acceptance Policy Record ID: AB5D-POL-004 Record version: 1.1.0 Published: 2026-08-10 Research cutoff: 2026-08-10 Source commit: 8fc9554267b1e1dc82abc4f422151e3ebbc90723 Status: Adopted Effective date: 2026-08-10 Sets conditions for accepting donated digital works, funds, services, or preservation material. ## Provisions 1. AB5D may decline a donation that falls outside the collection mandate, carries unclear title, creates disproportionate custody or preservation risk, or imposes incompatible restrictions. 2. Acceptance does not imply endorsement of the donor, artist, marketplace, or valuation. 3. Credit lines are agreed before accession. Anonymous credit may be used when operationally and legally appropriate. 4. Donors do not receive curatorial control, governance rights, tax advice, or a valuation from AB5D by reason of a gift. 5. Restricted gifts require a written public summary of material restrictions before acceptance. 6. A donation is not represented as accepted until custody and acceptance are independently confirmed. --- # Rights and Preservation Handbook Record ID: AB5D-POL-005 Record version: 1.1.0 Published: 2026-08-10 Research cutoff: 2026-08-10 Source commit: 8fc9554267b1e1dc82abc4f422151e3ebbc90723 Status: Adopted Effective date: 2026-08-10 Establishes minimum documentation for rights, source media, generative dependencies, rendering tests, display, checksums, and known preservation limits. ## Provisions 1. Ownership of a token is recorded separately from copyright, license, publicity, moral, and platform rights. 2. Rights statements report observed source metadata and are not expanded beyond that evidence. 3. A live work record should identify its generator, library dependencies, external assets, controls, viewport expectations, audio behavior, and tested runtime where known. 4. Official media and scripts may be checksummed without implying that AB5D has retained or may redistribute their bytes. 5. A still image is a reference representation and must not be described as a complete substitute for live behavior unless the work is explicitly static. 6. Preservation limitations and unverified behavior remain visible until a later observation resolves them. --- # Corrections and Revision Policy Record ID: AB5D-POL-006 Record version: 1.1.0 Published: 2026-08-10 Research cutoff: 2026-08-10 Source commit: 8fc9554267b1e1dc82abc4f422151e3ebbc90723 Status: Adopted Effective date: 2026-08-10 Defines how errors, new evidence, interpretation changes, and machine-record revisions are handled. ## Provisions 1. Anyone may propose a correction by naming the record ID, disputed field or claim, evidence, and requested change. 2. Typographic corrections may increment the patch version. Material factual changes increment the minor version. Structural or mandate changes increment the major version. 3. A revision entry records the date, affected records, nature of the change, and source commit. 4. Superseded material remains traceable through revision history even when the current page displays only the corrected statement. 5. A correction request has no adopted effect until reviewed and incorporated into a published revision.