# art

## poetry

> instead of using phonemic strings as modifiers for proper names, we instead contextualize phonemic strings by modifying them *jan Po li alasa e ijo = Po jan li alasa e ijo*\
> why, you ask? idk. maybe poetry? could be an alternate naming convention for those in jan culture who have been shunned out of their community - their jan-ness isn't prioritized. could also maybe be a taboo thing where if you don't want to invoke the person directly, you could say it like this instead.\
> \&#xNAN;*- jan Lakuse*

### leko nimi

> a while ago i had the idea of toki pona poetry which uses 4 lines of 4 words each and when you put them into sitelen pona they make leko nimis\
> \&#xNAN;*- kule epiku Atawan*

> When making the nimi leko, not only does it have to make sense when reading it from left to right, top to bottom, but it also needs to make sense when reading from top to bottom, left to right (or right to left idk)\
> \&#xNAN;*- jan Asen*

leko nimi is a form of toki pona poetry. there are 16 words organised into 4 lines of sitelen pona characters in a square. leko nimi can be read both vertically or horizontally.

!['tomo moku' - jan Likipi](/files/-MTOl3XARTF_yXCxer_M)

![- kule epiku Atawan](/files/-MTTJSLXpZFH0tm_veuF)


---

# Agent Instructions: 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:

```
GET https://omekapo.gitbook.io/jan-culture/lifestyle/art.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.