Hunter Storm Records Management System™ (HSRMS) Architecture

HSRMS Architecture

HSRMS uses multiple complementary structures rather than relying on a single numbering or categorization scheme. The principal components are listed in the following sections.

Corpus Scale and Technical Continuity Governance Standard

The Corpus Scale and Technical Continuity Governance Standard establishes requirements for maintaining the Hunter Storm information environment as the corpus expands in size, complexity, and technical scope.

The standard addresses scalability, continuity, and technical resilience so that growth in records, publications, properties, systems, and supporting infrastructure does not require fundamental redesign of the underlying information architecture.

Within HSRMS, the standard provides the continuity and scalability requirements that support long-term operation of the records-management environment.

View the Corpus Scale and Technical Continuity Governance Standard

Ecosystem Publication and Identifier Standard

The Ecosystem Publication and Identifier Standard establishes conventions for the publication, identification, and persistent referencing of materials across the Hunter Storm ecosystem.

The standard provides a common approach to publication identifiers, artifact identification, and related conventions across interconnected properties and publication environments.

Within HSRMS, the standard complements the Hunter Storm Classification Numbering System (HSCNS) by establishing ecosystem-level publication and identifier conventions while HSCNS provides the records-management numbering architecture.

View the Ecosystem Publication and Identifier Standard

Hunter Storm Classification Numbering System (HSCNS)

The Hunter Storm Classification Numbering System provides persistent identifiers for records and artifacts within the HSRMS.

The identifier is independent of subject classification, artifact type, property, series, visibility, lifecycle state, or presentation.

Identifiers are assigned according to controlled numbering rules and are intended to remain stable through revision, correction, relocation, supersession, or changes in presentation.

Legacy identifiers may be retained as previous document numbers where necessary to preserve continuity.

View the Hunter Storm Classification Numbering System (HSCNS)

Hunter Storm Classification System (HSCS)

The Hunter Storm Classification System establishes the classification architecture used to organize records according to subject, function, institutional context, or archival purpose.

Classification identifies what a record belongs to within the larger information environment. It does not, by itself, establish truth, credibility, importance, or causation.

View the Hunter Storm Classification System (HSCS)

Information Classification

Identifies information according to applicable sensitivity, confidentiality, handling, legal, regulatory, or other information-management requirements.

Information Classification is distinct from the Hunter Storm Classification System. HSCS describes the contextual or subject classification of a record; Information Classification addresses the handling characteristics of the information contained within or associated with the record.

Version Governance Standard

The Version Governance Standard establishes requirements for managing changes to documents, records, systems, and other significant artifacts while preserving historical continuity.

The standard distinguishes revision and correction from replacement or supersession and supports retention of relevant historical information, identifiers, relationships, and provenance.

Within HSRMS, the standard provides the governance framework for controlled change and complements the system’s requirements for persistence, continuity, provenance, and archival preservation.

View the Version Governance Standard

Hunter Storm Records Management System (HSRMS) Architectural Relationships

Component	Architectural Role
Archive	Long-term preservation
Artifact Type & Subtype Vocabulary	Functional artifact description
Governance Standards	Rules governing operation
HSCNS	Persistent identity and numbering
HSCS	Subject/context classification
HSRMS	Records-management architecture
Information Classification	Information sensitivity and handling classification
Lifecycle & Retention	Lifecycle management and disposition
Metadata Framework	Descriptive and management metadata
Property Registry	Ecosystem/property context
Provenance & History	Origin and historical continuity
Records Registry	Record-level index and metadata
Records Relationships	Inter-record relationships
Search/Application Layer	Retrieval and user-facing implementation
Series Registry	Functional/contextual grouping

RMS Ontology

Artifact Type and Subtype Vocabulary

Artifact types identify the primary functional form of a record or information product.

Controlled types include:

Briefing
Doctrine
Framework
Governance
Index
Legal
Marketing
Media
Policy
Principles
Publication
Report
Site Structural Artifact
Standards
Statement
Store

Subtypes provide additional specificity where the primary artifact type alone is insufficient. For example, a Publication may have a subtype such as Article, Book, Blog, Memoir, History, or Chronology.

Artifact type and subtype describe what an artifact is and how it functions; they are distinct from its subject classification.

Property Registry

The Property Registry establishes the properties, domains, and associated identifiers within the Hunter Storm ecosystem.

Property context allows records to remain connected to the site, institution, project, series, or other environment from which they originate.

Series Registry

The Series Registry provides functional or contextual groupings for records that belong together because of their subject, purpose, activity, project, or continuing body of work.

Series provide a level of organization between individual records and the larger system.

Records Registry

The Records Registry provides the structured record of individual artifacts and their identifying information.

A registry entry may include the artifact title, HSCNS identifier, artifact type and subtype, property, series, applicable classifications, information-classification status, URL, previous identifiers, provenance, relationships, lifecycle state, and other metadata required to establish context and continuity.

Metadata Framework

The Metadata Framework defines the information required to describe, identify, contextualize, manage, and retrieve records. Metadata may include subject/context classification, information-classification status, identity, ownership or authorship, dates, status, provenance, relationships, lifecycle information, and other contextual information appropriate to the record.

Records Relationships

Records do not exist in isolation. The Records Relationships structure provides a means of documenting connections between artifacts, including relationships such as:

associated with;
cites;
derived from;
documents;
part of;
references;
related to;
superseded by;
supersedes;
supports.

Relationships preserve context that cannot be represented adequately by a record’s title or classification alone.

Provenance and History

Provenance establishes where a record came from, its relationship to its originating creator or system, and relevant history of creation, modification, movement, or succession.

Attribution is treated as part of the architecture rather than as information dependent solely on a byline, copyright notice, external citation, or continued goodwill.

Where terminology, attribution, classification, or other metadata changes over time, the system may preserve both contemporaneous information and later interpretations rather than replacing the historical record.

The system therefore supports persistent connection between records and their originating context.

Lifecycle and Retention

Records may have different lifecycle requirements depending on their function, evidentiary value, operational importance, or archival significance.

Lifecycle management provides a framework for distinguishing active, superseded, archived, retained, and other appropriate states without assuming that every piece of working material must become a permanent record.

Disposable working material may remain outside the permanent record environment where appropriate. Records with continuing operational, evidentiary, historical, legal, or contextual value may require preservation.

Records Search

HSRMS is designed so that search and application layers can be built without redesigning the underlying records architecture.

The public-facing hub provides the conceptual and navigational structure. The registry, classification, numbering, metadata, and relationship models provide the information architecture beneath it.

A production search or application layer may be implemented when the size, use, or operational requirements of the corpus justify it.

System Principles

HSRMS is based on several core principles.

Persistence
Identifiers and relationships should remain stable enough to preserve continuity as records change location, presentation, or status.

Separation of Functions
Classification, artifact type, subtype, property, series, identifier, provenance, and lifecycle information serve different purposes and should not be conflated.

Extensibility
The architecture must accommodate additional properties, classifications, artifact types, subtypes, series, and records without requiring fundamental redesign.

Context
A record should remain understandable within the environment, body of work, activity, or system from which it originated.

Provenance
The origin and history of significant records should remain identifiable.

Continuity
Legacy identifiers, superseded records, historical versions, and relationships may be retained where necessary to preserve the history of the corpus.

Retrievability
Records should be structured so that they can be located and understood by future users and systems.

Proportionality
Records management should preserve what has continuing value without converting every transient working artifact into a permanent record.

Relationship to Governance

HSRMS operates within the broader Governance architecture of the Hunter Storm ecosystem.

Governance defines the rules under which the information environment operates. HSRMS defines the records-management architecture through which records are identified, classified, organized, related, preserved, retrieved, and operationalized.

The system therefore functions as a governed architectural component rather than as a standalone policy document.

Relationship to the Database

HSRMS is not synonymous with a particular database implementation.

A database may provide the technical storage and query environment through which the records architecture is implemented, but the database itself is not the architecture.

The classification model, numbering system, metadata structures, relationships, provenance, and governance requirements define the information architecture. Technical implementations may change without requiring the underlying conceptual model to change.

The system is therefore designed to remain portable across future technical environments.

Scope

HSRMS applies across the Hunter Storm information environment, including relevant websites, institutional and research properties, publications, frameworks, archives, media, structural artifacts, and other records or information products that require controlled identification or preservation.

The system is intended to scale beyond the currently published corpus and to accommodate additional historical and unpublished material as it is incorporated.

Documentation and Maintenance

HSRMS is itself subject to documentation, revision, and governance.

Changes to classification structures, numbering conventions, artifact vocabulary, metadata, relationships, or other system components should be documented sufficiently to preserve continuity and explain architectural decisions.

The system is designed to evolve without losing the history of how it evolved.

System Resources

The HSRMS architecture is supported by the following resources:

Classification System (HSCS)
Classification Numbering System (HSCNS)
Artifact Type and Subtype Vocabulary
Information Classification
Classification Crosswalk
Property Registry
Series Registry
Records Registry
Metadata Framework
Records Relationships
Provenance and History
Lifecycle and Retention
Governance Framework and Applicable Governance Standards
System Documentation
Archive
Records Search

Together, these components form the records-management architecture for the Hunter Storm corpus.

Hunter Storm