REFERENCE / FAQ
These answers describe the public system as it exists now: who maintains it, what it publishes, how it should run and where participation begins.
GripSky was founded and is maintained by Lin Guan as a public expression of his personal system. It shares an evolving worldview, a skill catalog, research questions and release history. Reusable skills and self-hosting are still being developed; each entry states its current scope.
Lin Guan (临观) founded and maintains GripSky. GripSky carries the public project; his ORCID record and personal work history identify him separately as its maintainer.
It explores how people understand, change and extend themselves, and how judgment can become reusable skills connected to information systems and AI—without giving up control as machines, vendors or operators change.
A personal system should remain inspectable, portable and open to correction. Public definitions and history support self-hosting, independent verification and shared improvement.
It is for people building long-lived personal systems, contributors studying human–AI collaboration, and clients who need a skill system or external information body designed and maintained around real work.
Worldview supplies revisable judgments. Skills organize knowledge and practice into callable abilities. The external body gives them memory, interfaces, computation and a place to act. Feedback can revise all three; this is not a one-way deduction or a finished organ architecture.
No. Some entries have public source documents, some describe internally used methods, and others are still exploratory. A public concept is not necessarily a runnable package. Consult each entry’s practice, openness and self-hosting status before using it.
A privacy-reviewed version of the worldview is public. Reusable skill definitions and implementations are intended for open release where privacy and security allow. Private runtime state, credentials and personal records do not travel with a public release.
Keep public definitions readable, host sensitive state under the owner’s control, document dependencies and preserve export, upgrade and removal paths. Managed operation should use the same portable form, not a version tied to one provider.
Subscribe by email for selected topics, follow the RSS release feed, or watch the relevant GitHub repositories. Worldview, skills, compatibility and research can move at different speeds.
Public corrections, evidence and implementations belong on GitHub. Deployment, managed operation, custom skills and continuing stewardship begin through the service contact channel with scope and privacy boundaries stated explicitly.