Skip to main content

V1 non-goals

These are product boundaries, not temporary documentation omissions:

  • universal exactly-once delivery across Kafka and Pulsar;
  • global ordering across all destinations or all tenants;
  • exact-time consumer visibility at deliverAt;
  • arbitrary per-message destination connection or credential configuration;
  • changing a message's destination Profile or payload through Reschedule;
  • online migration of an active message between destinations;
  • treating a local checkpoint upload as recovery authority before catalog publication;
  • transparent multi-cell failover beyond the one active recovery cell boundary;
  • making a native AUTO_FAST delivery queryable, cancellable, or reschedulable as a managed message;
  • treating V1 completion as automatic deployment approval for every environment;
  • treating later optimization, refactoring, or review work as permission to weaken the frozen V1 contract.

V1 completion closes the defined implementation and release gates; it does not turn these non-goals into implicit support.