Platform Continuation Status

Unit: lattice-platform-development Plan: LATTICE Platform Agentic Development Plan Review: Platform Continuation Review Updated: 2026-09-20 Working revision: b19e1e7192dbb04fca1894f01908e9a11d976a2f
Status: accepted after the first Surface control-plane implementation slice. Governing ADRs: ADR-A30, ADR-A32, ADR-A33

Purpose

This is the authoritative current state for the platform continuation unit. It is not a plan document. Design lives in solution-design-specification.md, data-architecture.md, and ux-design.md. What remains is verification of already-authored work, and that verification’s gaps are already documented. This file references them rather than re-deriving them:

Working Arrangement

Validation of implemented code follows the Agentic Development Contract. Work is validated by the human running the listed commands and reporting the result, not by the agent re-running build and test suites on its own initiative.

Evidence Recorded This Session

The following checks completed in this network-enabled environment, before the working arrangement above took effect:

Area Evidence Result
Toolchain mise-managed Java 21, Maven 3.9, Node 22, Python 3.11, Erlang 27, and Elixir 1.17 Passed
Root Python python -m unittest surface.test_surface mork_compilers.test_mork_compilers -v 76 tests passed
Workers python -m pytest workers/tests -q 38 tests passed
Java reactor mvn -f platform/pom.xml verify Passed
Frontend yarn check Passed
Compose PostgreSQL, RabbitMQ, Fuseki, and workspace services started Passed
PostgreSQL All five documented migrations applied. Host connection and expected tables verified Passed
RabbitMQ Host publish and consume smoke message Passed
Fuseki Base endpoint served. /$/server returned 401, consistent with its protected administration API Passed
Current API slice mise exec -- mvn -f platform/pom.xml -pl surface-workflow -am test Passed. 9 Surface workflow tests passed

The service smoke checks prove reachability. They do not prove the intended Java to RabbitMQ to Python worker flow, graph materialization, lifecycle persistence, release flow, or role authorization.

Worktree Boundary

Do not revert or remove changes outside a slice you are actively working on.

Verification Gaps

Sourced from the documents in Purpose. This is a pointer table, the documents linked are authoritative, not this summary.

Phase Handoff Remains unverified
0-1 phase-0-1-handoff.md Testcontainers integration, PostgreSQL-backed outbox persistence, end-to-end Java-to-RabbitMQ-to-Python retry test
2 phase-2-handoff.md HTTP endpoint, ledger and graph-family migrations against a live PostgreSQL, Playwright browsers, Studio E2E, Fuseki materialization, RabbitMQ retry/dead-letter/duplicate-delivery behavior
3 phase-3-handoff.md Maven/Java 21/Docker/ORAS/Cosign execution, registry push, signature verification, PostgreSQL ledger integration, RDF provenance publication, restore against a live registry
4 phase-4-handoff.md Python/Yarn/Playwright/RabbitMQ/Fuseki/compiler tests, yarn.lock regeneration and review
5 phase-5-handoff.md Python/Yarn/Playwright/RabbitMQ/graph-store integration commands
6 phase-6-handoff.md Python/Yarn/Playwright/PostgreSQL/RabbitMQ/graph-store integration commands

The current SurfaceRevisionApi slice postdates these handoffs and has only the regression gate below, no HTTP, persistence, or identity validation.

Commands to Run

Per the Agentic Development Contract, run these yourself and report the result back.

cd /Users/t4/work/lattice
mise exec -- mvn -f platform/pom.xml -pl surface-workflow -am test

Pass looks like: Tests run: 9, Failures: 0, Errors: 0, including SurfaceRevisionApiTest. This is a regression gate for the current slice only, it is not evidence against any row in the table above.

Reference Material