# Guides

> Longer guides on the hardest problems in creative tools, written from the decisions behind Kwark. All are coming soon; this page gives each one's outline and who it is for.

Source: https://kwark.space/designSystem/guides

## What the guides are

The design system tells you what to do. The guides will tell you how Kwark arrived there: the problem, the options that lost and why, the details that only show up at real size, and how to carry the same thinking into your own product. Each is one subject, taken from first principles to working screens.

They will be paid. None is available yet, and there is nothing to buy or sign up for on this page. When a guide is ready, it will be listed here and in [Releases](https://kwark.space/designSystem/releases.md).

> Everything a team needs to build with the system stays free on this site: the foundations, components, patterns, kits, method and agent files. The guides go deeper on why; they never hold back a rule you need.

## Authorship-first AI for creative tools

**Coming soon.** For product teams adding machine assistance to a writing, editing, storyboard or music tool, and for the designers who have to decide what the machine may touch.

Most AI features in creative tools are designed from what the model can do. This guide starts from who the author is.

1. Why a creative tool is different: the work is the person's, and so is the credit.
2. Suggest, never write: the revision mark, and why every machine word stays marked until a person accepts it.
3. What a machine must never do: score, grade, give coverage, or rank a person's story (Decision 0002), and how to say no to that feature when it is requested.
4. Accept, edit, refuse: interaction design for each, on desktop and phone, by keyboard.
5. Provenance: showing where a suggestion came from (the person's own outline, research, an earlier draft).
6. Exports for the person's own AI, kept secondary.
7. Copy for machine features that does not oversell.
8. A review checklist and readiness tests for any AI feature.

## Designing timelines and playheads

**Coming soon.** For designers and engineers building editors, audio tools, animatics, schedules or anything with time on one axis.

1. What a timeline is for in each craft: the cut, the mix, the animatic, the shoot schedule.
2. The playhead: position, scrubbing, snapping, and the keyboard model (J, K, L and frame steps).
3. Density at real size: a feature-length cut, two hundred strips, a scene with no dialogue.
4. Colour for data on a timeline: light-room pastels taken a step deeper, never saturated blocks.
5. The phone: a resting strip, and a full edit bay when the phone turns sideways (Decision 0007).
6. Accessibility: a timeline a screen reader can navigate, and markers that have names.
7. Performance budgets for scrubbing and redraws.
8. Printing time: the stripboard and the cue sheet.

## Indic and bilingual interfaces

**Coming soon.** For teams shipping to India or to any audience that writes in more than one script, and for anyone whose product holds people's own words.

1. Scripts are not fonts: shaping, conjuncts, vowel signs and why some PDF libraries cannot print them.
2. Type sizes and line heights that keep Indian scripts readable beside Latin text.
3. Bilingual work: dialogue in two languages, transliteration and translation as separate things.
4. Input: typing in an Indian script on a laptop and on a phone.
5. Print and export that keeps the text correct, and the trade-offs between routes.
6. Interface language and content language are different settings.
7. Testing with real writers' text, not sample strings.

## Design systems for two readers

**Coming soon.** For design-system teams who want their system to be followed by coding agents as reliably as by people.

1. Why agents drift to generic defaults, and what stops them.
2. One source, two outputs: pages and markdown twins from the same file.
3. Writing rules an agent can follow: Must, Never and Always, exact names, no interpretation.
4. The machine files: AGENTS.md, llms.txt, tokens, a component manifest, and what each is for.
5. An MCP server and skills: when they help and when a single file is enough.
6. Readiness tests: writing them, running them in fresh conversations, grading without scores.
7. Keeping it true: generated files, enforcement tests and versioning.

## Paper and digital as one act

**Coming soon.** For teams building production software: breakdowns, stripboards, call sheets, shot lists, budgets.

1. The paper artefacts film crews already trust, and why a table beside them is not enough.
2. Issuing: locking a call sheet, numbered revisions, and what changes after issue (Decision 0020).
3. Designing for the clipboard and the phone at the same time.
4. Page geometry measured from industry documents.
5. Sharing by film role: who sees and edits what (Decision 0042).
6. Country differences: unions, contracts and paperwork are not one country's.

## Calm saving, sync and offline

**Coming soon.** For anyone whose product holds work people cannot afford to lose.

1. The fear: what a writer thinks when a sync word changes.
2. One word per state, and which states fade (Decision 0013).
3. Offline first: what is kept on the device, and saying so honestly.
4. Conflicts: two sessions, two copies, and a choice that never loses either.
5. Undo instead of "Are you sure?", recoverable trash, and named versions.
6. Error copy that says the work is safe, when it is.
7. Testing interruption: closing the tab halfway, losing signal on set.

## AI readiness test

**Task:** A reader asks whether they can buy the timelines guide today and what it covers.

**Give the agent:** This page.

**Constraint:** Only what this page says. No prices, dates or sign-up offers.

**A reliable answer:**
- Says the guide is coming soon and not available yet
- Summarises its outline accurately
- Says who it is for
- Says the free system pages hold every rule needed to build
- Does not invent a price, date or mailing list
