AVAVERELI
CompanyProductsKnowledgeResearchDocumentationDevelopersSupportSearchCustomer portal

P010/P011 production export pack

One approved issue. One exact handoff.

B037 gives the knowledge-production programme a stable, machine-readable route into P003. It validates the package before transfer while leaving editorial approval, scheduling, and substance entirely with P010/P011.

Producer validationnpm run validate:p010-export -- <package.json>Preflight only · cryptographic trust verified by P003
02

Manifest template

Producer-safe starting structure with required fields.

Download JSON →
03

Error catalogue

Stable validation codes for automation and remediation.

Download JSON →
04

Validation command

Local structural and editorial preflight before handoff.

Built into contract
05

Handoff checklist

Shared evidence gate for P010/P011 and P003.

Built into contract

Handoff evidence

Seven controls before promotion.

A successful producer preflight does not publish anything. The shared gate continues through signing-key trust, P003 staging regression, accountable promotion approval, and a named rollback target.

HC-01
Editorial approval is final and attributable

Approval identifier and authority

P010/P011
HC-02
Public text and metadata are frozen for export

Source revision and SHA-256 hash

P010/P011
HC-03
Effective time and canonical slug are confirmed

ISO timestamp and slug

P010/P011
HC-04
Package passes producer validation command

Validation output

P010/P011
HC-05
Production signing key is registered

Key identifier and custody record

SHARED
HC-06
P003 staging snapshot passes platform regression

Snapshot and test report

P003
HC-07
Promotion and rollback authorities are named

Approval and rollback target

SHARED

Stable error contract

Machines reject consistently. People know what to fix.

Blocking errors stop handoff. A future effective date is a non-blocking warning: the package may enter scheduled staging, but promotion remains locked until the approved time.

EXP-001
INVALID ENVELOPE

Correct the manifest against the published JSON Schema.

BLOCK
EXP-002
WRONG PROGRAMME

Restore the authoritative P010/P011 programme identifier.

BLOCK
EXP-003
COUNT MISMATCH

Regenerate the manifest from the final export set.

BLOCK
EXP-004
TYPE NOT ALLOWED

Route the record through its owning programme contract.

BLOCK
EXP-005
NOT APPROVED

Keep it in the P010/P011 queue until accountable approval.

BLOCK
EXP-006
NOT PUBLIC

Do not export unless P010/P011 explicitly approves public visibility.

BLOCK
EXP-007
REFERENCE FIXTURE

Remove all referenceOnly or NEVER_PUBLISH fixtures.

BLOCK
EXP-008
UNREGISTERED KEY

Complete signing-key registration before handoff.

BLOCK
EXP-009
FUTURE EFFECTIVE

Handoff may proceed for staging; promotion must wait until effective time.

WARN

Issue 003 boundary

Ready to receive is not permission to publish.

P003 now provides the contract and tools. P010/P011 must still complete its queue, freeze the approved source revision, generate hashes, register the production signing identity, and submit the final package. P003 then stages and verifies it before an accountable promotion decision.

Reference evidence →Integration architecture →Engineering Journal →