OIC-GC-004 — VEIP dependency and interface dossier

[veraxis-protocol]

Owner

Arkadiy Miteiko (interim VEIP contract owner for Gate Closure v0.2). Claude Fable 5 may support implementation and dossier preparation but may not independently alter VEIP semantics or lifecycle commitments.

Required inputs

• OIC-OWNER-DECISION-002.
• Inventory of candidate VEIP repositories, versions, interfaces, licenses, fixtures, lifecycle behavior, and evidence.
• Warrant/execution-record boundary questions from OIC-GC-002.

Required outputs

• VEIP dependency and interface dossier.
• Immutable repository/version pin and interface inventory.
• Failure, lifecycle, security, provenance, licensing, and conformance-evidence gaps.
• Proposed OIC/VEIP responsibility boundary for owner review.

Acceptance criteria

• Every repository and artifact is provenance-recorded and hashable.
• Interface and lifecycle commitments are owner-approved or explicitly marked proposed/open.
• Missing conformance, security, licensing, and reproduction evidence is not softened.
• No adapter is implemented or executed.

Explicit non-goals

• No independent VEIP semantic changes by support actors.
• No VEIP adapter execution, envelope generation, admission, runtime decision, or gate opening.
• No license publication.

Dependencies

• Informs OIC-GC-002 and OIC-GC-008.
• Feeds OIC-GC-007.

Current gate impact

Required dependency evidence. Until owner-approved and consolidated, the semantic implementation gate remains BLOCKED.

[veraxis-protocol]

RECONCILIATION STATUS — 2026-08-17

Historical state:

• OIC-GC-004 was opened as the VEIP dependency and interface dossier item. PR veip: add dependency dossier preflight inventory #14 merged (86dcafd1472f2a5d8fe9cf4d47b5f0fa30eb02ab) supplying the dependency preflight inventory.
• PR veip: add dependency dossier preflight inventory #14 carried its own explicit ceiling: PREFLIGHT DEPENDENCY EVIDENCE — INCOMPLETE — NOT AN INTERFACE FREEZE. That ceiling is why this issue is not closable on veip: add dependency dossier preflight inventory #14, and it is preserved here rather than superseded.

Successor evidence (post-dates the original issue framing):

• Integration Slice 001 accumulated executable boundary evidence the original issue could not have referenced: currentness resolution, authority/admissibility, governed propagation across a real process boundary, reliance-time revalidation of both currentness and authority, correction handling, historical preservation, and execution-integrity discipline (single-use ordinals, digest-chained ordering, fail-closed refusal).
• PR Owner freeze: Integration Slice 001 RUN-003 claims #26 merged (549fa05dac5b36cf9f8c26c4d7c271e5a7d27c1f) freezing the RUN-003 claims, owner-freeze commit 831bf9e861bf2a1b3267617a85e29af37e4a9947, artifact SHA-256 79ae91418bdcbd4076a8e1dec28094a459cd3492293c831f28c62784d50be1f0.

What that evidence is, and is not, for this issue:

• It is not VEIP institutional validation, and is not cited as such.
• RUN-003 may be cited only within its frozen ceiling: internal technical demonstration of the supported properties, with the T-POS-04 propagation evidentiary limitation, synthetic authority and synthetic reliance throughout, and no institutional CDC reliance.
• Demonstrating that an OIC-side boundary behaves correctly under synthetic conditions says nothing about VEIPs responsibilities, lifecycle, or licensing.

Current status:

• OPEN — REBASELINED. Three strands are now distinguished:
  • A. Original VEIP repository/dependency inventory — supplied by PR veip: add dependency dossier preflight inventory #14 at preflight level; incomplete by its own statement.
  • B. Later OIC-side conceptual and execution-integrity boundary evidence — Integration Slice 001, internal technical assurance only.
  • C. What remains unestablished — everything in the closure conditions below.

Remaining closure conditions (all OPEN):

• Owner-attested VEIP/OIC responsibility boundary: which side owns currentness, authority, admissibility, correction and revocation, stated by both sides rather than assumed by one.
• VEIP version/release provenance, as applicable, at a pinned identity.
• Lifecycle commitments: support window, breaking-change policy, deprecation notice.
• Reliance / revocation / correction boundary: what VEIP undertakes when a relied-upon artifact is corrected or an authority is revoked.
• Currentness and authority ownership: which side is the system of record.
• Interface freeze status — currently not established; PR veip: add dependency dossier preflight inventory #14 explicitly disclaims it.
• Licensing and security gaps where still unresolved, coordinated with OIC-GC-008 — Licensing and dependency compatibility review #12.

Proposed successor acceptance test for #8:

#8 closes when a VEIP interface dossier exists at a pinned VEIP identity and states, in the dossier itself: (1) the responsibility boundary for currentness, authority, admissibility, correction and revocation; (2) lifecycle and breaking-change commitments; (3) the interface-freeze status with its evidence; (4) licensing and security posture; and (5) an explicit statement of what VEIP does not undertake. Acceptance requires the dossier to be attested by an owner on the VEIP side, not inferred from OIC-side observation. OIC-side execution evidence, including RUN-003, may support (1) but cannot satisfy it alone.

Claim ceiling:

• Nothing in this reconciliation establishes VEIP institutional validation, an interface freeze, production readiness, or any CDC authority or reliance.