Yinyang package maintenance

Use MODEL.md for the package's source roles, interpretive boundaries, and maintenance method. The core views state the numbered claims; essays develop their arguments. Read the affected source and its dependencies rather than reproducing the full philosophy in every file.

The user-facing work should be readable both within each piece and across the collection. Existing wording, section order, and examples are revisable. Preserve the relations that carry the argument, useful source attribution, and actual consumer contracts; remove repetition and obsolete scaffolding.

Authored and situated sources

The public Empty entrypoint owns its invocation; actual private entrypoints stay with their owners. Forming and revising working models connects philosophical expression and models. The six writing guides under references/formation/, including how to revise, own their actual directions. Environmental realization belongs to the environment guide; revision guidance belongs to the revision guide. The package guide owns common/situated structure and projection. Refer to these owners where a document needs their method instead of restating it.

Follow MODEL.md — Source and consumer roles for the six-question contract, source-refresh dependencies, whole-account coherence, private material, and common projection boundaries. That owner keeps these maintenance contracts together; this file locates them for repository work.

Edition and publication coherence

Keep complete English and Chinese reader editions aligned; model-facing maintenance prose is English. Preserve existing YY identifiers as references to their claims. Repair links when changing titles, paths, or anchors.

Diagram candidate JSON owns the authored relationships. Regenerate HTML/SVG and inspect the resulting relationships and readability when a diagram changes. Website and plugin copies are projections; edit their actual source owner. The public package owns the philosophical essays and practical guide; the native Site owns their presentation.

Preserve licenses, third-party notices, and public/private boundaries under MODEL.md and LICENSE. The philosophy is a usable example: recipients may adopt, combine, challenge, or author a different work.