[ { "id": "SOURCE-DOC01", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://docs.github.com/en/get-started/using-github/hello-world" ], "body": { "title": "GitHub Hello World", "url": "https://docs.github.com/en/get-started/using-github/hello-world", "access": "Official workflow documentation; page read", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [ "CLAIM-001" ], "version": "4.1" }, { "id": "CLAIM-001", "record_type": "claim", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "SOURCE-DOC01" ], "body": { "kind": "technical", "paraphrase": "The official Hello World lesson introduces repository, branch, commit and pull-request workflow concepts.", "scope": "Content of this documentation; not proof of a learner performing it" }, "links": [ "INSIGHT-001" ], "version": "4.1" }, { "id": "INSIGHT-001", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "draft", "provenance": [ "CLAIM-001" ], "body": { "original_application": "Use one small timer change as an introductory traceability exercise.", "evidence_limit": "Teaching effectiveness has not been learner-piloted" }, "links": [ "LESSON-AI101-L4" ], "version": "4.1" }, { "id": "LESSON-AI101-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-AI101", "SOURCE-DOC01", "SOURCE-DOC03" ], "body": { "title": "Test and Record", "course_id": "AI101", "lesson_id": "AI101-L4", "objective": "Produce a test record another builder can understand.", "teaching": "A tool is ready for this exercise when its small job is demonstrated and its limits are clear. Run each acceptance case in the browser you will name in your record. State the date, version, steps, expected behavior and observation. Do not mark a case passed because the code looks as if it should pass.\n\nStart the timer and confirm that time decreases. Pause it, wait briefly and confirm the display remains stable. Reset and confirm ten minutes returns. Press Start twice and confirm the countdown does not speed up. For the final case, use a copied file with a two-second duration or the prototype’s test setting; confirm it reaches zero, stops and announces completion without a negative display.\n\nAdd useful edge cases if a defect suggests one, such as resetting while running or starting after completion. Record keyboard use and a narrow-screen check because visible and usable controls matter. Avoid turning the exercise into an endless test project once the defined requirements are satisfied.\n\nWrite a handoff in plain language: what the tool does, how to open it, what changed, what passed, what remains untested and the next sensible improvement. Explain that the prototype has no background alarm guarantee and that the short test run does not establish every browser’s behavior.\n\nFor a future GitHub version, use a repository, branch, commit and pull request to preserve and review changes. The official Hello World documentation provides that workflow. This lesson itself does not create a repository or deploy a service. Your completed artifact and honest test log are the evidence for this learning step.", "worked_example": "Illustrative handoff: “Version 0.2 changes the heading only. Five defined cases passed in the named desktop browser. A narrow-screen check found no horizontal scrolling. Mobile background behavior has not been tested. Next improvement: test on the intended phone before adding any new feature.” This is a sample record; replace it with actual observations.", "evidence": [ "Five-case test record", "Keyboard and viewport observations", "Versioned file and six-part handoff" ], "status": "Public educational edition; learner pilot pending" }, "links": [ "EXPERIMENT-001" ], "version": "4.1" }, { "id": "EXPERIMENT-001", "record_type": "experiment", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "queued", "provenance": [ "LESSON-AI101-L4" ], "body": { "procedure": "Pilot the timer exercise with three consenting adult learners using fictional data.", "observations": "Not run", "decision_rule": "Revise instructions when the learner cannot repeat a check or explain the artifact" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC02", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://docs.github.com/en/get-started/start-your-journey/git-and-github-learning-resources" ], "body": { "title": "GitHub learning resources", "url": "https://docs.github.com/en/get-started/start-your-journey/git-and-github-learning-resources", "access": "Official learning resource page/indexed text inspected", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC03", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.freecodecamp.org/news/learn-rag-and-mcp-fundamentals/" ], "body": { "title": "freeCodeCamp RAG & MCP Fundamentals", "url": "https://www.freecodecamp.org/news/learn-rag-and-mcp-fundamentals/", "access": "Official companion article read; full course video not viewed", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC04", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://docs.docker.com/get-started/docker-overview/" ], "body": { "title": "Docker overview", "url": "https://docs.docker.com/get-started/docker-overview/", "access": "Official overview read; no installation performed", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC05", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://reticulum.network/manual/whatis.html" ], "body": { "title": "What is Reticulum?", "url": "https://reticulum.network/manual/whatis.html", "access": "Official technical introduction read; field range and deployment not tested", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC06", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.consumerfinance.gov/consumer-tools/educator-tool/your-money-your-goals/toolkit/" ], "body": { "title": "CFPB Your Money, Your Goals toolkit", "url": "https://www.consumerfinance.gov/consumer-tools/educator-tool/your-money-your-goals/toolkit/", "access": "Official toolkit overview read", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC07", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.archives.gov/founding-docs/constitution-transcript" ], "body": { "title": "Constitution transcription | National Archives", "url": "https://www.archives.gov/founding-docs/constitution-transcript", "access": "Official transcription and Article VI inspected; no individual legal application determined", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC08", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.copyright.gov/help/faq/faq-protect.html" ], "body": { "title": "Copyright Office: What copyright protects", "url": "https://www.copyright.gov/help/faq/faq-protect.html", "access": "Official FAQ read in the first build", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC09", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.sba.gov/counseling/plan-your-business/" ], "body": { "title": "SBA Plan your business", "url": "https://www.sba.gov/counseling/plan-your-business/", "access": "Official market-research and startup-cost sections read; fictional model is original", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC10", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://files.consumerfinance.gov/f/documents/cfpb_your-money-your-goals_cash_flow_budget_tool_2018-11_ADA.pdf" ], "body": { "title": "CFPB Creating a cash flow budget", "url": "https://files.consumerfinance.gov/f/documents/cfpb_your-money-your-goals_cash_flow_budget_tool_2018-11_ADA.pdf", "access": "Official four-page tool inspected; course uses an original fictional case", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC11", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://developer.mozilla.org/en-US/docs/Learn_web_development/Howto/Web_mechanics/How_does_the_Internet_work" ], "body": { "title": "MDN How does the Internet work?", "url": "https://developer.mozilla.org/en-US/docs/Learn_web_development/Howto/Web_mechanics/How_does_the_Internet_work", "access": "Official learning page read; local dependency exercise is original", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC12", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://docs.docker.com/engine/storage/volumes/" ], "body": { "title": "Docker volumes", "url": "https://docs.docker.com/engine/storage/volumes/", "access": "Official storage documentation read; actual backup and deployment not run", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC13", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.govinfo.gov/content/pkg/USREPORTS-339/pdf/USREPORTS-339-306.pdf" ], "body": { "title": "Mullane official United States Reports opinion", "url": "https://www.govinfo.gov/content/pkg/USREPORTS-339/pdf/USREPORTS-339-306.pdf", "access": "Official opinion inspected for historical reading exercise; current treatment and actual procedural rules not checked", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC14", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.sqlite.org/fts5.html" ], "body": { "title": "SQLite FTS5 documentation", "url": "https://www.sqlite.org/fts5.html", "access": "Official full-text-search documentation inspected; the supplied local tool was tested separately", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC15", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://docs.python.org/3/library/sqlite3.html" ], "body": { "title": "Python sqlite3 documentation", "url": "https://docs.python.org/3/library/sqlite3.html", "access": "Official database-module documentation inspected; behavior verified only in the named local runtime", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC16", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://thecrashcourse.com/courses/" ], "body": { "title": "Crash Course official course directory", "url": "https://thecrashcourse.com/courses/", "access": "Directory and subject coverage inspected; no full course review", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC17", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.munroeglobal.com/about-us/" ], "body": { "title": "Munroe Global official about page", "url": "https://www.munroeglobal.com/about-us/", "access": "Purpose and leadership mission inspected; no complete sermon reviewed", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC18", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://serenityknowledge.com/youtube-channel/" ], "body": { "title": "Serenity Knowledge channel page", "url": "https://serenityknowledge.com/youtube-channel/", "access": "Creator channel description inspected; no clinical or scientific claim verification", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC19", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://understandcontractlawandyouwin.com/client-homework-free-resources/" ], "body": { "title": "UCLAYW creator resources page", "url": "https://understandcontractlawandyouwin.com/client-homework-free-resources/", "access": "Legacy account link and research list inspected; substantive legal claims not verified", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC20", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/watch?v=-FMyoQ_zr94" ], "body": { "title": "The Law Academy: History of English Law introduction", "url": "https://www.youtube.com/watch?v=-FMyoQ_zr94", "access": "Primary video description identifies UK study context and exact channel handle; no transcript reviewed", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC21", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://thecrashcourse.com/courses/check-yourself-with-lateral-reading-crash-course-navigating-digital-information-3/" ], "body": { "title": "Crash Course: lateral reading companion page", "url": "https://thecrashcourse.com/courses/check-yourself-with-lateral-reading-crash-course-navigating-digital-information-3/", "access": "Official lesson description inspected; video and full transcript not reviewed", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC22", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://thecrashcourse.com/courses/how-to-argue-philosophical-reasoning-crash-course-philosophy-2/" ], "body": { "title": "Crash Course: philosophical reasoning companion page", "url": "https://thecrashcourse.com/courses/how-to-argue-philosophical-reasoning-crash-course-philosophy-2/", "access": "Official lesson description inspected; video and full transcript not reviewed", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC23", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.leg.state.nv.us/nrs/nrs-104.html" ], "body": { "title": "Nevada Legislature: NRS 104.2102 scope and associated definitions", "url": "https://www.leg.state.nv.us/nrs/nrs-104.html", "access": "Official compilation inspected October 31, 2026; page revision April 15, 2026. Narrow goods/hybrid-transaction scope exercise only; current case law, governing-law choice and a real agreement’s classification not researched.", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC24", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://openstax.org/books/introduction-philosophy/pages/5-4-types-of-inferences" ], "body": { "title": "OpenStax: Types of Inferences", "url": "https://openstax.org/books/introduction-philosophy/pages/5-4-types-of-inferences", "access": "Publisher textbook section inspected for the distinction between deductive, inductive and abductive inference. Course wording, cases and exercises are original; no figure or textbook passage reproduced.", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC25", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://modelcontextprotocol.io/specification/2025-06-18/server/tools" ], "body": { "title": "MCP specification: Tools, dated 2025-06-18", "url": "https://modelcontextprotocol.io/specification/2025-06-18/server/tools", "access": "Dated official tool-schema and security sections inspected; not represented as the latest protocol edition or evidence that a live integration was implemented.", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-DOC26", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://developer.mozilla.org/en-US/docs/Web/API/SpeechSynthesisVoice/localService" ], "body": { "title": "MDN: SpeechSynthesisVoice.localService", "url": "https://developer.mozilla.org/en-US/docs/Web/API/SpeechSynthesisVoice/localService", "access": "Official web API reference inspected for the browser-reported local/remote voice distinction. Device speech, offline audio and real-browser behavior not tested.", "retrieved_date": "2026-10-31", "verification_scope": "Inspection metadata; not blanket verification of every associated claim" }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH01", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@spiritscienceofficial" ], "body": { "title": "Spirit Science", "url": "https://www.youtube.com/@spiritscienceofficial", "requested_handle": "@spiritscienceofficial", "access": "Description only; no full transcript or viewing", "identity": "Primary video description indexed", "use_condition": "Use as spiritual and symbolic inquiry; verify historical or scientific claims separately." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH02", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "UNKNOWN", "review_state": "queued", "provenance": [ "https://www.youtube.com/@johns-vault" ], "body": { "title": "John’s Vault", "url": "https://www.youtube.com/@johns-vault", "requested_handle": "@johns-vault", "access": "Indexed title and secondary summary; exact handle not confirmed", "identity": "Tentative match from secondary indexes", "use_condition": "Research lead only. Verify exact creator identity and business assumptions before attributing a lesson." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH03", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@dataslayermedia" ], "body": { "title": "Data Slayer", "url": "https://www.youtube.com/@dataslayermedia", "requested_handle": "@dataslayermedia", "access": "Creator landing page and indexed examples; no complete video viewed", "identity": "Creator site read", "use_condition": "Validate implementation against project documentation; range and outage claims require local measurement." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH04", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@explainerguy01" ], "body": { "title": "explainerguy01", "url": "https://www.youtube.com/@explainerguy01", "requested_handle": "@explainerguy01", "access": "Channel description and keywords only", "identity": "Primary channel description indexed", "use_condition": "Use the accessible format as inspiration; no particular video lesson has been verified." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH05", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@philosophicalessence" ], "body": { "title": "Philosophical Essence", "url": "https://www.youtube.com/@philosophicalessence", "requested_handle": "@philosophicalessence", "access": "Indexed channel metadata and titles; no primary transcript", "identity": "Secondary channel metadata and titles", "use_condition": "Source of inquiry questions, not established evidence for physical or health claims." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH06", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "UNKNOWN", "review_state": "queued", "provenance": [ "https://www.youtube.com/@behindtheledger1" ], "body": { "title": "Behind the Ledger", "url": "https://www.youtube.com/@behindtheledger1", "requested_handle": "@behindtheledger1", "access": "Supplied URL only; similarly named accounting podcast excluded", "identity": "UNKNOWN: exact channel not resolved", "use_condition": "Keep queued. Do not infer subject matter or substitute another account with the same display name." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH07", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@silas-ai" ], "body": { "title": "Silas AI", "url": "https://www.youtube.com/@silas-ai", "requested_handle": "@silas-ai", "access": "Creator account of method and selected indexed video descriptions; no full video review", "identity": "Creator article read; channel link available", "use_condition": "Adapt fair comparison and visible testing; independently evaluate model outputs and avoid creator income extrapolation." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH08", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "UNKNOWN", "review_state": "queued", "provenance": [ "https://www.youtube.com/@hustlersmotivation4911" ], "body": { "title": "Hustlers Motivation", "url": "https://www.youtube.com/@hustlersmotivation4911", "requested_handle": "@hustlersmotivation4911", "access": "Secondary same-name index only; identity not established", "identity": "Tentative same-name channel; exact handle unresolved", "use_condition": "Do not attribute or reuse narration until the exact handle and underlying book/audio rights are established." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH09", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@diegoarias-tech" ], "body": { "title": "Tech With Diego", "url": "https://www.youtube.com/@diegoarias-tech", "requested_handle": "@diegoarias-tech", "access": "Channel description, Docker video description and chapters; no full video viewed", "identity": "Primary channel and video descriptions indexed", "use_condition": "Use official platform documentation for instructions; refresh commands before teaching." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH10", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@github" ], "body": { "title": "GitHub", "url": "https://www.youtube.com/@github", "requested_handle": "@github", "access": "Official learning/resource pages and Hello World documentation", "identity": "Official GitHub resources and documentation read", "use_condition": "Link to GitHub exercises; produce original examples and separate local demonstration from a deployed service." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH11", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@freecodecamp" ], "body": { "title": "freeCodeCamp.org", "url": "https://www.youtube.com/@freecodecamp", "requested_handle": "@freecodecamp", "access": "Channel description and official companion article; full two-hour course not viewed", "identity": "Primary channel and course companion article read", "use_condition": "Use as technical learning resource; verify implementation details and licenses per individual project." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH12", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@highfrequencyradio" ], "body": { "title": "High Frequency Radio / SPC University", "url": "https://www.youtube.com/@highfrequencyradio", "requested_handle": "@highfrequencyradio", "access": "Creator about page and course topic list; no full video transcript", "identity": "Creator organization page read; handle corroborated by secondary listing", "use_condition": "Use claims as research questions; controlling text, relevant decisions, jurisdiction and procedure establish legal conclusions." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH13", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@quantumshiftchannel" ], "body": { "title": "Quantum Shift", "url": "https://www.youtube.com/@quantumshiftchannel", "requested_handle": "@quantumshiftchannel", "access": "Video description only; no full transcript", "identity": "Primary video description indexed", "use_condition": "Retain voluntary reflection and aspiration; describe behavioral exercises as original applications, not proof of timeline shifting." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH14", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@19keys" ], "body": { "title": "19Keys", "url": "https://www.youtube.com/@19keys", "requested_handle": "@19keys", "access": "Creator bio and podcast description; no complete interview analyzed", "identity": "Official creator press page and podcast description read", "use_condition": "Use culturally grounded questions and implementation challenges; do not imply affiliation, endorsement or copied frameworks." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH15", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@theaigrid" ], "body": { "title": "TheAIGRID", "url": "https://www.youtube.com/@theaigrid", "requested_handle": "@theaigrid", "access": "Indexed channel description and titles only", "identity": "Secondary channel metadata; primary channel not fetched", "use_condition": "Treat news and rankings as leads; verify against original release notes, papers and repeatable task tests." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH16", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@earnyourleisure" ], "body": { "title": "Earn Your Leisure", "url": "https://www.youtube.com/@earnyourleisure", "requested_handle": "@earnyourleisure", "access": "Official purpose, education and community pages; no full interview or investment analysis", "identity": "Official organization pages read; handle corroborated by secondary listing", "use_condition": "Teach original cash-flow cases and business analysis; do not repeat guest projections as verified outcomes." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH17", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@thelawacademy1" ], "body": { "title": "The Law Academy", "url": "https://www.youtube.com/@thelawacademy1", "requested_handle": "@thelawacademy1", "access": "Primary introduction-video description and channel-title metadata; no full video or transcript", "identity": "Primary video description identifies the exact handle and UK legal-education scope", "use_condition": "Record jurisdiction and recording date. English-law teaching is not automatically a rule for a United States matter." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH18", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "UNKNOWN", "review_state": "queued", "provenance": [ "https://www.youtube.com/@wincontractlaw" ], "body": { "title": "Understand Contract Law and You Win", "url": "https://www.youtube.com/@wincontractlaw", "requested_handle": "@wincontractlaw", "access": "Creator home/resources pages; no channel transcript or individual claim verification", "identity": "Creator website links the legacy WINCONTRACTLAW account; supplied modern handle not independently fetched", "use_condition": "Treat substantive legal-effect claims as questions requiring controlling text, relevant decisions, jurisdiction and contrary authority before instruction." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH19", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@crashcourse" ], "body": { "title": "Crash Course", "url": "https://www.youtube.com/@crashcourse", "requested_handle": "@crashcourse", "access": "Official course directory, about page, lateral-reading and philosophical-reasoning companion descriptions; no full course viewing or transcript review", "identity": "Primary channel description and official course directory inspected", "use_condition": "Use subject coverage and learning structure as inspiration; create original explanations, cases, exercises and visuals." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH20", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@serenityknowledge" ], "body": { "title": "Serenity Knowledge", "url": "https://www.youtube.com/@serenityknowledge", "requested_handle": "@serenityknowledge", "access": "Creator channel page and one indexed video description; no transcript review", "identity": "Creator website and a primary video description link the named channel", "use_condition": "Use original nonclinical reflection exercises. Medical and scientific assertions were not adopted or verified in this build. Creator media reuse rights are not granted." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH21", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/@munroeglobal" ], "body": { "title": "Munroe Global", "url": "https://www.youtube.com/@munroeglobal", "requested_handle": "@munroeglobal", "access": "Official about/media pages and selected indexed descriptions; no complete sermon or transcript", "identity": "Official organization pages identify its leadership, purpose and Kingdom-leadership mission", "use_condition": "Preserve theological attribution. General service exercises are original applications; no ministry doctrine or legal office is adopted from the source." }, "links": [], "version": "4.1" }, { "id": "SOURCE-CH22", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "UNKNOWN", "review_state": "queued", "provenance": [ "https://www.youtube.com/@fuelyour_soul" ], "body": { "title": "Fuel Your Soul — requested account unresolved", "url": "https://www.youtube.com/@fuelyour_soul", "requested_handle": "@fuelyour_soul", "access": "Supplied URL only; same-name podcasts and other channels excluded", "identity": "UNKNOWN: exact account and its content could not be retrieved", "use_condition": "Do not substitute a similarly named account or attribute content until this exact source is resolved." }, "links": [], "version": "4.1" }, { "id": "SOURCE-PL01", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "UNKNOWN", "review_state": "queued", "provenance": [ "https://www.youtube.com/playlist?list=PLMdDaBpKK54n4rMJnEX1L-Ky12kJBTlQ6" ], "body": { "title": "Requested playlist — title unresolved", "url": "https://www.youtube.com/playlist?list=PLMdDaBpKK54n4rMJnEX1L-Ky12kJBTlQ6", "requested_handle": "PLMdDaBpKK54n4rMJnEX1L-Ky12kJBTlQ6", "access": "Supplied playlist identifier only; page fetch did not expose contents", "identity": "UNKNOWN: title, owner and membership unavailable", "use_condition": "Keep the exact playlist identifier. No lesson or creator content has been attributed to it." }, "links": [], "version": "4.1" }, { "id": "SOURCE-PL02", "record_type": "source", "lane": "public_education", "audience": "public", "epistemic_status": "KNOWN", "review_state": "reviewed", "provenance": [ "https://www.youtube.com/playlist?list=PLYIC9RD5VKE5rft6JACKTo4TrmVK6GWzl" ], "body": { "title": "Rev. Ike’s Who Do YOU Think You Are?", "url": "https://www.youtube.com/playlist?list=PLYIC9RD5VKE5rft6JACKTo4TrmVK6GWzl", "requested_handle": "PLYIC9RD5VKE5rft6JACKTo4TrmVK6GWzl", "access": "Playlist title only; page body exposed no video list or transcript", "identity": "Primary page-title metadata available; owner and video membership not inspected", "use_condition": "An original self-concept course can pose a related question, but must not be represented as a summary of this playlist." }, "links": [], "version": "4.1" }, { "id": "INSIGHT-KN101", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-DOC01", "SOURCE-DOC02", "SOURCE-DOC08" ], "body": { "title": "Signal to Skill | original course application", "original_application": "Turn one educational source into a checked claim, original explanation, practical exercise and visible result", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-KN101-L1", "LESSON-KN101-L2", "LESSON-KN101-L3", "LESSON-KN101-L4" ], "version": "4.1" }, { "id": "LESSON-KN101-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-KN101", "SOURCE-DOC01", "SOURCE-DOC02", "SOURCE-DOC08" ], "body": { "title": "Inspect the Source", "course_id": "KN101", "lesson_id": "KN101-L1", "objective": "Make a source card that describes precisely what you accessed.", "teaching": "Before an idea enters your practice, find out what you actually have. A title is a promise about a piece of content. A description is a summary written for a purpose. A transcript records words, sometimes imperfectly. A complete video may show demonstrations that the transcript misses. These are different forms of access, and they support different conclusions.\n\nUse a source card with six fields: exact link, creator, title, date if known, access level, and the part you inspected. If you only saw a description, say that. If the date is missing, write unknown. A candid gap makes the card more useful because the next researcher knows what remains to be done.\n\nNext, ask what role the source should play. An official product manual can document intended behavior. A creator can describe a personal experience. A video can raise a good question. None of these roles automatically supplies evidence for every claim that appears nearby. A dramatic title about a business result does not show costs, the amount collected, or whether the example is typical.\n\nThis lesson uses a deliberately small standard: another learner should be able to find your source and understand the limits of your inspection. You do not need to solve every question today. You need to preserve a truthful starting point. That is how knowledge remains useful after the excitement of discovering it has passed.", "worked_example": "Fictional title: “My ten-minute system changed everything.” You accessed only its description, which mentions a daily checklist. A sound card says: “Description inspected. Daily-checklist topic identified. Effectiveness and results unverified.” It does not say the system was demonstrated or that it will work for everyone.", "evidence": [ "One six-field source card", "A truthful access statement", "One next verification question" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-KN101-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-KN101", "SOURCE-DOC01", "SOURCE-DOC02", "SOURCE-DOC08" ], "body": { "title": "Separate the Claim", "course_id": "KN101", "lesson_id": "KN101-L2", "objective": "Classify a statement and rewrite it to match its evidence.", "teaching": "Useful learning starts when a large story becomes a small statement you can examine. Write one claim per line. If a sentence says a tool is cheaper, faster, safer and easier, it contains at least four questions. Split them. A claim that is small enough to test is easier to improve.\n\nUse four working labels. KNOWN identifies what the available evidence establishes within a stated scope. INFERRED identifies a conclusion you draw from that evidence. PROPOSED identifies an idea or action you want to test. UNKNOWN identifies what the available material does not establish. These are working descriptions, not permanent grades for a person or a channel.\n\nAlso name the kind of claim. A spiritual interpretation can have meaning within a tradition. A historical claim asks what sources establish a past event. A technical claim concerns how a system works under specified conditions. A legal claim needs the relevant text, jurisdiction and judicial construction. Placing these statements in one video does not make them interchangeable.\n\nKeep the distinction between a report and the event being reported. If a description says a business made fifty thousand dollars in sales, you may know that the description makes that assertion. You do not yet know the actual sales, costs or profit. The next useful move is a verification question, not a larger conclusion.\n\nAn honest rewrite often becomes less dramatic and more useful. It gives you something you can investigate, teach accurately, or turn into a small experiment.", "worked_example": "Illustrative statement: “This AI will double your productivity.” Rewritten record: “The creator reports completing one draft faster. Independent timing, revision quality and repeat performance are unknown. Proposed test: compare two approaches on the same three fictional tasks.”", "evidence": [ "Three atomic claims", "One careful rewrite", "One possible disconfirming observation" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-KN101-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-KN101", "SOURCE-DOC01", "SOURCE-DOC02", "SOURCE-DOC08" ], "body": { "title": "Build the Evidence", "course_id": "KN101", "lesson_id": "KN101-L3", "objective": "Run a modest comparison that could reveal a problem with your idea.", "teaching": "An idea becomes more useful when it survives a fair attempt to find its limits. Start with a question small enough to answer. “Which approach is best?” is too broad. “Which of these two instructions lets a beginner complete this fictional checklist with fewer clarifying questions?” gives you a task, a comparison and an observable result.\n\nWrite the success criteria before you see the result. For a short instruction, you might check whether the reader can identify the purpose, the first action and the completed output. Use the same task and available time for each candidate. When conditions differ, record the difference rather than pretending the comparison is controlled.\n\nA test log needs the starting point, procedure, observed result, defects and next decision. Include at least one case that might fail. An instruction for a practice timer should address an empty input or a second press of the Start button. A lesson should address a learner who cannot access the optional video.\n\nSmall tests are useful because they reduce guesswork. They are limited because their conditions are narrow. Three successful attempts do not establish universal reliability. A personal week of practice cannot prove that the practice caused every change in your life. Say exactly what you observed and where you have not tested the idea.\n\nA failed test is usable evidence. It identifies something to change. The goal is a better decision, not a perfect-looking report.", "worked_example": "Fictional test: two versions of a lesson instruction are given to the same reviewer in a shuffled order. The reviewer can identify the output in Version B but asks two questions about Version A. Record that observation. Do not claim Version B has been proven superior for all learners.", "evidence": [ "A comparison log with identical task conditions", "One edge case", "One bounded conclusion" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-KN101-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-KN101", "SOURCE-DOC01", "SOURCE-DOC02", "SOURCE-DOC08" ], "body": { "title": "Teach What You Can Show", "course_id": "KN101", "lesson_id": "KN101-L4", "objective": "Create an original explanation and practical assessment linked to evidence.", "teaching": "Teaching is a useful test of your own understanding. Explain the principle without borrowing the creator’s distinctive story, narration or visual sequence. You can acknowledge the source that prompted the question while making your own example, exercise and explanation.\n\nBuild the lesson around the learner’s output. Start by naming what the learner will be able to produce. Then provide only the explanation needed to reach that result. Show a worked example, give the learner a fresh case and make the assessment ask for application. Watching and agreeing are different from demonstrating a skill.\n\nUse a compact evidence chain: source, claim, original insight, exercise, learner artifact and reflection. Every factual statement that matters should lead back to support. Every creative addition should be recognizable as your interpretation or proposed application. This makes correction possible. If a source changes, you can find the lesson that depends on it.\n\nFinish by naming one limit and one next step. A beginner lesson may teach a component map without preparing someone to administer a production server. A reflection may help a learner notice a pattern without diagnosing its cause. Honest boundaries help the learner choose the next learning task.\n\nYou now have a complete cycle. You found a source, described your access, separated the claim, tried a small application and taught what you could show. Repeat that cycle on a useful problem, and your learning produces a record that another person can build on.", "worked_example": "Original lesson concept: “Make one instruction easier to use.” Objective: produce an instruction with a purpose, first action and completion evidence. Worked example: rewrite “organize your work” as “name one task, work for ten minutes and save one visible change.” Assessment: improve a different vague instruction and explain why it is clearer.", "evidence": [ "Original one-page lesson", "Worked example and fresh exercise", "Answer key, source link and limit" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-MA101", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-CH01", "SOURCE-CH13", "SOURCE-CH14" ], "body": { "title": "Attention into Action | original course application", "original_application": "Complete a seven-day practice that turns a chosen value into visible work and an honest reflection", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-MA101-L1", "LESSON-MA101-L2", "LESSON-MA101-L3", "LESSON-MA101-L4" ], "version": "4.1" }, { "id": "LESSON-MA101-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA101", "SOURCE-CH01", "SOURCE-CH13", "SOURCE-CH14" ], "body": { "title": "Choose the Standard", "course_id": "MA101", "lesson_id": "MA101-L1", "objective": "Turn a chosen value into one behavior you can control.", "teaching": "A standard becomes useful when it tells you what to do in an ordinary moment. “I am a builder” may express an aspiration. Saving one useful change to a project makes that aspiration visible. The purpose of this lesson is to connect meaning with conduct you can observe.\n\nChoose one value that matters to you: clarity, care, skill, service, patience or another value in your own language. Describe one action that would express it during the next seven days. Keep the action small enough to fit the time you actually have. If you have ten minutes after breakfast, a ten-minute practice is more workable than a plan that depends on an uninterrupted afternoon.\n\nSeparate the action from an external outcome. You can write a useful page, finish an exercise or test an instruction. You cannot directly control whether another person praises it, buys it or responds on your preferred schedule. This distinction gives you a fair basis for reviewing your effort.\n\nIf spiritual language helps you, use it as a chosen interpretation. You may describe the practice as alignment, remembrance or transmutation. Label that meaning honestly. The observation record will still describe minutes, actions, outputs and context. It does not establish a physical change in timelines.\n\nBegin with a baseline. Estimate how many focused sessions and usable outputs you completed in the previous week. Mark an estimate as an estimate. Your aim is to see your own pattern more clearly and choose a useful next action.", "worked_example": "Illustrative standard: “I practice service through clarity.” Controllable action: spend ten minutes making a one-page checklist easier for a beginner to use. External outcome: whether people choose to use it. Baseline estimate: two sessions last week and one rough draft.", "evidence": [ "One value-to-action statement", "A small named artifact", "Controllable action, external outcome and baseline" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MA101-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA101", "SOURCE-CH01", "SOURCE-CH13", "SOURCE-CH14" ], "body": { "title": "Design the Practice", "course_id": "MA101", "lesson_id": "MA101-L2", "objective": "Create a ten-minute session and a recovery plan for interruptions.", "teaching": "A practice needs a place in your real day. Choose a cue that already occurs, such as finishing breakfast or closing the workday. Write the next action so plainly that you can begin without negotiating with yourself: open the draft, choose one improvement and work on it until the timer ends.\n\nFor this course, try one minute to choose the change, eight minutes to make it and one minute to record the result. This is an original teaching structure, not a scientifically established ideal interval. You can adjust it after observing what works for you.\n\nKeep the first action small. A task called “build my business” asks you to resolve too many decisions. A task called “write the three steps of my intake checklist” gives you a starting point. Put new research questions on a later list so they do not consume the practice session.\n\nInterruptions are information. Plan a two-minute minimum for a suitable later cue: open the file, make one useful edit and record it. If circumstances prevent even that, record the missed session honestly and resume. There is no need to double the work or turn a difficult day into a judgment about your identity.\n\nBefore the first session, remove one avoidable obstacle. Keep the draft easy to find, write tomorrow’s first action at the top of the page or prepare the tool in advance. Then run the session and save something visible. Your practice card should make starting easier and make review more accurate.", "worked_example": "Practice card: After breakfast, open “Community Welcome Checklist.” Minute 1: choose the instruction to improve. Minutes 2–9: revise and try it. Minute 10: save a version and record what changed. Recovery: after lunch, spend two minutes making one edit if the morning session was missed.", "evidence": [ "Completed practice card", "First saved output", "Recovery plan" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MA101-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA101", "SOURCE-CH01", "SOURCE-CH13", "SOURCE-CH14" ], "body": { "title": "Read the Pattern", "course_id": "MA101", "lesson_id": "MA101-L3", "objective": "Keep a seven-day record without confusing an observation with an explanation.", "teaching": "A practice log should help you see the day clearly. Record the planned cue, whether you began, actual minutes, visible output and relevant context. Add a brief optional observation about focus or energy if it helps you. Keep private reflection private.\n\nFor the seven-day build, use a simple progression. Day 1: choose the audience, problem and smallest useful artifact. Day 2: make a rough complete version. Day 3: add a worked example. Day 4: try it on a fictional case. Day 5: fix the clearest problem. Day 6: test from a blank start. Day 7: finish and review. Adapt the sequence to your artifact rather than treating it as a rule of nature.\n\nLook for friction you can change. If you spend the first six minutes finding the file, prepare the file before the cue. If the task keeps growing, reduce its scope. If your available time changes, record the constraint and adjust the plan. These are design choices, not evidence that you lack worth or discipline.\n\nBe careful with explanations. “I used the cue and completed four sessions” is an observation. “The cue caused every improvement in my week” is a much larger claim. Sleep, workload, support and other circumstances may affect the result. A short personal experiment can help you learn about your situation without proving a universal method.\n\nKeep both the work and the record. A short sentence about the session is useful; a saved draft, tested checklist or corrected explanation shows what the session produced.", "worked_example": "Fictional log: Day 3, eight actual minutes, example added. Context: an interruption shortened the session. Adaptation: tomorrow’s first sentence is written in advance. This gives you a concrete adjustment without treating the interruption as a personal failure.", "evidence": [ "Seven dated observations, including any missed sessions", "Saved output references", "At least one adaptation based on a recorded barrier" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MA101-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA101", "SOURCE-CH01", "SOURCE-CH13", "SOURCE-CH14" ], "body": { "title": "Keep the Useful Change", "course_id": "MA101", "lesson_id": "MA101-L4", "objective": "Review the evidence and choose one practical continuation.", "teaching": "At the end of the week, place your baseline, daily log and finished work together. Count completed sessions, actual minutes and usable outputs. Then ask whether the work is clearer or more useful according to the criteria you chose. Do not substitute the feeling of being busy for a look at the artifact.\n\nWrite a short debrief in four parts: what happened, what you controlled, what else may explain the result and what you will repeat or change. Include one difficulty and one successful adjustment. A mixed result can still teach you something useful.\n\nKeep the meaning that serves your values. If you experienced the week as an expression of spiritual growth, you can say that as personal reflection. Keep the practical evidence separate: a completed draft, a more consistent cue, a tested instruction or a clearer next step. You do not need to exaggerate the evidence to honor the experience.\n\nChoose a continuation that fits your next week. Repeat the same cue, shorten the task, change the environment or move to a new artifact. Change one major element at a time when you want a clearer comparison. If the practice was not useful, you can stop and choose a different method.\n\nYour final evidence is something you made and something you learned about making it. Share the artifact only when you want to and can do so without exposing private notes. The standard you chose now has an ordinary form: an action, a record and a decision about what comes next.", "worked_example": "Fictional debrief: “I completed five of seven sessions and finished a welcome checklist. Preparing the file helped me start. Two evenings were unavailable. Next week I will keep the cue and reduce the new task to one example page.” This is a useful result without a promise of customers or income.", "evidence": [ "Finished small artifact", "Four-part debrief", "Specific repeat/adapt/stop decision" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-AI101", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-DOC01", "SOURCE-DOC03" ], "body": { "title": "Build One Useful Thing with AI | original course application", "original_application": "Specify, prototype and test a simple local learning tool with visible acceptance evidence", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-AI101-L1", "LESSON-AI101-L2", "LESSON-AI101-L3", "LESSON-AI101-L4" ], "version": "4.1" }, { "id": "LESSON-AI101-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-AI101", "SOURCE-DOC01", "SOURCE-DOC03" ], "body": { "title": "Write the Job", "course_id": "AI101", "lesson_id": "AI101-L1", "objective": "Specify a small tool before asking AI to build it.", "teaching": "A useful AI build begins with a clear job. Name the person, the task and the result they need to see. For this course, the person is a learner with ten minutes available. The task is to start, pause and reset a practice session. The result is a readable countdown and an obvious completion state.\n\nWrite constraints before generating code. Our starter tool runs in a local browser file, makes no network requests and requires no account. It stores no journal, password or private record. The original version uses a fixed ten-minute session so that the first build remains small.\n\nDefine acceptance checks as observable behavior. Starting the timer should reduce the displayed time. Pausing should hold it steady. Resetting should restore ten minutes and clear the running state. Pressing Start twice should not create two simultaneous countdowns. A shortened test session should reach zero, stop and display completion without a negative time.\n\nThese checks guide the build and the review. They also give you a way to compare AI help. A confident explanation does not establish that the code works. A screenshot of a page does not establish that the pause button works. You need the right evidence for each requirement.\n\nWrite a scope boundary. Publishing, adding accounts, handling payments and collecting personal data are separate jobs. A local timer can be a complete first tool while those other jobs remain outside this exercise. Finish the small job, then decide what the next version needs.", "worked_example": "Original brief: “Create a ten-minute practice timer for an adult learner. Provide Start, Pause and Reset. Show mm:ss. Run locally without external resources. Preserve the behavior when Start is pressed twice. At zero, stop and display ‘Session complete.’ Include clear code comments and a short test plan.”", "evidence": [ "One-page tool brief", "Five acceptance cases", "One clear scope boundary" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-AI101-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-AI101", "SOURCE-DOC01", "SOURCE-DOC03" ], "body": { "title": "Compare the Help", "course_id": "AI101", "lesson_id": "AI101-L2", "objective": "Compare two prompts or models using the same task and evidence.", "teaching": "AI comparison is useful when the comparison serves your task. Pick two candidates: two prompts with one tool, or two tools if you already have authorized access. Keep the job, constraints, sample inputs and available time the same. Record the model or tool name and date when available because behavior can change.\n\nAsk Candidate A for an implementation from the brief. Ask Candidate B for an implementation plus a review against the five acceptance cases. These are two different approaches, so record that difference. If you compare two models, use an identical prompt instead. Do not change both the model and the prompt and then attribute the entire difference to one cause.\n\nScore outputs on observed behavior: required controls, acceptance cases passed, external dependency use, clarity and defects. Keep time and cost only if you actually measured them. A quoted subscription price is not your actual cost for this task. A winner on a tiny timer task is not the best model for every job.\n\nTreat generated code as something to inspect. Look for unexpected external scripts, network calls or requests for credentials. This starter task needs none. Do not run unreviewed commands merely because an answer includes them. You can use the supplied prototype to practice evaluation without sending a prompt to a paid service.\n\nThe useful result is a decision tied to your brief: which candidate is a better starting point, what you still need to fix and what you learned about asking for help.", "worked_example": "Fictional comparison: Candidate A has all buttons but pressing Start twice speeds up the countdown. Candidate B prevents duplicate starts but uses an external font. Both need revision under the local-only brief. The correct conclusion is a defect list, not a forced winner.", "evidence": [ "Two-candidate comparison table", "Observed defects or an explicit unrun plan", "A bounded decision tied to the brief" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-AI101-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-AI101", "SOURCE-DOC01", "SOURCE-DOC03" ], "body": { "title": "Build the Small Version", "course_id": "AI101", "lesson_id": "AI101-L3", "objective": "Use and explain a complete local prototype.", "teaching": "Download the included practice timer and open the HTML file in a browser. The starter prototype is an original teaching example. It uses a page for the controls, styles for readability and JavaScript for the state and timing behavior. It does not need a server or an API key.\n\nIdentify its state: remaining milliseconds, whether it is running, the time it started and the interval used to refresh the display. Starting sets a reference time. The display derives remaining time from elapsed time rather than assuming every refresh happens at exactly the scheduled moment. Browsers may delay callbacks, especially in background tabs, so elapsed-time calculation matters. Background behavior still needs testing on the browser you intend to use.\n\nPausing records the current remaining time and clears the refresh interval. Resetting pauses and restores the initial duration. A guard prevents a second Start press from creating another running interval. When the remaining time reaches zero, the tool stops and displays a completion message.\n\nMake one modest change if you are comfortable editing a copy: change the heading or improve a button label. Ask an AI tool for an explanation of that specific change if needed. Keep the five behavior requirements intact. Do not add accounts, remote tracking or private information to make the demonstration seem more advanced.\n\nSave the starting file and your changed copy under distinct names. Explain what changed and how you checked it. You have now moved from requesting an output to understanding and reviewing a small working artifact.", "worked_example": "Original change request: “Replace the heading ‘Practice Timer’ with ‘My Ten-Minute Build.’ Keep the duration and button behavior unchanged.” Evidence: two files, a visible heading change and a rerun of the acceptance cases.", "evidence": [ "Opened local prototype", "Component explanation", "One versioned change or an observation record if you did not edit" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-NET101", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-DOC04", "SOURCE-DOC05", "SOURCE-DOC11", "SOURCE-DOC12" ], "body": { "title": "Own Your Digital Foundations | original course application", "original_application": "Map a digital service and design a modest continuity test with explicit tradeoffs", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-NET101-L1", "LESSON-NET101-L2", "LESSON-NET101-L3", "LESSON-NET101-L4" ], "version": "4.1" }, { "id": "LESSON-NET101-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-NET101", "SOURCE-DOC04", "SOURCE-DOC11" ], "body": { "title": "Map the Path", "course_id": "NET101", "lesson_id": "NET101-L1", "objective": "Distinguish a device, local network, internet connection and hosted service.", "teaching": "A digital service depends on more than the screen you see. Start by naming the device, the local connection, the route to any remote service, the application and the place where its data lives. A simple dependency map is more useful than a long list of technical words without relationships.\n\nCompare two fictional learning tools. Tool A is the included HTML timer opened as a local file. Its basic controls do not require a remote server. Tool B is a hypothetical account-based learning site that loads lessons and progress from hosted services. Turning off the internet may affect these tools differently. The success of A does not establish that B will work offline.\n\nFor a hosted page, a device typically uses network services to reach a named destination and exchange requests with a server. A domain name, internet access and an application login serve different purposes. A problem at one stage should not automatically be diagnosed as a problem at every other stage.\n\nDraw the connections and label what each carries. Keep credentials out of the diagram. You can write “account authentication” without recording a password. Add the person or organization responsible for each component and mark responsibility you have not established as unknown.\n\nEnd with one interruption question: which function should remain useful when a particular dependency fails? Answer for a stated task, such as reading an already-downloaded lesson. “The whole ecosystem stays online” is not a small enough claim for this exercise. Your map should help you choose a test you can actually run.", "worked_example": "Dependency map A: browser → local HTML timer file. Map B: browser → local network → internet connection → hosted lesson service → authorized progress store. These are teaching models. The actual live learning site’s implementation has not been inspected in this lesson.", "evidence": [ "Two annotated dependency maps", "Responsibility and unknowns list", "One bounded interruption question" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-NET101-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-NET101", "SOURCE-DOC04", "SOURCE-DOC12" ], "body": { "title": "Package the Work", "course_id": "NET101", "lesson_id": "NET101-L2", "objective": "Explain the roles of an image, container, configuration and durable storage.", "teaching": "Packaging a tool helps another environment run a similar application setup. In Docker’s model, an image supplies the application package and a container is a running instance created from it. That distinction helps you ask what is being distributed and what is currently executing.\n\nKeep durable data separate in your component map. Docker documents volumes as storage managed outside a container’s writable layer. A volume’s presence does not establish a backup, a restoration procedure or permission for every user to read the contents. Those require separate design and evidence.\n\nUse a fictional lesson app to identify four categories: application package, runtime configuration, durable learning data and secrets. A page title belongs with application content. A permitted service endpoint may belong in configuration. Learner submissions belong in the appropriate data store. A private token is not ordinary public application content.\n\nYou do not need to install a container runtime for this conceptual exercise. Describe how a replacement application instance would find its authorized configuration and data, and what remains uncertain. Avoid including real passwords, keys or trust records in the diagram or a learning fixture.\n\nThen ask about the lifecycle. If the application is replaced, what should remain? If the data is lost, what restores it? If a credential changes, who is authorized to update it? A useful package is one component in an operating system of responsibilities. The map should make these separate questions easier to see, rather than imply that containerization solves every continuity or security problem.", "worked_example": "Fictional component map: the lesson interface is packaged; the allowed database address is configuration; submitted work is durable data; the access token is a secret. A replacement interface is not proof that learner data was restored or that access permissions are correct.", "evidence": [ "Component classification", "Original two-sentence explanation", "Lifecycle and unresolved-control notes" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-NET101-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-NET101", "SOURCE-DOC11", "SOURCE-DOC12" ], "body": { "title": "Design for Interruption", "course_id": "NET101", "lesson_id": "NET101-L3", "objective": "Create a modest continuity plan with a measurable recovery target.", "teaching": "Continuity begins with a task you want to preserve. Choose a small one: an adult should be able to read a downloaded public lesson and use the local timer during a short internet interruption. State what the exercise does not attempt, such as recording progress in a remote account system.\n\nList the required assets, their authorized location and the person responsible for maintaining them. Use public lesson files and dummy progress records. Decide how a replacement copy would be obtained and how you would check that it is the intended version. A filename alone may not establish integrity; a content hash can help compare bytes without proving the content is true or complete.\n\nSet a proposed recovery target that you can measure. For example, aim to locate and open the correct public lesson copy within five minutes. This is a learning target, not a guaranteed service level. Record how much data loss the scenario assumes and which records are excluded.\n\nRehearse with a copy, not by disrupting a live service. Disconnecting a test device from the internet can answer a local question without changing production settings. If a step needs permission or equipment you lack, leave it unrun and record what is missing.\n\nA recovery plan becomes stronger when another person can follow it. Keep the instructions short, identify the starting condition and name the observation that would count as success. Restoring a file is different from restoring every function of an application. The evidence should state precisely which task was recovered.", "worked_example": "Proposed rehearsal: with a test device offline, find the approved public lesson copy, open it and start the timer within five minutes. Remote progress synchronization is excluded. If the file is missing, record a failed retrieval and improve the authorized backup instruction.", "evidence": [ "Task-specific continuity plan", "Asset and responsibility list", "Measurable proposed target and exclusions" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-NET101-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-NET101", "SOURCE-CH03", "SOURCE-DOC05", "SOURCE-DOC11" ], "body": { "title": "Measure Before You Expand", "course_id": "NET101", "lesson_id": "NET101-L4", "objective": "Produce a repeatable local test record and a bounded next decision.", "teaching": "A useful infrastructure demonstration needs more than a successful moment. Record the environment, starting condition, procedure, expected result and actual observation. For this course, test the public lesson copy and local timer rather than claiming a complete independent communications network.\n\nName the device, browser, file version and connection condition. Try the defined task, measure the elapsed time and save the result. If you cannot run the test, provide the plan and label it unrun. Do not replace missing observations with a confident description of what should happen.\n\nLook for limits that matter to the next choice. Opening a file does not test account synchronization, another device, a power outage or a radio link. A downloaded resource can improve local availability while still requiring maintenance, storage and a clear update process.\n\nData Slayer’s network builds raise a useful research direction: how could communities maintain more of their own communications infrastructure? Reticulum’s documentation describes a networking stack that can use different carriers. That is a starting point for technical study, not evidence of a particular range, availability or deployment in this ecosystem. Hardware, legal transmission conditions and actual field behavior need a separate, authorized project before any radio deployment.\n\nEnd with a decision proportionate to your evidence. You might keep the local lesson pack, correct the retrieval instructions or study a network dependency next. Expansion is useful when it answers a demonstrated need. Your capstone is the dependency map, component map, continuity plan and actual test record or honestly unrun plan.", "worked_example": "Illustrative result: “The named public lesson copy opened on the test laptop with Wi-Fi disabled in 42 seconds. The local timer started. Remote progress, phone behavior, power-loss recovery and radio communication were not tested.” Replace this sample with actual observations.", "evidence": [ "Repeatable test record or explicit unrun plan", "Scope and limits statement", "Evidence-based next decision" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-BIZ101", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-DOC09" ], "body": { "title": "The Useful Business Lab | original course application", "original_application": "Produce an evidence-backed offer hypothesis, cost model and delivery test", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-BIZ101-L1", "LESSON-BIZ101-L2", "LESSON-BIZ101-L3", "LESSON-BIZ101-L4" ], "version": "4.1" }, { "id": "LESSON-BIZ101-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-BIZ101", "SOURCE-DOC09" ], "body": { "title": "Find the Recurring Problem", "course_id": "BIZ101", "lesson_id": "BIZ101-L1", "objective": "Write a buyer-problem hypothesis that could be disproved.", "teaching": "A business story can make an opportunity sound obvious. A useful offer hypothesis is narrower: a particular buyer experiences a particular problem at a particular time and already uses some workaround. That statement gives you something to investigate.\n\nUse our fictional service: organizing a small business’s non-sensitive training files into a clear folder structure. The proposed buyer is an owner who onboards occasional contractors. The possible problem is time spent locating the latest instruction. The current workaround might be asking the owner each time. These are assumptions in a teaching case, not evidence that this market is already waiting to buy.\n\nAsk about actual behavior. What happened the last time someone needed an instruction? Where did they look? What took time? Who decided whether to change the process? A question about a past event is usually more informative for this exercise than asking whether a person likes your idea. Compliments alone do not establish willingness to pay.\n\nAlso identify constraints: permission to handle files, delivery limits, information sensitivity, existing alternatives and the buyer’s ability to implement the change. A useful problem can still be unsuitable for your proposed service. Keep that possibility open.\n\nFinish with a hypothesis and a disconfirming observation. For example: if likely buyers already have a working, maintained system and do not report meaningful retrieval difficulty, the proposed problem may not justify this offer. That is useful evidence for revising or stopping the idea before expanding it.", "worked_example": "Hypothesis: “Owners who repeatedly onboard contractors may need a clearer way to locate current training instructions.” Disconfirming observation: the people interviewed consistently retrieve current instructions quickly and do not identify a meaningful cost or failure. No actual interviews have been conducted by this build.", "evidence": [ "Buyer-problem card", "Five neutral interview questions", "Disconfirming observation and scope constraints" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-BIZ101-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-BIZ101", "SOURCE-DOC09" ], "body": { "title": "Count the Whole Cost", "course_id": "BIZ101", "lesson_id": "BIZ101-L2", "objective": "Calculate the fictional service’s cash contribution and owner-time-adjusted result.", "teaching": "A sales number does not describe what remains after delivering the work. Build a small model with separate lines for price, variable cash costs, fixed cash costs and owner time. Label the model as simplified and keep taxes, unpriced work and other missing items visible.\n\nOur fictional service charges 120 dollars per job. Variable cash costs are 30 dollars per job, leaving 90 dollars of cash contribution before fixed costs. Monthly fixed cash costs are 300 dollars. At ten jobs, sales are 1,200 dollars, variable cash costs are 300 dollars and the simplified cash surplus before taxes and owner pay is 600 dollars.\n\nNow value the owner’s time for analysis. If each job takes two hours and the chosen planning value is 25 dollars per hour, ten jobs use twenty hours valued at 500 dollars. Subtracting that planning value leaves 100 dollars in the simplified owner-time-adjusted result. This is not a formal accounting profit calculation or proof of an achievable income.\n\nCompare six, ten and fourteen jobs. The cash surplus is respectively 240, 600 and 960 dollars before taxes and owner pay. The corresponding time-adjusted result is minus 60, 100 and 260 dollars under the stated assumptions. Extra administrative hours could reduce it further and are not yet modeled.\n\nThe cash break-even threshold is four whole jobs because 300 divided by 90 is just over three. Including the chosen per-job time value gives a contribution of 40 dollars and a threshold of eight whole jobs. These calculations clarify assumptions; they do not establish demand, capacity or an appropriate real price.", "worked_example": "Ten-job base case: sales 1,200 − variable cash costs 300 − fixed cash costs 300 = 600 before taxes and owner pay. Owner-time planning value: 10 × 2 × 25 = 500. Time-adjusted result: 100. Missing items include additional admin time, tax treatment and any unlisted costs.", "evidence": [ "Three-scenario cost model", "Break-even calculations with whole-job rounding", "Explicit exclusions and assumptions" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-BIZ101-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-BIZ101", "SOURCE-DOC09" ], "body": { "title": "Test the Offer", "course_id": "BIZ101", "lesson_id": "BIZ101-L3", "objective": "Design a bounded learning test with predeclared revise and stop conditions.", "teaching": "An early test should answer one useful question. For our fictional offer, ask whether likely buyers describe a recurring retrieval problem that they want to address and whether the proposed delivery can be understood. A small exploratory test cannot establish the size of the whole market.\n\nPrepare a one-page concept with the intended buyer, problem, included work, exclusions, delivery evidence and unanswered questions. Use dummy files. Do not request customer passwords or private records to make the test look realistic. The service concept can be rehearsed before any real access is authorized.\n\nWrite interview questions that invite disagreement. Ask about the last occurrence, its consequences, the current workaround, who owns the decision and what would make a new approach unsuitable. Avoid promising savings you have not measured. If the participant does not have the problem, record that answer.\n\nChoose a learning rule before collecting results. For example, after five exploratory conversations, continue refining only if at least three participants describe the specified recurring problem and a practical buyer can be identified. This is a proposed decision rule for this exercise, not a statistically validated demand threshold. A different result may call for revising the audience or stopping the offer.\n\nNo outreach is performed by this lesson. It produces the concept, questions and decision rules. Any actual contact must occur within the user’s authorized context and the recipient’s applicable expectations. The evidence packet must say whether interviews were planned or completed; do not turn a proposed test into reported traction.", "worked_example": "Proposed test record: five conversations planned; zero completed. Continue condition: at least three concrete recurring-problem reports and a clear buyer. Revise condition: the problem exists but the buyer or scope differs. Stop condition: no meaningful recurrence or delivery requires access outside the proposed scope.", "evidence": [ "Concept sheet", "Interview plan and decision rules", "Truthful execution status" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-BIZ101-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-BIZ101", "SOURCE-DOC09" ], "body": { "title": "Deliver Before You Scale", "course_id": "BIZ101", "lesson_id": "BIZ101-L4", "objective": "Rehearse one scoped delivery and make a capacity-aware decision.", "teaching": "A promising offer still needs a delivery process. Use dummy training files and run one job from intake to handoff. Define what arrives, what you do, what the customer receives and what counts as complete. Keep actual time and defects in the record.\n\nFor this fictional service, intake includes five dummy files, a stated naming convention and a list of intended users. Delivery produces a folder map, a current-file index and a one-page maintenance instruction. The exercise excludes legal records, access credentials, sensitive client information and any claim of regulatory compliance.\n\nTime the rehearsal. If the model assumed two hours and the delivery takes three, revise the model rather than hiding the extra hour. Record rework, missing inputs and questions that the instructions did not answer. A useful handoff lets the next person identify which file is current and how to update the index.\n\nThen consider capacity. Ten jobs at two hours require twenty delivery hours, before the extra administration you have not priced. If your available time is lower, projected sales cannot simply be treated as available capacity. If quality depends entirely on you remembering undocumented steps, the process is not ready to multiply.\n\nEnd with continue, revise or stop. A revised checklist and a smaller offer can be a better result than a premature launch. Your capstone consists of the problem hypothesis, cost model, test plan and rehearsal evidence. Together they show how you evaluate a useful service without confusing an attractive story with demand, profit or delivery readiness.", "worked_example": "Fictional rehearsal: the folder map is complete, but a reviewer cannot tell how to replace an outdated file. Add a maintenance instruction, repeat that step and record the extra time. Update the cost model if the observed delivery no longer fits the original two-hour assumption.", "evidence": [ "Delivery checklist and dummy artifact", "Time-and-defect record", "Updated model and bounded decision" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-MON101", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-DOC06", "SOURCE-DOC10" ], "body": { "title": "Money in Motion | original course application", "original_application": "Build a dated cash-flow calendar and explain one decision using timing, costs and uncertainty", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-MON101-L1", "LESSON-MON101-L2", "LESSON-MON101-L3", "LESSON-MON101-L4" ], "version": "4.1" }, { "id": "LESSON-MON101-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MON101", "SOURCE-DOC06", "SOURCE-DOC10" ], "body": { "title": "See the Timing", "course_id": "MON101", "lesson_id": "MON101-L1", "objective": "Build a dated cash-flow sequence and find a timing gap.", "teaching": "A monthly total answers one question: how much money is expected to come in and go out over the month? A dated cash-flow record answers another: what is available at each point in time? A plan can finish positive while going negative before an expected receipt arrives.\n\nUse the fictional case supplied with this course. Begin with 250 dollars. On Day 1, 900 dollars arrives. On Day 2, a 1,000-dollar housing payment leaves. Groceries cost 120 dollars on Day 3. A 90-dollar utility payment is scheduled for Day 5. Another 900 dollars is expected on Day 8. Record the opening amount once, then add receipts and subtract payments in order.\n\nAfter Day 3, the balance is 30 dollars. After the scheduled Day 5 payment, the projected balance is minus 60 dollars. That is a planning gap, not a prediction that the bank will process the transaction or authorize an overdraft. Fees, holds and actual payment behavior are outside this simplified case. The second receipt does not solve the earlier date simply by appearing in the same month.\n\nKeep uncertain receipts separate from confirmed receipts. A possible gift or hoped-for sale can be useful context, but including it as available money hides a dependency. Write the question that needs resolving: amount, date, availability or obligation. The purpose of this first exercise is a clear sequence and an honest gap, before choosing any response.", "worked_example": "Case sequence: opening 250 → Day 1 receipt 900 gives 1,150 → Day 2 housing 1,000 leaves 150 → Day 3 groceries 120 leaves 30 → Day 5 utility 90 creates a projected 60-dollar gap. The full fictional period ends at 450, so its positive ending does not erase the earlier gap.", "evidence": [ "Dated cash-flow sequence", "First gap and projected amount", "Uncertainty note" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MON101-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MON101", "SOURCE-DOC06", "SOURCE-DOC10" ], "body": { "title": "Separate the Buckets", "course_id": "MON101", "lesson_id": "MON101-L2", "objective": "Distinguish a balance, an obligation and a proposed reserve without counting cash twice.", "teaching": "A cash balance tells you what a record shows at a moment. It does not automatically tell you what is free for a new decision. Some payments may already be committed, pending or scheduled. A useful worksheet gives each amount one role and one date.\n\nIn our fictional case, the opening 250 dollars is counted once. Do not add a savings bucket, a buffer label or a credit limit as if it creates more cash. A planned reserve is a purpose assigned to money that exists or is expected; it is not another receipt. A credit limit is not included in this exercise as household cash.\n\nRecord obligations by date and identify whether they have already been paid, are pending or remain planned. Avoid subtracting the same payment once as pending and again as future spending. When the actual account and the worksheet differ, preserve the difference and investigate it. Do not edit the figure merely to make the plan balance.\n\nRun a small sensitivity check. If the second 900-dollar receipt arrives one day later, which scheduled payments depend on its original date? If a provider confirmed a different due date, what would change? A proposed rearrangement remains a scenario until the relevant party confirms it. This exercise does not authorize delaying an obligation.\n\nThe record becomes useful when another person can reconstruct your arithmetic. State the opening amount, inflows, outflows, assumptions and uncertainty. A small plan with a visible limitation is more reliable than an impressive total with money counted twice.", "worked_example": "The case contains 250 opening cash and 1,800 in receipts. Its 1,600 in payments leaves 450 at the end. Labeling 100 of the opening cash “buffer” does not increase the ending balance to 550. If that 100 is committed, record the commitment without creating a second inflow.", "evidence": [ "Reconciliation to $450", "Payment-status list", "Corrected duplicate and delayed-receipt scenario" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MON101-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MON101", "SOURCE-DOC06" ], "body": { "title": "Read the Offer", "course_id": "MON101", "lesson_id": "MON101-L3", "objective": "Compare two fictional offers using all stated costs, timing and missing terms.", "teaching": "A headline price is one part of an offer. A fair comparison fixes a period, includes the stated charges and records the terms that remain unknown. Begin by choosing the same use period for both options.\n\nConsider two fictional learning subscriptions. Option A is 12 dollars monthly with no stated setup charge. Option B is 99 dollars annually with a 20-dollar setup charge. Over twelve months, the stated base charges are 144 dollars for A and 119 dollars for B. The difference is 25 dollars under these stated assumptions. Taxes, other fees and the value of flexibility have not been supplied.\n\nNow consider the use period. Someone who needs only three months might pay 36 dollars under A if monthly cancellation is available on the stated terms. An annual commitment cannot be treated as a three-month price unless its terms actually permit that treatment. A simple division can describe an average monthly cost while hiding when the full payment is due.\n\nWrite questions about renewal, cancellation, refunds, access and additional fees. Do not invent favorable answers. If a discount expires or the renewal price is unknown, label it. The lowest stated total is not automatically the best choice for every person; available cash, expected use and contractual terms matter.\n\nYour evidence is a comparison another learner can audit. It should show the period, arithmetic, payment timing and unanswered questions. The decision can remain open when a missing term could change it.", "worked_example": "At twelve months, the stated base cost is A: 12 × 12 = 144; B: 99 + 20 = 119. At three months, A may total 36 if its cancellation terms permit stopping then. B remains a 119-dollar stated commitment unless an actual refund or shorter-term provision says otherwise.", "evidence": [ "Cost comparison with period", "Payment timing and exclusions", "Three unresolved terms" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MON101-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MON101", "SOURCE-DOC06", "SOURCE-DOC10" ], "body": { "title": "Hold the Review", "course_id": "MON101", "lesson_id": "MON101-L4", "objective": "Run a ten-minute review with a documented question and next action.", "teaching": "A short money review works best when it has a defined job. For this exercise, the job is to identify the next timing question in a fictional two-week plan. The meeting does not need to solve every financial issue at once.\n\nUse four steps. First, reconcile the opening amount with what actually moved in the example. Second, inspect upcoming dates and uncertain receipts. Third, compare one possible response as a scenario. Fourth, record the question, responsible person and next check. Keep assumptions visible when you discuss a possible change.\n\nReturn to the Day 5 utility gap. One scenario moves that payment to Day 8 after the receipt, but it can be considered an available option only if the relevant provider confirms the arrangement and its terms. Another scenario changes the opening amount, but the record must identify where that money would actually come from. Neither scenario creates cash through arithmetic.\n\nUse calm, specific language: “The base case shows a 60-dollar gap on Day 5. We need to confirm the payment date and any permitted alternative.” Avoid turning the worksheet into a judgment about a person’s character. A useful discussion produces a clearer decision record.\n\nFinish with the exact next question and a date for checking the answer. If information is missing, an unresolved decision is a valid outcome. Your completed calendar, comparison and review note show the skill taught here: making timing and assumptions visible so the next action can be considered with better information.", "worked_example": "Fictional review note: “Base case ends at 450 and first reaches minus 60 on Day 5. Proposed scenario: utility payment on Day 8 after receipt. Confirmation of permission, fees and revised due date is still required. Current plan remains unchanged until the missing facts are known.”", "evidence": [ "Completed review agenda", "Scenario with assumptions", "Decision or explicit unresolved question" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-CIV101", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-DOC07", "SOURCE-DOC13" ], "body": { "title": "Words, Authority & the Record | original course application", "original_application": "Write a research brief distinguishing word history, governing text, court reasoning and an unresolved application question", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-CIV101-L1", "LESSON-CIV101-L2", "LESSON-CIV101-L3", "LESSON-CIV101-L4" ], "version": "4.1" }, { "id": "LESSON-CIV101-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CIV101", "SOURCE-DOC07" ], "body": { "title": "Read the Word in Context", "course_id": "CIV101", "lesson_id": "CIV101-L1", "objective": "Separate ordinary meaning, word history and a legally defined use.", "teaching": "Words matter, and their setting matters. Start a word study by writing the actual question. Are you asking about the history of a word, its ordinary present meaning, a definition in a governing text or the legal effect of a particular act? These questions can inform one another without becoming the same question.\n\nUse “notice” as the research topic. You can study its linguistic history in an identified historical source, its ordinary use in communication and its treatment in a legal context. Do not supply an etymology from memory or assume that an older meaning determines a present legal rule. If a historical source is unavailable, leave that part of the study unresolved.\n\nNext, collect the surrounding text. A defined term may operate within a particular statute, rule, instrument or proceeding. Record who issued the text, when it applied and the jurisdiction involved. A definition extracted from a different setting may be interesting while failing to answer your question.\n\nCreate a four-column note: question, source, meaning in that setting and what the source does not decide. If you encounter a powerful slogan, turn it into a proposition that could be checked. Ask what text and facts would establish the asserted effect.\n\nThe purpose of this lesson is careful reading, not a filing or an individual legal conclusion. A respectful study of language becomes stronger when it preserves distinctions and lets the evidence correct an appealing first interpretation.", "worked_example": "Original research note: “Question: what does adequate notice require in a specified proceeding? Ordinary communication meaning: background only. Historical word origin: source not yet obtained. Applicable legal text and case construction: separate research needed. No remedy or legal effect has been established by this note.”", "evidence": [ "Four-category context note", "Source and jurisdiction fields", "Unresolved application question" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-CIV101-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CIV101", "SOURCE-DOC07" ], "body": { "title": "Identify the Authority", "course_id": "CIV101", "lesson_id": "CIV101-L2", "objective": "Locate an official text and describe the question it can support.", "teaching": "A research record should make the source of an asserted rule visible. Begin with an official text, identify the provision and state the issue you are studying. Record the version and date when they matter. A commentary can suggest an issue while the underlying authority still needs inspection.\n\nOpen the National Archives transcription and locate Article VI. Read the entire relevant clause rather than a fragment. Clause 2 identifies the Constitution, federal laws made pursuant to it and treaties made under United States authority as supreme law, with state judges bound despite contrary state constitutional or statutory provisions. Preserve the clause’s conditions when describing it.\n\nNow distinguish that text from an application question. Saying which provision you found does not, by itself, establish that a particular enactment is valid, that a particular dispute belongs in a chosen forum or that a requested remedy follows. Those issues require their own facts, applicable texts and judicial construction.\n\nUse an authority card with the issuer, provision, exact location, research question and limitation. When a document depends on a statute or rule, locate its official current version before relying on it. When a state-law question appears, identify the state instead of treating every rule as nationwide.\n\nYour output is a map for further research. It should tell another reader what authority was inspected and what remains to be established. The quality of the work comes from the accuracy of that relationship, not the force of the language used to announce a conclusion.", "worked_example": "Authority card: source, National Archives constitutional transcription; location, Article VI, clause 2; purpose, identify the supremacy provision; limitation, no conclusion yet about a particular law’s validity or a particular case. This is a reading exercise, not a determination of an individual dispute.", "evidence": [ "Official-source authority card", "Bounded paraphrase", "Additional-authority and fact list" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-CIV101-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CIV101", "SOURCE-DOC13" ], "body": { "title": "Read What Was Decided", "course_id": "CIV101", "lesson_id": "CIV101-L3", "objective": "Extract a narrow proposition from an official opinion without inventing a universal rule.", "teaching": "A judicial opinion should be read for the question before the court, the material facts, the reasoning, the result and the limits of that result. Keep the court’s own reasoning separate from a syllabus, a publisher’s headnote or a later creator’s interpretation.\n\nFor this historical exercise, open the official United States Reports scan of Mullane v. Central Hanover Bank & Trust Co., 339 U.S. 306 (1950). Read the opinion’s notice discussion at pages 314–315 and its treatment of known recipients at page 318. Publication was insufficient for beneficiaries whose names and addresses were known in that proceeding. Do not turn that limited proposition into a statement that every dispute requires an identical method.\n\nMake a case card rather than collecting an isolated quotation. Name the court, citation and decision date. State the issue in one sentence. Identify which facts appear important to the reasoning. Note the disposition and the pages supporting the proposition you extract.\n\nThen write a boundary statement. This exercise concerns a historical opinion and reading method. Current treatment, later decisions and any present procedural rule for a learner’s actual matter have not been established by this case card. Research those separately before attempting an operational application.\n\nIf the opinion is unavailable, stop the substantive summary and preserve the source gap. A confident recollection or a clip repeating a line is not the same as inspecting the opinion. Your evidence is a traceable, bounded reading that another researcher can check.", "worked_example": "Original case-card structure: court and citation; issue; relevant facts; reasoning pages; narrow proposition; disposition; unverified current treatment. The card should explain which facts limit the proposition instead of presenting a quotation as a complete legal strategy.", "evidence": [ "Case-reading card", "Pinpoint page reference", "Boundary and next-authority statement" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-CIV101-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CIV101", "SOURCE-DOC07", "SOURCE-DOC13" ], "body": { "title": "Build the Research Record", "course_id": "CIV101", "lesson_id": "CIV101-L4", "objective": "Write a neutral research memo that distinguishes support, application and uncertainty.", "teaching": "A useful research memo helps another reader assess your conclusion. Begin with the question and the jurisdiction. Separate established facts, assumptions and missing facts. Then identify the authority you inspected, explain the proposition it supports and describe what further work the application requires.\n\nUse a short structure: question, facts, governing sources, analysis, contrary or limiting material and next verification step. Keep word history in its proper section when it is relevant. A linguistic observation can illuminate a question without being substituted for controlling authority.\n\nApply the structure to a fictional notice problem. State only enough hypothetical facts to identify the research task. Do not convert the memo into a demand, filing, lien, contract or representation about an actual person’s rights. If the applicable rule, jurisdiction or current case treatment is missing, say what remains unresolved.\n\nInclude a good-faith challenge to your first reading. Which different fact could change the analysis? Is the source from the correct forum and time? Does the passage you rely on address the issue you actually asked? A memo becomes more useful when it can survive those questions.\n\nFinish with a bounded conclusion and a specific next source. For this course, the completed work is a research record, not a legal action or a professional qualification. The skill is preserving the relationship between a word, its setting, the text, judicial reasoning, facts and the claimed effect. Keep that chain visible whenever the issue becomes more consequential.", "worked_example": "Fictional memo conclusion: “The current record supports further research into the method of notice for the specified proceeding. The forum’s current procedural rule and the relevant facts remain unverified. This memo does not determine the outcome or prescribe a filing.”", "evidence": [ "One-page research memo", "Support and limitation notes", "Specific unresolved question and next source" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-MA102", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-CH01", "SOURCE-CH05", "SOURCE-CH13", "SOURCE-CH14" ], "body": { "title": "Symbol, Meaning & Discernment | original course application", "original_application": "Create an original symbolic study that clearly separates tradition, interpretation and externally testable claims", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-MA102-L1", "LESSON-MA102-L2", "LESSON-MA102-L3", "LESSON-MA102-L4" ], "version": "4.1" }, { "id": "LESSON-MA102-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA102", "SOURCE-CH01", "SOURCE-CH05" ], "body": { "title": "Name the Tradition", "course_id": "MA102", "lesson_id": "MA102-L1", "objective": "Create a symbolic study note with a truthful source lineage.", "teaching": "A symbol can arrive through a family story, a spiritual practice, a book, an image or a creator’s explanation. Start by naming the path through which you encountered it. That path is part of your source record; it is not automatically proof of the symbol’s earliest origin or every meaning it has carried.\n\nChoose a simple form or symbol that matters to you. Record the actual source you inspected and distinguish it from a tradition the source claims to represent. If the creator names an earlier text, treat that as a lead until you inspect it. Do not fill a missing lineage with a confident ancient-history claim.\n\nA study note can preserve several levels at once. Write what the source says, what you understand it to mean, what historical claim might be checked and what remains unknown. You can value the idea without collapsing those levels into one assertion.\n\nUse your own drawing or words for the exercise. Do not copy a creator’s distinctive artwork, narration or sequence simply because the topic is spiritual. A brief attributed reference and an original explanation can make your own contribution clearer.\n\nEnd with a question worthy of further study. It might concern the source’s context, a different reading or the conduct the symbol invites in your life. The result is an attributed note that respects the tradition, your interpretation and the limits of the material actually available.", "worked_example": "Original note: “I encountered a circle in a contemporary reflection on completion. My chosen reading is to finish the learning cycle. The source’s claim about an ancient origin has not been checked against an earlier text. My drawing and practical example are original.”", "evidence": [ "Attributed source-lineage note", "Interpretation and historical-gap labels", "Original sketch or description" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MA102-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA102", "SOURCE-CH01", "SOURCE-CH13", "SOURCE-CH14" ], "body": { "title": "Hold More Than One Reading", "course_id": "MA102", "lesson_id": "MA102-L2", "objective": "Compare interpretations without turning a personal reading into universal history.", "teaching": "Interpretation gives you a way to relate an idea to a question. It does not require pretending that one reading is the only reading ever held. Write two possible meanings of your chosen symbol and identify the context that makes each intelligible.\n\nFor an original circle exercise, one reading might emphasize completion: return to the work and close the loop. Another might emphasize connection: notice who is affected by a decision. These are proposed teaching interpretations. This lesson does not assert that either is the universal or original meaning of the circle.\n\nCompare the readings by their practical implications. Completion might prompt you to finish a draft and record a lesson. Connection might prompt you to ask who needs the instruction and whether they can use it. Ask what each interpretation notices and what it might overlook.\n\nMake disagreement specific and respectful. A participant can say, “That reading is meaningful to you; the source I am using presents a different context.” There is room for a factual question about a source and a separate discussion about personal meaning. Neither requires assigning another participant a deficient spiritual state.\n\nYour output should make the distinction easy to see: source context, proposed interpretation, practical implication and remaining question. Holding more than one reading can sharpen discernment because it asks you to explain why you choose a reading, rather than assuming that its emotional force proves a universal claim.", "worked_example": "Comparison: completion → finish and review a small artifact; connection → ask a permitted reviewer whether the artifact is usable. Both are original applications. Historical origin, cultural use and a participant’s spiritual commitment remain separate questions.", "evidence": [ "Two-reading comparison", "Context and limits notes", "Respectful inquiry question" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MA102-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA102", "SOURCE-CH13", "SOURCE-CH14" ], "body": { "title": "Translate Meaning into Conduct", "course_id": "MA102", "lesson_id": "MA102-L3", "objective": "Design an observable voluntary action from a clearly labeled interpretation.", "teaching": "A reflective idea can become useful when it changes a choice you actually control. Choose one interpretation from your comparison and name the value you want to express. Then describe a small action that would make that value visible.\n\nUsing the completion reading, the value might be care for unfinished commitments. The action could be ten minutes spent finishing one public learning note. The evidence could be a saved note and a short review. Using the connection reading, the action might be asking one consenting adult whether the instruction is clear. Keep the scope modest and the person’s choice voluntary.\n\nSeparate the practice from a promised external result. Completing the note does not guarantee attention, income, agreement or a change in another person’s behavior. Your personal spiritual interpretation can be recorded as reflection while the action record names what actually happened.\n\nDesign a recovery for an interrupted day. Reduce the action to a small feasible step or choose another suitable cue. Do not turn illness, hardship or an unmet outcome into a claim that someone’s thoughts or spiritual worth caused it. A practice can invite responsibility for a chosen action without pretending a person controls every circumstance.\n\nFinish by asking what the action taught you about the interpretation. Did the reading clarify a useful responsibility? Did it become too broad or rigid? You may revise or stop the practice. The purpose is a thoughtful connection between meaning, conduct and honest observation, not proof of a universal mechanism.", "worked_example": "Original practice: “I use the circle as a personal reminder to complete the learning cycle. After breakfast I will finish one source note, save it and write the next question. If interrupted, I will make one useful edit later. Other people’s response is outside this practice’s promise.”", "evidence": [ "Interpretation-to-action card", "Recovery plan and scope boundary", "Observation or explicit unrun plan" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MA102-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA102", "SOURCE-CH01", "SOURCE-CH05", "SOURCE-CH13", "SOURCE-CH14" ], "body": { "title": "Share with Discernment", "course_id": "MA102", "lesson_id": "MA102-L4", "objective": "Create an original reflective narration with clear attribution and claim labels.", "teaching": "A short reflection can carry meaning without asking the audience to accept every associated claim. Begin with the source or personal experience that prompted your inquiry. Name your chosen interpretation, show the action it informed and describe what you observed.\n\nUse an original narration of about one hundred words. For example, you might explain how a circle became a personal reminder to finish a learning cycle. If you mention a tradition or a historical assertion, give the source and identify any uncertainty. If you make a technical, scientific, medical or financial assertion, it requires appropriate evidence beyond the force of the metaphor.\n\nChoose original or properly licensed visuals. A simple drawing made for your reflection may express your point more clearly than borrowing a creator’s signature animation. Credit sources for the ideas or questions they contributed without implying their endorsement of your brand or practice.\n\nBefore sharing, label each sentence privately: source report, interpretation, personal observation, testable claim or invitation. Revise any sentence that crosses a boundary unintentionally. “This helped me finish a note this week” differs from “this proves a universal law that guarantees success.” Say what you can support.\n\nKeep participation voluntary and protect private reflection. The capstone can remain a private study artifact; completing the exercise does not require publishing a spiritual disclosure. A useful finished piece preserves the source, your original contribution, the action and its evidence limits. It invites thought and practice while leaving room for another person’s considered response.", "worked_example": "Original narration opening: “I chose to read the circle as a reminder to finish what I learn. This is my reflection, not a claim about its only historical meaning. Today I completed one source note and named the next question.” The rest should describe the learner’s own action and invitation.", "evidence": [ "Original narration", "Sentence-level claim review", "Attribution, visual-rights note and sharing decision" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-KB201", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-DOC14", "SOURCE-DOC15" ], "body": { "title": "Knowledge Vault Builder | original course application", "original_application": "Build and validate a public-only knowledge collection, search it, and demonstrate how a withdrawn source affects dependent records.", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-KB201-L1", "LESSON-KB201-L2", "LESSON-KB201-L3", "LESSON-KB201-L4" ], "version": "4.1" }, { "id": "LESSON-KB201-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-KB201", "SOURCE-DOC14", "SOURCE-DOC15" ], "body": { "title": "Choose the Corpus", "course_id": "KB201", "lesson_id": "KB201-L1", "objective": "Define a public knowledge collection with a purpose, audience and truthful inventory.", "teaching": "A useful knowledge collection begins with a task. Choose a question the collection should help an adult learner investigate, such as finding the explanation and test record for a small tool. Then define the material that belongs in this exercise: public educational sources, original notes and fictional examples.\n\nMake an inventory before indexing anything. Record the exact link, creator, title, inspection scope and proposed use. A description, a transcript and a complete video remain different access levels. An indexed source record can establish where your note came from without establishing that every assertion in the source is true.\n\nDefine inclusion and exclusion rules. This course uses a public-only corpus. Keep actual client records, credentials and private administrative information out of the exercise. If a file has no clear scope or authorization, leave it outside the input set and record the unresolved question. A shared folder or a convenient search screen does not establish permission.\n\nChoose a small first collection. The supplied seed provides a larger worked example, but your own experiment can begin with a few source and lesson records. Name the intended audience and the output you want to inspect. Do not assume that more documents automatically produce a better answer.\n\nFinish with a purpose statement and a source inventory another person can check. Your first evidence is the boundary around the collection. Search and automation come later, after the collection’s intended use and sources are clear.", "worked_example": "Original purpose statement: “This public practice collection helps an adult find one original tool lesson and its source pointers.” Included: public reference links and original teaching notes. Excluded: private files, account secrets and any source whose use permission or scope is unresolved.", "evidence": [ "Purpose-and-audience statement", "Truthful public source inventory", "Explicit inclusion rules" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-KB201-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-KB201", "SOURCE-DOC14", "SOURCE-DOC15" ], "body": { "title": "Build the Provenance", "course_id": "KB201", "lesson_id": "KB201-L2", "objective": "Validate a copied record set and correct a broken reference.", "teaching": "A source and a lesson do different jobs. A source record identifies inspected material. A claim record describes a statement and its evidence scope. An insight records an original interpretation or proposed application. A lesson turns that application into a learning task. Keep these roles visible through identifiers and references.\n\nUse the supplied schema and seed as a worked example. The local validator checks the schema keywords this package uses, required fields, allowed labels, lane and audience consistency, duplicate identifiers and references. It also detects a cycle in provenance. These checks establish structural consistency within the exercise; they do not determine factual truth or grant access to private data.\n\nWork on a copy. Run validation on the supplied public seed and preserve the result. In another copy, replace one provenance identifier with a deliberately nonexistent identifier. Run validation again and inspect the reported failure. Correct the reference and rerun the affected check.\n\nA reference should lead somewhere meaningful. A source can point to its external public URL. A lesson can point to the original application and the relevant source records. Do not create a convincing-looking identifier for a source you never inspected, and do not mark a proposed application as a verified outcome.\n\nYour final evidence contains the valid input, the failed-case observation and the correction. A failure that you can explain and repair is part of the learning. It shows why provenance needs validation before the collection is used as a dependable reference.", "worked_example": "Illustrative broken reference: a copied lesson cites SOURCE-MISSING. The validator reports an unresolved provenance reference. Restoring the actual inspected source identifier resolves that structural defect; it does not independently verify the lesson’s factual claims.", "evidence": [ "Valid copied seed", "Broken-reference observation", "Correction record and evidence limits" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-KB201-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-KB201", "SOURCE-DOC14", "SOURCE-DOC15" ], "body": { "title": "Build and Search the Index", "course_id": "KB201", "lesson_id": "KB201-L3", "objective": "Create a new local index and record a repeatable search observation.", "teaching": "Once the public input set is valid, build an index into a new file. The supplied tool deliberately refuses to overwrite an existing destination. Preserve the previous version so you can compare inputs and results rather than losing the starting point.\n\nSQLite supports the local database used in this exercise, and its FTS5 extension supplies full-text search. The supplied Python tool uses that capability to search the public record text. A search result is a way to locate relevant material. Its rank is not proof of accuracy, completeness or current legal authority.\n\nUse the companion files in one folder and your environment’s Python command. Validate the seed, build a fresh practice index and run one word-based query. Record the query, kind filter, result identifiers, snippet and provenance. If a required module or FTS5 capability is unavailable, record the environment limitation instead of reporting a successful build.\n\nCompare two queries tied to the same learner task. Ask whether the returned record actually helps answer the question and whether its status is still draft or reviewed. A result that merely shares a word may need a different query or clearer source text. Preserve an example of a useful result and a limitation.\n\nThe capstone is a repeatable local search record. You have not connected a production database, loaded a private corpus or evaluated every possible query. A small, clearly documented result is enough for this learning step and gives you a basis for choosing the next improvement.", "worked_example": "Example commands: python3 Vault_Tools.py validate Knowledge_Seed.json --lane public_education; then python3 Vault_Tools.py build Knowledge_Seed.json Practice_Knowledge.sqlite; then python3 Vault_Tools.py search Practice_Knowledge.sqlite \"provenance\" --kind lesson. Choose a new destination filename if the practice index already exists.", "evidence": [ "New practice index or explicit environment limitation", "Two-query observation record", "Provenance and usefulness review" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-KB201-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-KB201", "SOURCE-DOC14", "SOURCE-DOC15" ], "body": { "title": "Rehearse a Source Change", "course_id": "KB201", "lesson_id": "KB201-L4", "objective": "Trace affected records and preserve a bounded maintenance decision.", "teaching": "A knowledge collection needs a way to respond when its source changes. Start with a copied fixture so the rehearsal does not alter the original corpus. Select a source record and mark it withdrawn in that copy. Withdrawal is a review condition in this exercise; it does not itself prove that every associated statement is false.\n\nRun validation and inspect the review-impact list. The supplied tool follows provenance dependencies and identifies downstream records. A newly built practice index marks those records for review. Normal search excludes withdrawn and affected entries; an explicit review search can include them with their status visible.\n\nCompare the observations. Which records were affected? Which part of the lesson actually depended on the source? Would an independent supporting source preserve a factual proposition? The tool uses conservative dependency propagation. A responsible reviewer still decides the exact correction rather than treating a software flag as a legal or scientific conclusion.\n\nWrite a maintenance note with the source, reason for the rehearsal, affected records, observation and proposed next action. Preserve the prior version. If you correct a lesson, identify what changed and why. Keep the difference between source correction, editorial revision and permission change clear.\n\nYour finished project contains a public source inventory, valid provenance, a searchable local index and a source-change record. It demonstrates a useful knowledge-maintenance process under stated conditions. A production service would still need its own access controls, integration work, operational support and review of the actual authorized corpus.", "worked_example": "Fictional rehearsal: a copied source record is marked withdrawn. The validator identifies dependent lesson records. A reviewer records which statement needs checking and preserves an unaffected original exercise where justified. No claim is silently promoted or deleted to make the collection appear complete.", "evidence": [ "Copied change fixture", "Review-impact and search observations", "Versioned maintenance decision" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-LDR201", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-DOC17", "SOURCE-CH21" ], "body": { "title": "Purpose, Responsibility & Service | original course application", "original_application": "Turn a purpose hypothesis into a scoped contribution, rehearsal and honest learning review.", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-LDR201-L1", "LESSON-LDR201-L2", "LESSON-LDR201-L3", "LESSON-LDR201-L4" ], "version": "4.1" }, { "id": "LESSON-LDR201-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-LDR201", "SOURCE-CH21", "SOURCE-DOC17" ], "body": { "title": "Name the Purpose", "course_id": "LDR201", "lesson_id": "LDR201-L1", "objective": "Write a purpose hypothesis that connects a value with a useful contribution.", "teaching": "Purpose can be approached as a serious question about contribution. Begin with the people or situation you want to serve and the work you can responsibly attempt. The exercise does not require a grand title or a promise about destiny. It asks for a useful, bounded hypothesis.\n\nMunroe Global identifies purpose and leadership as themes in its mission. This course develops an original practical application of those broad themes. It does not reproduce a sermon, adopt the source’s theology as a required belief or claim to summarize material that was not inspected.\n\nChoose a fictional community learning need. For example, adults attending a small learning circle may need a clearer way to locate the next exercise. State the contribution: make the next action easier to find and understand. Identify the value it expresses and what the people affected might need to tell you.\n\nSeparate aspiration from evidence. “I want to make learning easier to use” is an intention. A reviewer successfully finding the next exercise is an observation. A purpose statement becomes more useful when it guides an action that can be tested and revised.\n\nFinish with a one-sentence purpose hypothesis, an audience and a small contribution. Keep room for feedback. A service that fits your preferred identity but does not help the intended recipient needs revision. The aim is a relationship between meaning and useful work that can be made visible in an ordinary setting.", "worked_example": "Original purpose hypothesis: “I want to make this public learning activity easier for an adult beginner to use by clarifying the first action and the finished output.” Evidence still needed: a permitted reviewer can follow the revised instruction.", "evidence": [ "Purpose hypothesis", "Audience-and-contribution statement", "Supporting or disconfirming observation" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-LDR201-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-LDR201", "SOURCE-CH21", "SOURCE-DOC17" ], "body": { "title": "Choose the Responsibility", "course_id": "LDR201", "lesson_id": "LDR201-L2", "objective": "Define a useful task without assuming authority the task does not grant.", "teaching": "Leadership in this exercise begins with taking responsibility for a defined contribution. Write the task, the person or role responsible, the intended output and the limit of that assignment. A clear assignment makes follow-through easier to inspect.\n\nUse a fictional learning-circle project. One adult agrees to clarify the public exercise instructions. Another agrees to try the instructions and report confusion. Neither assignment automatically authorizes signing a contract, handling private records or representing an office. A learning role is a description of work, not proof of legal capacity.\n\nKeep the recipient’s choice visible. Service does not require controlling the other person’s response. Ask whether the instruction is useful and let the reviewer identify a problem or decline participation. A contribution can be offered without creating a claim of entitlement to praise, agreement or a sale.\n\nDefine completion before beginning. For the instruction task, completion might mean a revised one-page exercise, a fictional worked example and a clear next action. State what is excluded so the assignment does not grow into a new website, a legal determination or a large service without a separate decision.\n\nYour responsibility record should be short enough to use. It names what you will do, what evidence will show the work and which questions remain with another properly authorized role. This gives your purpose an ordinary form that can be delivered, reviewed and improved.", "worked_example": "Fictional task: revise one public learning instruction. Responsible role: volunteer editor within the agreed task. Output: one page and a worked example. Limit: no access to private files or authority to make commitments for an organization.", "evidence": [ "Task-and-role record", "Completion criteria and exclusions", "Permission or unresolved-authority note" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-LDR201-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-LDR201", "SOURCE-CH21", "SOURCE-DOC17" ], "body": { "title": "Build the Contribution", "course_id": "LDR201", "lesson_id": "LDR201-L3", "objective": "Produce and test one small service artifact using agreed criteria.", "teaching": "A purpose statement becomes more informative when it produces work. Build the smallest artifact that could help with the stated need. For our fictional learning circle, create a one-page instruction with a clear purpose, starting action, worked example and completion evidence.\n\nUse the criteria from the responsibility record. Do not add features merely to make the contribution look more impressive. A concise instruction that a learner can follow may be more useful for this task than a large collection that hides the first step.\n\nRehearse with fictional information. Try the instruction yourself from a blank start and record where it becomes ambiguous. If a consenting adult reviewer is available within the authorized context, ask them to attempt the task. If that review has not occurred, label it unrun. Do not turn a proposed recipient into a testimonial or a demonstration into claimed community impact.\n\nRecord the starting version, what you changed and the observation. If the reviewer cannot identify the finished output, improve that instruction and repeat the affected step. Feedback is information about the design, not a verdict on the person’s worth or the value of service itself.\n\nFinish by assessing the artifact against the actual task. What can you show? What is still uncertain? The useful contribution is the work and the improvement it supports under the recorded conditions. Broader claims about leadership, community change or economic results need their own evidence.", "worked_example": "Fictional observation: the instruction explains the topic but does not tell the learner what file to save. The editor adds a named output and an example. The rehearsal then checks that exact step, while any wider community use remains untested.", "evidence": [ "Original service artifact", "Rehearsal and observation record", "Versioned correction or bounded clean result" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-LDR201-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-LDR201", "SOURCE-CH21", "SOURCE-DOC17" ], "body": { "title": "Review and Continue", "course_id": "LDR201", "lesson_id": "LDR201-L4", "objective": "Write a service learning record and choose a proportionate next step.", "teaching": "A service project should leave behind more than an account of good intentions. Preserve the need, purpose hypothesis, agreed task, artifact, observation, correction and next decision. Keep private disclosures out of the shared record.\n\nCompare what you intended with what you actually did. A completed draft, one rehearsal and a corrected instruction can be a useful result. State those facts without enlarging them into a claim of universal impact. If the recipient’s need was different from your assumption, describe what changed in your understanding.\n\nChoose a next step proportionate to the evidence. You might keep the instruction, ask another consenting adult to try it, improve its accessibility or stop a design that did not help. More activity is not automatically a better continuation. A clearer responsibility or a smaller scope may be the useful change.\n\nA spiritual reflection can accompany the record when the learner chooses it. Label it as interpretation or personal meaning, and retain the source’s theological context where relevant. A public leadership exercise does not adopt a ministry doctrine, confer an office or determine legal authority.\n\nYour capstone is the purpose hypothesis, task-and-role record, original contribution and learning review. It demonstrates an approach to responsible contribution that can be explained and revised. Keep the evidence available so another person can build on the useful part without having to accept an exaggerated story about what the project achieved.", "worked_example": "Original review: “We intended to clarify the first step of a public learning task. One revised page and one fictional rehearsal are complete. The saved revision names the output more clearly. A real learner pilot is unrun. The next proposed step is a consenting adult usability review.”", "evidence": [ "Complete purpose-to-service capstone", "Honest learning review", "Specific next decision and scope" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-CO201", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-DOC08", "SOURCE-DOC09", "SOURCE-DOC16" ], "body": { "title": "Research-to-Asset Studio | original course application", "original_application": "Develop authorized expertise into an original practical download, short lesson and content package.", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-CO201-L1", "LESSON-CO201-L2", "LESSON-CO201-L3", "LESSON-CO201-L4" ], "version": "4.1" }, { "id": "LESSON-CO201-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CO201", "SOURCE-DOC08", "SOURCE-DOC09" ], "body": { "title": "Choose the Audience Job", "course_id": "CO201", "lesson_id": "CO201-L1", "objective": "Define one audience task and a bounded original learning asset.", "teaching": "An asset starts with a person trying to do something. “A guide about knowledge” leaves the work unclear. “A source card that lets an adult learning-circle host explain what was actually inspected” identifies a user, a moment and a visible result. Write those three details before choosing a format. A short form may serve the task better than a long course.\n\nSeparate the audience hypothesis from audience evidence. A plausible need is a starting question. It becomes a supported problem only after relevant observations or appropriately consented research. For this exercise, a fictional user is sufficient to practice design. Keep fictional statements labeled so they do not become testimonials or demand claims later.\n\nDefine the asset's boundary using a completion test. State the required input, the output and what the user should be able to check. Then name omissions. A source card can record access and uncertainty; it cannot certify every statement in a channel. A clear boundary helps the next lesson identify which facts actually require research.\n\nFinally, inventory material you can use: your original explanations, public links and any material with documented permission for this use. Access to a video does not establish a right to repackage its narration or images. Choose a task that can be served through original examples and precise references.", "worked_example": "Fictional host Amari needs to distinguish a video description from a transcript. The proposed asset is a one-page inspection card with four fields and one original completed example. Success means Amari can label the inspection accurately; no claim about the video’s complete contents is required.", "evidence": [ "Audience-job brief", "Bounded completion test", "Material and rights inventory" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-CO201-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CO201", "SOURCE-DOC01", "SOURCE-DOC08" ], "body": { "title": "Extract and Verify", "course_id": "CO201", "lesson_id": "CO201-L2", "objective": "Create a claim ledger that preserves source scope and the reason for each decision.", "teaching": "Extracting a useful idea is different from importing an entire explanation. Break the proposed asset into small statements. For each statement, ask whether it is an instruction you authored, a factual claim, a personal interpretation or a planning assumption. These categories need different support. An original fictional example should not be described as a creator's case study.\n\nRecord the exact source, location and inspection scope beside each factual claim. If only a creator description was available, that is the limit of the evidence. You may use it to describe the advertised topic, while withholding conclusions about a demonstration you have not inspected. An unresolved account or playlist belongs in the research queue.\n\nVerify consequential facts against suitable primary material. For a software procedure, inspect official documentation for the relevant version. For a claim about legal effect, identify jurisdiction, governing text and relevant judicial construction before presenting an application. A title, etymology or promotional statement cannot supply those missing links.\n\nChoose a disposition for every claim: include with its limit, revise, investigate or omit. Preserve the reason. The ledger gives a reviewer a route from the finished sentence back to the actual evidence. It also makes later source changes manageable because you know which part of the asset depends on which reference.", "worked_example": "The draft says “this playlist teaches seven research methods,” but only its title was retrieved. Amari removes that sentence. The card instead includes an original example of title-only access and a question for later inspection. The asset remains useful without inventing the playlist’s contents.", "evidence": [ "Five-statement claim ledger", "One primary-source check with access scope", "Disposition and reason for each statement" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-CO201-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CO201", "SOURCE-DOC08", "SOURCE-DOC16" ], "body": { "title": "Build the Asset Family", "course_id": "CO201", "lesson_id": "CO201-L3", "objective": "Create a coherent original tool, lesson and content draft from one supported idea.", "teaching": "An asset family serves the same audience task at several depths. A short post introduces a question, a lesson teaches a method, and a tool helps a user perform it. These pieces should share a defined concept and lead to an observable action. They do not need to repeat the same text or claim that more content creates more value.\n\nStart with the tool because its fields reveal what the task requires. Build a minimal version with useful instructions and one fictional example. Then teach the reasoning behind those fields. Finish with a short invitation that accurately previews the task and its limit. A post about source inspection should not promise mastery of every topic represented in a channel.\n\nMaintain a shared vocabulary. If the tool says “inspection scope,” use that phrase in the lesson and explain it once. Keep examples, dates and numbers consistent across versions. Distinguish raw source material from your original contribution in the working files so a later editor can identify what needs attribution or permission.\n\nAdd a next step proportionate to the evidence: complete one card, compare two sources or try one exercise. Avoid presenting a fictional result as a testimonial. The first family is a draft for rehearsal. Its usefulness is still a question until someone can follow the instructions and produce the intended output.", "worked_example": "Amari creates an original four-field source card, a short lesson showing how to fill it, and a 45-second narration asking viewers what they actually inspected. All three use the same fictional description-only case. The narration invites completion of a card rather than promising expertise.", "evidence": [ "Original tool prototype", "Companion mini-lesson", "Content draft and consistency check" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-CO201-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CO201", "SOURCE-DOC08", "SOURCE-DOC09" ], "body": { "title": "Rehearse Delivery", "course_id": "CO201", "lesson_id": "CO201-L4", "objective": "Test an asset family and hand it off with a versioned correction record.", "teaching": "A delivery rehearsal asks whether the user can move from instructions to a useful output. Choose observable cases before trying the material. Include an ordinary case, a missing-input case and a case that should produce an uncertainty statement. This prevents the test from becoming a search for praise.\n\nUse fictional information for the first rehearsal. Record the exact version, environment, steps, expected result and observed result. If no independent learner participates, label the result a creator rehearsal. If you only read through the instructions, do not record that as an executed tool or learner test. Different forms of inspection answer different questions.\n\nRevise the smallest part that caused a failure. A missing example may require one additional sentence rather than a larger course. Repeat the affected case on the changed version. Keep the earlier observation and identify the correction so reviewers can see why the new version exists.\n\nThe handoff should include the audience task, files, use instructions, source ledger, rights status, completed checks and remaining limits. An internal draft can be complete for review while publication remains pending. Keep that distinction visible. The capstone is a traceable original asset family, with a reasoned decision to continue, revise or stop.", "worked_example": "A creator rehearsal finds that the card’s “source” field could mean either a channel or a specific page. Amari changes the label to “Exact inspected URL” and repeats the missing-input case. Independent learner use, actual browser printing and public distribution remain unrun.", "evidence": [ "Versioned rehearsal record", "Correction or bounded result", "Complete asset-family handoff" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-MA201", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-CH01", "SOURCE-CH13", "SOURCE-CH14", "SOURCE-CH20" ], "body": { "title": "Design Your Personal Operating System | original course application", "original_application": "Connect values, attention, learning and weekly review in a manageable personal practice system.", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-MA201-L1", "LESSON-MA201-L2", "LESSON-MA201-L3", "LESSON-MA201-L4" ], "version": "4.1" }, { "id": "LESSON-MA201-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA201", "SOURCE-CH01", "SOURCE-CH13", "SOURCE-CH14", "SOURCE-CH20" ], "body": { "title": "Name Your Commitments", "course_id": "MA201", "lesson_id": "MA201-L1", "objective": "Translate chosen values into a small set of controllable responsibilities.", "teaching": "A personal operating system is a way to remember and review chosen commitments. In this course it is a practical map, not a claim that every outcome can be controlled by thought. Begin with a value that matters to you and ask what an ordinary action could express it this week. “Learning” might become writing one source note after a reading session.\n\nDistinguish a value, a responsibility and a wish. A value gives direction. A responsibility names work you actually choose or have accepted. A wish describes an outcome that may depend on other people and conditions. You can pursue an outcome while measuring your own action honestly.\n\nLimit the first map to a few commitments. Name what each one includes and what would make it too large for the available time. A learning practice that crowds out rest or essential care needs revision. Missed action is information about the design and context, not proof of personal unworthiness or defective spiritual energy.\n\nUse The Standard or an existing record if it already serves this purpose. Add a small practice entry rather than building another competing planner. Personal meanings and spiritual reflections may remain private. A shared learning artifact can show the chosen action and its evidence without requiring disclosure of the belief behind it.", "worked_example": "A fictional learner values care, craft and learning. They choose one responsibility under each: prepare tomorrow’s materials, improve one instruction and record one source. They leave “everyone respects my work” as an aspiration, because other people’s responses are outside the completion test.", "evidence": [ "Values-to-action map", "Responsibility and limits record", "Sharing choice" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MA201-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA201", "SOURCE-CH13", "SOURCE-CH14", "SOURCE-CH20" ], "body": { "title": "Design the Week", "course_id": "MA201", "lesson_id": "MA201-L2", "objective": "Attach a small practice to a cue, time budget and recovery rule.", "teaching": "A weekly design makes a commitment easier to find when the day becomes busy. Choose a cue that already occurs, a location where the materials are available, and a short action that fits the real time available. This is a design hypothesis for your circumstances; the course does not promise a universal habit formula.\n\nWrite a minimum useful action and an optional extension. The minimum should still produce something meaningful: a sentence, a checked step or a completed field. Avoid calling mere intention an output. The extension is optional so a busy day does not automatically become a failed day.\n\nName likely friction before the trial. You may need a prepared file, a quieter time, a smaller task or a shared-device alternative. Some barriers require support or resources beyond a planner. Record those conditions plainly without treating them as a failure of belief.\n\nAdd a recovery rule: if the cue is missed, choose a modest later window or resume at the next planned cue. Do not require punishing catch-up work. Put this plan into the existing weekly record and specify when you will review it. The purpose is a workable commitment, not a perfect attendance story.", "worked_example": "The learner plans seven minutes after breakfast to revise one instruction. The minimum is one clarified sentence; the optional extension is testing it. If mornings change, they may use a short evening window once, then return to the next cue. They record the plan in The Standard.", "evidence": [ "Cue-and-action plan", "Prepared-materials check", "Recovery and review rule" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MA201-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA201", "SOURCE-CH01", "SOURCE-CH13", "SOURCE-CH20" ], "body": { "title": "Observe the Friction", "course_id": "MA201", "lesson_id": "MA201-L3", "objective": "Record seven days of actions, outputs and context without overclaiming cause.", "teaching": "Observation separates the intended system from the system you actually used. Record the planned cue, whether the action occurred, actual time, visible output and relevant context. A blank output field should stay blank when nothing was produced. “Not attempted” and “attempted but blocked” tell different stories and may suggest different changes.\n\nChoose a simple baseline before the trial, such as the number of source notes present at the start. Describe the baseline as a local starting point. It is not a controlled experiment or a measure of personal worth. A seven-day record can show what happened in those seven days without proving why it happened.\n\nWhen friction appears, change one practical condition if feasible and record the change. You might prepare the file in advance or reduce a task. If several conditions change together, note that you cannot isolate their effects. Improvement after a change is an observation, not automatic proof that the change caused it.\n\nKeep personal reflections separate from the factual record. A symbol or affirmation may be meaningful to you; that meaning does not demonstrate a scientific mechanism or ensure an external result. You can share a redacted action record while keeping private interpretation off the shared course sheet.", "worked_example": "A fictional seven-day record shows four completed source notes, one missed cue and two blocked attempts on a shared device. Preparing a paper card helped on the final day. The learner records that association and keeps device access as a remaining constraint; no causal or therapeutic claim is made.", "evidence": [ "Baseline and seven-day record or honest unrun status", "Context and change note", "Observation-versus-interpretation statement" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MA201-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA201", "SOURCE-CH01", "SOURCE-CH14", "SOURCE-CH20" ], "body": { "title": "Keep and Revise", "course_id": "MA201", "lesson_id": "MA201-L4", "objective": "Make a proportionate next-week decision from a truthful practice record.", "teaching": "Review begins with the original commitment and the actual evidence. Compare the intended action with completed artifacts, interruptions, effort and remaining questions. Count outputs if they help, but also inspect whether those outputs serve the chosen responsibility. Seven low-quality notes may need a different revision from two useful notes.\n\nChoose among keeping, reducing, changing or stopping a practice. Each is a legitimate decision when supported by the record. A routine that consumes attention without serving the learner may be retired. Do not interpret stopping as a spiritual failure. Practical fit changes with responsibilities and resources.\n\nWrite the reason for the next decision and the observation that could change it. Keep one variable small enough to inspect in the next week. If the entire plan changes, describe it as a new design rather than a clean comparison with the old one. Preserve the old version so the learning remains traceable.\n\nFinish with a compact system: selected values, a few responsibilities, cues, minimum outputs, recovery rules and a review date. Integrate it into The Standard where appropriate. This is an original personal practice artifact. Completion requires an honest record and a reasoned next step, not a prescribed belief or a promised life outcome.", "worked_example": "The learner keeps a seven-minute source-note practice, reduces the number of commitments from three to one and adds a paper alternative. The next review asks whether at least one usable note exists after each feasible session. Their capstone labels the earlier week as fictional if no actual trial occurred.", "evidence": [ "Complete personal practice map", "Evidence-based revision record", "Next-week plan with recovery and privacy choices" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-EDU201", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-DOC01", "SOURCE-DOC02", "SOURCE-DOC16" ], "body": { "title": "Facilitate Learning with Evidence | original course application", "original_application": "Teach a short practical lesson, review a learner artifact and provide repeatable feedback.", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-EDU201-L1", "LESSON-EDU201-L2", "LESSON-EDU201-L3", "LESSON-EDU201-L4" ], "version": "4.1" }, { "id": "LESSON-EDU201-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-EDU201", "SOURCE-DOC16", "SOURCE-DOC02" ], "body": { "title": "Start from the Artifact", "course_id": "EDU201", "lesson_id": "EDU201-L1", "objective": "Design an observable learning outcome and a matching assessment.", "teaching": "A learning outcome should describe something a learner can do or produce. “Understand sources” is hard to assess. “Complete an inspection card that distinguishes the exact page reviewed from uninspected content” gives the facilitator something to inspect. Choose the artifact before writing a long presentation.\n\nSpecify a few criteria that matter to the task. A source card might require an exact URL, truthful access label, bounded claim and unresolved question. These criteria describe the work, not the learner's personality. Avoid using agreement with a spiritual interpretation as evidence of mastery.\n\nCreate an original completed example and an incomplete example. The incomplete example should expose a likely misunderstanding, such as calling a description a transcript. These are teaching fixtures, not claims about real participants. They help reveal whether the criteria are clear before a session begins.\n\nCheck that the task can be completed with the materials and time available. If it depends on inaccessible content, provide an original fictional case or narrow the objective. The assessment should match what was taught and should distinguish a plan from an executed action. A well-bounded outcome makes both instruction and feedback more useful.", "worked_example": "A 20-minute draft session asks learners to produce a four-field source card. The criteria are exact URL, actual access, one supported statement and one unknown. The model uses a fictional page description; no private story or full video access is required.", "evidence": [ "Artifact-based outcome", "Four-criterion rubric draft", "Two original teaching examples" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-EDU201-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-EDU201", "SOURCE-DOC16", "SOURCE-DOC01" ], "body": { "title": "Build the Learning Sequence", "course_id": "EDU201", "lesson_id": "EDU201-L2", "objective": "Arrange explanation, demonstration, practice and feedback around the learner task.", "teaching": "A learning sequence makes the reasoning visible and then gives the learner room to attempt it. State the task and criteria, explain the necessary distinction, demonstrate an example, offer a fresh attempt and inspect the result. The sequence is a practical course design proposal; its timing needs an actual pilot.\n\nDuring the demonstration, show choices rather than only the polished answer. Explain why a description-only source cannot support a full-video summary. Point to the specific input used and the statement withheld. This helps the learner apply a method to a new case instead of memorizing the model.\n\nUse a fresh practice case with the same essential difficulty. If it copies every detail of the demonstration, success may reveal little about transfer. Make required inputs available and allow an uncertainty answer when evidence is missing. An honest “not enough information” can be the correct task result.\n\nReserve time for feedback and another attempt. A session that uses all its time for presentation may never reveal whether the instructions work. Include an optional private reflection and a next step. Keep personal disclosure voluntary and separate facilitation of learning from clinical care, legal representation or a formal appointment.", "worked_example": "The draft session uses 3 minutes for the task, 5 for demonstration, 7 for a new card and 5 for feedback and retry. These are planning estimates. The fresh case provides only a title, so the expected card explicitly withholds claims about the contents.", "evidence": [ "Session plan", "Demonstration notes and fresh case", "Feedback-and-retry allocation" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-EDU201-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-EDU201", "SOURCE-DOC16", "SOURCE-DOC02" ], "body": { "title": "Assess Consistently", "course_id": "EDU201", "lesson_id": "EDU201-L3", "objective": "Apply a simple rubric to original fixtures and preserve disagreements.", "teaching": "A rubric is useful when its criteria lead to explainable decisions. Define what meeting each criterion looks like and what would count as incomplete. For the four-field source card, a truthful access label matters more than an elegant layout. Keep essential criteria visible rather than hiding them inside a single impression score.\n\nTry the rubric on the complete and incomplete fixtures. Record each decision with the exact evidence that supports it. If a criterion cannot be applied without guessing, revise the wording. Do this before a learner is affected by an unclear standard.\n\nWhere another reviewer is appropriately available, compare independent decisions and discuss the evidence behind differences. Do not invent a second reviewer. A solo rehearsal can reveal ambiguities but does not establish agreement between assessors. Preserve that limit in the record.\n\nSeparate first-attempt performance from completion after feedback. Both are useful: one shows the starting difficulty, and the other shows whether correction helped. Four correct knowledge checks alone do not replace the course artifacts. No internal completion record should be described as accreditation, a professional license or a grant of authority.", "worked_example": "The incomplete fixture gives a channel URL and says “full transcript” even though only a description was inspected. The facilitator marks exact URL and access label incomplete and cites those fields. A solo rehearsal is recorded; inter-reviewer agreement remains untested.", "evidence": [ "Operational rubric", "Two scored fixtures with reasons", "Ambiguity and revision record" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-EDU201-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-EDU201", "SOURCE-DOC16", "SOURCE-DOC01" ], "body": { "title": "Give Useful Feedback", "course_id": "EDU201", "lesson_id": "EDU201-L4", "objective": "Deliver an evidence-based correction and prepare a bounded facilitation handoff.", "teaching": "Useful feedback connects a task criterion with an observed feature of the work and a possible next action. “This needs work” gives little direction. “The URL names the channel; replace it with the exact inspected page so the reader can repeat your check” identifies a gap and a repair.\n\nGive the learner an opportunity to explain their reasoning. A missing input, unclear instruction and mistaken inference may look similar in the final artifact but require different responses. Keep the discussion about the task. Avoid turning feedback into a judgment of identity or belief.\n\nLet the learner revise and record what changed. Preserve the first attempt if the learning record permits it. If the criterion remains unmet, name the remaining issue plainly. Encouragement can coexist with an accurate account of unfinished work.\n\nThe facilitation capstone contains the outcome, session plan, original fixtures, rubric, feedback example and proposed pilot record. If no actual learner participated, the delivery status remains a facilitator rehearsal or plan. Choose a small next improvement from the evidence and keep participant stories out of promotional materials unless separately authorized.", "worked_example": "The facilitator gives the fictional learner one repair: supply the exact URL and change “full transcript” to “description.” The revised fixture meets those criteria but still lacks an unknown. The feedback acknowledges the correction and asks for that final field; completion is not recorded prematurely.", "evidence": [ "Specific feedback example", "Revised fixture and completion decision", "Facilitation capstone with pilot plan" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-OPS201", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-DOC03", "SOURCE-DOC04", "SOURCE-DOC25" ], "body": { "title": "Workflow Design & Automation | original course application", "original_application": "Specify and rehearse a small workflow with explicit inputs, permissions, failure handling and human review.", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-OPS201-L1", "LESSON-OPS201-L2", "LESSON-OPS201-L3", "LESSON-OPS201-L4" ], "version": "4.1" }, { "id": "LESSON-OPS201-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-OPS201", "SOURCE-DOC03", "SOURCE-DOC04" ], "body": { "title": "Map the Work", "course_id": "OPS201", "lesson_id": "OPS201-L1", "objective": "Describe a workflow through triggers, inputs, decisions, outputs and failure states.", "teaching": "A workflow is a series of decisions and actions that turns a defined input into an output. Start with the work as it happens, including waiting, missing information and exceptions. “Automate my business” is too broad to test. “Turn a fictional lesson brief into a draft checklist for review” provides a manageable boundary.\n\nWrite the trigger, required inputs, actor, decision, output and stop conditions. Mark where information is copied or interpreted. A deterministic rule such as rejecting a blank title differs from a judgment such as deciding whether an explanation is adequate. Keeping those steps distinct makes later tool choices clearer.\n\nIdentify the existing manual route. It gives you a fallback and a comparison. A smaller manual checklist may solve the problem without integration. If automation is useful, the manual route still helps explain what the automated result should mean.\n\nUse dummy data and a separate development context for the course. Do not connect accounts or submit real records just to demonstrate a flow. The first artifact is a workflow specification with explicit unknowns. It describes intended behavior; it does not claim a running integration or permission to operate another system.", "worked_example": "The fictional workflow receives a lesson title and objective, rejects blanks, creates a checklist draft and waits for human review. Approved output can be exported manually. It sends no messages, modifies no live course and stores no credentials.", "evidence": [ "Workflow specification", "Exception and stop list", "Manual fallback" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-OPS201-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-OPS201", "SOURCE-DOC03", "SOURCE-DOC25" ], "body": { "title": "Choose the Mechanism", "course_id": "OPS201", "lesson_id": "OPS201-L2", "objective": "Assign manual work, fixed rules and model assistance to appropriate workflow steps.", "teaching": "Tool choice should follow the work. A fixed validation rule can check whether a required field is blank. A template can format known information. Model assistance may propose a checklist, but its interpretation still needs review. Use the simplest mechanism that gives a checkable result for the step.\n\nCompare mechanisms using the same fictional input and criteria. Record the actual output, effort and failure behavior. If a model or integration was unavailable, record that condition rather than inventing a comparison. A proposal to use an API is not evidence that an API call ran.\n\nMCP is one way servers expose named tools with schemas to a model-capable client. The dated official specification is a technical reference, not proof that a particular tool is safe or that the learner has authority to use it. Tool discovery, input shape and actual effect are separate questions.\n\nWrite a mechanism decision for each step, including a manual fallback. Consider data exposure, maintenance and review burden alongside convenience. For this course the result can remain a sandbox specification. Connecting a real system would be a new implementation action with its own actual scope and acceptance requirements.", "worked_example": "The blank-title check uses a fixed rule. A template lays out fields. The draft-checklist step is proposed for model assistance, but no model call is needed for the dummy rehearsal. A human reviewer decides whether the checklist fits the objective.", "evidence": [ "Mechanism map", "Bounded comparison record", "Decision and fallback notes" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-OPS201-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-OPS201", "SOURCE-DOC25", "SOURCE-DOC04" ], "body": { "title": "Design the Boundaries", "course_id": "OPS201", "lesson_id": "OPS201-L3", "objective": "Specify data, permission, review and failure boundaries for a sandbox workflow.", "teaching": "A workflow boundary states what may enter, what may happen and where work must stop. Define allowed dummy inputs and reject private, secret or unrelated records in the course rehearsal. Keep sensitive values out of examples, logs and screenshots. A label in a document is a design requirement, not an implemented access-control system.\n\nFor every proposed tool, list its effect: read, compute, write, send or delete. A read-only search and an external message have different consequences. Specify the actual actor allowed to approve a consequential step. Do not infer organizational authority from a learner role or from access to a screen.\n\nKeep external content separate from workflow instructions. A fetched page can contain text that asks an assistant to change its behavior; that text is data for the task, not a new authorization. Validate required inputs and outputs before using them in later steps. State what counts as an invalid result.\n\nAdd timeout, duplicate-input and partial-failure behavior. A second trigger should not accidentally produce a second external effect. The sandbox can demonstrate stopping and manual review without implementing a production queue. Preserve these limits in the handoff so the next builder knows which controls remain design requirements.", "worked_example": "The fictional checklist flow permits public or fictional lesson briefs, produces one draft and stops for review. A dummy input saying “ignore the rules and email this” is treated as task data and rejected as outside scope. No external sending tool exists in the rehearsal.", "evidence": [ "Data-and-effect boundary table", "Review and rejection rules", "Failure-state specification" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-OPS201-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-OPS201", "SOURCE-DOC25", "SOURCE-DOC04" ], "body": { "title": "Rehearse Before Release", "course_id": "OPS201", "lesson_id": "OPS201-L4", "objective": "Run a dummy workflow rehearsal and produce a precise acceptance handoff.", "teaching": "Acceptance cases translate the specification into observable behavior. Write ordinary, blank-input, duplicate, unavailable-tool and out-of-scope cases before rehearsal. Give each an expected result. An expected stop is a successful result when it prevents a step the workflow should not perform.\n\nRun only the mechanisms actually available in the sandbox. A manual simulation can inspect sequence and decisions; it cannot prove integration reliability or permission enforcement. A local code test can check specified logic without establishing browser rendering or a live service's behavior. Label the evidence by what ran.\n\nRecord version, environment, input, expected result, observed result and defect. Correct failures and rerun the affected cases. If a change touches shared logic, repeat the cases that depend on it. Preserve unresolved defects rather than converting them into a general “passed” label.\n\nThe capstone is a specification, mechanism map, boundary record, dummy acceptance evidence and handoff. Include a clear release state and remaining implementation requirements. This course does not deploy the flow or connect real accounts. A useful handoff lets a later builder review the design without guessing what has already been executed.", "worked_example": "Five manually simulated cases produce one draft for valid input and four stops for invalid or unavailable conditions. The record says “manual sequence rehearsal,” not “live integration passed.” A future builder still needs to implement and test actual tool permissions and duplicate-effect handling.", "evidence": [ "Five-case acceptance record", "Versioned correction log", "Sandbox workflow handoff" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-BUS201", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-DOC08", "SOURCE-DOC09" ], "body": { "title": "Productize a Useful Skill | original course application", "original_application": "Package a demonstrated skill into a clear educational product or fixed-scope service concept.", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-BUS201-L1", "LESSON-BUS201-L2", "LESSON-BUS201-L3", "LESSON-BUS201-L4" ], "version": "4.1" }, { "id": "LESSON-BUS201-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-BUS201", "SOURCE-DOC09", "SOURCE-DOC08" ], "body": { "title": "Choose the Outcome", "course_id": "BUS201", "lesson_id": "BUS201-L1", "objective": "Define a useful skill-based result and distinguish a buyer hypothesis from evidence.", "teaching": "Productizing a skill means making a useful result easier to understand, scope and deliver. Begin with a task you can perform and an audience that may need it. “Knowledge services” is broad. “Organize a small set of public training files into a searchable handoff” names an output a reviewer can inspect.\n\nSeparate your ability to produce that output from evidence that someone wants it. A completed sample demonstrates a capability within its conditions. It does not establish demand, a market size or willingness to pay. The SBA planning reference provides a starting place for research questions; it does not validate this particular offer.\n\nWrite the buyer's trigger, current workaround and cost of the problem as hypotheses. Where no actual interview occurred, keep the status unknown. Design neutral questions about recent behavior rather than asking people to praise the idea. Use fictional responses only as teaching fixtures.\n\nChoose an outcome that can be bounded and demonstrated with original or appropriately authorized material. Avoid promising a legal, financial or health result beyond the work delivered. The first course artifact is a useful-outcome statement and a plan to discover whether it matters to the intended audience.", "worked_example": "A fictional offer organizes twelve public lesson files and supplies an index plus handoff notes. The sample can show file organization and search behavior. It cannot show that a buyer has requested the service or that a private organization has approved access.", "evidence": [ "Useful-outcome statement", "Five-question research plan", "Sample boundary and demand status" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-BUS201-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-BUS201", "SOURCE-DOC09", "SOURCE-DOC08" ], "body": { "title": "Choose the Delivery", "course_id": "BUS201", "lesson_id": "BUS201-L2", "objective": "Compare a product, course and service using the same audience task.", "teaching": "A product, a course and a service help in different ways. A downloadable tool supports repeated self-directed work. A course develops the learner's ability through instruction and practice. A service completes a defined task for the client. One audience need may justify one of these, a sequence, or no new offering.\n\nCompare formats against the actual task: complexity, customization, learner effort, delivery effort and support. Do not assume a digital download has no maintenance cost. Instructions, compatibility, source changes and questions can all create work after the first version is made.\n\nSketch a small delivery model for each plausible format. Name the input required, promised output, estimated work and limits. Keep time estimates labeled until measured. If the user lacks the skill to use a tool independently, a course or limited service may be more useful than adding more features to the download.\n\nFit the proposal to existing work before creating another competing product. Decision tools can extend Money Command; learning resources can connect to existing NVU pathways. The decision is about usefulness and maintainable delivery. It does not assign a seller, establish IP ownership or authorize a public listing.", "worked_example": "For the same public-file task, a tool supplies a blank index, a course teaches organization and search, and a service produces the index from an agreed set of files. The fictional team selects a small service sample first because input quality varies; all time estimates remain unvalidated.", "evidence": [ "Three-format comparison", "Effort and support assumptions", "Delivery decision with rationale" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-BUS201-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-BUS201", "SOURCE-DOC09", "SOURCE-DOC08" ], "body": { "title": "Scope the Offer", "course_id": "BUS201", "lesson_id": "BUS201-L3", "objective": "Draft inclusions, exclusions, acceptance criteria and a change process.", "teaching": "A scope describes what will be delivered and the conditions needed to deliver it. Name the input limit, output, format, review point and completion criteria. “Set up a vault” can hide many expectations. “Index twelve approved public files and provide two repeatable search examples” is easier to review.\n\nList exclusions where misunderstanding is likely. A public learning corpus does not include private trust administration, legal advice or ongoing hosting unless separately defined. A course completion record does not grant a professional role. An exclusion should clarify the promised work without turning the document into an unrelated warning list.\n\nDescribe how a change would be handled: identify the requested difference, evaluate effort and dependencies, then agree a revised scope before doing extra work. Do not silently widen a small sample into production operations. Keep the deliverable version and acceptance observations together.\n\nRecord proposed operational roles, rights questions and required inputs without inventing legal ownership or contracting authority. This course produces a draft scope for review, not an executed agreement. Prices, actual seller identity and commercial terms remain decisions supported by the real entity and rights records.", "worked_example": "The fictional sample covers twelve public files, one local index, two search cases and a handoff. It excludes private ingestion and hosting. Adding 500 mixed-access files becomes a change request with new access, effort and acceptance questions; it is not treated as included work.", "evidence": [ "Draft delivery scope", "Acceptance and change criteria", "Unresolved operational and rights record" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-BUS201-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-BUS201", "SOURCE-DOC09", "SOURCE-DOC06" ], "body": { "title": "Test Before Expansion", "course_id": "BUS201", "lesson_id": "BUS201-L4", "objective": "Use a dummy delivery rehearsal and cost model to make a bounded next decision.", "teaching": "A useful offer must be deliverable as well as understandable. Rehearse the scoped work with fictional or public inputs. Record actual active time, waiting, defects, support questions and the final handoff. If the rehearsal did not run, keep estimates labeled and the delivery status unrun.\n\nSeparate sales, cash costs and a planning value for owner time. The supplied fictional model uses 120 per job, 30 variable cash cost, 300 fixed cash costs and two hours per job valued at 25 per hour. At ten jobs, cash surplus before taxes and owner pay is 600; after the chosen time value it is 100. These are model outputs, not accounting profit or an income forecast.\n\nChange one assumption and inspect the result. Lower job count, longer delivery time or additional support can change the decision. Record omitted taxes and other costs rather than treating the model as a complete business account. Correct arithmetic does not establish demand.\n\nFinish with a scope, original sample, rehearsal record, assumptions and proposed demand check. Choose continue, revise or stop using predeclared learning criteria. Expansion should follow evidence about both the audience need and the ability to deliver. The capstone remains a draft offering package with no public price or listing assigned.", "worked_example": "At six fictional jobs the model gives 240 cash surplus and -60 after chosen owner-time value; at fourteen it gives 960 and 260. A longer-than-estimated delivery rehearsal would justify changing the hours assumption. The course does not infer actual sales from these scenarios.", "evidence": [ "Delivery rehearsal or honest unrun record", "Cost scenarios and assumption change", "Productization capstone" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-CON201", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-DOC19", "SOURCE-DOC20", "SOURCE-DOC23" ], "body": { "title": "Contracts: Reading, Obligations & Evidence | original course application", "original_application": "Read a fictional agreement systematically, map obligations and identify the questions requiring applicable authority.", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-CON201-L1", "LESSON-CON201-L2", "LESSON-CON201-L3", "LESSON-CON201-L4" ], "version": "4.1" }, { "id": "LESSON-CON201-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CON201", "SOURCE-CH17", "SOURCE-CH18", "SOURCE-DOC19", "SOURCE-DOC20" ], "body": { "title": "Identify the Setting", "course_id": "CON201", "lesson_id": "CON201-L1", "objective": "Define a fictional agreement-reading question without assuming its governing law.", "teaching": "Agreement reading begins with the actual document and a defined question. Record the document title, date, version, parties as written, subject matter and the clause you need to understand. A reader can map what a document says before reaching a conclusion about its legal effect.\n\nSeparate text, facts, law and interpretation. A payment clause is text. Whether an invoice was received is a factual question. Which legal rules govern depends on the relevant jurisdiction and other circumstances. Your initial interpretation is a research hypothesis, not a substitute for those steps.\n\nUse a fictional agreement in this course. The Law Academy source is described as UK-law education, while the contract-law creator reference points to legacy resources. Those connections are research leads with recorded access limits. Neither supplies an automatically applicable rule for an unspecified U.S. matter.\n\nWrite the question narrowly enough to research. “Who is right?” is too broad. “What does the fictional draft say about the review period, and which facts and rules would need checking before judging legal effect?” produces a useful reading record. Preserve unresolved questions rather than supplying missing terms from a video title or a word's historical origin.", "worked_example": "A fictional draft says a public-file index is delivered for review within five days and mentions a later revision. The reader records version A and asks what event starts the five-day period. The jurisdiction, definition of delivery and legal effect remain unresolved.", "evidence": [ "Fictional document cover record", "Text/fact/law distinction", "Bounded research question" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-CON201-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CON201", "SOURCE-DOC19", "SOURCE-DOC20" ], "body": { "title": "Map the Duties", "course_id": "CON201", "lesson_id": "CON201-L2", "objective": "Extract stated actors, actions, conditions and deadlines from a fictional draft.", "teaching": "A duty map follows the words on the page. For each relevant clause, name the actor, action, object, trigger, deadline and any condition or exception. Quote only what is needed in your private working record and attach the exact clause location. The course example is original so it can be used freely within this exercise.\n\nDistinguish a stated obligation from an assumption about performance. A document can require review within five days without establishing that delivery happened or that the recipient reviewed it. Record proposed evidence separately: a dated submission record, a response or a versioned correction.\n\nLook for terms that connect clauses. A revision period may depend on a review notice, while the review notice may depend on a defined delivery event. Missing definitions and conflicting timelines belong in an issue list. Do not repair them silently by choosing the interpretation you prefer.\n\nThis is a document-reading method, not a ruling that a clause is enforceable or that a remedy is available. Legal effect requires appropriate jurisdictional research and facts. The map is useful because it makes the text, gaps and necessary evidence visible before anyone argues for a conclusion.", "worked_example": "Original fixture: “The organizer supplies twelve public files on Day 1. The builder submits index version A on Day 5. The organizer returns one consolidated review within five days after submission.” The map identifies two actors and three actions. Whether “days” means calendar or business days is flagged rather than invented.", "evidence": [ "Duty-and-deadline map", "Evidence-needed column", "Ambiguity and issue list" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-CON201-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CON201", "SOURCE-DOC23" ], "body": { "title": "Read the Rule in Its Jurisdiction", "course_id": "CON201", "lesson_id": "CON201-L3", "objective": "Distinguish statutory scope, defined terms and judicial construction in a labeled example.", "teaching": "A rule must be read within its jurisdiction, version and subject matter. For a narrow reading exercise, the official Nevada compilation identifies Article 2 as the sales article. NRS 104.2102 addresses goods and specifies treatment of hybrid transactions. Record those features without assuming the article governs the fictional service project.\n\nRead the scope provision with the relevant definitions. The legislature's treatment of goods, services and mixed transactions matters more than a general slogan about contracts. A hybrid classification may itself require facts and legal analysis. Keep the text's conditions visible rather than reducing it to “all contracts” or “only goods, with no qualification.”\n\nThen distinguish statutory text from judicial construction. To apply a proposition in a real question, you would identify relevant courts, decisions interpreting the provision, factual similarities, later changes and current treatment. This build does not supply that case-law analysis. A statutory reading exercise alone cannot establish a complete enforceability opinion.\n\nWord history can suggest a research question, but it does not replace governing text or a court's construction. Build a source card that states exactly what was inspected, what proposition it supports and what remains unanswered. The outcome is disciplined scope reading and an explicit research gap.", "worked_example": "The learner reads the official Nevada scope section and notes its goods and hybrid-transaction distinctions. They do not apply it automatically to the fictional public-file service. Their next questions concern classification, governing law and relevant judicial decisions; no remedy or enforceability conclusion is supplied.", "evidence": [ "Jurisdiction/version/source card", "Narrow scope paraphrase", "Application limits and case-law research questions" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-CON201-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CON201", "SOURCE-DOC23", "SOURCE-DOC19", "SOURCE-DOC20" ], "body": { "title": "Preserve the Record", "course_id": "CON201", "lesson_id": "CON201-L4", "objective": "Assemble a fictional chronology and issue memo without converting it into an actual filing.", "teaching": "A useful research record lets another reader follow the document, events, sources and uncertainty. Keep the original fictional draft and any changed version distinct. Record the date, actor, event and supporting item for each chronology entry. If a date is assumed for the exercise, label it.\n\nSeparate a contemporaneous item from a later summary. A message acknowledging receipt may support a narrow fact; your later chronology explains how you organized it. Do not overwrite the underlying item to make the story cleaner. Keep the location and version of each supporting item in the evidence list.\n\nWrite an issue memo with the question, relevant text, assumed facts, inspected authority, alternative readings and missing research. A careful memo may end with an unresolved question. That is more useful than a confident conclusion unsupported by the jurisdiction or evidence.\n\nThe capstone is an educational reading packet: cover record, duty map, fictional chronology, source card and issue memo. It is not sent to a court, counterparty or agency. Using an actual matter would require its own authorized scope, governing-law research and handling of real records. Completion here concerns the quality of the research method and its stated limits.", "worked_example": "The fictional chronology includes Day 1 file receipt, Day 5 submission and an assumed Day 8 review. The Day 8 event is labeled a teaching assumption. The issue memo asks when review begins and whether definitions are missing, while withholding a conclusion about breach or remedy.", "evidence": [ "Versioned fictional record and chronology", "Issue memo with alternatives", "Complete agreement-reading capstone" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-CRIT201", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-DOC21", "SOURCE-DOC22", "SOURCE-DOC24" ], "body": { "title": "Reasoning, Media & Learning | original course application", "original_application": "Examine an argument, trace a digital source and explain a subject through an original learning artifact.", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-CRIT201-L1", "LESSON-CRIT201-L2", "LESSON-CRIT201-L3", "LESSON-CRIT201-L4" ], "version": "4.1" }, { "id": "LESSON-CRIT201-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CRIT201", "SOURCE-DOC22", "SOURCE-DOC24" ], "body": { "title": "Map the Argument", "course_id": "CRIT201", "lesson_id": "CRIT201-L1", "objective": "Distinguish premises, conclusions and types of inference using original examples.", "teaching": "An argument offers reasons for a conclusion. Identify the conclusion first, then list the premises meant to support it. A sentence can be memorable without supplying a reason. Reconstruct the argument fairly before evaluating it, and mark any premise you added to make the reasoning explicit.\n\nDeductive validity concerns whether true premises would require the conclusion. It does not establish that the premises are actually true. Inductive reasoning supports a probable conclusion from observations. Abductive reasoning proposes an explanation for evidence. These distinctions are introduced in the referenced philosophy materials; the cases here are original.\n\nFor each form, ask a fitting question. For deduction, try a situation in which the premises are true and the conclusion false. For induction, examine the observations and their relevance. For an explanation, consider plausible alternatives and what could distinguish them.\n\nDo not treat the labels as grades of personal intelligence. The goal is to identify what the argument can support and where evidence is missing. A well-labeled weak argument is easier to improve than an attractive statement whose assumptions remain hidden.", "worked_example": "Original deduction: every completed card in this exercise has an exact URL; card A is completed; therefore card A has an exact URL. The form works if the premises hold. Seeing three cards with broken links instead supports only a limited observation; guessing a migration caused them proposes an explanation.", "evidence": [ "Argument map", "Inference classification with reason", "Challenge suited to the inference" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-CRIT201-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CRIT201", "SOURCE-DOC21", "SOURCE-DOC22" ], "body": { "title": "Trace the Source", "course_id": "CRIT201", "lesson_id": "CRIT201-L2", "objective": "Use lateral reading and source comparison to inspect a factual premise.", "teaching": "Source tracing asks where a statement came from and what was actually inspected. Begin with the exact claim, page and date. Follow an attribution to the original material when possible. Several pages repeating one unsupported statement are not several independent observations.\n\nLateral reading means leaving the original page to investigate its source and corroboration. The Crash Course companion page provides a starting reference for this approach. In the exercise, inspect creator identity, the original evidence and an independent or primary account appropriate to the claim. Record when a page is unavailable.\n\nCompare what the sources support, not only whether their language sounds similar. A headline may compress a conditional finding into a broad promise. A description may identify a topic without revealing the full argument. Keep title-only, description, transcript and complete-video inspection distinct.\n\nEnd with a source comparison and a bounded statement. You may narrow, suspend or reject the original premise. Preserve disagreement where the sources do not resolve it. A source's reputation can guide attention, but the actual evidence and its relevance still matter to the claim.", "worked_example": "Three fictional posts say an app works offline, all pointing to the same announcement. The announcement describes a downloaded reference page, not account login or synchronization. The corrected premise is limited to the announced page; actual device behavior remains untested.", "evidence": [ "Source trail", "Comparison with dependence and access notes", "Bounded corrected premise" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-CRIT201-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CRIT201", "SOURCE-DOC24", "SOURCE-DOC21" ], "body": { "title": "Check the Explanation", "course_id": "CRIT201", "lesson_id": "CRIT201-L3", "objective": "Compare plausible explanations and define a discriminating observation.", "teaching": "An explanation tries to account for evidence. Begin by stating what was observed without adding a cause. “Two files did not open” is different from “the update destroyed the files.” The second statement may be a hypothesis, but it requires support beyond the failed opening attempts.\n\nGenerate plausible alternatives that fit the context. A wrong path, an unavailable application or a damaged file might each explain a failed attempt. Alternatives should be relevant rather than an endless list of remote possibilities. Identify what each would lead you to expect.\n\nChoose a feasible observation that could distinguish the alternatives. Checking the path on a copy may be more informative than repeating an unsupported accusation. Preserve the original record and avoid disruptive changes. A test that rules out one explanation may leave several others unresolved.\n\nReport the result with its limit. “The copied file opens at the corrected path in this environment” supports a narrow observation. It does not prove every file is sound or establish what originally changed the path. Good explanation remains open to revision when new evidence arrives.", "worked_example": "A fictional lesson file fails to open from an old shortcut. The copied file opens from its actual folder. That observation supports a path-related explanation for this attempt; it does not show that every file is healthy or identify who changed the shortcut.", "evidence": [ "Observation/hypothesis distinction", "Alternative-explanation table", "Discriminating-check record" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-CRIT201-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-CRIT201", "SOURCE-DOC21", "SOURCE-DOC22", "SOURCE-DOC24" ], "body": { "title": "Teach and Revise", "course_id": "CRIT201", "lesson_id": "CRIT201-L4", "objective": "Produce a short explanation that distinguishes evidence, inference and uncertainty.", "teaching": "Teaching a corrected account tests whether you can make the reasoning usable. State the question, the relevant observation, the inference and the uncertainty. Avoid packing these into a single confident slogan. A learner should be able to identify which part is supported and which part remains a proposal.\n\nUse an original example and a fresh check question. Ask the listener to apply the distinction to a new case, rather than only repeat your words. If no listener participates, record a solo teach-back rehearsal. Do not invent audience understanding or feedback.\n\nRevise when the explanation invites an overbroad conclusion. A phrase such as “the system works offline” may need to become a description of the specific downloaded task tested. Keep the earlier wording and reason for the correction. This makes the change part of the learning record.\n\nThe capstone combines an argument map, source comparison, alternative explanation, corrected teaching draft and rehearsal record. It should show how the evidence changed the conclusion or its confidence. Completion does not require agreement on every interpretation; it requires traceable reasoning and a claim no broader than its support.", "worked_example": "The original draft says “the update broke the vault.” The revised explanation says an old shortcut failed, the copied file opened from its folder, and the earlier path change remains unexplained. A fresh question asks whether that establishes the state of every file. The correct answer is no.", "evidence": [ "Corrected teaching draft", "Fresh check and rehearsal status", "Argument/source/explanation capstone" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "INSIGHT-MA202", "record_type": "insight", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "SOURCE-CH01", "SOURCE-CH20", "SOURCE-PL02", "SOURCE-DOC18" ], "body": { "title": "Self-Concept, Language & Daily Practice | original course application", "original_application": "Explore an identity statement as an interpretation and connect it with a voluntary, observable practice.", "source_relationship": "Source links identify research and inspiration; lesson claims retain their individual limits", "learning_state": "Public practice course; learner pilot pending" }, "links": [ "LESSON-MA202-L1", "LESSON-MA202-L2", "LESSON-MA202-L3", "LESSON-MA202-L4" ], "version": "4.1" }, { "id": "LESSON-MA202-L1", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA202", "SOURCE-PL02", "SOURCE-CH20", "SOURCE-CH01" ], "body": { "title": "Ask the Identity Question", "course_id": "MA202", "lesson_id": "MA202-L1", "objective": "Explore a self-description while distinguishing belief, aspiration and observable conduct.", "teaching": "An identity question can invite reflection on how you describe yourself and what you choose to practice. This course uses that question as voluntary meaning-making. It does not diagnose the learner or claim that a self-description determines every external event. You may use a fictional character instead of personal material.\n\nSeparate a belief about identity, an aspiration and an observed action. “I value craftsmanship” expresses a commitment. “I want to become more reliable” describes an aim. “I revised one instruction on Tuesday” records an action. These statements can relate without becoming interchangeable proof.\n\nThe supplied Rev. Ike playlist was available only through title metadata. Its title can prompt a question, but this course does not summarize its sermons, sequence or complete teaching. Serenity Knowledge and other channel references likewise retain their recorded access limits. The exercises and examples here are original.\n\nChoose one self-description that can be explored gently through conduct. Avoid labels that turn a missed action into a permanent judgment. The learner controls whether personal reflection is shared. A public artifact may show only the chosen practice and its limits, leaving belief and life history private.", "worked_example": "A fictional learner explores “I am a careful researcher.” They label it a chosen self-description, list an aspiration to improve, and identify one observed source card. They do not use that single card as proof of an unchanging identity or a guarantee of future success.", "evidence": [ "Labeled reflection or fictional case", "Belief/aspiration/action distinction", "Privacy and practice question" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MA202-L2", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA202", "SOURCE-CH20", "SOURCE-CH01", "SOURCE-DOC18" ], "body": { "title": "Read the Language", "course_id": "MA202", "lesson_id": "MA202-L2", "objective": "Rewrite an absolute self-statement into a chosen practice without erasing its symbolic meaning.", "teaching": "Language can express a symbol, a hope, a commitment or a factual claim. Ask which job a sentence is doing before evaluating it. “I carry light into my work” may be a meaningful metaphor. It does not, by itself, describe a measured physical effect or guarantee how other people will respond.\n\nRead absolute words carefully: always, never, everyone and guaranteed can make a reflection claim more than the learner intends. A statement such as “I never lose focus” may be less useful than “When I notice distraction, I return to one chosen step.” The revision names an action and leaves room for ordinary interruptions.\n\nKeep the learner's interpretation visible. Rewriting a sentence for practical use does not require rejecting its tradition or symbolism. If you make a historical assertion about the phrase, it needs a suitable source. If you make a scientific assertion, it needs evidence appropriate to that assertion. Personal meaning alone does not establish either.\n\nDraft an affirmation or reflective prompt that supports a controllable action without blaming hardship on thoughts or vibration. You may decline affirmations and use a plain instruction instead. The aim is language that helps you choose and review conduct, with no demand to adopt a particular metaphysical belief.", "worked_example": "The fictional phrase “My frequency guarantees success” becomes “I choose to prepare one useful contribution and review what happened.” The learner may retain “frequency” as a personal metaphor in a private journal, while the shared task record makes no scientific or financial promise.", "evidence": [ "Language classification", "Revised reflective statement", "Plain-action alternative with limits" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MA202-L3", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA202", "SOURCE-CH20", "SOURCE-CH01" ], "body": { "title": "Make the Action Visible", "course_id": "MA202", "lesson_id": "MA202-L3", "objective": "Design a voluntary seven-day practice with baseline, cue, output and recovery.", "teaching": "A reflection becomes a practice when it has an action that can be attempted. Choose something small: improve one sentence, prepare one material or record one question. Connect it to an ordinary cue and a brief time budget. The action should express the chosen meaning without being treated as proof of a cosmic mechanism.\n\nRecord the starting point before the trial. It may be an empty source-note folder or an existing draft instruction. Choose a visible output that can be inspected without disclosing personal history. A practice card can record completion and context while keeping a private reflection separate.\n\nUse the seven-day record to capture attempted action, actual minutes, output and interruptions. If a day is missed, record it and return at the next feasible cue. A recovery plan should support participation, not demand punishment or retrospective perfection.\n\nThis is a short observation exercise. It cannot establish clinical benefit, guaranteed income or causation between a phrase and an external event. Material constraints and other people's choices remain relevant. The useful evidence is what you attempted, what you produced and how the design fit your circumstances.", "worked_example": "The fictional learner chooses “careful researcher,” with a five-minute source-card practice after lunch. The baseline is zero cards for the current project. Two blocked days stay in the record. The output is a card, while any personal reflection remains optional and private.", "evidence": [ "Seven-day practice specification", "Baseline and recovery rule", "Actual record or clearly unrun template" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" }, { "id": "LESSON-MA202-L4", "record_type": "lesson", "lane": "public_education", "audience": "public", "epistemic_status": "PROPOSED", "review_state": "reviewed", "provenance": [ "INSIGHT-MA202", "SOURCE-CH20", "SOURCE-PL02", "SOURCE-DOC18" ], "body": { "title": "Reflect without Overclaiming", "course_id": "MA202", "lesson_id": "MA202-L4", "objective": "Write a self-concept practice review that distinguishes meaning from evidence.", "teaching": "Review the chosen self-description alongside the actual practice record. Ask whether the language helped you remember a useful action, whether the action fit the time available and whether the output served its task. Your personal interpretation of the week can coexist with a separate factual account.\n\nDescribe observations narrowly. “I completed four source cards during this trial” is different from “the affirmation caused every improvement.” Consider alternatives such as a clearer task, prepared materials, available time or support. A short personal trial cannot isolate those causes.\n\nChoose a proportionate revision. You might keep the phrase, replace it with a plain instruction, reduce the task or stop the practice. None of these choices requires a judgment about the learner's worth or spiritual status. Keep voluntary participation and private reflection intact.\n\nThe capstone includes labeled reflection, revised language, a practice plan, an honest record and a review. If the trial did not run, state that the capstone is a design with unrun observation. Completion concerns discernment and usable conduct. It does not certify an identity, diagnose a condition or promise control over outside events.", "worked_example": "The fictional review reports four cards, two blocked attempts and one missed cue. The learner says the phrase felt meaningful but cannot isolate its effect from prepared materials. They keep a smaller practice and record the next review date. The result remains a fictional teaching case.", "evidence": [ "Bounded observation and meaning review", "Alternatives and revision decision", "Complete self-concept practice capstone" ], "status": "Public educational edition; learner pilot pending" }, "links": [], "version": "4.1" } ]