Eve library

V8-002 evidence pack — multi-process journal and HITL safety

Evidence

Revision 1

On this page

Work-package charter#

  • Task ID: V8-002
  • Owner: V8 Loom/Yemaya persistence and HITL maintainers; implementation owner: Elikem Agudogo
  • Accountable product: V8 Ariadne/Yemaya
  • Priority: P0
  • Target milestone: 2026-07-15 SOTA gap-closure program
  • Risk tier: Critical duplicate allocation, lost journal, stale-review, conflicting-edit, evidence-invalidation, and repeated-publication risk
  • Dependencies: @oshun/database, PostgreSQL advisory locks and constraints, StageJournal, the Loom HITL queue, case revision storage, authenticated V8 release reports, and mixed-lineage contracts
  • Affected schemas and content slots: Journal, HITL review, immutable case revision, evidence-ledger, and publication transaction schemas; no production case slot was migrated or released by this package
  • Rollout strategy: Fail closed without a configured durable database, transact allocation/review/revision/publication mutations under database locks, and retain the in-memory path only as an explicit offline adapter
  • Rollback strategy: Revert the five source increments and corresponding additive migrations in reverse order before deploying a prior service; never dual-run process-local and PostgreSQL allocators for one case namespace
  • Evidence-pack location: This file

Implementation and closure mapping#

The seven checked requirements are implemented by this source chain:

Commit Boundary
d430228c4eb9f95c0dd656e5f49d9de205987227 Store-owned atomic journal sequence/attempt allocation and restart-safe in-memory conformance
bb75ba13357740ad56ffec86bfeebaa8af0434f2 PostgreSQL journal allocation, constraints, replay, and fail-closed production composition
44df7eff1b7eabcaf4d113e569eb54ae7bb1adc0 Durable monotonic HITL IDs plus compare-and-set resolution
5f1368dc804923338ecae92cf0fcb3bf7451bcd5 Transactional edit-and-approve into immutable case revisions with five-class evidence invalidation
80078c9c6ebf1ba96ba20c07f51053444ee9e73c One edit/apply/reverify/sign/resume transaction with authenticated mixed lineage

The original live PostgreSQL evidence used independent pools, reconnects, concurrent writers/reviewers, real Ed25519 authentication, migration idempotency, and cleanup. It proved exact 1..60 journal sequences, restart at 61, unique HITL allocation across 0..59 and restart at 60, one-winner review races, immutable revisions, stale/conflicting edit rollback, all five evidence classes invalidated before re-verification, and signature-failure rollback without partial publication.

Current verification record#

The current refresh ran against source commit 649ae21ae3c44c9c8e259067674348e9ad51b205 on app-dev-server, Linux 6.8.0-134-generic x86_64, Node.js v24.15.0, pnpm 10.25.0, Git 2.43.0, TypeScript 6.0.3, and Vitest 4.1.7. No model/provider credential was used.

UTC interval Exit Command and result
2026-07-29T11:09:35.403Z–2026-07-29T11:10:20.676Z 0 pnpm --dir apps/v8/loom-service exec vitest run --config vitest.config.ts --maxWorkers=1 (41 passed, 3 environment-gated integration cases skipped); pnpm --dir libs/yemaya/case-pipeline exec vitest run --config vitest.config.ts --maxWorkers=1 (38/38); pnpm exec tsc --noEmit -p apps/v8/loom-service/tsconfig.json; pnpm exec tsc --noEmit -p libs/yemaya/case-pipeline/tsconfig.lib.json

The skipped cases are not substituted for the original live PostgreSQL proof; they are reported as skipped in this no-credential refresh. The current non-database suites still exercise restart, duplicate, stale-review, conflicting-edit, replay, invalidation, signature, and atomic rollback behavior.

Adversarial, artifact, and authority evidence#

  • Negative fixtures cover duplicate (case, seed, stage, attempt) and (case, seed, sequence) identities, two-client allocation races, stale expected revisions, conflicting edits, direct resolution of edit-and-approve, failed verification, mixed-lineage mismatch, and a corrupted release signature. Each must reject or roll back for the intended reason.
  • Unit, contract, persistence integration, migration, real-cryptography, and transaction/recovery coverage are applicable and retained. Browser/mobile, accessibility, media-quality, provider, performance, and Unreal automation are inapplicable to this backend persistence package.
  • Test reviewers and keys are fixtures, not human authority. No policy requires a signed human release decision to implement the transaction boundary, and no real reviewer approval or production publication is claimed.
  • No V8-002 implementation blocker remains. Production rollout and full case-release/canary evidence remain external V8-005 work and are not inferred from local PostgreSQL.
Current artifact SHA-256
libs/yemaya/case-contracts/src/journal.ts c8d9a9050485b39663bf04042cae4a59dc042710bf57f7310e67dfd150ed8edd
apps/v8/loom-service/src/postgres-journal-store.ts aa866efdbf5407d4631b6b31107e59f4e420133a7552a3a95392ea9f631dd3c0
apps/v8/loom-service/src/postgres-hitl-queue.ts 77ee5a8f644d959f5c34efe8274a48a596441eb812f1464005034c29967b6ad4
apps/v8/loom-service/src/postgres-case-review-store.ts a0702811220a81441d9b8716b87243dfccfc1de175c9461ac32775b749988437

The additive database definitions are versioned inside apps/v8/loom-service/src/journal-migration.ts as migrations 202607230001 through 202607230005. No screenshot, media probe, model/data license, or placed runtime artifact belongs to this boundary. The generated portfolio capability views do not model package-internal PostgreSQL operations; the completed-work-package admission verifier now derives and enforces this package's evidence linkage from the ledger.