Maintaining the Yinyang collection

Yinyang develops a philosophy for assisting personal recursive self-improvement, realized through Yinyang and a collection of reusable Skills. Personal RSI concerns improved understanding, judgment, creation, action, and the methods producing those improvements within a person's actual support relations. The essays own its argument; descriptions, collaboration, and tools give it practical form. Each member under skills/ owns its entrypoint, methods, references, documents, diagrams, scripts, and other supporting resources. Independent members retain their own purpose and specialist responsibilities. Collection membership does not make every resource part of Yinyang or impose its philosophical account.

The collection offers its working Skills as examples for adoption, combination, and independent authorship. Yinyang's philosophy is this example's developed account, not a required worldview for recipients. Its literary/philosophical form can inspire a differently organized work. Preserve the distinction between maintaining the existing implementation and authoring another one. The website projects selected source documents and diagrams; maintain their meaning here, with source revision and rights traceable in that reading surface.

The root README editions are the collection entrance. Keep their descriptions aligned with the actual members and preserve full semantic parity. English is the first reading language for English-capable readers and models; model-facing maintenance prose remains English.

Use the native English Skill identifier for package names, entrypoint headings, catalog links, and website titles in both reading languages. Put the Chinese invocation cue and purpose in description, prefixed with <用户自制> for these author-created Skills, followed by the accurate English discovery description. The website renders that source description as readable text, including its literal angle brackets. Names and descriptions have separate display roles.

Public method and private instances

skills/yinyang/ retains canonical essays, diagrams and shared method sources at their established paths. It has no public Skill entrypoint and is not a distributed Full package. The author's actual entrypoint and personal models stay at their private owner. skills/yinyang-empty/ is the Empty edition: reverse alignment, crossed roles and dialectical return, six formation guides, Core views as attributed suggestions, practice overview, formation/revision, daily collaboration, and Personal guidance. Empty contains no docs/ or diagrams/. Recipients develop their own philosophy, Personal material, and six complete working accounts with their model; the public package ships no private substance. Empty supplies unfilled Personal and Situated starters, with four empty Personal areas plus six actual starters marked status: unfilled; these are templates rather than actual accounts. The simple route retains the six original actual files, direct model synthesis and private Git/GitHub persistence, with no Hindsight installation requirement. Optional native Hindsight configuration implements the same six full questions, revision steps and whole-six coherence, projected to those paths or an explicit all-six binding. Both practice routes start from Empty. Keep one shared philosophy/method source for those tools.

Shared method content remains authored under skills/yinyang/references/. scripts/build-yinyang-empty.py projects its declared selection into Empty, relocating the selected guides and converting links to omitted essays into optional public reading links. It adapts the shared source's distribution sentence to Empty's unfilled starters. Empty's entrypoint, README editions, and package guidance are authored in its own tree. Do not edit generated Empty references independently. build-plugins.py invokes the selection builder in the same check/apply mode before packaging Empty. Only yinyang-empty is an installable Yinyang plugin, under Yinyang Personal and Internal Use License 1.0. Recipient updates use the chosen edition, preserving their private philosophy, Personal, Situated, and independently authored additions.

Yinyang's MODEL.md owns interpretation of the shared philosophical claims, formation method, reader editions, and supporting resources. Its documents and diagrams live inside skills/yinyang/references/. Other members keep their own instructions and resources. Do not import another repository's philosophical content merely to follow its directory organization.

Publication boundary

The owner selected a fresh public history after correcting the license and removing website implementation source on 2026-11-01. Preserve the private recovery archive and build future public changes on the replacement public main. Do not merge pre-replacement branches back into public ancestry; reapply needed contributions onto the current tree. Replacing history reduces ordinary access to prior versions but cannot revoke earlier license grants or erase external copies and caches. The earlier 2026-10-14 noncommercial edition remains history.

Private website implementation and public reading content

Website implementation source stays in the author's private native Site repository. Do not restore a website snapshot or its exporter to this collection. Canonical Yinyang prose and diagrams remain in skills/Yinyang/ and are projected into the public website through its native content publication route. The Site owns rendering, deployment, rights presentation, and its private source recovery. Publish the reviewed collection source, regenerate the Site's reading projection, and verify the public reader and its canonical links. These are separate repositories with separate histories; the Site's implementation is not a public download. Preserve its existing identity and runtime.

The collection is published as a clean public GitHub repository. Anyone may view, clone, and download it without an application, invitation, download code, or continuing-access grant. Historical private source must stay in its private archive; never publish excluded manuscripts or private records through history. GitHub supplies source archives and independent forks. This collection accepts conversation through Issues and does not accept pull requests of any kind; the author owns revisions and publication. Song requests are for boluopai only, not recording submissions. CONTRIBUTING.md owns the reader-facing guidance. The website presents reading editions and package introductions; all source and downloads go to GitHub package directories or its native repository ZIP. Codex recipients normally install selected plugins from the boluopai GitHub marketplace; archives remain an optional source route. Keep the installation entrance and commands in the GitHub README and docs/codex editions. The website is for reading and introductions, with source links to GitHub; do not repeat installation buttons across its pages or maintain a separate website installer. The catalog at .agents/plugins/marketplace.json owns plugin identity, version and presentation. scripts/build-plugins.py --apply assembles complete portable packages in plugins/ from tracked skills/ sources; its default mode checks byte, mode and coverage equality. Do not edit generated plugin copies. Increment the affected plugin version when its shipped content changes, regenerate, check native installation and discovery, then publish the source and generated packages together. No separate GitHub Release or tag workflow is required. Official directory submission uses a ZIP of the same generated plugin; it is a publisher artifact, not a website download service. Keep private personal adaptations outside plugin caches and never include them in distribution.

Yinyang essays, shared methods, and Empty original material uses the Yinyang Personal and Internal Use License 1.0. It permits downloading, private use and modification, and assistance with paid work. Redistribution and provision as a product or service for others require separate permission, subject to its platform and legal exceptions. Independent outputs remain independently owned. Other packages retain their MIT licenses. LICENSING.md owns the mixed scope; the same scope applies to website reading projections. Site implementation, photos, recordings, and third-party material keep separately stated rights.

Earlier valid CC BY-SA 4.0 and CC BY-NC-SA 4.0 grants remain effective. The owner's 2026-11-01 direction is to correct licensing and the public tree before replacing the public repository history. Preserve a private recovery copy, repository metadata needed by current consumers, and usable public URLs. No pre-replacement history may be merged into the new public ancestry.

Publish only authorized reusable material. Personal accounts, private source quotations, health or psychological records, relationship narratives, accounts, private paths, conversation identifiers, and links exposing those materials stay with their actual private owner. Do not retrieve private personal materials merely to maintain this collection or create a public index that reconstructs a portrait.

Unpublished manuscripts, their reading editions, PDFs, figures, source files, and private source records are excluded from public packages. General ideas may be developed in the existing essays as standalone exposition with independently public references where relevant. Publication of any original or anonymous manuscript requires fresh explicit user authorization. Do not reintroduce excluded source through links, assets, history, or provider previews.

Review the whole public change, including assets, metadata, published Git history, and link destinations. Reusable packages must remain meaningful without private sources. Keep conceptual reading links local to their owning complete package; verify moved references, source locators, and asset paths. Preserve actual permissions, consent, and publication authority.

Do not maintain a download application, approval service, access-code system, publication-secret workflow, or separate package ZIP generator for this collection. Use GitHub's public archive and native collaboration functions. Website reading editions retain their own source and publication workflow.

Maintain each account at its existing owner rather than duplicating it in the collection root. Do not add interpretation registries, automatic personal-data feeds, or synchronization services for this collection.