Useful first. Evidence close behind.

What we cover

We cover material changes where AI and music genuinely meet: products, artists and culture, research, rights and policy, business, communities, events and opportunities.

A story should help someone understand a change, make a decision or take a useful next step. A press release, loud claim or trending argument is not enough by itself.

How we choose and verify stories

We prefer primary records: product documentation, laws, court filings, research papers, terms, price pages, organizer pages and direct statements. Reputable reporting can add interviews and context. Social posts and aggregators are usually leads, not final evidence.

A company or artist announcement proves what that party said. It does not automatically prove the claim. Disputed, inferred and not-publicly-disclosed details are written with visibly different levels of certainty.

Sources are labeled by their actual role: primary record, official statement, original reporting, secondary coverage or community evidence. A secondary article is not described as primary merely because it links to the underlying source.

How we write and quote

We write in original language, link the central source and separate fact from claim and analysis. We do not reproduce another publication’s headline, opening, structure or substantial passages.

Direct quotes are used only when the exact words matter. They stay short, exact and attributed. There is no automatic safe word count; context and necessity matter.

Images, screenshots and generated media

We prefer original, public-domain or properly licensed media. Official screenshots, logos and press images need a documented source and usage basis. Credit alone is not permission.

Generated artwork is editorial illustration, not evidence. It must not pretend to be a real interface, person or event photograph. Material composites and generated images are disclosed, and self-hosted news images require provenance, rights, modification and alt-text records.

Read the copyright and media process →

Automation and responsibility

Automation can help monitor sources, compare information, transcribe, organize, draft, format and check work. It is not treated as a source. Factual output is checked against cited evidence.

Nik McFly currently owns story selection, framing, publication, corrections and removals. The site does not label an item as human-reviewed unless that review actually occurred.

A story receives an item-level disclosure when AI materially shaped its published analysis or wording, generated or substantially altered media, simulated an identity, or published without ordinary human editorial control.

Routine spellcheck, formatting and research organization do not add a badge to each page. When a disclosure is useful, it appears as a short note beside the affected article or inside the existing image caption.

Corrections and removals

Confirmed errors are corrected in proportion to their impact. A material correction that changes meaning receives a visible note; minor spelling, formatting and link repairs may not.

Credible copyright, privacy, safety and impersonation requests receive priority review. Media may be temporarily disabled while the evidence is checked.

The correction route must accept any aimusic.events page. A reader should not need to know how the site stores a news story, guide, answer or listing.

Report a factual correction → · Make a copyright or media request →

Reader data and subscriptions

We collect only data needed for a stated purpose. Private submissions, contact details, newsletter addresses and anti-abuse information stay separate from public editorial evidence.

Before personal data is collected, the site must explain who operates the service, why the data is needed, which providers receive it, how long it is kept and how a person can withdraw consent or exercise applicable rights. Email delivery and engagement tracking must be described accurately.

Accessibility and reader experience

Public pages and forms target WCAG 2.2 Level AA. Automated checks are supported by manual keyboard, screen-reader, zoom, contrast, focus, motion and mobile testing.

Policy and request pages must be easy to find and usable without technical knowledge. Internal codes and workflow labels stay out of the reading experience unless they help someone make a decision.

About this policy

This is the site’s operating standard. It reduces risk but does not guarantee accuracy, security, accessibility or legality in each jurisdiction. A control counts as implemented only when the public experience, records and tests support the claim.

The policy is reviewed at least twice a year and when publication methods, automation, service providers, commercial relationships or relevant obligations materially change.

About aimusic.events and its editor → · How the site works →