Project Direction

Monque development is usage-driven. The directions below are intentionally unversioned and do not commit to a delivery timeline.

Direction

Management Ecosystem

Keep management APIs framework-neutral while adapters handle host-framework mounting.

• Maintain OpenAPI as the stable third-party contract
• Keep host-owned authentication and action-grained authorization
• Add framework adapters only when there is clear demand

Dashboard

A bundled operator UI for inspecting Queue Views and operating existing Jobs through the Management Surface.

• Ship as an asset/UI package that can be served by framework-specific adapters
• Use the same REST-shaped Management routes as HTTP clients with first-party oRPC typing
• Start with polling and existing Job actions
• Defer realtime updates, Job creation, and visibility filtering until core APIs support them

Orchestration And Pipelines

Higher-level primitives for coordinating multi-step work when the core model is ready.

• Code-first orchestration for related Jobs
• Declarative pipeline definitions where configuration is a better fit
• Lifecycle visibility through core events and Management surfaces

Operational Scale

Large-deployment controls that need careful core, API, and operator-design work.

• Namespace-aware or multi-tenant operations
• Rate limits, priority controls, and operational policy hooks
• Standalone Dashboard server or Docker packaging after the bundled Dashboard and serving adapters exist