Complete the capstone scenario and learning framework - #14
Merged
Conversation
comwanga
marked this pull request as ready for review
July 21, 2026 09:06
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
BitScope needs to progress from isolated Bitcoin Core demonstrations into a coherent capstone laboratory: policies should be represented as typed data, scenarios should produce reproducible evidence, attacks should only be evaluated when applicable, lifecycle events should be reusable across scenarios, and learners should have a guided path through the material.
The previous flat navigation also exposed every tool at once and did not indicate the selected page, making first-time orientation unnecessarily difficult.
Impact
Learners can now work from foundational node concepts through wallets, transactions, Script, verified scenarios, and advanced tools in a deliberate sequence. Treasury recovery executions and existing Phase 3 scenarios produce stronger lifecycle and proof artifacts, while Challenge Mode connects curriculum objectives to verifiable scenario outcomes.
Validation
npx tsc --noEmit.npm run build.