Repository navigation
Description
🤖 Generated by the Agentic Engineer
User Story
As a client, I want to book a free first meeting or agreed paid consultancy at a genuinely available time, so that I can get focused advice. As the sole operator, I want iCloud-aware booking and control over accepted engagements, so that bookings do not conflict with my schedule or authorize unpaid work.
Motivation and scope
Future consultancy covers GitHub, Agentic Engineering, Platform Engineering, Software Engineering and client engagement. The published public catalogue uses Other requests / Andre opgaver as its fourth, unpriced offering (business-site#457); this case-by-case enquiry route supersedes the separate public-card proposal in #3980. This issue retains the private booking capability below, with public activation still dependent on #3940. Bookable weekday windows are 16:30–19:00 in Europe/Copenhagen. Full days are possible by agreement; the operator explicitly opens their dates and hours. A free calendar gap alone does not grant availability, and the window is not a promise to fill every evening. Configure a weekly capacity limit before activation, consistent with the business's limited operator time unless the owner changes it.
The new client's first introductory meeting is free. Every portal request submission is also free. These narrow free paths do not exempt paid consultancy or software implementation from operator approval, the accepted agreement and verified full payment in #3934.
Proposed Solution
Reuse maintained booking/calendar components where their licensing, cloud-native deployment, iCloud integration and integration footprint fit the portal. Apple documents supported third-party calendar authorization and an app-specific-password alternative. Choose and test the actual adapter before claiming compatibility; an iCloud login is distinct from the clients' sign-in providers.
Keep the operator calendar private: compute busy intervals server-side from explicitly selected calendars. Clients and agents receive only the available slots they need, never private event names, descriptions, locations, attendees or employer/customer details. Do not publish a public calendar feed as the integration. The maintainer performs calendar authorization/secret setup privately; do not ask for Apple credentials in chat, change shared credentials or create a paid account.
Write confirmed bookings to a dedicated consultancy calendar without modifying unrelated events. The portal stores durable appointment state and reconciliation evidence. Coordinate local interval reservations, fresh calendar checks, payment state and idempotent event creation; do not pretend the portal and iCloud share one atomic transaction.
Acceptance Criteria
- Decide reuse/build, the maintained iCloud adapter, the approved operating cost and connection/revocation lifecycle. Prove actual private iCloud integration before customer activation; mocked calendar tests are not live proof.
- Configure Europe/Copenhagen weekday windows 16:30–19:00, meeting durations, lead time, buffers, holidays and weekly capacity. Sessions must end within the allowed window. Full-day slots require explicit operator-opened dates/hours and a confirmed day definition, not an inference from empty calendars.
- Preserve recurring/all-day busy events and timezone/DST semantics. Expose only available slots; test that neither another customer nor an agent can read private calendar details.
- Make slot selection a durable, server-enforced reservation with an explicit expiry and final conflict recheck. Concurrent requests cannot both claim an overlapping interval. Unknown, stale or unavailable calendar state cannot confirm a new booking.
- Provide one server-authorized free introductory meeting per new client, with clear duration and audited eligibility; clients cannot manufacture additional free entitlement by changing a request, product ID or identity provider. Do not silently merge identities by email.
- Let clients submit all product/consultancy requests without a fee or automatic commitment. Free intro/intake does not open a paid project or authorize implementation.
- Keep the operator in control of accepted consultancy, fixed-quote scope/price/duration and agreement version. Paid appointments require recorded acceptance, independently verified full funding and the original durable confirmation's sender-acceptance evidence for that version before final confirmation/delivery. Prepared mail, sender acceptance and actual inbox receipt are distinct; reuse the shared service-start policy rather than duplicate funding or mail queries.
- Reconcile expired reservations, late/duplicate payment events, iCloud creation failures and external calendar edits. Never confirm a conflicting appointment or charge a second time on retry; surface a clear operator resolution path for rescheduling/refund decisions without an agent moving money.
- Cancel/reschedule only the appointment's own calendar event, preserve an audit history, apply the agreed policy and notify the client clearly. Refund/dispute/cancellation prevents further paid delivery pending operator resolution.
- Show consultancy appointments on the operator's schedule and clients' own histories, separately from the software-build FIFO queue. Booking a meeting cannot advance or claim a software order.
- Deliver the same EN/DA, mobile, keyboard and System/Light/Dark experience as the site, with honest unavailable/pending/payment/confirmed states.
- Exercise two isolated synthetic clients through free-intro and paid-appointment paths, including duplicates, overlap races, DST, provider outage, rejection, quote changes, missed payment, cancellation, restart and recovery. Publish no real schedule/client data in test evidence.
- Merge reviewed implementation in both rollout states, prove the deployed booking and real calendar effects, then activate the public booking route through Activate the verified portal within the unified business site #3940. Do not close on issue creation or a visual prototype.
Delivery and outstanding decisions
This booking programme continues the human-selected work to complete the business site and portal under #3934. The maintainer approved the operating policy in a native interactive reply on 16 November 2026: a 30-minute free introduction; paid duration fixed by the approved quote; 150 booked minutes per Copenhagen week; 15-minute before/after buffers; 24-hour lead time; starts every 15 minutes; a 30-day booking horizon; 10-minute reservation holds; client cancellation/rescheduling until 24 hours before, with later changes handled by the operator and no automatic fee or loss of the free introduction. Preserve weekday 16:30–19:00 windows and full-day dates/hours opened explicitly by the operator. Fixed quotes remain mandatory, with no hourly rate. These approved values still need explicit configuration and source/live acceptance; approval does not activate booking, authorize a real payment or provide calendar credentials. #3917 continues to track unavailable business/contact facts; no customer facts or compliance claims are invented here.
The native child hierarchy records sequential source delivery, with one booking child active at a time:
- business-site#656: default-off policy and private interval availability.
- business-site#657: durable interval reservations, one free introduction per stable client and shared paid-service authority; booking migration v32 is reserved after operator v29, immutable mail producer proof v30 and worker claims v31.
- business-site#658: maintained CalDAV adapter, owned-event reconciliation and private connection/revocation proof.
- business-site#659: native EN/DA customer/operator appointment journeys and deployment acceptance.
The selected source direction reuses calendar protocol libraries in the existing Go/PostgreSQL runtime; no new service, subscription or paid enrollment is selected. The maintained go-webdav client supports bounded expanded calendar reports and conditional object writes. Its current client has no dedicated FreeBusy or DeleteCalendarObject method; the adapter must test the actual supported operations and provider semantics. These source/API facts do not prove iCloud compatibility. The human privately authorizes calendar selection and credential setup; real calendar effects, current funding, durable sender acceptance, recovery and deployed user paths remain acceptance gates. The parent stays open until those outcomes are proved; a source merge alone does not complete it.
Metadata
Metadata
Assignees
Labels
Type
Fields
Projects
- StatusShow more project fields📥 Backlog
Activity
chore: agent-claim #3981 nonce=1d34cf7c86aabc4ffb1130350bdbc0d6
chore: agent-claim #3981 nonce=a176527c096fa3938597899624af5062
devantler commentedon Nov 16, 2026
The maintainer approved this operating policy through the coordinator's native interactive question on 16 November 2026. The direct human reply was verified before recording it here.
This resolves the operating-policy question. Explicit configuration, shared purpose/agreement/funding/confirmation checks and the booking source slices remain required. Private calendar selection/credential authorization, actual calendar effects and deployed user-path proof remain separate gates; this approval authorizes no credential operation or real money transaction. #656 remains the only active booking child while its review and the operator-bundle integration hold finish.