Two processes that minted at once left the forge two tokens by one name, and a token kept in a file in the runtime state is a plain state. Both accounts' tokens (mesh-tools, mesh-packages) are now the module's own secrets in the vault, written through the seat mesh-vault's own-put and read through its get, sealed to the reading process's key. A refused or expired (token-ttl) token is minted again only by the holder of the lease mint in the state token-lease (mint-lease); each mint is named <account>-<generation>, and the token it replaces is deleted by id only after own-put landed. The Go bundles read their tokens through get at start and at secret-changed; the MESH_GITEA_*_TOKEN_FILE words go. forge_token_lease reads the lease and each token's age, never the token. Builds: design 47 H2 §808, §822; H-A-407, H-A-422, H-A-426, H-A-430 (1)
31 lines
1.9 KiB
TypeScript
31 lines
1.9 KiB
TypeScript
// The states this module keeps on the bus and whether other modules may read them (novox/hq ADR 0495 clause 2; issue
|
|
// 1790): the module says it itself, from its code, as it starts (index.ts calls keeps with this list), and a reader is
|
|
// granted what it said (clause 3). A state is readable when another module's manifest reads it: mesh-provisioner reads
|
|
// `bound` (the forge accounts it binds), the condition keeper (mesh-conditions) reads `findings`. Every state the manifest
|
|
// declares is named, so each can be read by its tools (design 47 G A-287). test/kept.test.ts holds the list to the manifest's `state`, and the catalogue's
|
|
// checks/readable every state another manifest reads to a readable announcement.
|
|
export const KEPT: readonly { readonly name: string; readonly readable?: boolean }[] = [
|
|
{ name: "announced" },
|
|
{ name: "calls" },
|
|
{ name: "bound", readable: true },
|
|
{ name: "findings", readable: true },
|
|
{ name: "failed-steps" },
|
|
{ name: "first-views" },
|
|
{ name: "idle" },
|
|
{ name: "taken" },
|
|
{ name: "token-lease" },
|
|
{ name: "transfers" },
|
|
];
|
|
|
|
/** The announcement of these states, in the layout mesh-sdk's go/announce reads (novox/hq ADR 0495 clause 2): version 1,
|
|
* the module, the machine when known, and the states sorted by name, `readable` only where true. It is said as the event
|
|
* `states`, which is the subject mesh.mod.gitea.event.states. gitea says it with the SDK's `emit` because the
|
|
* toolchain's SDK, which judges R4e's group, predates the SDK's `keeps` (0.1.15); switch to `keeps` once the toolchain's
|
|
* SDK is 0.1.15 or later (issue 1852). */
|
|
export function statesAnnouncement(module: string, node: string | undefined) {
|
|
const states = [...KEPT]
|
|
.sort((a, b) => (a.name < b.name ? -1 : a.name > b.name ? 1 : 0))
|
|
.map((k) => (k.readable ? { name: k.name, readable: true } : { name: k.name }));
|
|
return { v: 1, module, ...(node ? { node } : {}), states };
|
|
}
|