atlas
1efbb72fdd
an archetype carries its own notification-router flows for its agents
...
ArchetypeMeta gets flows, checked when the controller stores the record: every todo must go to the new members recipient, which the router expands to the agents of the archetype. The operator's flows document refuses members. The router reads the archetype records and each roster agent's archetype key, and its NATS grant gains read on both buckets.
2026-11-11 21:40:17 +01:00
..
agent_token.rs
swarm: drop the -agent client suffix refusal from authelia and the queue responder
2026-10-24 15:02:32 +02:00
introspect.rs
swarm-nats-auth: give issued user JWTs an exp
2026-10-17 16:29:55 +02:00
keystore.rs
swarm-nats-auth: read the callout issuer and user seeds from the store
2026-10-06 14:53:33 +02:00
main.rs
swarm: drop the -agent client suffix refusal from authelia and the queue responder
2026-10-24 15:02:32 +02:00
nkey.rs
swarm-nats-auth: read the callout issuer and user seeds from the store
2026-10-06 14:53:33 +02:00
oidc_secret.rs
name the mint, not the publisher, as the writer of the client secrets
2026-10-30 16:57:58 +01:00
policy.rs
an archetype carries its own notification-router flows for its agents
2026-11-11 21:40:17 +01:00
request.rs
swarm-nats-auth: answer callout requests concurrently, skip expired ones
2026-10-17 23:36:01 +02:00
respond.rs
swarm-nats-auth: give issued user JWTs an exp
2026-10-17 16:29:55 +02:00
xkey.rs
swarm-nats-auth: answer callout requests concurrently, skip expired ones
2026-10-17 23:36:01 +02:00