Jinkō Context

Use this skill to explain Jinkō's shared mental model and vocabulary. Keep answers practical: the goal is to help a user or agent navigate Jinkō artifacts without confusing project organization, scientific content, and immutable versions.

Navigation and Version Management

Jinkō project navigation behaves much like working in a Git repository, but for scientific modeling artifacts instead of source-code files.

• A Project is like the repository: it is the boundary for a concrete scientific modeling effort, including sources, data, models, protocols, trials, reports, and collaboration history.
• Folders are like repository directories: they organize related project items by workflow, experiment, disease area, evidence package, or analysis thread. Folders help humans and agents find context, but they are not themselves the scientific artifact.
• Project Items are like tracked files or domain objects in the repository: each item has an identity and represents a Jinkō artifact such as a model, protocol, trial, data table, source, output set, report, or folder-like organizational item.
• Snapshots are like immutable commits for a specific project item: each snapshot captures the content of that item at a point in time. The latest snapshot is the head, while older snapshots remain available for traceability and comparison.

This Git-like structure makes Jinkō easier for agents to navigate because agents can separate three questions:

• Where is the work organized? Look at the project and folders.
• Which artifact is being discussed? Identify the project item.
• Which exact state of the artifact matters? Use the snapshot, or use head when the user wants the latest state.