Yinyang sources and private updates

This page explains the author's common-source and private-instance relationship. The public Skill is Empty. Its own package guide owns recipient installation and updates.

The established skills/yinyang/ path maintains essays, diagrams and shared formation methods. Actual entrypoints and personal accounts stay with their private owners. Readers can study the philosophy or form their own practice from Empty; the shared writing directory is not a Full Skill distribution.

Common and situated content

The six bilingual formation guides define the full questions and reading roles of orientation, person, counterpart, relationship, environment and revision. Each synthesis instruction draws on the six complete guides and relevant actual grounds. Formation and revision owns their distinct subjects, connected scope and whole-six coherence.

The practice overview explains edition and condensation choices; this page locates the private files and their updates:

Read all six complete actual accounts in ordinary collaboration. Persist intended private source in Git and a private GitHub repository through the actual account and publication owner, checking private visibility, committed content and reader retrieval. Original records retain their owners; secrets stay outside ordinary repository files. The shared writing source contains no actual private accounts.

The complex route projects checked bodies to the same six paths, or binds the six questions, native IDs, and complete bodies through private references/situated/index.md. See Hindsight configuration. Formation and revision owns their content and whole-account checking.

Philosophy retains its authored source. Personal remains human-readable topic articles in the existing four subject groups, with usable navigation and original source links. Direct source/article editing remains available. In the native route, substantive Knowledge Pages can maintain those articles and project Markdown into existing private reading paths, with Observations backstage. Migrate affected derived articles as revision needs, preserving readability and unique grounds. Corrected Personal understanding must inform later synthesis; all products can return to originals without requiring chained generated summaries. The Personal guide owns that reading arrangement.

Keep meaningful Personal material names in the person's native language; body language follows its consumer. Preserve instrument identifiers where useful. Both references/personal/ and references/situated/, including optional native bindings and private generated bodies, stay private. Common projection protects both trees; it does not change bank state, GitHub visibility or runtime consumers. Independently authored philosophy retains its own source.

Questionnaire and assessment material

When a situated version has questionnaire or assessment records, organize this distinct part of personal evidence under references/personal/questionnaires/. Use its README.md as a readable inventory linking dated records and their original sources. Connect it from personal/README.md and personal/sources.md. Group records by occasion or instrument according to what makes them easy to retrieve; repeated completions remain separate dated observations.

Keep each record's instrument name, language and version when known, completion date and context, result and score direction, and access to original answers or the report. Distinguish a questionnaire response, a performance test, a report's written conclusion, and a later interpretation. Preserve conflicting findings and missing information explicitly; a report without item answers must not be expanded into invented responses. Existing private measurement systems and medical-document collections can retain their originals, with useful results and working links maintained here instead of duplicate archives. Undated material remains undated until its source establishes a date.

This organization makes measurements available alongside narrative material without turning them into a complete personal account or automatically revising the working models. The Psychology guide owns selection, scoring and interpretation. The directory and all filled records remain private; the distributed package supplies this organizing method, not another person's records or placeholder results.

Project common resources into the author's private instance

scripts/sync-common.py compares the common writing source with an existing private Skill. With --apply, it copies common resources, preserving the private entrypoints, README editions, MODEL and AGENTS files, and both references/personal/ and references/situated/ trees.

python3 /path/to/shared/yinyang/scripts/sync-common.py \
  --source /path/to/shared/yinyang --target /path/to/private/yinyang

The source is identified by its formation method, the target by its actual SKILL.md. It does not inspect private trees, create a new person's accounts, or publish runtime. Unmatched common files and common-path symlinks require ownership inspection. Existing host and private cloud owners deliver the checked private source and read back the consumers.

Empty recipients update from Empty's own package contract. Independently authored philosophy and methods stay with their own source rather than being overwritten by this author's common-resource projection.

Personal and public boundaries

Personal accounts remain private even when formalized or written for models. Private quotations, biography, psychological and health records, relationship narratives, account information, private paths and conversation identifiers, and unpublished manuscripts stay with their actual owners. General abstraction does not authorize public links that reconstruct private sources.

Return only authorized reusable insights to the collection. Yinyang original material uses Yinyang Personal and Internal Use License 1.0; other independent members retain their own MIT licenses. Follow the collection guide and the actual publication owner for permissions, attribution, and source review. A private adaptation need not be published.