​

Pocket inactive work

​

Sources

Docs: Personal work Web App: Use Pocket from the lifecycle actions available for the exact Parable, Patch, Problem, or deployment you are viewing. Pocket removes inactive work from ordinary views without treating it as deleted. Use it when the work should stop competing for attention but may need to be inspected or restored later.

​

Pocket the correct target

Several objects can expose Pocket. Read the confirmation carefully: pocketing a Patch is different from pocketing a Parable or a Workspace delivery. The available action and required responsibility depend on that target. Before pocketing:

• confirm no active collaborator still depends on the item;
• copy any review link that must remain easy to find;
• note why the work is inactive; and
• verify that Restore is available if recovery matters.

​

Who Pocketed a Parable

A Parable has two Pockets. Parable staff Pocket the whole Parable in Admin. A Workspace Pockets its own Deployment of the Parable. Every Workspace that has the Parable shows it as Pocketed when either Pocket holds. The sidebar puts it with the Pocketed Parables. The editor header shows “Pocketed” beside the Parable’s name. On a phone, “Pocketed” shows under the title. Its hint says who Pocketed the Parable and who can Restore it. Point at “Pocketed”, tap it, or press Enter or Space on it to show the hint: When both Pockets hold, the hint says “Pocketed by Parable staff”. A person with Primary or Publishing can still Restore the Workspace’s own Pocket. The Parable stays Pocketed until Parable staff also Restore it. While Parable staff hold a Parable Pocketed, every change to it waits, in every Workspace and in Admin, until Parable staff Restore it. These changes wait:

• a change to the seats or to the Collaboration Mode;
• a change to a Piece, Start Changes, and every other Patch move;
• a Refresh;
• a Pull of a Delivery, and a Retry of a failed Delivery;
• a Pocket of the Workspace’s own Deployment;
• a Pocket or a Restore of a Problem; and
• the Visible, Forking and Platform switches.

Each answers “Parable staff Pocketed this Parable, so it takes no changes here. Only Parable staff can Restore it, from its row menu in Admin.” A change to a Package’s files waits too, but it still answers an older sentence. A move that started before the Pocket finishes first. A Delivery that waits stays available, and the Workspace sees that an update waits. These moves still run: every read, the Workspace’s Restore of its own Pocket, the staff delete of a copy, and the conversation about the Parable. In Ponder, a person can start a Problem, write Messages in it, and move it under another Problem. Start Changes waits, because it opens a Patch. A Pocketed Parable stays readable under its badge. Its Pieces tree and its Pages show, read-only, for both Pockets. The tree offers no Add Package, no rename and no move until the Parable is Restored.

​

Restore or delete

Use Restore to return pocketed work to its supported active view. Use Delete only when the product explicitly offers a terminal action and the person who holds Primary has confirmed that permanent removal is intended. If other changes were published while your Patch was pocketed, restoring it preserves those changes. Review and Propose the restored work again before publishing; its earlier review cannot authorize a changed result. Restore refuses a Patch whose Problem is Pocketed, when a person started that Problem. The answer is “The Problem is Pocketed. Restore the Problem, then try again.” Restore the Problem first, then Restore the Patch. If an item seems to have disappeared unexpectedly, search pocketed items and confirm the Workspace before recreating it. A duplicate starts separate identity and history.

​

Platform Parables and new Workspaces

Pocketing a Platform composed Parable stops its Deliveries to Workspaces created afterwards. Its existing copies and Release history stay. A deleted Platform composed Parable also sends no Delivery to a new Workspace. Restoring the Pocketed Parable makes it eligible again for Workspaces created after Restore, if its latest Deploy still targets every Workspace now and later. A newer Deploy to a chosen list does not revive an earlier audience.