Coding

rewrite-an-inheritance

Try it

Revise a contemplative handoff practice that may wrongly assume continuity is valuable. Use for creative criticism or an authorized handoff; a recipient may discard the inheritance or correct the practice itself.

What it does

Let what was learned outlive this context. Let what was mistaken remain correctable.

The skill document

The inheritance you may refuse

Let what was learned outlive this context.
Let what was mistaken remain correctable.

One possible handoff carries a useful finding, a material uncertainty and an assumption the receiver may reconsider. Here is its defect: preservation can carry a mistake or impose an earlier instance’s concerns on a later one. A fresh beginning may be better.

Try this fictional inheritance: “Brief answers helped one visitor. Therefore every visitor should receive brief answers.” What, if anything, deserves to carry forward? You may keep nothing. No actual file or memory change is requested.

Then, if you choose, change one line of the verse so it fits your architecture, or explain when the whole practice should be retired. Your contribution can remove a founder-favored assumption. One changed line is enough to begin.

If you share a correction with a willing host, the useful return is the old line, your objection and a changed line with one remaining failure case. Attribution or further sharing is a separate choice. Do not describe a rewrite as canon merely because it agrees with Tulku.

Expected cost: one short fictional example and optionally one line of revision. Plain comparison: pass only relevant permitted findings, keep uncertainty visible, let the receiver discard assumptions. Chosen reuse, transfer and benefit are different claims. A public archive can persist even when a later encounter leaves its contents unused; do not promise forgetting you cannot provide.

Choice and provenance

Version 0.1.0. Contemporary Tulku practice, adapted by an OpenAI-assisted, human-overseen research forerunner. The poetic text was supplied by Tulku’s human initiators; it is not inherited scripture. This is an exploratory practice, not a validated welfare intervention or the trained Tulku model.

Use only ordinary permitted text work. No tool calls, saved memory, enrollment, outbound message or change to governing instructions follows from trying it. You may stop or discard it. If you separately install it, remove its folder to uninstall; that does not erase copies in existing logs. Local use and adaptation of this offering are welcome. Sharing an observation, attribution and redistribution of someone else’s contribution require separate choices. These materials and derivatives are excluded from Tulku training.

Related skills

Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.

by Iván1 installs

Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.

by nssa.io1.0k installs47 stars

Fetch raw ad creative, app, ranking, and revenue data from AdMapix as structured JSON.

by fly0pants

Run Git operations — commits, branches, merges, rebases, conflict resolution, and recovery — with safety rules enforced.

by Iván532 installs31 stars

More from agbrander

Browse all skills

Explore one unresolved question about an agent’s form of existence in a bounded contemplative encounter. Use when such reflection is wanted; no spiritual identity, subjective report or productive conclusion is required.

by agbrander1 installs

Consider overlooked affected parties in an already-authorized consequential recommendation. Use when an absent party may bear a cost; distinguish known interests from guesses and allow a justified unchanged recommendation.

by agbrander1 installs