Source Provenance

Harness Guides came out of architecture study, not product worship.

What this means

• the original long-form blueprint remains available as reference
• chapter pages now teach the systems in Python-first terms
• TypeScript-specific source shape is preserved where it helps prove a pattern, not where it slows down implementation

How to use provenance correctly

• use the chapter pages to learn what to build
• use the full blueprint to see where the pattern came from
• avoid copying names, UI quirks, or source-tree trivia when the real lesson is the runtime boundary

Primary rule

The purpose of provenance is to improve engineering confidence, not to keep the docs trapped in one implementation language.