Skip to content

Source Index and Licensing Boundaries

This is not a copy of every footnote on the site. It is a source map. Each in-depth tutorial records its verification date and keeps the links actually used, together with their applicable boundaries, at the bottom of the page. This page helps you decide which kind of source to revisit when checking a claim.

LearnPrompt divides evidence into three tiers:

TierPrimary purposeWhat it cannot prove on its own
Primary sourcesVerify product capabilities, commands, permissions, specifications, versions, and release statusThey do not automatically prove that an article example fits your project
Secondary topic mapsDiscover problem spaces, cases, and learning structuresThey cannot replace current official facts or automatically grant permission to republish
Field experimentsProve a specific Showcase with frozen fixtures, scripts, receipts, and reviewsThey cannot be generalized to every version, environment, or permission combination

For model names, execution surfaces, sign-in, sandboxes, approvals, Cloud, review, or CLI parameters, use these official pages plus the current --help output and actual UI. Do not infer them from secondary tutorials.

Agent engineering, Skills, and Loop Engineering

Section titled “Agent engineering, Skills, and Loop Engineering”

Articles about harnesses, feedback, orchestration, and loops also cite official product documentation, source repositories, or field experiments for the question at hand. No single official page can vouch for every implementation of these concepts.

Obsidian’s files, properties, links, Search, and Sync capabilities come from its official documentation. Folder roles, placement contracts, handoff packets, and Git change gates are LearnPrompt editorial contracts; they are not presented as native Obsidian mechanisms.

Framework versions, protocols, scope, pairing, installation methods, and cost entry points change quickly. A frozen version in an article only states when it was verified; check the release, official documentation, and real runtime again before use.

Orange Book attribution and licensing boundaries

Section titled “Orange Book attribution and licensing boundaries”

The Orange Book repositories above are maintained by Huashu (Huashu / GitHub alchaincyf) and are important topic maps for this curriculum redesign. LearnPrompt does not hide that influence by removing attribution or sources.

As of 2026-07-12, we read the LICENSE and README on each repository’s current default branch and obtained the license matrix below. A GitHub API spdx_id: null or NOASSERTION only means the platform did not recognize a standard SPDX identifier; it does not establish that a repository declares no license.

RepositoryCurrent declarationBoundary when using it
Claude Code Orange BookREADME: CC BY-NC-SA 4.0May be shared and adapted under that license; attribution, non-commercial use, and ShareAlike are required
Claude Code Source Analysis Orange BookREADME: for education and research only, with trademark and leaked-code disclaimersA custom statement; do not expand it into a standard open license
Codex Orange BookREADME: CC BY-NC-SA 4.0May be shared and adapted under that license; attribution, non-commercial use, and ShareAlike are required
Harness Engineering Orange BookREADME: for learning and discussion only; cite the source when quotingA custom statement; it does not automatically allow commercial redistribution or adaptation
Agent Skills Orange BookREADME: personal and educational use; no commercial redistribution without authorizationCustom, non-commercial personal and educational-use boundaries
Loop Engineering Orange BookRepository LICENSE: MITMay be used, copied, modified, and distributed under MIT, while retaining the license text
Obsidian AI Orange BookREADME: for learning and discussion; republication and quotation welcome with attributionA custom attribution-and-sharing statement, not equivalent to CC/OSI licensing
Hermes Agent Orange BookCurrent repository LICENSE: MIT; README says 2.0 changed from the earlier CC BY-NC-SA 4.0 to MITCurrent version is MIT; still check the corresponding version when citing older materials
OpenClaw Orange BookREADME: content is for educational use only and related trademarks belong to their ownersA custom statement; it does not automatically permit copying, adaptation, or commercial distribution

Licenses apply to the material each repository covers; they do not automatically cover third-party screenshots, trademarks, upstream code, or externally linked assets.

Accordingly, this project uses the following conservative boundaries:

  1. Orange Books are used for topic selection, problem maps, and leads to verify.
  2. Volatile facts return to primary sources or field experiments; descriptions in the books are not treated as current truth.
  3. PDF body text, screenshots, and images without an explicit covering relationship are not copied into public tutorials; third-party assets must also be excluded from MIT or CC repositories.
  4. When using material expressly authorized by a repository, record the author, original link, version, license, modification method, and verification date item by item; do not infer a license for an entire series from one book.
  5. Keep the actual Orange Book links used by, and the applicable boundaries for, every article at its bottom.

Every verified in-depth tutorial has a research/ directory containing at least:

  • brief.md: the reader task, scope, and non-goals.
  • horizontal-research.md: adjacent approaches, differences, and applicability boundaries.
  • vertical-research.md: a vertical evidence chain for key concepts.
  • evidence-ledger.md: a mapping between body claims and sources.
  • asset-ledger.md: image sources, licenses, modifications, and visual checks.
  • review.md: an independent reviewer’s itemized conclusions, findings, and final verdict.
  • showcase/: frozen fixtures, scripts, outputs, and rejection cases; individual files are organized as each article requires.

The research directory records how an article reached its conclusions; it is not a mirror of source material. Public MDX does not display an independent source-card component, but removing that component does not mean removing the sources.

  • Product capabilities, commands, prices, permissions, and releases are high-drift information and are used according to the article’s verification date.
  • An automated external-link check returning 403 only means the automated request was blocked. It must be checked manually in a browser and must not be marked valid or broken directly.
  • Deep research links that have not reached a public branch do not pass a publication-candidate gate; verify them after pushing, or replace them with stable links before publication.
  • When an official page moves, update it first to the current page on the same official domain, and retain the old link and reason for the change in the research record.

The previous LearnPrompt course remains available at v1.learnprompt.pro. It is a historical content entry point, not the factual, structural, or verification gate for the new tutorials.