01Worldview02Skills03External body04Research05Updates06ServicesSubscribe to updates

REFERENCE / FAQ

What GripSky is, in plain terms.

These answers describe the public system as it exists now: who maintains it, what it publishes, how it should run and where participation begins.

01

What is GripSky?

GripSky is the public body of a personal system maintained by Lin Guan. It publishes an evolving worldview, the skills derived from it, research questions, release history and self-hosting paths.

02

Who maintains GripSky?

Lin Guan (临观) founded and maintains GripSky. The organization carries the public project; the maintainer remains a separate person with an ORCID record and personal work history.

03

What problem does it address?

It explores how one person can turn judgment into reusable skills, connect those skills to information systems and AI, and keep control when machines, vendors or operators change.

04

Why is it maintained in public?

A powerful personal system should remain inspectable, portable and open to correction. Public definitions and history make self-hosting, independent verification and shared improvement possible.

05

Who is it for?

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.

06

How do worldview, skills and the external body relate?

Worldview supplies revisable judgments. Skills turn those judgments and repeated practice into callable abilities. The external body gives those abilities memory, interfaces, computation and a place to operate in the world.

07

Is GripSky open source?

The desensitized worldview is public, and reusable skill definitions and implementations are intended to be released openly where privacy and security allow. Private runtime state, credentials and personal records do not travel with a public release.

08

What is the ideal way to run it?

Keep public definitions readable, host sensitive state under the owner’s control, document dependencies and preserve export, upgrade and removal paths. Managed service should operate the same portable form, not create a lock-in-only edition.

09

How can I follow changes?

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.

010

How can I contribute or commission work?

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.