cmd/

Command acceptance exercises access-issuer against a real Kubernetes API server.

Command docsgen rewrites the generated regions of the documentation: the text between `<!-- generated: name -->` and `<!-- /generated -->`.

Command resource-proxy fronts a service that knows nothing about sluis with a sluis resource server's front door: it verifies the caller's token, serves the RFC 9728 metadata, writes an audit line per request, and proxies to the service -- and, optionally, gives the service an identity of its own for what it calls in turn.

Command sluis is the whole product in one binary, one image and one chart (docs/decisions/0032), and one process: `sluis serve` is the issuer, the hub, the console and, beside them, the controllers its document names.

Command sluis-backup is the backup module as an AWS Lambda function.

Command sluis-cloudflare is the Cloudflare module as an AWS Lambda function: the STS minter and the credential rotation, answering other modules' calls.

Command sluis-github is the GitHub module's controller as an AWS Lambda function: the organisations' team passes and the links pass, on a schedule or when the console asks.

Command sluis-google is the Google module as an AWS Lambda function: the directory refresh of the connected workspaces, on a schedule or for one workspace.

Command sluis-issuer is the issuer module as an AWS Lambda function: the issuer, the signer and the console in one process, in one arm64 `bootstrap` binary (docs/decisions/0072).

Command sluis-slack is the Slack module's controller as an AWS Lambda function: the workspaces' user-group passes, on a schedule or when the console asks.

Command sluisctl is what a person on a laptop runs.