> For the complete documentation index, see [llms.txt](https://omekapo.gitbook.io/jan-culture/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omekapo.gitbook.io/jan-culture/traditions/phrases.md). # phrases ## greetings > jan people say "kama pona" in informal settings when they're greeting a person. in some other contexts, this may be different. when a person just woke up, they might say "lon pona", when they're meeting at a restaurant, they might say "moku pona", and so on\ > \&#xNAN;*- jan Melako* > after a while, 'seme li lon' starts being so common that no one expects an answer from it, much like 'what's up' of english. perhaps it starts being shortened to 'semilon' or something like that (we know how much toki pona likes to abbreviate stuff! (see kuntu and omekapo)), and at that point, semilon just starts being another kind of hello (but, y'know, probably cooler than toki)\ > \&#xNAN;*- kala pona Tonyu* ## farewells > "The jan culture has some fixed formulae for farewells, but a common practice is just providing a heartfelt, small advice. It doesn't need to be specifically related to the person or the situation at had. Each jan builds a library of personal farewells that use with different people and in different circumstances, and it is generally considered kind and nice to provide this kind of advice. Some examples are:\ > \- o moku e kala pona!\ > \- o lon poka seli! (in the cold season)\ > \- o noka ala e pipi!\ > \- o moku e telo!"\ > *- jan Tomen* > to say goodbye, they usually just say whatever the person is going to do before pona. "pali pona" if the person is going to work, "lape pona" if they're going to sleep, "musi pona" if they're going to do some entertaining thing. yes, this moku pona conflicts with the hi one, but :context: .\ > \&#xNAN;*- jan Melako* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://omekapo.gitbook.io/jan-culture/traditions/phrases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.