CCAR-F / Free worksheet and question practice
Will the next phase receive the context it needs?
Write a handoff that keeps separate issues and their evidence intact. Then revise it when one source changes, carry the updated context into the next phase, and explain what your finite local checks cannot establish.
Use Python 3.10 or newer and its standard library. No package installation, account, key or network service is needed after download. You edit a JSON worksheet and assess its prose with a human rubric. Your files and results stay on your computer; this page collects no submissions or completion history.
Download the handoff worksheet (ZIP)Open the worksheet locally
- Check
python3 --version(Windows:py -3 --version). - Extract the worksheet into a new empty folder and open a terminal in that folder. Read
README.md,CONTRACT.mdandWORKSHEET.md. - Read the supplied source fixture. Copy
handoff.jsontoMY_HANDOFF.jsonand edit the copy. Keep the fixture and checker unchanged. The starter is intentionally incomplete. - Follow the worksheet’s digest and trace steps, then run the contract check below. Windows uses
py -3in place ofpython3.
python3 check_contract.py --digests MY_HANDOFF.json python3 check_contract.py MY_HANDOFF.json python3 check_contract.py --self-test
Digest output helps bind the local artifacts; it does not validate the packet. The self-test exercises the checker’s finite acceptance and rejection cases; it does not grade your handoff. Use a disposable folder separate from customer or production work.
Write, carry forward, then revise
- Keep issues separate. Record the facts and source identity for each issue. Put the findings up front, with headed details that a person can inspect.
- Supply the next phase. Copy the first phase’s required evidence and facts into the second phase’s initial context. Record the explicit save → prepare → load → simulated dispatch sequence bound to the artifact digests.
- Handle the changed case. Source A advances while source B is preserved. Update the affected facts and context without silently replacing the other issue’s evidence.
- Explain the boundary. Use the human rubric to assess what the handoff communicates, what remains unresolved and why a passing structural check is insufficient.
A person assesses the reasoning
Open RUBRIC.md and review your original and changed rounds. Assess whether the findings are useful, issues remain distinct, evidence supports the claims, and the next phase can understand the changes and limitations. Write your reasons in a separate local MY_REVIEW.md rather than treating the checker’s exit code as a reasoning score.
The checker validates a finite shape, source identities, artifact digests, context presence and simulated ordering. It does not judge prose adequacy, entailment, real dispatch, durable storage or a real agent’s use of context.
Compare after your attempt
Keep your worksheet. Extract the separate worked answer into another empty folder, open a terminal there, and check its supplied handoff.json as shown below. Compare its walkthrough and rubric reasoning with your own.
Reveal the worked answer download
The worked answer is one example for these supplied fixtures. Its passing contract check does not establish that its prose is uniquely correct or generally effective.
python3 check_contract.py handoff.jsonDownload the separate worked answer (ZIP)
Try three explained practice questions
Apply the worksheet ideas to three original synthetic decisions: separate issue facts, organize findings, and supply the next phase’s initial context. Each question has one answer under its stated contract. Use the explanations to revisit your handoff and human rubric.
This is free practice with independently reviewed explanations. It covers only part of these skills and does not measure mastery, exam readiness or pass probability. These are not official exam questions. Your selections stay in this page’s memory and disappear when you reload; no answers or completion history are saved or submitted.
Practice question 1
Practice question 2
Practice question 3
What this exercise establishes
These are original synthetic fixtures and an offline worksheet. The trace is a local representation of ordering, not an executed agent workflow. Version labels and digests identify the supplied bytes; mutable local files are not an authenticated or immutable evidence store.
No Claude, Agent SDK, MCP service, model or remote provider is executed. Passing the finite checks does not establish mastery, transfer effectiveness, exam readiness or correctness for other systems. These materials are not official exam questions or a full exam simulation.
Check the download bytes
SHA-256 identifies each supplied archive. It is a byte comparison, not a reasoning assessment or proof of authenticity.
- Worksheet ZIP SHA-256
- 10a1ca327d7a182c3ce043b172aa9b4a1e5d09357ebbbf42758cb7bf1e2f962e
- Worked answer ZIP SHA-256
- 5985850fddb9c78c7e1190cc491ef9c845a9358478484c9c7b015e35e6ad8a42