Ecosystem Publication and Identifier Standard

The identity architecture of the entire ecosystem. This standard defines how works are named, numbered, tracked, and preserved across all properties. It establishes namespaces, series rules, canonical identifiers, legacy handling, provenance requirements, and cross‑property interoperability—forming the foundation for every durable publication in the Hunter Storm ecosystem.

Hunter Storm™ Ecosystem — Master Standard

Executive Summary

The Hunter Storm™ Ecosystem Publication and Identifier Standard establishes the unified identity, numbering, provenance, and cross‑property interoperability framework used across all Hunter Storm institutional properties. It defines how works are persistently identified, how series and namespaces function, how legacy identifiers are preserved, and how publication records maintain verifiable provenance over time.

This standard ensures that every publication—whether issued by Hunter Storm™, BSI, SDSUG, or ZSG—shares a consistent architectural foundation while retaining its own institutional character and namespace. It separates identity from classification, versioning, and location, enabling long‑term continuity, scalable corpus growth, and durable cross‑property linkage.

By codifying persistent identifiers, historical metadata rules, and a common publication record model, the standard provides the backbone for ecosystem‑wide interoperability, future registry expansion, and the Hunter Storm Records Management System. It is the authoritative reference for how durable works are named, tracked, related, and preserved across the entire ecosystem.

Purpose

The Hunter Storm ecosystem includes multiple distinct properties serving different functions, audiences, and publication models. This standard establishes a common identity, publication, numbering, provenance, and cross-reference architecture across those properties while preserving the individual character and institutional purpose of each.

The objective is interoperability without unnecessary uniformity.

This standard is the authoritative reference for how publications and other durable works are identified across the ecosystem.

Individual properties may implement the standard differently according to their content model. Each property maintains its own namespace and publication series while remaining interoperable with the ecosystem as a whole.

Scope and Applicability

The Hunter Storm™ Ecosystem Publication and Identifier Standard applies to all durable works published across the Hunter Storm ecosystem, including Hunter Storm™, Black Star Institute (BSI), Sonoran Desert Security (SDSUG), and ZStormGirl (ZSG). It governs the identity, numbering, provenance, and cross‑property interoperability of publications, reports, frameworks, assessments, institutional documents, and other works intended for long‑term reference or archival preservation.

This standard applies to:

All publication series issued by any participating property
All works assigned a canonical identifier
All works requiring persistent provenance, traceability, or cross‑property linkage
All records managed within the Hunter Storm Records Management System (HSRMS)
All future properties or institutional units that join the ecosystem

This standard does not apply to:

Ephemeral content, temporary notices, or short‑lived communications
Informal commentary, creative works, or media posts that do not require canonical identifiers
Draft materials not yet assigned a publication identity
Internal working documents unless formally published as part of a series

Where a property maintains its own publication and identifier standard, that property‑specific standard must implement and remain interoperable with this master standard. In all cases, the master standard serves as the authoritative reference for identity architecture, numbering rules, legacy handling, and cross‑property interoperability.

Registry Roadmap

The Hunter Storm™ ecosystem may expand to include a centralized Artifact and Publication Registry that aggregates identifiers, metadata, and cross‑property relationships across all participating properties. The registry will function as an index and interoperability layer—not a replacement for the authoritative publication record maintained by each issuing property.

The roadmap for registry development includes:

Unified Metadata Model — Establishing a shared schema for identifiers, legacy numbers, provenance fields, and cross‑references.
Cross‑Property Synchronization — Creating automated or semi‑automated mechanisms for ingesting publication records from Hunter Storm™, BSI, SDSUG, and ZSG.
Relationship Mapping — Supporting parent/child works, successor publications, related series, and cross‑domain linkages.
Historical Continuity — Preserving legacy identifiers, prior versions, and superseded records without altering canonical identities.
Scalable Corpus Architecture — Ensuring the registry can grow from hundreds to millions of works without renumbering or structural changes.
Public and Internal Access Layers — Providing a public‑facing index for discoverability and an internal governance layer for audit, verification, and stewardship.

The registry will evolve incrementally. Early versions may provide simple cross‑property indexing, while later versions may support advanced provenance queries, relationship graphs, and integration with the Hunter Storm Records Management System (HSRMS). At all stages, the registry must preserve the core principles of this standard: persistent identity, non‑recycled numbering, historical continuity, and property‑specific authority.

Governing Principles

1. Identity is Persistent

A canonical identifier identifies a work and should remain associated with that work throughout its lifecycle. Identifiers are assigned; they are not periodically recalculated.

2. Fixed‑Width Numeric Padding (Six‑Digit Format)

Sequential publication numbers use a fixed six‑digit, zero‑padded format to ensure consistent sorting, predictable formatting, and long‑term corpus stability across the Hunter Storm ecosystem.

Examples:

BSI‑DCT‑000001
BSI‑DCT‑000002
SDSUG‑CYB‑000001
SDSUG‑CYB‑000002

The padding is mandatory and applies to all identifiers in all properties and all publication series.

Corpus Size Justification

The Hunter Storm ecosystem is designed for indefinite expansion across multiple properties, publication families, and long‑term institutional output. A six‑digit numeric width provides:

Capacity for 999,999 works per series without renumbering
Stable alphanumeric sorting across registries, indexes, and automated systems
Predictable formatting for machine‑readable identifiers, cross‑property references, and archival systems
Uniformity across properties regardless of differing publication volumes
Future‑proofing for extremely large corpus growth without structural changes

This padding level is intentionally generous. It anticipates the ecosystem’s multi‑property scale, long operational lifespan, and the cumulative output of research, doctrine, governance, analysis, and institutional publications.

Identity Format

Numbers always appear in the format:

000001 → 000002 → 000010 → 000100 → 001000 → 010000 → 999999

The underlying registry or software may use any internal representation required for storage or computation, but the public identifier always uses five‑digit zero‑padding.

This ensures that identifiers remain stable, sortable, and interoperable across all systems, properties, and future expansions.

3. Numbers Are Never Recycled

Once an identifier has been assigned, it remains permanently associated with its historical record.

An identifier is not reassigned to another work.

4. Renumbering is Not Correction

A migration from a legacy identifier to a canonical identifier does not imply that the underlying work was erroneous.
Where an earlier numbering system was used, the earlier identifier is preserved as a legacy identifier.
The canonical identifier becomes the current public identifier.

5. Historical Information is Preserved

Legacy identifiers, prior titles, publication dates, versions, and other historical metadata may be retained in the publication record. Historical metadata should not be unnecessarily repeated in reader-facing titles or headings.

6. Publication Identity is Distinct from Location

An identifier must not depend upon:

the current URL,
website navigation,
menu position,
category position,
publication order on a page,
or database record position.

URLs may change. Navigation may change. The identity of the work should not.

7. Series are Namespaces, not Filing Tricks

A publication series establishes a meaningful namespace within an issuing property. The sequence belongs to that series.

For example:

SDSUG-CYB-1

and

SDSUG-PQC-1

may both legitimately exist because they belong to different publication series.

8. Classification and Identification are Different Functions

A domain, topic, category, collection, or research area describes what a work concerns.
An identifier identifies the work.
These functions should not be unnecessarily collapsed into one number.

9. Versioning is Separate from Identity

A revision of a publication does not ordinarily create a new work identifier.
Where appropriate, version metadata records changes to the existing work.
A substantially new work, edition, or successor publication may receive a new identifier according to the applicable series rules.

10. Provenance Remains Inspectable

Where practical, each publication record should establish:

author
issuing property
publication date
identifier
version or edition
canonical URL
methodology
sources or references
related works
relevant external identifiers
applicable legacy identifiers

The objective is not merely presentation of authority, but preservation of verifiable provenance.

Ecosystem Namespace Architecture

Property	Namespace	Identifier Pattern	Primary Model
Hunter Storm™	`HS`	`HS-[SERIES]-[NUMBER]`	Research, analysis, publications, essays, institutional work
Black Star Institute	`BSI`	`BSI-[SERIES]-[NUMBER]`	Doctrine, research, frameworks, assessments
Sonoran Desert Security	`SDSUG`	`SDSUG-[SERIES]-[NUMBER]`	Practitioner research and institutional publications
ZStormGirl	`ZSG`	No mandatory report sequence	Creative, media, legacy blog, and brand content

The namespace identifies the issuing property.

The series identifies the publication family.

The sequential number identifies the work within that series.

Publication Record Model

Where applicable, a publication record should support the following fields:

Field	Purpose
Canonical Identifier	Permanent public identity of the work
Legacy Identifier	Historical identifier, if one existed
Title	Official work title
Issuing Property	Organization or property responsible for publication
Series	Publication series or collection
Publication Type	Report, framework, doctrine, assessment, article, etc.
Author	Authorship attribution
Publication Date	Original publication date
Edition	Edition designation where applicable
Version	Current version
Status	Current, superseded, archived, withdrawn, etc.
Canonical URL	Preferred web location
Related Works	Parent, child, successor, companion, or related publications
External Identifiers	DOI, ISBN, archive identifier, or other applicable identifiers
Sources	Evidence and reference material
Methodology	Method used to produce the work
Revision History	Material changes over time

Not every property or content type requires every field.

Legacy Identifier Policy

Legacy identifiers are historical metadata.

A migration record may state:

Legacy identifier: Cybersecurity 2026 Collection — Report No. 1
Current identifier: SDSUG-CYB-1

The legacy identifier should remain searchable and machine-readable where practical.

The public-facing page should normally emphasize the current canonical identifier rather than displaying multiple historical identifiers in the title.

A central registry may maintain the complete crosswalk between legacy and canonical identifiers.

Cross-Property Interoperability

Each participating property maintains its own identity.

The properties do not share a single numerical sequence.

Instead, they share the same architectural rules.

The relationship is therefore:

Common Standard → Property Namespace → Publication Series → Sequential Identifier

rather than:

One giant global number assigned to everything.

This preserves institutional distinction while permitting a unified ecosystem registry.

Property Implementations

The current implementations are:

Black Star Institute — Publication and Identifier Standard
Sonoran Desert Security — Publication and Identifier Standard
ZStormGirl — Content Identity and Provenance Standard

Each implementation should link to this master standard.

This master standard should link to each implementation.

Registry and Future Expansion

The ecosystem may eventually maintain a centralized publication registry containing the identifiers and metadata of works across participating properties.

The registry should function as an index and relationship layer rather than replacing the authoritative publication record on the originating property.

The architecture must remain valid regardless of corpus size.

No assumption is made regarding the eventual number of works.

A sequence may naturally progress from:

1 → 2 → 10 → 100 → 1,000 → 100,000

without requiring renumbering or artificial padding.

Integrity Rule

An identifier is an identity, not a prediction.

The numbering system must never require knowledge of how large the corpus will eventually become.

The ecosystem is designed to preserve historical continuity while permitting indefinite expansion.

Related Standards

Black Star Institute — Publication and Identifier Standard
Sonoran Desert Security — Publication and Identifier Standard
ZStormGirl — Content Identity and Provenance Standard

These property-specific standards implement this ecosystem standard within their respective publication models.

Status: Ecosystem Standard
Owner: Hunter Storm™
Scope: Cross-property publication identity, numbering, provenance, and interoperability

Hunter Storm