P010/P011 reference integration

The contract works before editorial content enters it.

B036 exercises the signed-package boundary with synthetic fixtures only. It proves failure handling, valid staging, lineage, and rollback planning without publishing an article or changing P010/P011’s queue.

Reference snapshots staged1
Publications created0
Real editorial records used0
Production signing keys0

Scenario evidence

Expected failures fail closed.

Each scenario records the expected and actual decision. The only staged record is explicitly synthetic, non-promotable, and excluded from the public publication registry.

DR-01

Malformed package

Expected: INVALID_PACKAGE

Actual decisionINVALID_PACKAGE
PASS
DR-02

Programme mismatch

Expected: PROGRAMME_MISMATCH

Actual decisionPROGRAMME_MISMATCH
PASS
DR-03

Untrusted signing identity

Expected: UNTRUSTED_SIGNER

Actual decisionUNTRUSTED_SIGNER
PASS
DR-04

Draft editorial record

Expected: RECORD_REJECTED / NOT_APPROVED

Actual decisionRECORD_REJECTED / NOT_APPROVED
PASS
DR-05

Eligible synthetic fixture

Expected: STAGE

Actual decisionQUARANTINE
PASS

Staged lineage

Every route can be traced backwards.

The reference snapshot demonstrates the lineage chain that an approved Engineering Journal export will use later. The canonical route is reserved in evidence only; it is not present in the public journal.

  1. 01/knowledge/reference-publication-fixture
  2. 02reference-p010-publication-001
  3. 03SNP-P010-REF-0001
  4. 04PKG-P010-REF-0001
  5. 05P010_P011 / REFERENCE-ONLY-001

Editorial boundary

Issue 003 stays in its queue.

This dry run does not alter, approve, schedule, or publish “Trust Before Intelligence” or any future issue. When P010/P011 produces an approved export and registers a production signing identity, P003 can process it through the proven contract without re-authoring its substance.

Integration architecture →Engineering Journal →Foundation baseline →