“Maintenance is a silent form of justice — a new work that does not need to erase who came before: Creating, sharing and crediting authorship”

Maintenance is a silent form of justice because it determines which works, relationships, and authorships will remain visible after the attention of launch has moved elsewhere. New creation does not have to erase those who came before. It can preserve provenance, renew permission, care for formats, and distribute the labour that keeps a work understandable and correctable. In an age of generative systems and rapid circulation, maintenance prevents innovation from being financed by forgetting.

Cultural organisations are often structured around beginnings. Funding supports production, communications celebrate an opening, and success is counted while the audience is present. Later, links fail, staff change, licences expire, and the account holding the only editable copy becomes inaccessible. Each event appears to be a minor technical problem. Together they decide whose contribution remains recognised and who must spend time proving that a boundary ever existed.

Maintenance attends to the full social life of a work. It includes fixity checks, migration, accessible presentation, renewed consent, responsive correction, and deliberate closure. It also recognises that a technically intact asset can be socially damaged. A photograph may render perfectly after losing its maker's name, and an automated guide may keep answering after its evidence has become impossible to reconstruct.

Preservation distributes memory and power#

An institution shapes future knowledge when it chooses what to describe, migrate, and fund. Keeping only polished outputs can erase drafts, negotiations, and collective labour. Keeping everything without limits can extend exposure far beyond the agreement under which material was contributed. Just maintenance selects what is needed for understanding and accountability, protects what creates risk, and records why retention or deletion was chosen.

An institution shapes future knowledge when it chooses what to describe, migrate, and fund.

UNESCO's Charter on the Preservation of Digital Heritage addresses the danger that digital resources will be lost through obsolescence, instability, and inadequate policy. Its significance reaches beyond large archives. Even a modest creative project needs defined responsibility, continuity, and decisions about access that respect legitimate rights, privacy, and cultural diversity.

The important question is not simply how much storage is available. It is which relationships must remain attached to every asset. A useful record links files, versions, contributors, permissions, restrictions, dependencies, review dates, and responsible people. When those links break, the object begins to look ownerless and unrestricted. Maintenance preserves boundaries as well as content.

Credit requires care after publication#

Attribution can decay while the work itself remains unchanged. A platform crops a caption, an aggregator copies an image without context, or a translated edition adds substantial labour that nobody records. Credit should therefore be operational information. It travels with the asset where possible, appears on a stable public page, and connects to an internal record that can be corrected without concealing earlier versions.

Creative Commons' overview of CC licences shows that attribution can involve naming the creator, linking the licence, and indicating changes. Preserving these conditions across exports and reuse is continuing work. An organisation that automates distribution should also build checks that prevent licence and credit information from being stripped away.

The World Intellectual Property Organization's work on AI and intellectual property helps distinguish authorship, ownership, licensing, access to material, and technical generation. Maintenance cannot settle every legal dispute, but it keeps the records required to examine one fairly. Without shared evidence, the party controlling the platform can impose the most convenient history.

Case 1: a neighbourhood archive loses its names during migration#

A community association spends ten years collecting photographs of shops, celebrations, and campaigns. Every deposit has a record naming the photographer, describing people shown, noting an approximate date, and setting access conditions. During a move to a modern platform, the contractor imports files and titles but leaves the remaining fields in a legacy database. The old service is cancelled before anybody tests the relationships.

The new gallery is faster and easier to browse, yet it has turned a community collection into an anonymous image bank. A publisher downloads a photograph and credits only the association. A portrait whose access was limited to the cultural centre appears in search results. No image has vanished, but provenance, recognition, and restriction have been redistributed without a decision.

The association pauses downloads, restores records from backups, and asks depositors to review essential information. It defines fields that no future migration may omit, keeps the old system available until sampled records pass inspection, and creates a route for correcting public use. The publisher receives the photographer's proper credit, while restricted images are removed from indexing.

The acceptance test now includes social integrity. A migration is not complete because every JPEG opens. Names, permissions, narratives, and correction mechanisms must still work. Contractors can perform technical tasks, but responsibility for the trust placed in the collection remains with the organisation.

Copies protect a work only when they can be tested#

Common risks are predictable: accidental deletion, silent corruption, a lost password, reliance on one drive, or a proprietary format tied to discontinued software. A proportionate preservation plan uses multiple copies, separate locations, integrity checks, documented formats, access controls, and restoration exercises. Copying without verification merely multiplies uncertainty.

The NDSA Levels of Digital Preservation organise practical progress across storage, integrity, security, metadata, and formats. They are not an automatic certification or a single prescription for every collection. They help a team describe its actual position and choose a demonstrable improvement, such as separating copies or recording file changes.

The US Library of Congress provides digital-format sustainability information covering factors such as transparency, adoption, dependencies, and the preservation of significant properties. A production original, preservation copy, and access derivative can serve different purposes, provided identifiers and documentation keep them connected.

A restoration exercise is an act of accountability because it turns assurance into ability. It must restore descriptions, rights, restrictions, captions, and history alongside the file. If a recovered copy reinstates withdrawn content or loses corrected credits, the technical recovery recreates a harm that the organisation had already recognised.

Case 2: a school exhibition depends on a personal account#

A teacher hosts a video exhibition made by four cohorts of students on a free service. The decision makes an ambitious opening possible, and every work initially includes reviewed captions, permissions, and agreed credit. When the teacher moves to another school, the account remains attached to an email that nobody monitors. Two years later, the provider announces deletion of inactive projects.

The school discovers that it holds no complete export. Some originals remain on old phones, captions exist only inside the platform, and permission forms cannot be matched reliably to assets. Available downloads add a watermark and remove accessibility features. The exhibition had remained reachable, but it had never been maintained.

A mixed staff and student team recovers originals, exports captions as independent files, assigns stable identifiers, and links each work to its permission and review date. Custody moves to an institutional account with two responsible roles and a succession record. Former students help decide which works stay public, move to internal access, or close.

The outcome shows that continuity does not require perpetual exposure. Responsible maintenance can close a work with care. Documentation preserves recognition and learning while the media stops circulating beyond current consent. Institutional memory does not need to turn a person's adolescence into a permanent display.

Artificial intelligence creates dependencies that also age#

An AI-assisted work depends on more than its final output. Model version, reference materials, significant instructions, filters, selection decisions, and human review may all matter. Saving every interaction can create privacy risks; saving nothing makes explanation impossible. Proportionate documentation keeps what governance requires without collecting sensitive material by default.

The NIST AI Risk Management Framework treats governance, context, measurement, and management as continuing practices. A launch assessment expires when the model, audience, data, or purpose changes. Cultural teams need recurring tests, incident records, and a named person with authority to pause a system rather than merely report concern.

Vendor dependence is another form of maintenance debt. A low-cost feature can become essential before its terms change or it disappears. Organisations reduce that fragility by retaining usable exports, documenting alternatives, and testing an exit while they still have time. An untested exit plan is a hope, not resilience.

Case 3: a museum assistant outlives its source map#

A small museum builds a conversational assistant for an exhibition about industrial memory. The corpus combines curatorial essays, interviews, and transcripts. During launch, a curator reviews answers each week. Staff later change, the provider is upgraded, and nobody can find the map that connected passages to versions, permissions, and sensitivity rules.

A visitor asks about a workplace accident. The assistant attributes a statement to a person who never made it, then presents as fact an interpretation that families had asked the museum to qualify. The confident institutional voice hides uncertainty. The model contributes to the error, but missing maintenance allows it to reach the public.

The museum disables open answers, explains the incident, and rebuilds the corpus with identifiers, dates, and confidence levels. Families and subject specialists review disputed passages. The interface links sources, distinguishes quotations from synthesis, and routes sensitive questions to trained staff. Every future update must pass a documented test set.

The C2PA Content Credentials specification offers mechanisms for attaching verifiable claims about origin and editing to digital resources. It can strengthen traceability, but it cannot determine whether consent was free or an interpretation is fair. Technical proof needs human governance and a usable process for challenging incorrect claims.

Accessibility, security, and exit are part of continuity#

A work becomes unavailable before it disappears if an update breaks keyboard navigation, shifts captions out of time, or introduces inaccessible contrast. Accessibility is not a one-time launch review. It belongs in tests after every migration, template change, and substantial update. People encountering barriers need a reporting route, but they should not become the unpaid quality-assurance department.

Security conditions also evolve. Data that once appeared harmless may later support identity, location, or health inferences when combined with new tools. Reviewing access, minimising duplicates, and applying retention periods limits exposure. Preservation is not indiscriminate accumulation; documented deletion can protect a relationship better than endless storage.

Every project needs an ending plan. Contract closure should identify who receives assets and responsibilities, which licences survive, how contributors will be notified, and what must be destroyed. Without a handover, closure becomes abandonment: orphaned accounts, data without a custodian, and credit no authorised person can correct.

A care schedule turns intention into practice#

Each collection needs accountable ownership without making one person carry it alone. Shared knowledge, budget, and succession are part of the design. A concise register can schedule monthly, annual, and event-triggered checks for links, copies, integrity, permissions, accessibility, credits, vulnerabilities, costs, and continued necessity. Incidents update the schedule.

Useful indicators examine outcomes: actual restoration time, assets with complete provenance, credit corrections resolved, expired permissions detected, accessibility tests passed, and critical dependencies without alternatives. They also ask who performs the labour and whether it is recognised. Maintenance becomes unjust when invisible workers hold responsibility without authority or resources.

The best moment to fund maintenance is before creation. Time and money for description, verification, response, and closure prevent later emergencies. If an organisation cannot sustain a complex function, a smaller durable choice may be more responsible. Reducing technical scope can protect cultural ambition by preserving what gives the work meaning.

Maintenance is a silent form of justice because it upholds rights after the launch no longer attracts attention. It keeps the file connected to its history, the name to its contribution, permission to its limit, and innovation to accountable care. New work does not erase those who came before when continuity is designed as a shared, reviewable, and properly resourced commitment.