Learning labs
Learn kapi by running it
Every lab is a short session in a sample company's repository, run by the real kapi engine in your browser. Press play and the first chapter runs; each Next runs the following one, with a line on what it shows. Type your own commands at any point, and share a link to the chapter you are on.
- Nothing to install and nothing leaves your machine: the engine downloads once, about 20 MB, when you press play.
- Read the series in order. Each lab is a few minutes; all of them together are about an hour. (115 min)
- The projects are the samples the documentation and the recordings use, so what you see here is what you get on your own machine.
Start here: your writing
A company repository in one language: operator documentation, interface strings and a marketing page. Read the project's context in, ask what applies to a file, run the checks like tests, record a decision, and edit a block through the engine. No second language, no server, no credential. Northsea: Northsea Maritime Systems sells software to port and fleet operators: Compass, the berth plan, and Tidewatch, the alerting service. One repository, one language, three surfaces.
A project and its files
What kapi reads, and how it addresses every piece of content.
- project
- recipe
- collection
- point
Context: what applies here
Two questions a writer or an agent asks before touching a file.
- context
- voice profile
- terms
- point
Check content like tests
A gate that runs offline, and a decision that changes what it finds.
- check
- finding
- fails and reports
- exit codes
Edit through the engine
Read a revision, change one block, and keep every other byte.
- change contract
- revision
- if_match
- write-back fidelity
Add languages
The same content with three languages added. Watch kapi up recycle what the project established and draft the rest, read where every language stands, approve a batch of translations as a change set, and see the manifest a deployed page's language picker follows. Compass: The Compass interface, shipped in English at four North Sea terminals, with operators who read Norwegian, German and Dutch, and a page whose language picker reads what the loop ships.
One more axis
The same content, the same point, and three languages added.
- target languages
- lifecycle ladder
- ship gate
- ship states
Recycle first, draft the rest
One verb catches every language up, and asks a provider only for what is left.
- kapi up
- content memory
- recycle
- demo provider
Review moves the edge
A review in the morning is why a language is offered in the afternoon.
- review queue
- decide
- established
- established gate
Hand off, and carry work in one file
A bilingual file for a translator, and a parcel for another machine.
- extract
- bilingual exchange file
- merge
- .kpz parcel
The context engine
One lab that draws the context graph above the terminal: the content and the point it sits at, the voice and terms in force there, the content memory and the record of decisions. Read the context in, converge, review, and watch what each command adds. Compass: The Compass interface, shipped in English at four North Sea terminals, with operators who read Norwegian, German and Dutch, and a page whose language picker reads what the loop ships.
The content engine
A storefront's catalog and prose, through the engine's own verbs: inspect the model behind any format, run tools and flows with every prompt in the open, then set up a project that remembers its memory and terms and holds a draft to them. KapiMart: A storefront and order platform for small retailers: an interface catalog, an About page, three locales at different stages, its terms and a content memory.
Any format, one model
A JSON catalog and a Markdown page, read into the same blocks.
- content model
- block
- run
- inline code
Tools, flows and the demo provider
One tool at a time, then a flow, with every prompt in the open.
- tool
- flow
- source → flow → sink
- provider
A project remembers
Set up a project, give it memory and terms, and hold a draft to them.
- kapi init
- kapi add
- store import
- content memory
Explore the engine
The engine explorers, played as labs or opened as playgrounds: the flow workspace, the segmentation comparison, format conversion, document structure from a PDF, vision, audio and video, the bundle format, and a free terminal. A chapter sets what the explorer shows and says what to look at; a playground opens the explorer and leaves it to you. Every explorer takes your own files too. Engine explorers: The engine's own fixtures: a few documents in several formats, three PDFs, images with printed and handwritten text, a short clip, and a content bundle. Every explorer takes a file you bring as well.
Flow workspace
Build a flow on the canvas, run it, and open what each step attached.
- flow
- tool
- pipeline
- trace
Segmentation
Compare the sentence splitters on the cases that trip them up.
- segmentation
- SRX
- UAX-29
- overlay
File conversion
A Word handbook, an Excel workbook and a slide deck, rewritten as the document formats the engine generates.
- reader and writer
- generative format
- document family
- structure
Structure and layout
Reading order, outline and geometry, recovered from a PDF.
- geometry
- reading order
- structure tier
- PDFium bridge
Vision
Text and layout recognised in an image, on your device.
- OCR
- layout regions
- geometry
- handwriting fallback
Audio and video
Speech and on-screen text as timed content.
- timed blocks
- subtitle cues
- frame OCR
- speech recognition
Bundle anatomy
One content bundle, read part by part, then round-tripped through the engine.
- content bundle
- envelope
- block
- run
Free terminal
A terminal of your own, with sample files to start from.
- ad-hoc commands
- formats
- the browser engine