Naming, Attribution, and Provenance

The consistent use of the name Hunter Storm throughout this site, its systems, classifications, numbering structures, archives, and future technical infrastructure is intentional.

It establishes a persistent connection between the work and its originating creator.

The convention exists in part because of the historical importance of preserving attribution. Over time, the creator’s name was repeatedly removed, obscured, displaced, or separated from work and records associated with her. The naming architecture was therefore designed so that attribution would not depend solely upon a byline, copyright notice, external reference, or the continued goodwill of another party.

The creator’s name is consequently incorporated into the identity of the systems themselves.

This principle applies across the entire environment. It is not limited to the Hunter Storm Classification System (HSCS), Hunter Storm Classification Numbering System (HSCNS), or Hunter Storm Records Management System (HSRMS). It governs the naming of systems and infrastructure developed for this site and research environment as a matter of architectural provenance.

This approach also deliberately differs from a common engineering practice of assigning systems arbitrary or thematic names—such as mythological figures, fictional characters, spacecraft, animals, or other memorable internal codenames. Such names can be useful operationally, but they do not inherently preserve authorship or provenance.

The systems developed here are therefore named for their source rather than disguised behind unrelated codenames.

The objective is not self-aggrandizement. It is continuity. The name identifies where the system came from, who built it, and whose body of work it belongs to. The attribution is part of the architecture.

Related Governance Pages

AI and Automation Governance — Establishes rules for responsible automation, AI‑assisted decision-making, and machine‑supported institutional processes to ensure accuracy, transparency, and operational integrity.
Audit and Verification Governance — Defines the institution’s audit posture, verification procedures, and evidence‑based review mechanisms to maintain accountability and prevent governance drift.
Classification System (HSCS) — Provides the structural taxonomy for organizing institutional content, ensuring consistent categorization, discoverability, and cross‑domain alignment.
Classification Numbering System (HSCNS) — Establishes the numbering schema used across documents, pages, and collections to maintain traceability, version clarity, and archival precision.
Communications Governance — Governs institutional communication standards, messaging consistency, escalation pathways, and public‑facing clarity across all channels.
Continuity and Succession Governance — Defines continuity posture, succession rules, and operational safeguards that ensure the institution remains stable across transitions, disruptions, or leadership changes.
Data Governance — Establishes rules for data stewardship, retention, classification, access control, and ethical handling across all institutional systems.
Document Governance — Establishes document lifecycle rules, numbering schema, metadata fields, archival requirements, and publication integrity standards.
Ethics and Conduct Governance — Sets behavioral expectations, ethical standards, conflict‑of‑interest rules, and conduct requirements for all institutional participants.
Governance Framework — Serves as the central anchor for all governance domains, providing structure, routing, and authoritative definitions for the institution’s governance architecture.
Identity Standards — Brand assets, usage rules, accessibility requirements. Defines brand assets, usage rules, accessibility requirements, and identity presentation standards to maintain institutional clarity and trust.
Information Security Governance — Provides the institution’s security posture, protection requirements, threat controls, and information‑handling standards.
Naming, Attribution, and Provenance — Establishes the site-wide naming and attribution convention used across Hunter Storm systems, classifications, archives, and infrastructure, preserving creator identity, authorship, continuity, and architectural provenance.
Operational Integrity Governance — Ensures operational consistency, reliability, and compliance across all institutional processes, systems, and workflows.
Policy Lifecycle Governance — Defines how policies are drafted, reviewed, approved, updated, retired, and archived to maintain institutional coherence and accountability.
Records Management System (HSRMS) — Establishes the records-management architecture used to classify, identify, organize, preserve, relate, and govern records across the Hunter Storm ecosystem, providing a structured foundation for continuity, provenance, retrieval, and long-term stewardship.
Risk and Threat Governance — Establishes risk posture, threat assessment rules, mitigation strategies, and institutional resilience frameworks.
Site Index — Provides the full structural map of the institution’s digital footprint, including domains, collections, governance hubs, and continuity nodes.
Stakeholder Engagement Governance — Defines how the institution interacts with stakeholders, manages expectations, communicates decisions, and maintains trust.
Transparency and Stewardship — Governs decision logs, change records, disclosures, and stewardship responsibilities to ensure institutional integrity and visibility.
Website Governance — Establishes site structure, update cadence, editorial rules, and digital maintenance standards for all institutional web properties.

Hunter Storm