Appendix J
Appendix J — Reader Exercises and Answer Notes
Exercises to test transfer, not just recall. Answer notes follow each set.
#J.1 — Mathematical exercises
- Using the base cases , compute through by hand, keeping a derivation column.
- Verify Cassini's identity for : compute and confirm it equals .
- Use Binet's formula to estimate via , and confirm the nearest integer is the exact value.
- Compute the ratio and its signed error from .
- Explain why naive recursive computation of is impractical, and state the running-time class of iteration and of matrix exponentiation.
Answer notes. (1) , each the sum of its two predecessors. (2) . ✓ (3) ; nearest integer . ✓ (4) ; error . (5) Naive recursion is exponential () because it recomputes overlapping subproblems; iteration is linear (); matrix exponentiation is logarithmic ().
#J.2 — Method exercises
- For a system you work on, complete the RFPA Framing Canvas (Appendix C). Which of the four moves is weakest?
- Take a recent output your team accepted. Rewrite its acceptance as an AVPT Execution Record (Appendix D). Was validation independent of how it was produced?
- Identify one derived artifact your team edits in place. Describe how you would convert it to a regenerate-not-patch pipeline.
- Design a termination policy (success / resource / failure) for a repeated process you run.
- Classify three "X follows a pattern" claims you have heard using the Claim Matrix (Appendix F).
Answer notes. These are open-ended; a good answer (6) names a specific weakest move and why; (7) honestly identifies whether any check could have failed if the output were wrong; (8) names the canonical source and the read-only derived artifacts and a deterministic build; (9) states all three termination types with concrete thresholds; (10) assigns each claim a category and a refutation test, downgrading any claim with no possible refutation.
#J.3 — Integration exercise
- Run the Reader's Implementation Workbook (Chapter 28 / Appendix uses) on one small real problem over a two-week horizon. Complete at least one full frame → cycle → gate → terminate loop, preserve the evidence, and write a one-paragraph review comparing your recovery capability before and after.
Answer note. Success is not a perfect outcome; it is a completed loop with preserved evidence and an explicit gate decision. If your Recover move failed at the start (no preserved prior state existed), that discovery is itself a valuable result — it is the most common finding, and fixing it is often the whole win.