Status: zone-aware workspace publication runtime backlog

[mdheller]

Status snapshot

This issue captures the current workspace-control-plane / data-ingestion / cataloging / enrichment publication lane so the status is preserved in-repo.

Merged baseline:

• PR Thread zone metadata through Lampstand ingest artifacts #95: Lampstand now propagates zone_ref / topic_ref through ingest artifacts and emits a publication_request.
• PR Wire zone-aware Lampstand smoke into standard smoke path #96: zone-aware Lampstand smoke is wired into the standard smoke path.

Current main includes:

• zone-router publication planning
• semantic-bridge validation for EventEnvelope, MembraneDecision, ZonePublicationRequest, ZonePublicationPlan, and ZonePublicationRecord

Open / stacked work:

• PR Add retry policy and dead-letter handling for zone publication #388 adds retry policy and terminal-failure handling for zone publication.

Accomplished:

1. Zone-aware local ingest via Lampstand.
2. Zone metadata preserved through payload, envelope, receipt, and catalog entries.
3. Publication request generated from ingest results.
4. Zone-router planning from request to topic/plan.
5. Semantic validation membrane for request/plan/record artifacts.
6. Initial local transport, outcome, retry, and terminal-failure semantics designed in stacked runtime branches.

Remaining from original spec:

1. Real broker transport adapter, starting with Kafka-compatible publish.
2. Runtime dropzone/membrane enforcement.
3. Enrichment workers for classification, entity extraction, topic tagging, and memory-mesh writes.
4. Workspace control-plane visibility for publication jobs, retries, terminal failures, replay, quarantine, and promotion.
5. Full zone-to-zone broker topic taxonomy and replay paths.
6. CI flattening once the stacked runtime branches are accepted.

Recommended order:

1. Finish and flatten the publication runtime stack.
2. Add replay/requeue for terminal failures.
3. Add real Kafka-compatible transport.
4. Add dropzone/membrane runtime enforcement.
5. Add enrichment workers and memory-mesh integration.
6. Surface state in workspace control-plane APIs/UI.

Rule: avoid fighting concurrent agents. Verify main before each tranche and keep new work isolated until adjacent upstream changes are understood.