ARI Metadata Policy & Schema v3.0.1 — Alignment Patch

ARI v3.0.1 — Metadata Policy & Schema Alignment Patch

Release Date: 2026-01-10
Status: Active
Type: Patch-Level Governance + Schema Alignment
DOI: 10.5281/zenodo.17743096

---

Summary

This patch release updates both the ARI Metadata Policy and its corresponding JSON schema to ensure that governance metadata semantics are fully aligned. The update introduces the required domain field, clarifies the meaning of type as an authority-level classifier, and resolves classification ambiguity identified after the v3.0.0 release.

This is a non-breaking governance patch. No new rules were introduced and no existing rules were removed. The corrections improve structural clarity, semantic consistency, and machine-validatability for downstream tooling such as Stamp and CRI-CORE.

---

What Changed in v3.0.1

Metadata Policy

• Updated metadata header to include the new domain field
• Corrected type from "governance" → "normative" to align with authority semantics
• Confirmed policy status as Active
• Version incremented from 3.0.0 → 3.0.1 to reflect metadata-level correction

JSON Schema

• Added domain as a required field
• Introduced domain enum:
  • governance
  • methodology
  • enforcement
  • documentation
  • case-study
• Updated schema $id to ari-metadata-3.0.1.json
• Updated description to indicate alignment patch
• Preserved all v3.0.0 semantics and required fields

---

Governance Impact

• No policy rules were changed
• No enforcement semantics were altered
• No ADR was generated (patch-level alignment only)
• No downstream breaking changes to ARI governance

This release restores complete consistency between policy text, metadata format, and schema validation requirements.

---

Version State

• ARI_VERSION: 3.0.1
• Metadata Policy: v3.0.1
• Metadata Schema: v3.0.1

All components are now synchronized.

---

Next Steps

• Stamp will adopt domain-aware validation in its first release
• CRI-CORE will integrate domain semantics into enforcement contracts
• No immediate retroactive normalization is required for older files
• All new documents MUST follow v3.0.1 metadata format

---

_{© 2026 Waveframe Labs — Independent Open-Science Research Entity · Governed under the Aurora Research Initiative (ARI)}

ARI Metadata Policy v3.0.0 — Canonical Metadata Schema Revision

ARI Metadata Policy v3.0.0 — Release Notes

Release Date: 2026-01-09
Status: Active
Type: Major Governance Release
DOI: pending until Zenodo registers the version DOI

---

Summary

This release introduces Metadata Policy v3.0.0, a major governance upgrade that replaces Metadata Policy v2.0.0 and establishes the canonical metadata schema for all Aurora-governed artifacts. The new specification enforces stricter structure, clearer authorship rules, mandatory DOI usage, explicit dependency graphs, and machine-validatable fields designed to support downstream tooling like Stamp and CRI-CORE.

This is a breaking governance change and sets the foundation for fully automated metadata validation across the Aurora ecosystem.

---

What’s New in v3.0.0

1. Mandatory Structured Metadata Fields

v3.0.0 formalizes the following fields as required for all governed Markdown artifacts:

• title
• version
• status
• doi (concept or version DOI depending on context)
• author (structured block)
• maintainer (structured block)
• created
• updated
• license
• ai_assisted
• ai_assistance_details (conditional)
• dependencies
• anchors

This transforms metadata from descriptive text into a strict, machine-validated schema.

---

2. Revised AI-Assistance Disclosure Rules

The enum for AI assistance has been updated:

• none
• partial
• extensive

Rules now include explicit conditional validation and prohibit AI from being listed as an author.

---

3. DOI Requirements

Documents must now explicitly include:

• Concept DOI for top-level or conceptual governance documents
• Version DOI for versioned releases
• TBD placeholders allowed only prior to archival publication

This ensures traceability and archival permanence across all layers of the Aurora stack.

---

4. Dependency & Anchor Semantics

Documents must declare:

• Explicit dependency paths
• Stable anchor tags following canonical naming:
  SYSTEM-DOCUMENT-vMAJOR.MINOR.PATCH

This unlocks deterministic provenance graphs and future automatic lineage tools.

---

5. Canonical JSON Schema Updated

The schema has been revised to:

• enforce new required fields
• validate updated enums
• reject non-authorized fields
• ensure immutability of created and correctness of ISO-8601 dates
• support machine enforcement through Stamp and CRI-CORE

The schema now fully reflects the governance logic of v3.0.0.

---

Breaking Changes

This release introduces major structural changes:

• v2.0.0-compliant metadata is now invalid under v3.0.0
• repositories using older metadata formats must update before future validation tooling will work
• automation relying on v2 schema must update validator logic

However, retroactive normalization is not required immediately. The new rules apply going forward.

---

Why This Matters

This is the first Aurora release that makes metadata:

• deterministic
• enforceable
• automation-ready
• tool-agnostic
• audit-aligned
• reproducibility-oriented

It provides the infrastructure needed for:

• Stamp (metadata injector/normalizer)
• CRI-CORE (enforcement engine)
• Forge (metadata-preserving PDF generator)
• future lineage systems (Tracelink, Glyphtrace)

With v3.0.0, the metadata layer becomes mature, stable, and ready to anchor the entire ecosystem.

---

Recommended Actions for Maintainers

• New documents MUST use v3.0.0 metadata format.
• Legacy documents MAY be updated incrementally; no immediate requirement.
• Tooling should update schemas and validation logic without delay.
• Repositories should adopt version DOIs for all future releases.

---

ARI v2.0.0 — Constitutional Governance Normalization Release

ARI v2.0.0 — Constitutional Governance Normalization Release

This release establishes Aurora Research Initiative (ARI) v2.0.0 as the authoritative, binding
governance framework for the Aurora ecosystem.

Version 2.0.0 represents a constitutional normalization of ARI’s institutional law, replacing
implicit or provisional governance with formally ratified policy, constraints, and change-control
mechanisms.

This release supersedes all prior governance interpretations.

---

What This Release Does

ARI v2.0.0 formally ratifies and normalizes the Core Governance Stack, including:

• Metadata Policy v2.0.0
  Mandatory authorship, AI-assistance disclosure, schema canonicalization, and institutional validity rules.

• Epistemic Doctrine (Normalized)
  Audit-first cognition, provenance as identity, falsifiability requirements, and role independence.

• Governance Model & Role Separation Charter
  Explicit separation of governance, method, tooling, engineering, and case-study authority.

• Method Constraints (AWO)
  Formal limits on method-level capabilities, reasoning exposure, and governance non-interference.

• Tooling Constraints (CRI-CORE)
  Deterministic enforcement authority, integrity validation, and explicit prohibition of epistemic inference.

• Change Control & Versioning Policy
  ADR-based governance change control and Global Ecosystem Release Tag requirements.

• Institutional Architecture Definition
  Canonical positioning of ARI within the Aurora ecosystem.

---

Architectural Outcomes

• Governance rules are law, not tooling behavior
• Enforcement is mechanical, not interpretive
• Epistemic validity is binary, not reputational
• Human authority is constrained by role, not privilege
• Negligence, bypass, and self-approval are structurally prevented

---

ADR Ratification

This release ratifies the following Architecture Decision Records (ADRs):

• ADR-0001 — Metadata Enforcement, Authorship, and Schema Canonicalization
• ADR-0002 — Adoption of Core Governance Stack (Genesis)
• ADR-0003 — Enforcement Authority and Governance Non-Override

All future governance changes must proceed via ADR prior to enforcement.

---

Institutional Status

• ARI Version: 2.0.0
• Status: Active — Constitutional Governance Baseline
• Scope: Governance, epistemics, constraints, architecture
• Authority: Binding across AWO, CRI-CORE, Waveframe Systems, and all case studies

This version is the authoritative reference for institutional correctness within the Aurora ecosystem.

---

Notes on Derived Artifacts

This release establishes governance and policy at the source level (Markdown).
Derived artifacts (PDFs) will be generated in a subsequent packaging release and must inherit
authoritative metadata in accordance with ARI policy.

---

Compatibility & Enforcement

• Existing repositories must be updated to comply with Metadata Policy v2.0.0
• Artifacts lacking required metadata are institutionally invalid
• Enforcement failures must halt execution and be logged

---

Citation

Please cite the specific version used.

Concept DOI:
https://doi.org/10.5281/zenodo.17743096

A version-specific DOI will be minted by Zenodo upon release.

---

This release marks the transition of ARI from a governance proposal to an enforceable institutional system.

ARI v1.0.1 — Initial Institutional Governance Release

ARI v1.0.1 — Initial Institutional Governance Release

This release establishes the foundational institutional framework for the Aurora Research Initiative (ARI).
It formalizes ARI’s epistemic, governance, and operational rules, including:

Core institutional architecture

Governance principles and constraints

Documentation structure and repository layout

Identity, attribution, and provenance standards

Future expansion pathways and case-study integration

This version represents ARI’s first stable snapshot and serves as the authoritative reference for all governance, provenance, and methodological work across the Aurora ecosystem.