For a returning PromptKB user, which currently documented workflows produce a portable deliverable, what should they do next, and what approval or identity must not be assumed? Selected capabilities from four captured product pages, not a full release chronology, independent verification or measured user benefit.
Manual selection, not verified truth. Exact quote matching checks text membership only. Source metadata is supplied, not authenticated. Line numbers refer to the pasted source, not necessarily the upstream page. No model execution is attested.
4/4 claims included; 0 excluded. 2 unresolved questions.
Reviewed claims
C1
Bring local UTF-8 text or Markdown files into Source Brief at /brief/. Inspect each full text and its metadata, then explicitly add a source or replace its existing ID. Capture a review snapshot before replacing an updated document if you need the earlier evidence; importing resets current decisions rather than carrying approval forward. This is text intake, not PDF or Word extraction.
S1 — Source Brief with local text-file intake — release candidate; lines 18–18, 1 exact occurrence(s).
Choose UTF-8 text files (.txt, .md or other plain text). No PDF, Word, HTML extraction, URL fetch, upload or automatic filename matching.
S1 — Source Brief with local text-file intake — release candidate; lines 19–19, 1 exact occurrence(s).
Inspect full text, edit metadata and choose Add or an exact source ID to Replace for each file. Replacement keeps the ID, not approval. Capture a review snapshot before staging updates if you need the earlier evidence.
S1 — Source Brief with local text-file intake — release candidate; lines 19–19, 1 exact occurrence(s).
Replacement keeps the ID, not approval.
C2
Keep calendar work JSON after preparing an ICS if you need the same event file on a return visit. Reopen it at /packs/calendar-drafts/ and review again: opening does not restore approval, and changing the source or answer creates a separate event rather than correcting the earlier entry.
S2 — Calendar draft and work-file guide; lines 53–53, 1 exact occurrence(s).
Download after preparing an ICS to retain that exact file. Opening requires preview and approval again. Unchanged downloads then reuse the same bytes, UID and creation time, rather than creating another identity.
S2 — Calendar draft and work-file guide; lines 54–54, 1 exact occurrence(s).
Editing the source or answer—even whitespace—discards the event identity in this tab. A later approved download creates a separate event; it does not correct the earlier calendar entry.
C3
For an expense list, review each receipt at /packs/receipt-ledger/ before exporting CSV. The CSV carries record label, merchant, date, currency and total—not source evidence or notes. Keep the separate work JSON if you need that reasoning later; approval is not saved.
S3 — Receipt ledger and work-file guide; lines 67–67, 1 exact occurrence(s).
The CSV includes only record_label, merchant, date, currency, total, not sources, evidence or notes.
S3 — Receipt ledger and work-file guide; lines 34–34, 1 exact occurrence(s).
Explicit downloads are the only way to keep work across visits. Sources, raw answers, notes and any attached original recordings/reviews are included, even when unfinished, excluded or edited since import. Unredacted, unencrypted and unsigned; no approval is saved.
S3 — Receipt ledger and work-file guide; lines 3–3, 1 exact occurrence(s).
Keep the original source beside each answer, approve receipts individually, and export only those you checked.
C4
To ask a colleague for a Test Bench assessment, export a review packet and send them to /lab/peer/. They can download a return file for the sender to preview and apply, with existing judgments archived. Treat reviewer labels as unsigned statements, not proof of who reviewed the work.
S4 — Peer review return editor; lines 3–3, 1 exact occurrence(s).
The sender exports a review packet from Test Bench. Open it here, assess the criteria, and download a return file. The sender previews it before applying it; existing judgments are archived, not silently replaced.
S4 — Peer review return editor; lines 4–4, 1 exact occurrence(s).
This page cannot verify who reviewed a file or whether a model ran.
Review appendix — excluded claims
None.
Review notes
Same-agent editorial selection from four real, captured PromptKB product pages, not independent model runs, a verified release chronology or measured recipient comprehension. The first draft used the live pre-intake Source Brief page; the updated draft uses the captured local release candidate. Import UI inspection confirmed the old locator is intentionally retained on replacement, so it was explicitly updated to the candidate capture identity. Other claims were reread against their unchanged full sources before fresh approval. Source quotes are extracted main-text lines, not original HTML bytes or upstream line numbers. Keep work JSON for complete sources and both reviews; the reading brief omits source bodies. The recommended actions are editorial guidance, not evidence that a calendar or accounting import has occurred. No email, reviewer request or discovery notification was sent for this report.