Skip to content

Add product requests, progress and an oldest-first operator queue #3937

Open
12 of 12 issues completed
Open

Description

@devantler

🤖 Generated by the Agentic Engineer

User Story

As a client, I want to request a product and see understandable progress, so that I know the next action. As the sole operator, I want eligible orders oldest first, so that I finish them one after another.

Acceptance Criteria

  • Implement free request submission followed by owner-approved project/quote, client acceptance of that exact agreement version and verified full payment before paid work. The accepted billing decision selects a Numina invoice by default, or supported Stripe card/MobilePay collection, with one path per order. Funding must bind the exact accepted version and amounts; browser returns, the retired manual credit ledger and irreversible-payment claims cannot authorize work. Retain the current website/app/service guides; the new consultancy guide is pending confirmation in Add consultancy as the fourth Devantler Tech offering #3980.
  • Validate the product and bounded brief on the server, persist a confirmation, and make retries idempotent so refresh/double-click does not create duplicate orders.
  • Keep one authoritative durable portal queue and a versioned API over the same server-side authorization used by the UI. business-site #20 adds a thin MCP adapter and least-privilege worker capabilities; neither it nor GitHub owns a second queue. GitHub issue/PR references are optional, allow-listed code-delivery evidence. Labels/comments/issue closure, tool arguments and agent assertions cannot set approval, agreement or payment facts. Absent/failed GitHub integration cannot create eligibility or erase intake; client briefs are untrusted data and private records never enter public artifacts.
  • Release eligibility only for current owner-approved scope, recorded agreement acceptance and independently verified full payment for the same order/version. Reject partial, authorized-only, mismatched, disputed, stale and unknown evidence; recheck before claims and execution checkpoints and pause on revoked authorization.
  • Keep free first-meeting entitlement and scheduled consultancy appointments distinct from the software-build queue (Add private iCloud-aware consultancy and first-meeting bookings #3981). A meeting, whether free or paid, cannot start a software order.
  • Store original server-assigned submission time plus a deterministic tie-break; neither clients nor status updates can reset queue priority.
  • Separate pending decisions/waiting-for-client/cancelled work from eligible work without hiding their history; show the operator why a request is not ready. A skipped or paused order keeps its original timestamp.
  • Atomically claim the oldest eligible order with one initial active software-order slot, expiring leases and fencing against stale workers. Concurrent sessions, restart, duplicate requests, expired claims and release/renewal retries cannot execute twice or publish after lease loss. An older request becoming eligible does not automatically preempt active work. Explicit audited operator pause/resume/override decisions preserve original order and never waive authorization.
  • Validate status transitions and optimistic concurrency; persist an append-only published timeline and separate operator-only notes. Clients cannot change delivery status or read another client's details.
  • Demonstrate free submission, durable portal intake, operator-approved quote, exact agreement acceptance, independently verified settled funding, atomic queue claim, sanitized progress, client review and verified delivery with two isolated customers and two competing workers. Include tied submission times, new eligibility without preemption, requote, cancellation/revocation, restart, duplicate/out-of-order mutations, stale fences and GitHub unavailability. Test the actual production-invoked policy; API-only controls pass before adding MCP.

Scope and prerequisites

The order/queue module belongs to the unified devantler-tech/business-site application and private /portal area. It shares #3936's server identity/session/data authorization; public page code or same-origin browser state does not grant customer, operator or worker authority. Preserve the root public frontend and never include private records in its static output or public cache.

The queue ownership decision and shared API/MCP boundary are recorded on #3935 and reconciled on #3934. business-site #20 owns the worker API, MCP adapter and reviewed client-work priority integration; this issue owns durable client/operator order policy, not a second executor. Preserve the initial invitation-only access for both private individuals and business customers, Danish-law launch controls in business-site #21, and separately authorized included-hosting maintenance. New features and larger iterations need a new agreement; covered maintenance is not a second paid feature order or arbitrary new scope.

Deliver the client/operator order slice separately from worker API/MCP integration. Use default-off enabled/false/unset controls and fail closed on missing broker/storage/authorization configuration. No paid work or public routing is enabled by an issue update, mock preview or merged foundation. #3939/#3940 retain deployment and verified handoff.

Size: M for the client/operator order slice. Depends on #3935's remaining implementation decision and #3936's verified identity/access slice. Do not expose other customers' identities or promise delivery dates inferred from queue position. Ordering software does not automatically authorize executing a customer's free-text brief.

Activity

  1. added theissue type on Oct 7, 2026
  2. added a commit that references this issue on Oct 9, 2026
  3. self-assigned this
    on Oct 9, 2026
  4. added a commit that references this issue on Oct 12, 2026
  5. added a commit that references this issue on Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Fields

Priority

None yet

Start date

None yet

Target date

None yet

Effort

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions