FORK-003 · Baseline Tags

✓ Ratified in pack 0.1.0

Standard 0.1.0 · Fork Management. Ratified September 10, 2026.

Version history · All versions & release notes

Every patch line identifies its unpatched starting source SHA with a v<VERSION>+patch.baseline tag.

Requirement

Patch providers MUST tag the commit that represents the unpatched baseline source state for a patched version.

The tag MUST use the form:

v<VERSION>+patch.baseline

This tag scheme applies regardless of the upstream project tag convention.

Rationale

Recipients need an unambiguous starting point for source comparison, provenance review, and audit evidence.

The +patch.baseline suffix is deliberately a source baseline marker. It does not identify an official patched release or artifact. Official OSERA patched releases are defined by REL-003 through the applicable ecosystem profile. Java release naming is defined in REL-003-JAVA.

The <VERSION> segment in v<VERSION>+patch.baseline SHOULD correspond to the source branch version in FORK-002 and the upstream version segment in the official patched-release identifier defined by REL-003.

Evidence

Patch evidence SHOULD include the baseline tag, the commit SHA it resolves to, and the corresponding upstream version or artifact.

Illustrative examples

Repository	Baseline tag
patch-spring-framework	v5.3.39+patch.baseline
patch-gson	v2.8.8+patch.baseline
patch-activemq	v5.14.5+patch.baseline

These examples show the ratified naming convention, not an inventory of published patches.

Version history

This page preserves the proposed historical source. Open the central version register for current history and publication status.

Structured requirements and checks

These definitions come from this page's source front matter. Profile inheritance remains defined by the referenced parent; these are local definitions, not a resolved conformance catalog.

schema-version: 0.1.0
sequence: 30
standard_id: FORK-003
title: Baseline Tags
summary: Every patch line identifies its unpatched starting source SHA with a
  `v<VERSION>+patch.baseline` tag.
doc-status: Ratified
standard-version: 0.1.0
candidate-pack: OSERA-SP-0.1.0 ratified
ratified-in: OSERA-SP-0.1.0
ratified-date: 2026-09-10
fitness-role: Required check
type: FORK
category: Fork Management
applies-to:
  - Patch providers
  - Enterprise recipients
requirements:
  - id: FORK-003.REQ-001
    level: MUST
    text: Patch providers must tag the unpatched baseline source commit using
      v<VERSION>+patch.baseline.
    checkability: automated
    checks:
      - id: FORK-003.CHECK-001
        title: Baseline tag exists and resolves to a commit
        type: repository
        severity: blocking
        implementation: osera-fitness.fork003.baseline_tag
        evidence:
          - baseline_tag
          - baseline_commit

Source provenance

Source snapshot: Reconstructed from the source recorded at ratification; snapshot verification pending.

Historical source at 51e0afe · Source SHA-256: 1826bce1155f761364b3dc8ef7d246d0094bdc20f99e519b3d0083501ea13509.

Supporting guidance links point to the same historical Git revision; this prototype is not a self-contained release archive.