kapi status

$ kapi status

Show how far the project's content has progressed and whether it clears the project's gates: a derived dashboard, like git status. The standing is recomputed from the working tree on every run; nothing is tracked as state.

A project with target languages also gets per-language coverage: for each target locale, how much of the content is translated and whether it clears its ship gate. A locale that is behind is reported as pending rather than as an error, because target-language drift is normal, expected work.

This is the informational counterpart to 'kapi check --ship' (the quality gate), and it never fails.

Commandstatus

Groupwork

Try it

Runs in your browser against a small sample file. Edit the command before running, or press Run to execute it as shown.

$ kapi status

Flags

Flag	Type	Default	Description
--emit	string		with --ship, write the manifest to this path (e.g. ship.json) instead of stdout
--json	bool	false	output the structured result as JSON
--lang	stringSlice		with --review, list only these languages (repeatable, or comma-separated); the source language is one of them
--locale	string		limit to a single target locale
--project, -p	string		path to a kapi.yaml project recipe or its directory (auto-discovered from cwd if omitted)
--review	bool	false	list the blocks awaiting review in every language, the source language among them, instead of the coverage grid; approve one with a decide operation sent to `kapi apply`
--ship	bool	false	emit the minimal ship.json picker manifest (locale → {shippable, state, not_governed}) instead of the coverage grid; state is established (approved by a person), translated, withheld or not_gated, and a language picker offers only shippable locales and badges the ones not approved as AI-translated
--source-lang	string		source language (overrides the project's source_language)

← Back to the Command Reference