majordomus continuity

Continue work on another machine: publish this checkout's newest handover as a signed record in refs/majordomus/continuity, exchange records with a git remote, and plan and resume a handover another device published — with its source compatibility, lineage and trust decided before anything is written

Usage

majordomus continuity [OPTIONS] <COMMAND>

This command groups the commands below and is not run on its own, so it carries no example.

Commands

majordomus continuity status This device, the record this checkout continues, the store against its remote (no network), every line of work, and what other devices published that could be resumed here
majordomus continuity records Every published handover the local store admits, by line, and every file it refused
majordomus continuity device This device's identity — the mesh node key, created when absent — and its label; with --label, rename it
majordomus continuity plan Decide, writing nothing, whether and how a published handover can be resumed here: trust, lineage, source compatibility, uncommitted work at the origin
majordomus continuity publish Publish this checkout's newest handover as a signed record for another machine; refused when it carries a secret or a machine path
majordomus continuity sync Exchange published handovers with a git remote: fetch, merge as a union, push; an unreachable remote leaves what is pending pending
majordomus continuity resume Resume a published handover when its plan is ready: write it into this checkout's handovers, carry its decisions, and continue its line

Arguments

argument	value	default	description
--repo	<PATH>	—	Start the search for the repository root here (default: the current directory) (accepted by every subcommand)
--discovery	vcs \| filesystem	vcs	How declarative files are enumerated (accepted by every subcommand) `vcs` — Tracked files, through the version-control index (the layer's contract); a layer none of which is tracked is read from the work tree `filesystem` — A walk of the work tree with the same glob semantics; untracked files included
--strict	flag	—	Refuse to proceed when any file of the layer carries an error diagnostic (accepted by every subcommand)
--share	<DIR>	—	The tool distribution's share directory (kinds.yaml, schemas/); default: $MAJORDOMUS_SHARE, then the repository's own share/, then the one beside the executable (accepted by every subcommand)
--format	text \| json	text	Output shape (accepted by every subcommand) `text` — Lines for a person `json` — One JSON document, deterministic

Where this comes from

Declared once in apps/majordomus-cli/src/cli.rs: clap for the structure, typed Rust metadata beside it for the examples. This page, majordomus continuity --help, docs/generated/cli.md and docs/generated/cli.json are projections of that one declaration.

The whole command line on one page: the registry's command-line page. The task lifecycle (init, start, finish, doctor, ...) belongs to the shell tool, a different program: Commands and its specification.