Editorial policy

Sonic Weaver is made by one person, the owner of Novus Stream Solutions in London, Ontario, who writes and maintains its product guidance by checking claims against the current browser implementation, the live engine catalogue, reproducible local tests, primary Web Audio and Canvas documentation, and the dated product changelog. The byline identifies who is responsible; it does not invent a named expert or professional credential.

Articles carry the byline Sonic Weaver. That byline is represented as a Person in structured data, working for Novus Stream Solutions. It stands for the one person who builds Sonic Weaver and writes its guidance, not a fabricated named expert or a credential we cannot substantiate.

Product and workflow claims are checked against the current application, catalogues, tests, and representative browser-local output before publication.

• Visualizer behaviour is sourced first to the live engine catalogue, draw registry, and the editors that read those contracts.
• Limits, fallbacks and unsupported cases are published beside capabilities rather than hidden in release notes.
• A green automated test is evidence for the behaviour it exercises, not proof of every quality or accessibility outcome.

Readers can report a specific statement, route, source, or reproducible result that appears wrong or stale.

• Correction requests go to visualizers@novusstreamsolutions.com; article links pre-fill the page title and URL.
• Confirmed errors are corrected at source so page copy, metadata, search, RSS, and LLM output do not preserve competing versions.
• A substantive correction earns a real updated date; formatting-only edits do not manufacture freshness.

AI may assist outlining, code review, test generation, or draft editing, but it is not treated as a source or an accountable author.

• A human-directed review checks generated claims against the repository, current output, and primary sources before publication.
• AI-generated citations, measurements, credentials, quotations, and product behaviour are rejected unless independently verified.
• Accountability remains with the developer behind the Sonic Weaver byline.

Technical, platform, standards, and API claims prefer the organization that owns the specification or implementation.

• Product behaviour is sourced first to the current code, registries, fixtures, tests, and measured output.
• External facts prefer official Web Audio, Canvas, and related platform documentation, standards bodies, and original research.
• Third-party summaries may provide context but do not replace a primary source for a precise or time-sensitive requirement.

Published and updated dates describe real editorial events and are shared by the visible article, metadata, schema, sitemap, and RSS feed.

• An updated date is recorded only after a substantive revision to the article body or a correction that changes meaning.
• Time-sensitive platform guidance is reviewed against current official documentation before its date is advanced.
• Superseded routes use permanent redirects; a moved article does not remain published in full at two self-canonical URLs.

Include the page URL, the exact statement, and a primary source or reproducible result where possible. Email visualizers@novusstreamsolutions.com. Confirmed substantive corrections receive a real modified date.