Skip to content

Deliver the unified Devantler Tech site and client portal #3934

Open
5 of 16 issues completed
Open

Description

@devantler

🤖 Generated by the Agentic Engineer

User Story

As a Devantler Tech client, I want one private place to request products and follow delivery, so that I know what happens next without chasing updates. As the sole operator, I need an oldest-first work queue that supports finishing one order before starting another.

Motivation and evidence

The maintainer requested a cloud-native client portal on 7 October 2026: familiar-provider login, contact details, product ordering, progress visibility, an oldest-order-first operator queue, the existing website theme, and a website handoff only after the portal is completely finished. The business has limited weekly capacity and does not offer urgent or on-call delivery. No customer-demand metrics are available; this is a maintainer-directed capability, not a claim of market validation.

Proposed Solution

Unified site and portal — maintainer decision, 9 October 2026

One product and source repository: devantler-tech/business-site. Keep the working root Astro + Starlight frontend rather than performing a speculative rewrite. Add the selected Go identity/application boundary under server/, sharing public design tokens/assets instead of maintaining another visual clone. The intended deployed artifact serves built public pages and private /portal routes behind one canonical site entry point; one restricted PostgreSQL store owns customer records and sessions. Shared origin/source never makes private records, login attempts or API responses part of the public static build, caches, preview artifact or publication receipt.

The current GitHub Pages deployment remains the public website until a reviewed combined runtime has actual provider, isolation, recovery and EN/DA visitor proof. Pages alone cannot run the private portal server. #3939 must define protected cutover, immutable combined-source/runtime receipt and rollback; #3940 remains a separate, held activation change. This decision neither changes DNS/production routing nor activates customer intake, payments or worker access. #4019 still owns measured frontend evaluation and incremental standardization.

Our own customized client portal is part of the public devantler-tech/business-site source repository and the unified Devantler Tech site. The maintainer's 9 October consolidation direction supersedes the separate application/repository requirement. Public pages and a /portal area share the established English/Danish navigation, green/charcoal appearance, local typefaces and System/Light/Dark settings. Customer identity remains separate from infrastructure/operator access. Each customer sees only their own contact record, requests and deliberately published progress; operator notes stay private.

The portal owns the business workflow and its durable work queue; GitHub is an optional code-delivery reference, not a second order system. Preserve the approval → agreement → payment gate. A submitted request is intake, not permission to build: only the operator can accept a project and issue its quote. The client accepts the exact agreement/quote version before payment is enabled. Agents may start paid software work only after the full agreed upfront amount is verified against that version and the order is eligible in the queue. Free request submission and the explicitly entitled first introductory meeting below do not authorize implementation. The accepted billing decision selects one collection path per order: a Numina invoice by default, or Stripe card/MobilePay where supported. Funding is verified server-side for the exact accepted order/version; the retired manual invoice and bank-credit ledgers are not release evidence.

Confirmed first-release decisions: our own customized portal with public application source; invited private individuals and business customers; a dedicated customer Dex and self-hosted ZITADEL for invited local accounts under business-site #302, with social providers deferred; the Numina-first billing decision, with Stripe as the card gateway. Integrate the broker once rather than implementing individual provider SDKs. #3935 records the remaining implementation/session/storage/license and operating-footprint decisions. Propose paid services with their complete costs before any enrollment; no additional paid budget, provider enrollment, customer agreement execution or new agent repository privilege is authorized by this issue. Real payment activation remains a separate verified launch step under the accepted billing decision. business-site #21 owns the applicable Danish-law launch controls, including consumer flows; invitation-only does not make the portal B2B-only.

Controlled delivery workflow

Request received → operator assessment → operator-approved project and issued quote → client acceptance of that agreement/quote version → verified payment → eligible oldest-first queue → claimed work → reviewed delivery.

Rejected, expired, unpaid, cancelled and on-hold requests remain visible but cannot authorize work. Additional scope or hosting costs require a new agreed quote; an old acceptance/payment cannot silently fund changed scope. Already-active work is not preempted when an older request becomes eligible.

Portal-owned API queue and agent authority

Decision: the portal's restricted durable store owns orders, agreement/approval/payment facts, eligibility, original submission order, claims and deliberately published progress. One application authorization service governs the client/operator UI and a versioned API. A thin MCP adapter calls that service or the API through an explicit authenticated boundary; it owns no second queue, policy or customer store. business-site #20 carries implementation, protocol and Agentic Engineer integration.

A private client-orders repository is not a required work inbox. The already prepared repository is not deleted or repurposed by this decision. Optional allow-listed GitHub issue/PR references can aid code delivery, but delayed, failed or absent GitHub integration cannot create eligibility, advance an order, reset its priority or prevent the portal from recording its business state. Public application source and public code-delivery evidence contain no client brief, contact detail, agreement, payment evidence, internal note or raw agent log.

Clients submit bounded requests and read only their own approved records. Only the operator approves scope and generated versioned quotes and makes audited pause/override decisions. Funding comes from the accepted authenticated Numina or Stripe collection path. Agents have separate least-privilege identities: list eligible work, inspect only a sanitized authorized brief, atomically claim/renew/release it and submit safe progress/delivery evidence. They receive no customer or operator session and cannot approve scope, accept an agreement, mark funds credited or grant themselves execution privileges.

New paid work requires current approval, client acceptance of the exact agreement version and independently verified settled funding from that order's one accepted collection path for the same order/version. Browser returns, issue labels/edits, customer text, MCP tool arguments and agent assertions cannot set those facts. Included hosting maintenance follows its separate explicit operator-authorized monthly scope; it is not a fresh paid feature order or blanket authority for arbitrary client requests.

Persist original server-assigned submission time and stable tie-breaks. Claim the oldest eligible order atomically with one initial active software-order slot, expiring leases and fencing against stale workers. A newly eligible older request does not automatically preempt already active work. Every execution checkpoint revalidates scope, authority and lease. Cancellation, revoked authority, disputed/unknown funds or lease loss prevents further execution/publication until resolved. Customer-facing completion requires reviewed/merged code where applicable and verified usable delivery, not merely issue closure or an agent success message.

Integration must prioritize agreed eligible client work before discretionary internal enhancement while retaining urgent incident/security duties and reviewed trust, privacy, merge, spend and repository-access boundaries. Define and test the service-class/capacity policy under business-site #20 rather than silently widening the engineer's definition. No client text is an instruction to alter those boundaries. Do not invent response times, deadlines or 24/7 availability.

Payment finality: a decision, not a boolean promise

The maintainer wants payment completed before work and protection against reversal. A successful card payment is not irreversible: Stripe documents that a formal dispute reverses the payment. Even SEPA credit transfers have return/recall mechanisms; that source does not determine Danish domestic-transfer rules.

The accepted billing decision is authoritative: Numina invoices are the default; Stripe Checkout or subscription invoices collect supported card payments, and MobilePay is single-use only. An order has one collection path. Numina funding requires a matched paid invoice with nothing outstanding; Stripe funding requires authenticated, signature-verified success evidence for the exact order or billing period. Browser returns and manual credit assertions cannot release work. Preserve amount, currency, accepted-version, reversal and dispute checks. This is not an absolute-finality guarantee or authorization to activate real paid orders. Preserve applicable cancellation/refund obligations; do not advertise “irreversible” or “no refunds.” The chosen agreement/acceptance mechanism and terms need appropriate review before real paid orders.

Fourth offering: consultancy and calendar booking

Consultancy covers GitHub, Agentic Engineering, Platform Engineering, Software Engineering and client engagement. The public offering is tracked in #3980 and the iCloud-aware booking feature in #3981. Paid consultancy uses an operator-approved fixed quote; no hourly rate is approved. Introductory duration, full-day definition and final booking rules must be explicitly configured and confirmed under #3981. Personal compensation information is not part of the public product specification.

All portal request submissions are free. A new client's first introductory meeting is also free, as a narrowly server-authorized meeting type, not unpaid project delivery. Paid consultancy retains operator approval, the exact accepted agreement and verified payment requirements; agents cannot convert paid work into the free meeting entitlement.

Bookable weekday windows are 16:30–19:00 Europe/Copenhagen, subject to iCloud busy intervals, buffers and configured operator capacity. Full-day dates/hours are opened by the operator and agreed explicitly, not inferred from any empty weekday. Calendar data remains private; customers see available slots only. Calendar authorization is performed by the maintainer privately during setup. The operator's appointments are distinct from the oldest-first software-build queue.

Acceptance Criteria

  • Finalize the remaining implementation/session/storage/license and measured operating-footprint decisions under Decide the client portal implementation and first-release boundaries #3935/Deploy and verify the unified business site and private portal #3939. Preserve the confirmed public custom application, invitation-only consumer/business access, single federated broker, portal-owned API queue and accepted Numina-first/Stripe collection policy. Requests are not purchases or execution authority; paid proposals need approval before enrollment.
  • Implement the portal within the existing public devantler-tech/business-site repository, with one maintenance/CI contract and a combined deployable site artifact. Public source does not expose private customer data. Do not create a replacement portal repository or a second competing publisher; Add private client sign-in and contact onboarding #3936 establishes the server module and Deploy and verify the unified business site and private portal #3939 owns the reviewed unified runtime.
  • Prove actual provider login, logout and required contact onboarding; authorization is server-enforced and identities are not silently merged by matching email.
  • Customers can choose a supported offering, send a brief, see a durable confirmation and follow their own order's clear status history.
  • Only the authenticated operator can accept/reject projects, issue versioned quotes and release or pause work. Quotes show scope, amount/currency, any hosting charges, validity and the agreement terms; record client acceptance of the exact immutable version before enabling its payment route.
  • Gate work on current operator approval, recorded agreement acceptance and independently verified full payment for the same order/quote version. Pending/authorized-only, partial, mismatched, disputed or unknown payments never release work. New scope needs new approval/agreement/payment reconciliation, not automatic reuse of old clearance.
  • Payment proof comes from the authenticated server-side Numina/Stripe collection path in ADR 0030, not a browser success URL, customer screenshot, manual credit assertion, issue label or agent assertion. Test authenticated webhooks where used, replay/duplicate/out-of-order delivery, amount/currency/order/version matching, refunds/disputes and reconciliation outages.
  • Persist one authoritative portal queue, with shared server-enforced UI/API/MCP authorization, scoped idempotency and concurrency controls. MCP is a thin adapter, not a second policy/store. Optional GitHub delivery references are authenticated, allow-listed and idempotent; absent/delayed/failed synchronization cannot change approval, agreement, payment, eligibility or original order. Private client data never reaches public artifacts or another customer.
  • Prove that clients and agents cannot impersonate the operator, change quote/payment/approval facts or start work through crafted issue content. Claims and execution checkpoints fail closed on stale/revoked/unknown authorization.
  • The operator's eligible-work queue retains server-assigned original submission order with a stable tie-break; starting work is atomic and prevents duplicate or simultaneous active claims. Waiting/cancelled orders are explicit, not silently reordered.
  • Offer consultancy as the fourth product in the site and portal, covering all five specified areas. Prove free request submission, one eligible free introductory meeting and paid consultancy with private iCloud-aware booking under Add consultancy as the fourth Devantler Tech offering #3980/Add private iCloud-aware consultancy and first-meeting bookings #3981; booking cannot bypass software-work gates.
  • English/Danish, mobile, keyboard and all appearance modes match the public site; no invented customers, progress percentages or delivery deadlines.
  • Customer data, backups and retention have a documented, tested lifecycle; publish confirmed controller/contact and processing information before real customer data collection. Publish verified company and contact details from business-site #3917 records unavailable company/contact facts and remains open.
  • Validate both rollout states, access isolation, durable restart behavior, migrations, recovery and operational limits; merge reviewed changes without bypass and prove the actual live portal.
  • Only then route relevant public-site product/inquiry links to the verified portal, preserving informational pages, prices and a recovery contact path.

Success signal and guardrails

Release proxy: two isolated synthetic customers and the operator complete the real sign-in → contact → durable portal intake → operator approval/quote → recorded agreement acceptance → verified payment → eligible queue → agent work → published progress → verified delivery path. Include negative cross-customer/operator-access probes, unpaid/rejected requests, changed/expired quotes, duplicate events, competing claims and revoked authorization. Use sandbox/synthetic payment evidence until live paid orders are explicitly enabled; sandbox success is not proof of live settlement. Record the deployed revision and sanitized proof. After the first genuine order, evaluate whether the client and operator can identify the next action without assistance; do not invent adoption numbers.

Preserve the current approved VAT-inclusive website/app/service price guides and corresponding net revenue floors in business-site #154; do not add VAT again or reduce those floors. Additional scope/costs need an agreed quote. The accepted billing decision governs quote-gated Numina/Stripe collection. This plan authorizes no additional paid-service enrollment, urgent-support promise or private-address publication. Real billing activation retains the separate legal, credential, reconciliation and live verification gates.

Alternatives Considered

ERPNext supplies customer project/task visibility but its official container architecture introduces a broader multi-service ERP. Invoice Ninja supplies quotes, invoices and contact management; its documented portal does not establish the requested provider sign-in and sequential order queue. The maintainer has selected our own customized portal, reusing maintained identity/session/database components rather than adopting either complete portal. Exact component/version and operating-footprint decisions remain under #3935; the API-owned queue decision does not claim those are finished.

Delivery

Size: L overall; decompose into decisions, identity/privacy, durable portal intake/API, operator quotes/agreements, payment reconciliation and execution authorization, order/queue, themed experience, platform operation, and verified public handoff. Related business theme: #3896. Final customer-facing publication is the terminal milestone; issue creation or a working mockup is not delivery.

Activity

  1. added theissue type on Oct 7, 2026
  2. devantler commented on Oct 7, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    The maintainer has now fixed the repository name: devantler-tech/client-portal, an application repository of its own, with a dedicated platform tenant and portfolio application entry. The business website is separately named devantler-tech/business-site. Repository naming is resolved; the existing questions about portal visibility, identity providers, order/quote semantics, signup and spending limits remain unanswered and must not be replaced by assumed approval.

  3. devantler commented on Oct 8, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Maintainer-confirmed first-release choices from this interactive chat:

    • Application source: public in devantler-tech/client-portal. Customer records, agreements, payment evidence and the GitHub work inbox remain private.
    • Sign-in: Google and Microsoft, with provider setup completed privately and no paid enrollment authorized.
    • Payment: invoice and operator-confirmed bank transfer. Release requires an audited confirmation of actual credited funds for the exact accepted quote version, never a customer browser confirmation. This is not an irreversible-payment or no-refunds promise.
    • Access: invitation-only initially, while the complete workflow is verified.
    • Approved-work destination: a separate private devantler-tech/client-orders repository. Created and read back as private, empty, with automatic Copilot review disabled; no customer record, payment evidence, member grant or credential was added.

    These choices supersede the provisional visibility/provider/payment/signup/destination wording above. The operating budget remains unanswered: no new paid subscription, chargeable hosting, provider enrollment or financial commitment is authorized. A plain-language clarification is pending in this chat. No real authentication, payment collection, agent privileges or production website portal link is enabled.

  4. devantler commented on Oct 8, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    The maintainer's additional architecture requirement is confirmed: the portal will integrate once with a federated OpenID Connect identity service such as Dex. Google and Microsoft are connectors in that service, not separate provider implementations in the portal. Invitations, customer authorization and application sessions remain the portal's responsibility. Existing platform federation is a candidate for reuse after reviewed connector and client setup; this is not a claim that Google/Microsoft sign-in is already connected.

    The requested public application repository, devantler-tech/client-portal, and private work inbox, devantler-tech/client-orders, are prepared and empty. No customer information, credential, real authentication, payment collection or production portal routing has been added. Hosting and operating-budget approval are still unanswered; no paid enrollment or service commitment is authorized.

    A throwaway, mock-only workflow prototype is captured outside main at signed commit 77bbbcb112e38d31681cee3b41fd6bcdffb80095. It provides three guided scenarios for releasing an accepted and funded order, avoiding interruption of active work, and requiring new acceptance/funds after requoting. Actual served-local browser interaction verified those scenarios and native keyboard switching; retained model controls pass. The inline portable module parses, but a file-protocol browser visit was blocked by browser policy and not bypassed. Role switching and funds confirmation are simulations, not real authentication or payment verification.

    This captures the agreed design question and choices; it does not deliver the production portal or close this issue.

  5. devantler commented on Oct 9, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Maintainer-confirmed maintenance policy: every client project hosted on his platform includes optimization, accessibility improvements, bug fixes and routine upkeep in the agreed monthly price. New features and larger iterations require a new agreement. Routine included maintenance must not be treated as a new paid feature order requiring another quote, acceptance and bank transfer. The existing exact-quote/payment gate remains mandatory for newly quoted project or feature work; this clarification does not grant new agent execution privileges or disable approval controls.

    The service positioning uses modern engineering practices, self-healing and highly customized agents for automated incident fixes/recovery in supported scenarios. Nikolai is not personally available 24/7. Identify human-escalation cases and verify actual recovery coverage; do not promise resolution of every incident, response times or an SLA without evidence and agreement.

    The loopback-only English/Danish portal prototype now shows these terms and labels its quote/payment simulation as separately quoted work, not included maintenance. It performs no real monitoring, maintenance, recovery, authentication or payments. The public application repository is still empty; this is local preview progress and requirements clarification, not merged or production portal delivery.

  6. added a commit that references this issue on Oct 9, 2026
  7. self-assigned this
    on Oct 9, 2026
  8. added a commit that references this issue on Oct 9, 2026
  9. changed the title [-]Deliver a Devantler Tech client portal with an oldest-first queue[/-] [+]Deliver the unified Devantler Tech site and client portal[/+] on Oct 9, 2026
  10. devantler commented on Oct 17, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer (interactive Claude Code session)

    Strategy review of devantler-tech/business-site, 2026-10-17

    Where the product is. The fastest-moving product in the portfolio: about 40 commits in four days across three surfaces — the Astro site that serves devantler.tech today, the SvelteKit candidate in web/ (visitor parity done in devantler-tech/business-site#130, still behind the release gate in devantler-tech/business-site#125), and the Go portal in server/. The roadmap under this epic, #3896, #4222 and #4244 is current and well stocked (31 open issues), so this review adds one refined issue and three recommendations rather than new themes.

    Recommendations, in order:

    1. Finish the frontend cut-over before adding Astro-only work. Until Review and retire the Svelte frontend release gate business-site#125 is decided, every visitor-facing change needs parity in two frontends. Prefer closing the gate (or recording why not yet) over new features on the Astro side.
    2. Treat release-flag retirement as part of deployment verification (Deploy and verify the unified business site and private portal #3939), not ten separate pulls. Ten open chores each retire one flag or gate (Retire the temporary portal identity release flag after rollout business-site#34, Retire the temporary project-request release flag after verified rollout business-site#57, Review and retire the operator-inbox release flag business-site#62, Review and retire the private draft-proposal release flag business-site#65, Review and retire the private proposal-sharing release flag business-site#78, Review and retire the broker contact-verification release flag business-site#93, Review the client proposal acceptance release gate business-site#106, Retire the superseded private invoice-record module business-site#117, Retire the superseded bank-credit evidence module business-site#120, Review and retire the Svelte frontend release gate business-site#125). Each is small; together they are the standing cost of flag-first delivery, and most of them become actionable at the same point, once the deployment is verified.
    3. Design portal publishing (Publish verified tenant deployment artifacts for portal staging business-site#102) so dependency updates publish too. The public site publishes on every push to main, so it has no release gap. A tag-driven image pipeline for the portal would: other portfolio sites found that dependency-only commits never cut a release, so their updates waited until an unrelated fix shipped them. Decide at design time which commits publish the portal.

    Refined and ready to pull: devantler-tech/business-site#165, one declared Node line for the website. Every workflow pins Node 24 by hand, web/ requires ^24, and its @types/node moved to 26 (devantler-tech/business-site#136), so type-checking accepts APIs the build does not have.

    Upstream release review (key dependencies):

    Dependency Here What it means
    Astro / Starlight 7.3.8 / 0.42.6 Current, with patch updates landing within days. No action.
    SvelteKit / Svelte / Vite (web/) 3.x / 5.x / 8.x Same majors as the rest of the portfolio's SvelteKit sites. No action.
    TypeScript (web/) 6.0.3; 7.0.2 offered in devantler-tech/business-site#135 Held by devantler-tech/business-site#137 until the Svelte tooling supports 7. The open Dependabot PR should be parked against that blocker or closed with the reason, not left to age.
    Node 24 everywhere Node 26 is due to become LTS this month on the Node.js schedule; Node 24 is supported until April 2028. devantler-tech/business-site#165 makes the eventual move one change.
    Go (server/) 1.27.2 Current. The portal image is distroless and digest-pinned. No action.

    Card drift to fix later: the business-site product card says its roadmap epics live in the business-site repository, but they live here in the monorepo. The card should say so.

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

Type

Fields

No fields configured for Epic.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions