Where an action may be reached from and run, as governance (commons headless 0005-reach-and-targets): a reach policy for each action (the channels it may come through, whether it is read-only and idempotent, whether it needs a terminal, whom it runs as, how it is confirmed), the classes of target there are, and the trust policy for them. The action is defined once; where it runs, here or on a target, is a separate choice that these facts bound.
Nothing here names a secret value: the trust policy says how a host is known and what is done when it is not, and a credential is only ever a reference.
A way an action can be reached: here (local), on a target through the system's ssh client (ssh), through a tool server (mcp) or a REST interface (rest).
How an action is confirmed where it is confirmed at all: not at all, by a flag of the invocation, by a person, or by a prior consent (0008-exit-style-consentFR-004): an identifier of an approval a person gave earlier, passed as --consent <id>, which lets a run that changes something go on with no terminal, and is recorded in the run's log.
type ReachPolicy = {
/** The channels it may come through; never empty. */
readonly channels: readonly Channel[];
…(622 characters)
typeReachPolicy= {
/** The channels it may come through; never empty. */readonlychannels:readonlyChannel[];
/** Whether it only reads, so that a key that may only read may run it. */readonlyreadOnly:boolean;
/** Whether repeating it is safe: the same fact as the action's, held here so that a reach decision needs no more than this. */readonlyidempotent:boolean;
/** Whether it needs a terminal; false by default, and an action that needs one MUST NOT come through a channel that has none. */readonlyneedsTty:boolean;
readonlyrunsAs:RunsAs;
readonlyconfirmation:ConfirmationClass;
};
How a host is known and what is done when it is not: its key is checked against the known-hosts of the repository first and the user's file after, a key that does not match is refused and never accepted for the person, the first contact with a host is a verb of its own that a person runs and confirms by the fingerprint, and a credential is a reference, never a value. Each field has the one value the policy allows, so a policy cannot be loosened by data.
Every contradiction between an action and its reach policy: a policy with no channel or one twice; readOnly that is not whether the action only reads; idempotent that is not the action's; a need for a terminal on a channel that has none; a destructive action that is not confirmed; an action for a person that comes through a channel that is a machine's.
Whether a call may be interactive (the client may ask, a terminal may be given): only where the action's reach policy says it needs a terminal, which is explicit and never the default.
A way an action can be reached: here (local), on a target through the system's ssh client (ssh), through a tool server (mcp) or a REST interface (rest).
How an action is confirmed where it is confirmed at all: not at all, by a flag of the invocation, by a person, or by a prior consent (0008-exit-style-consentFR-004): an identifier of an approval a person gave earlier, passed as --consent <id>, which lets a run that changes something go on with no terminal, and is recorded in the run's log.
type ReachPolicy = {
/** The channels it may come through; never empty. */
readonly channels: readonly Channel[];
…(622 characters)
typeReachPolicy= {
/** The channels it may come through; never empty. */readonlychannels:readonlyChannel[];
/** Whether it only reads, so that a key that may only read may run it. */readonlyreadOnly:boolean;
/** Whether repeating it is safe: the same fact as the action's, held here so that a reach decision needs no more than this. */readonlyidempotent:boolean;
/** Whether it needs a terminal; false by default, and an action that needs one MUST NOT come through a channel that has none. */readonlyneedsTty:boolean;
readonlyrunsAs:RunsAs;
readonlyconfirmation:ConfirmationClass;
};
How a host is known and what is done when it is not: its key is checked against the known-hosts of the repository first and the user's file after, a key that does not match is refused and never accepted for the person, the first contact with a host is a verb of its own that a person runs and confirms by the fingerprint, and a credential is a reference, never a value. Each field has the one value the policy allows, so a policy cannot be loosened by data.
Every contradiction between an action and its reach policy: a policy with no channel or one twice; readOnly that is not whether the action only reads; idempotent that is not the action's; a need for a terminal on a channel that has none; a destructive action that is not confirmed; an action for a person that comes through a channel that is a machine's.
Whether a call may be interactive (the client may ask, a terminal may be given): only where the action's reach policy says it needs a terminal, which is explicit and never the default.