# Book Isle personal reading evidence portfolio: test learning with three small tasks

Language: en
Canonical: [Book Isle personal reading evidence portfolio: test learning with three small tasks](<https://allluckly.cn/en/guides/nasbook-personal-reading-evidence-portfolio/>)
中文：[中文 HTML](<https://allluckly.cn/guides/nasbook-personal-reading-evidence-portfolio/>)
English: [English HTML](<https://allluckly.cn/en/guides/nasbook-personal-reading-evidence-portfolio/>)
Published: 2026-11-03T00:00:00+08:00
Modified: 2026-11-03T09:34:11+08:00
Author: Bison

Combine source evidence and personal answers for explanation, discrimination and application tasks, retaining counterexamples and return tests instead of using reading time or highlights as mastery proof.

English translation of the [Chinese original](<https://allluckly.cn/guides/nasbook-personal-reading-evidence-portfolio/>), translated on 2026-11-03. Original publication dates, attribution, code and version notes are retained.

Post-reading gains can sound broad, while explaining a concept, recognising an exception and completing a small application require concrete checks. Build a three-sample personal portfolio, each with its task, answer and source evidence. This is not project-wide reference archiving or an automatically scored learning report; you select and verify the samples manually.

## Turn learning claims into checkable tasks

Choose three specific actions: explain a concept, decide whether it fits an example, and write a short procedure under stated conditions. Define input and expected output rather than claiming to understand the whole book or reciting terminology. Limit claims to material actually read. Sources may span chapters or books, but preserve each independently; the number of books is not itself evidence of learning quality.

## Task one: explain, then calibrate against the text

Leave the passage and explain the concept in three to five sentences, including its subject, relationship and one limit. Return to the source and mark omissions or meaning changes rather than replacing your answer with copied wording. Date initial and corrected answers. Use manual chapter/phrase or page references if precise links are absent. This task supports an explanation claim, not competence in every real situation; state that evidentiary limit.

## Task two: discriminate with a nearby counterexample

Construct two personal examples differing in one important condition and decide where the method fits or judgement must remain open. Label them as your reasoning, not author cases or measured outcomes. Write reasons before checking source limits. Mark unsupported conclusions unresolved. Retain a corrected misclassification instead of selecting only easy successes, and do not use the personal exercise to score other people’s abilities.

## Task three: specify a small application and stopping rule

Choose a low-risk observable application, such as organising a passage, comparing plan conditions or scheduling a review. Define inputs, a few actions, acceptance and when more information is needed. Try a self-made sample if you actually perform it; otherwise label it a proposal rather than verified effectiveness. Distinguish source-derived steps from additions. A usable sample does not validate an entire theory or every context.

## Keep a task evidence card, not an isolated quote

For each sample record task, answer, source, revisions and unknowns in ordinary text, without assuming a portfolio panel. Keep minimal locator extracts with edition and chapter/page. Separate personal reasoning rather than merging quotations from several books into an unattributed conclusion. Use available notes/bookmarks and an external mapping; no export is assumed to preserve every custom relationship. The future reader should understand both support and limits.

## Run a return test using only the cards

Leave reading and search, then use one card alone to find the correct edition and passage. If a step depends on recent thumbnail memory or guessing, improve the address rather than polishing the summary. Locate the same task in an external readable record and check basic provenance remains understandable. Preserve source files separately. Test all three individually and record failures; one working sample does not validate the portfolio or every reading record.

## Let the results guide the next review

Use the failure type to choose one next step: revisit definitions, examine boundary passages or investigate missing prerequisites. Date the review. Time, pages and note counts describe effort but do not substitute for task performance. Retest with another example while retaining earlier answers and errors. Keep the portfolio lightweight rather than generating many empty fields or duplicate samples for every book.

## Acceptance and the scale of the claim

Finish with genuine answers or explicit incompletion for all three tasks, recoverable evidence, separated author/personal contributions and actionable next steps. Limited tasks do not establish comprehensive mastery. A single pass still identifies useful next work. Preserve important output versions, records and source files separately. The portfolio states current ability, support and limits, without inventing app certification or presenting a personal exercise as a universally valid learning assessment.

## Related guides and sources

[Book Isle question-led chapter reading: separate initial questions from final answers](<https://allluckly.cn/en/guides/nasbook-question-led-chapter-reading/>); [Book Isle rereading annotations: preserve extracts and date new interpretations](<https://allluckly.cn/en/guides/nasbook-rereading-interpretation-log/>).

Checked on November 3, 2026: [Apple public version information](<https://itunes.apple.com/lookup?id=6766198898&country=cn>) lists Book Isle 1.1.3, requiring iOS / iPadOS 15.6 or later. Feature scope follows the [official App Store description](<https://apps.apple.com/cn/app/id6766198898>) and the installed version. This article describes actions and content checks you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and application controls are identified separately, and code observations or personal inferences are not presented as verified automatic capabilities.

