A project marked Completed can still contain an open request or an approval for yesterday's artwork. Before moving it off the active worklist, check the linked work and the current approval. Then follow the same project's history from the archive view.
This optional guide belongs to Part 4, Test the app you built. It helps you specify a closure check for an existing Overskill app. If you are still choosing your records and roles, start with the client-portal guide.
The exercise uses a fictional design studio. Here, archive means changing which list shows a project while retaining its records. The local preview changes a copy of the supplied example; it does not connect to your app or save a real project. You will leave with a worked decision, a history lookup to repeat and a request for a non-writing readiness view.
1. Decide what makes a project eligible
Write the rule before adding an Archive button. For this exercise, an assigned staff member may propose moving an unarchived project when:
- The project is in that staff member's workspace and assigned to them.
- Its phase is Completed.
- The linked-task inventory is complete, every referenced task resolves to the same project and workspace, and every task is Done.
- The current deliverable exists, and its approval names that exact current revision with an Approved decision.
A known open task or approval mismatch holds the proposal. A missing record or unknown field also holds it, with the missing evidence stated explicitly. An absent task list cannot stand in for “no unfinished tasks.” Duplicate IDs or inconsistent parent links must be resolved before trusting the proposal.
Already-archived projects receive no second archive change. These are declared rules for the example; decide the equivalent rules for your workflow.
Overskill's Data editing help describes requesting an archive field or status and updating the relevant queries. The readiness check below is a requirement to build and test in your app, not a built-in completed-project workflow.
2. Compare five different closure decisions
Start with Original six-case exercise · staff-A view in the Evidence snapshot selector. Staff S-A1's membership in Workspace A and assignment to P101–P105 are supplied assumptions. The staff view contains five projects. A sixth belongs to another workspace and appears only in the separate complete teaching key. This separation in fictional data does not enforce real permissions.
Review the project evidence
This exercise changes an in-memory copy of fictional records. It does not archive an app record, enforce permissions, delete data or establish a retention rule.
Section links and Back/Forward within this page keep the exercise state. Leaving this page, reloading or Reset exercise restores the original fictional evidence.
Scroll horizontally to compare all columns.
| Project | Evidence in the original snapshot | Decision |
|---|---|---|
| P101 · Workshop display | T101 and T102 are Done. Current D101-R2 has approval AP-D101-R2. | Eligible proposal |
| P102 · Festival poster | The project says Completed, but T103 is Open. | Hold: unfinished work |
| P103 · Bookshop cards | D103-R2 is current; AP-D103-R1 approves the earlier R1 only. | Hold: current revision lacks its approval |
| P104 · Studio window | T105 points to D104, which is absent from the supplied records. | Unknown/hold: missing deliverable |
| P105 · Sample booklet | The project is already archived. | Unchanged |
The denominator is five: one eligible proposal, two known holds, one unknown/hold and one already archived. Open Inspect P103 to compare the current revision with its older approval. Keep that older approval as history; it cannot approve a later revision.
Then inspect P104 and follow T105 to the missing D104. The lookup stops at the gap. Do not fill in a revision or infer approval because the project has a Completed label.
3. Preview one change and compare the exact lists
Choose Reset exercise, then Preview P101 in archive. The expected list membership is:
Scroll horizontally to compare all columns.
| View | Before | After the local preview |
|---|---|---|
| Active | P101, P102, P103, P104 | P102, P103, P104 |
| Archive | P105 | P101, P105 |
Only P101.archived changes from false to true. Project and task IDs, parent and workspace links, request text, history events, revision records and approvals stay the same. P104's missing deliverable stays missing. The preview does not repair the other projects or approve their work.
Compare exact identities and values as well as totals. Two lists can have the right counts while containing the wrong projects. View the staff-A projection JSON to inspect the supplied before and after records in your browser. The Complete teaching key beside the exercise provides a separate relation diagram and textual map for all six fictional cases.
4. Find the request and both versions from Archive
A retained ID is useful only if the intended person can follow it to the history they need. After previewing P101, choose Find P101 in the archive → and open the project.
- Open T102 · Prepare revised display artwork. Read the original request and its Created and Done events. The event IDs, actors and timestamps are retained.
- Choose Follow D101 →, then open D101-R2 · current. Its supplied text is “Revised fictional artwork for P101.” Approval AP-D101-R2 names R2.
- Return to D101 and open D101-R1 · historical. Its text is “Initial fictional artwork for P101.” The older AP-D101-R1 still names R1.
The current and historical approvals remain separate. These are lookups in the exercise's supplied records, with fictional text rather than real artwork files. Repeat the path in your actual app to verify that its records, files and history can be opened by the intended person. A successful local preview cannot establish that result.
5. Recheck when the evidence changes
Use the Evidence snapshot selector to try the boundary cases. Each selection loads a separate fictional variant and clears the earlier preview.
- T102 reopens before archive: P101 is held because a linked task is now Open. An earlier eligible decision no longer applies.
- Current revision changes to R3: the approval for R2 does not approve R3. Keep the old approval attached to its own revision.
- Linked T102 is missing or P101 phase is unknown: show unknown evidence and hold the proposal.
- Actor membership is unknown: no staff projection is formed. Counts are unavailable; this does not mean there are zero projects.
- Recheck the projected after-state: P101 is already archived, so there is no second change.
Also try Archived P105 gains open work. The exercise retains P105's archived state and identifies an unresolved policy. Decide who should handle reopened work, where it should appear and whether an explicit unarchive action is appropriate. Do not silently invent that policy or reassign the work.
For a real write, eligibility must be checked against current records at the time of the change. A task or approval can change after someone reviews a proposal. The shared-record editing guide covers the separate problem of stale views and server-side version checks.
6. Request a readiness view in your existing app
Download the project archive review card. It includes the filled example, blank expected/actual checks and a request you can adapt. Keep unobserved actual-app results marked Not tested, even after completing this exercise.
Begin with a view that explains eligibility without changing real records. In the affected app's AI Prompt Builder, adapt this request with your actual project list, actor rules and linked-record inventory:
Prepare a non-writing archive-readiness view for [existing project list].
Use my declared actor scope and exact linked-record inventory.
Show which unarchived Completed projects have every linked task Done
and an Approved decision for the current deliverable revision.
Show known blockers and unknown evidence separately.
Already-archived projects stay unchanged.
Preview exact active/archive IDs and the only proposed field changes.
Retain project/task/deliverable identities, parent and workspace links,
request history, versions and approvals. Show a path from Archive
through the project and request to current and older approval records.
Do not delete, merge or reparent records.
Use the fictional example first. Re-evaluate when work reopens or a
revision changes. No real writes or scheduled archive in this pass.
Report missing evidence and the unresolved policy for reopened work.
Before testing a write, establish an isolated test path. Preview uses the same app database as the live app; opening Preview alone does not isolate a data change. Define and verify the real write behavior separately.
Record the tested app revision, actor, expected IDs, exact changed fields and observed result. Repeat the P101 history path after the change and after reopening the app. Check the old and current approval records and any files your workflow uses. Use the private-record access guide to test both allowed access and denial for a different workspace, including direct links and files. Hiding a row from Active does not make it private.
Archive in this exercise defines list membership. It supplies no deletion authority, backup, restoration guarantee or legal retention period. Keep those policies separate, and bring the completed card back to the affected app with the first missing or failed history check.