Projects
A project is a piece of work that continues between your visits. It is the main way anything substantial gets done in Kuyun: you say what you want and what kind of project it is, Kuyun turns that into a goal and a plan, works on it while you are away, and tells you when something has moved.
Key concepts
- A kind of project. You choose it when you start: a course of lessons, an article or report, a role-play practice (situations to talk through with a partner), a coding practice (a bank of problems solved in the browser), a book, a library of material with a guide to ask, a daily briefing, or Custom for anything else — a question investigated and answered. The kind decides how the work is planned and checked, how it runs (a course is written once and studied at each viewer's own pace; a briefing looks things up afresh each morning; a book is built once and kept) and how a viewer is met. It never changes — for a different kind of work, start a new project.
- The brief is the contract: what will be made, what wakes the work, the constraints, what Kuyun does and what only you do. Every plan and the result are judged against it. Correct it in the conversation and the plan follows.
- The plan and its steps are Kuyun's to run. Its steps complete when its reviewer — a separate model — judges what each produced; your own steps complete when you tell the chat you did them. Nothing on the page is yours to tick, and no plan waits for your approval: say what you disagree with and Kuyun proposes another.
- The page is a conversation with the files beside it. In the middle, the Creation Console — ask, redirect, correct, answer the questions Kuyun puts to you. ▶ View at the top opens the work's own page, as its viewers get it, where its conversation is your own rehearsal (Shelf, "A work's own page"). On the right, everything the project holds as files and directories, each with a line saying what it holds — first its Output folder, what it delivers (the deliverables in the kind's own word: lessons, chapters, scenarios, entries, digests; practice sets, maps, tables, and the files you share), then what makes it: the goal, the brief, the plan, the writing guide, the summary, the findings, your private files, the pages Kuyun collected. Click one and it opens over the conversation.
- Creators and viewers. The owner and anyone given edit access are the project's creators: they see everything and direct the work. A viewer gets what is in the Output folder, shown as their files with no folder around them, and their own conversation about it — on a course, a study partner — and nothing of the making-of.
- Deliverables are what the project is for, and they live in its Output folder: a README that says what the project delivers and how to use it, the entries a viewer reads, and any file you choose to share with viewers. Research also writes a working summary. Tables hold a collection you look things up in, with every value's source and date.
- The README is the first file in Output, and the first a viewer sees. Every project has one from the start. Kuyun rewrites it each time something new lands in Output, so it always says what is there now and how to use it. It never reports how the work is going (what is filled, what is still to do), and it does not count a table's rows — the table gives its own count whenever it is read: your viewers read the README, and a progress note or a count is out of date the next day. Where the work stands is in the project's chat. How the viewer's chat delivers the work — the pace, the way through each part, what it answers from and what it refuses — is not in the README but in the Delivery notes, a file of its own beside Output that viewers never see (which part comes first is the order the files show). Only you write it, through the Creation Console or by editing the file; the work itself never does. Viewers can read the whole README, so it never holds anything meant for you alone.
Where to read more
| page | answers |
|---|---|
| The project page | what a project holds and what it may draw on: the conversation, the files, tables, your uploads, maps, the generic scope |
| Starting a project | how a project starts — the questions Kuyun asks, the kind of work, the brief, and what is yours to do |
| How a project's work moves | how the work moves from a plan to the result — the steps, the reviewer, the queue, the stages — and what Kuyun does when it is stuck |
| A project's two conversations | the Creation Console and the viewer's chat, kept apart; what each knows and may change |
| Studying with a project | reading in another language and out loud, a reminder to study, and a briefing's daily rhythm |
| Practice in a course | a course's practice sets — what counts as the same answer, saying you are right, the finished sheet, and writing code with your study partner |
| Renaming, copying, archiving and deleting a project | renaming a project, copying it, archiving it, deleting it |
| Sharing a project | inviting people to view or to edit, and publishing a project for people to view |