majordomus mesh

majordomus / mesh

Usage

majordomus mesh <COMMAND>

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

Commands

• majordomus mesh status Whether the mesh runs in this checkout's server and why not when it does not, with every provider's state and the registry's tallies
• majordomus mesh nodes Every node the running server has observed, deduplicated by node identity, with trust, presence, endpoints and provenance
• majordomus mesh identity This machine's node identity, public half only; absent is an answer, not an error
• majordomus mesh doctor Prove the mesh prerequisites on this machine alone: declaration, identity, sockets, multicast, broadcast, the protocol end to end, and the host firewall
• majordomus mesh firewall What the host firewall must admit for the declared mesh and whether it does; `apply` admits it, as root
• majordomus mesh peers Every machine and runtime this checkout's server cooperates with, each link's state, and the active sessions; --full for every session and claim
• majordomus mesh peer One runtime: its machine, liveness, link, sessions and claims; exits 10 when it is not known here
• majordomus mesh state The state every linked runtime converges on, summarised with its digest; --full for every session, claim, handover and review
• majordomus mesh events The cooperation journal's events after a Lamport stamp, in Lamport order
• majordomus mesh verify Prove cooperation now: local health, a live round with every peer this server dials, and convergence; exits 10 when a check fails
• majordomus mesh claim Claim repository paths for a session; exits 10 naming the claims it meets when an exclusive claim on any linked runtime holds them
• majordomus mesh release Release a claim this server's current run holds
• majordomus mesh session Open, update or close a session on the mesh
• majordomus mesh handover Publish a handover of this checkout to the mesh, or consume one another runtime published
• majordomus mesh review Ask the mesh for a review, or answer a request

Arguments

Arguments: none.

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 mesh --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.