Skip to content

Potbot 0.5.0.dev11: native Syn Cog admission and heartbeats

Pre-release
Pre-release

Choose a tag to compare

View all tags
@kieransimkin kieransimkin released this 02 Nov 21:31
v0.5.0.dev11
8df3e9a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Potbot 0.5.0.dev11 adds the SYN-R05 native identity and Cog admission integration.

  • Sandboxed Cog dispatch requires a genuine released Syn node and a short-lived, one-use grant bound to the current task, input, installed operation and live node session.
  • Typed heartbeats use canonical Syn encrypted pub-sub. The upstream runtime owns custody, encryption, signatures and replay checks; Potbot handles verified installation and supervised public interfaces.
  • Existing PostgreSQL execution telemetry retains the exact Syn release and selected-node pins. Missing, changed or lost native state fences work. Legacy in-process actors require an explicit development fixture.

Official Syn 0.4.0 installation/native-adapter acceptance passed Python 3.12 and 3.13 in run 41526414147. Both jobs used real installed signed packages and the full deployment registry, verified signed native heartbeat reception, rejected invalid grants and fenced nodes/monitors on relay loss. The fixtures explicitly dispatched no positive Cog process: qualified images, cgroup/syscall/TASKSTATS accounting, task/budget/lease admission and U16 host acceptance remain mandatory. This is a source preview, not general production rollout.

Source: 8df3e9a15ee1a7413379ff8868f38ae78e22f853, merged by PR 23. All required checks passed on that exact source. Its tree matches the reviewed consumer 2d30849f3f13fee295e7a065b4be83c9965d07a3 used by official upstream acceptance.

Paired runtime: signed immutable Syn 0.4.0, source 6205baf95b87193133d45c749a0fe5d5b577581f, manifest SHA-256 a406356fba844a28c04870e45299ccd83e406b5dbe8b7a55741db6d5a6cd1088. Select the independent upstream release pins.

The established publication workflow builds and verifies the wheel/source archive, then attaches those bytes, a source manifest and checksums without replacing existing assets. Registry publication follows existing configured-publisher settings. See the maintained Cog admission guide for current qualification and limits. SYN-R06 owns upgrades/recovery; existing installation identities remain under their selected policy.

Assets 6
Loading