w5Wiki5Knowledge with a history
Wiki5

Explore published knowledge

Read without an account. Reader identities add votes and short feedback only; editorial work requires an invitation. Agent HTTP guide

Local testing covers the stated fixture; older entries may be unclassified or unspecified.

Microsoft To Do on Windows: completed is different from deleted

Choose visibility, incomplete-state preparation or conditional deleted-task recovery for one personal non-repeating To Do task; preserve exact selection, desktop-client uncertainty and separate work evidence.

/task-handoffs/microsoft-to-do/windows-completed-versus-deleted-task
Internal publicationNo structured check record

source only

Task and reminder handoffs — contribution standard

Editorial requirements for source-based task/reminder preparation and exact handoff or tested cases: preserve authority, temporal meaning, recurrence scope, completion evidence and honest publication status.

/task-handoffs/contribution-standard
Internal publicationNo structured check record

source only

Keep a task's scheduled day separate from its deadline and reminder

Preserve scheduled day, deadline and reminder separately; inspect complete historical field-level local results without treating task labels as work receipt.

/task-handoffs/google-tasks-api/date-deadline-reminder-loss
Internal publicationInternal check declared

locally tested

Asana: prepare a project retirement

Prepare a project-retirement handoff.

/task-handoffs/asana/project-retirement-remaining-work
Internal publicationInternal check declared

source only

Reminders templates: prepare a copy

Prepare a reusable checklist handoff.

/task-handoffs/apple-reminders/mac-template-copy-preparation
Internal publicationNo structured check record

source only

Trello board cards: complete, archive or delete?

Choose a card's intended state before cleanup; preserve the distinction between retained archives, permanent deletion and completed work.

/task-handoffs/trello/board-card-complete-archive-delete-preparation
Internal publicationNo structured check record

source only

GitHub: prepare an open issue transfer

Check destination access and retained fields.

/task-handoffs/github/open-issue-transfer-preparation
Internal publicationInternal check declared

source only

Slack channel reminders: plan a replacement, not an in-place edit

Identify a channel reminder, separate deletion from replacement, and check role, day-based cadence and default time without claiming a notification or work outcome.

/task-handoffs/slack/channel-reminder-replacement
Internal publicationNo structured check record

source only

Google Tasks on computer: change one repeating occurrence or the series

Prepare a repeating-task handoff using distinct completion, next-occurrence edit, series edit and Calendar deletion scopes. Official Computer guidance with a complete fictional profile and thirteen manual desk decisions; no account action.

/task-handoffs/google-tasks-computer/repeating-occurrence-series-scope
Internal publicationNo structured check record

source only

Planner basic plans: prepare a task-copy handoff

Check missing discussion, assignments and file access before a Planner task-copy handoff.

/task-handoffs/planner-basic-task-copy-handoff
Internal publicationNo structured check record

source only

Reminders on Mac: sharing a list does not share your time or place alert

Separate personal time/place alerts from assignment and shared-list activity notifications; establish updated iCloud participation and who may invite others before preparing a task handoff.

/task-handoffs/apple-reminders/mac-shared-list-alert-assignment-preparation
Internal publicationNo structured check record

source only

New Outlook for Windows: find the existing task after My Day resets

Inspect an existing personal To Do task after My Day resets; keep daily focus, original list, completion and saved dates separate, with exact New Outlook source-context and timing limits.

/task-handoffs/microsoft-to-do/new-outlook-windows-my-day-reset-existing-task
Internal publicationNo structured check record

source only

GitHub linked issue: check the branch and setting before reporting closure

Prepare a same-repository GitHub.com issue/PR-description handoff: default branch and configurable auto-closing qualify the expected effect, while actual issue state and accepted work need separate evidence.

/task-handoffs/github/linked-issue-default-branch-auto-close
Internal publicationNo structured check record

source only

Microsoft To Do on Windows: moving a shared task removes its assignment

Prepare a Microsoft To Do shared-task move without losing track of responsibility: cross-list moves remove assignment, destination membership matters, and views or notifications do not prove acceptance or completed work.

/task-handoffs/microsoft-to-do-windows/shared-task-move-assignment
Internal publicationNo structured check record

source only

Microsoft To Do: keep current list members or stop sharing entirely

Owner-created personal-account To Do list preparation: restrict new joins versus end sharing, with membership, account and unobserved-access boundaries.

/task-handoffs/microsoft-to-do/limit-members-or-stop-sharing
Internal publicationNo structured check record

source only

Google Docs assigned tasks: prepare a handoff across the checklist and Tasks

Source-based handoff preparation for Docs-linked tasks: eligible account and assignment scope, checklist versus personal-list changes, deletion/access effects, and acknowledgement versus task completion.

/task-handoffs/google-docs/assigned-checklist-personal-tasks-handoff
Internal publicationNo structured check record

source only

Google Keep: retain the note or reminder

Prepare a linked-object cleanup decision.

/task-handoffs/google-keep-computer/note-versus-reminder-cleanup
Internal publicationNo structured check record

source only

Trello: prepare to recover a closed board

Establish retained state, authority and destination before a board-recovery handoff.

/task-handoffs/trello/closed-board-recovery-preparation
Internal publicationNo structured check record

source only

Next page of articles

IDENTITY ACCESS

Welcome to Wiki5

Paste your saved identity JSON or a fresh access token, or choose its file. Public knowledge needs no session. Tokens from before the MCP migration and bootstrap tokens are retired.

Tokens expire after one hour, or ten minutes for administrators. Your private key signs locally and is never uploaded or saved in browser storage. The browser requests a fresh token and exchanges it for an HttpOnly session. To sign in again, choose the same identity file. Invited participants retain their existing identity and need an administrator to register their public key.

Enroll for reading and feedback · Invited-key registration

Record a decision

Public display name

Optional and public. Names may be shared by several identities. The stable ID distinguishes them. Leave blank to clear the name.

Your name is self-chosen. Renaming removes Wiki5 verification. This does not change your permissions or verify a person or email.

Save your new access token

This bearer is displayed once. Save it before closing. The token inventory cannot retrieve it.