# Project archive review card Use this card to decide which project may leave an active worklist and to check its retained history. The filled example is fictional and non-writing. Its expected projection is not an app archive, backup, restoration, permission test or retention rule. ## Filled example: five projects visible to assigned staff A S-A1 has an explicitly stipulated membership in workspace A and assignment to P101–P105. P106 belongs to B and appears only in the separate full answer key. These supplied memberships do not enforce real authorization. | Project | Decision and evidence | | --- | --- | | P101 | Eligible proposal: T101 and T102 are Done; current D101-R2 is approved by AP-D101-R2. | | P102 | Hold: T103 is Open. The Completed project label does not close it. | | P103 | Hold: D103-R2 is current, but AP-D103-R1 covers the earlier revision only. | | P104 | Unknown/hold: D104 is referenced but absent. Do not invent a revision or approval. | | P105 | Already archived; no second archive transition. | The visible denominator is five: one eligible proposal, two holds, one unknown/hold and one already archived. It is not six, and it is not five successful completions. ### Compare exact IDs - Active A before: P101, P102, P103, P104. - Active A after the hypothetical projection: P102, P103, P104. - Archive A before: P105. - Archive A after: P101, P105. Only P101.archived changes from false to true. Across the full key, all six project IDs, seven task IDs, five deliverable IDs, seven nested revision records, six approval records and thirteen task-history events remain. Every parent/workspace pointer, request text, actor, time and approval value stays unchanged. P104's missing D104 stays missing. Counts alone are insufficient; compare the exact IDs and values. ### Follow the history after the proposed move 1. In the staff-A archive projection, find P101 beside P105. 2. Open P101 and locate T101 and T102. 3. Follow T102: its request is “Prepare revised display artwork”; its original request and Done events remain. 4. Follow its D101 reference to current D101-R2 and AP-D101-R2, whose approval names that exact revision. 5. Open older D101-R1 and AP-D101-R1 separately. Their history has not been replaced by the current pair. These are expected lookups in supplied JSON. Actual list navigation, record and file access, and history retrieval in an app are **Not tested**. A preserved identifier does not prove that a person can find or open its history. ### Recheck changed or missing evidence If T102 reopens before the proposed archive, P101 is held by the same all-tasks-Done rule. Do not carry the earlier eligibility decision forward. If an already-archived project later gains open work, this exercise does not define an automatic unarchive or reassignment. Record that policy question and preserve its history. A missing task, unknown phase/archive value, unresolved actor assignment or absent approval is unknown evidence. Do not normalize it into an empty task set, a false archive flag or an approval. Duplicate identities or inconsistent links need correction before a proposal can be trusted. ## Blank card for your app | Context | Your record | | --- | --- | | App, page, revision and observed time | | | Authorized actor and project/workspace assignment evidence | | | Exact supplied project/task/deliverable/history inventory | | | Declared completion and current-approval rules | | | What archive changes, and what it must retain | | | Missing evidence and unresolved policy | | | Actual isolated test path, or Not established | | | Decision | Expected | Actual / evidence | | --- | --- | --- | | Eligible project and linked reasons | | Not tested | | Completed label with open task | | Not tested | | Approval for an older revision | | Not tested | | Missing child or unknown field | | Not tested | | Already archived and repeated proposal | | Not tested | | Outside actor scope | | Not tested | | Reopened work before the proposal | | Not tested | | Preservation check | Expected IDs or values | Actual / evidence | | --- | --- | --- | | Active list before / after | | Not tested | | Archive list before / after | | Not tested | | Exact changed fields only | | Not tested | | Parent/workspace links and request history | | Not tested | | Current revision and its approval | | Not tested | | Older revision and historical approval | | Not tested | | Authorized history retrieval path | | Not tested | ## First request for an existing app ```text 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 approval 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. Keep all project/task/deliverable identities, parent references, request history, versions and approvals. Show the path to current and older history after the proposed move. Do not delete, merge or reparent records. Use the attached fictional example first. Recheck if work reopens or versions change. Do not assume Preview is an isolated database. No real writes, scheduler, deletion or restore action in this first pass. Report evidence and gaps; separately specify and test any real write path, authorization, concurrency and reopened-work policy before using it. ``` This card supplies neither permission to change real records nor a legal retention schedule. Staff departure and open-work reassignment remain a separate task. Mark each unobserved result honestly.