Pergamum Pulse

PREP — Pergamum Requirement Execution Publisher

1. Responsibility

PREP is the Pergamum-side publisher of the Requirement Execution Package defined by FOGE-REC.

The constitutional flow is:

Pergamum Pulse governed requirement semantics
        ↓
PREP
  validates publication prerequisites and freezes the package
        ↓
ARTIF-ADENGINE-REQUIREMENT-EXECUTION-PACKAGE
        ↓
comp.PREP.OUTPUT.REQUIREMENT-EXECUTION-PACKAGE.v0_2
        ↓
FOGE

PREP does not reinterpret source law, methodology, standards, admitted PP-MAP objects, PP-MD decisions, or rights outcomes. It publishes the governed transfer artifact that carries those already-governed semantics into FOGE.

PREP MUST NOT infer that requirement semantics are governed merely because a Pergamum object/version exists, resolves, was extracted successfully, or has HECATE structural/conformance evidence. Before publication, every exact requirement object/version entering the package MUST resolve through canonical Pergamum governance evidence. HECATE may prove conformance in that evidence chain, but governance/admission authority remains a separate PP/TrustGate decision.

2. Artifact contract

PREP produces:

• artifact type: ARTIF-ADENGINE-REQUIREMENT-EXECUTION-PACKAGE;
• runtime identifier type: ARTID;
• owning specification: FOGE-REC;
• replay mode: RECORDED;
• canonical payload schema: https://schemas.zayaz.io/foge/requirement-execution-package/0.2.0/requirement-execution-package.schema.json.

A package version is immutable after publication. A semantic change requires a new package version and fresh governed publication evidence.

2.1 Replay governance

The package output is governed by TG-RP as RECORDED. Replay SHALL NOT regenerate a historical Requirement Execution Package from current Pergamum state. It verifies the recorded immutable artifact and its original lineage.

For comp.PREP.OUTPUT.REQUIREMENT-EXECUTION-PACKAGE.v0_2, the replay manifest SHALL pin at minimum:

• the exact package ARTID and package version;
• the recorded package artifact hash / canonical package digest;
• the PREP engine CMI and configuration snapshot that governed publication;
• the exact authoritative-basis and selected-requirement provenance lineage needed to resolve the package inputs;
• the canonical admission/governance receipt for every exact requirement object/version frozen into the package, including the HECATE/TrustGate evidence chain used at publication time; and
• the original governed publication evidence/receipt required to establish that these were the bytes actually published.

The RECORDED pass criterion is integrity equality between the anchored recorded package and the referenced package plus complete resolution of the recorded input lineage. The artifact is anchored at creation/publication time, not reconstructed at replay time.

3. Canonical CSI transport contract

The canonical transport definition for the v0.2 package is:

Property	Governed value
CSI	comp.PREP.OUTPUT.REQUIREMENT-EXECUTION-PACKAGE.v0_2
Producer	PREP
Consumer	FOGE
Direction	PREP output → FOGE input
Artifact type	ARTIF-ADENGINE-REQUIREMENT-EXECUTION-PACKAGE
Identifier type	ARTID
Payload schema	https://schemas.zayaz.io/foge/requirement-execution-package/0.2.0/requirement-execution-package.schema.json
Lifecycle	published, immutable-version, version-pinned
Replay	RECORDED
Compatibility	exact v0.2 payload semantics; a breaking payload change requires a new governed CSI version

The CSI transports the package; it does not grant compilation authority. FOGE SHALL still run the complete FOGE-REC compilation-authority gate against the exact package instance and fresh evidence context.

Unknown, aliased, inferred, or locally substituted CSI values are non-authoritative.

4. Publication prerequisites

PREP may publish a Requirement Execution Package only when the package:

1. conforms to the registered FOGE-REC schema;
2. resolves to the registered artifact type and ARTID identity contract;
3. carries an exact canonical digest over the digest-excluded package projection;
4. preserves authoritative Pergamum object/version lineage;
5. proves, for every exact requirement object/version included in the package, canonical PP admission through trusted governance evidence bound to the exact requirement semantics;
6. proves publication-time currentness for every admitted requirement version, including non-revoked, non-superseded and non-invalidated state;
7. carries the HECATE conformance evidence required by the requirement object's governing specification without treating HECATE as admission authority;
8. carries or resolves the appropriate TrustGate/PP governance evidence establishing requirement admission/current authority for that object class;
9. preserves applicability, Data Need, satisfaction, alternative-pathway, evidence, derivation, estimation, reuse and supersession semantics; and
10. is backed by the governed publication and rights evidence required by the owning specifications.

PREP publication does not imply that a later FOGE compilation is authorized. Admission is a durable historical fact about an exact immutable requirement version; currentness is a use-time fact. A later FOGE compilation MUST freshly resolve that the admitted requirement version is still current, non-revoked, non-superseded and non-invalidated for that compilation time. Historical replay MAY prove the recorded admission/governance state that existed at the historical publication time without requiring the version to remain current today.