Absolute requirement, already designed in ARCHITECTURE.md 2.1/2.5 and now R39, but not built: every connector today is a subprocess inside the binary on the host Archie runs on, so a customer network that accepts no inbound connection cannot be reached, and target credentials sit in the binary rather than on the target's side.
Build the runner: registers once with a token and connects outbound only; long-polls for judged actions matching its labels (network, environment); runs them with the credentials held on the runner's side; refuses anything other than the judged action (R18); streams results and logs; can be ephemeral or long-lived. Extend it to sandboxed task runs.
Done when: a judged action executes on a host Archie does not run on, through a runner that opened the connection, and the same action is refused when the runner is given a different digest.
Absolute requirement, already designed in ARCHITECTURE.md 2.1/2.5 and now R39, but not built: every connector today is a subprocess inside the binary on the host Archie runs on, so a customer network that accepts no inbound connection cannot be reached, and target credentials sit in the binary rather than on the target's side.
Build the runner: registers once with a token and connects outbound only; long-polls for judged actions matching its labels (network, environment); runs them with the credentials held on the runner's side; refuses anything other than the judged action (R18); streams results and logs; can be ephemeral or long-lived. Extend it to sandboxed task runs.
Done when: a judged action executes on a host Archie does not run on, through a runner that opened the connection, and the same action is refused when the runner is given a different digest.
sam
added the featurehigh labels 2026-11-16 01:39:39 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Absolute requirement, already designed in ARCHITECTURE.md 2.1/2.5 and now R39, but not built: every connector today is a subprocess inside the binary on the host Archie runs on, so a customer network that accepts no inbound connection cannot be reached, and target credentials sit in the binary rather than on the target's side.
Build the runner: registers once with a token and connects outbound only; long-polls for judged actions matching its labels (network, environment); runs them with the credentials held on the runner's side; refuses anything other than the judged action (R18); streams results and logs; can be ephemeral or long-lived. Extend it to sandboxed task runs.
Done when: a judged action executes on a host Archie does not run on, through a runner that opened the connection, and the same action is refused when the runner is given a different digest.