Unicity Briefing — Friday, 25 September 2026

A cluster of CI-focused PRs reshaped how the codewall pipeline runs and self-maintains. #64 introduced issue forms, a Claude-powered auto-fix workflow, and automatic reopen-for-testing on merge, while #66 pinned Claude to Opus 5.5 for consistent autofix behavior and #67 enforced Codewall policy directly on Claude Code prompts. #65 switched the build to consume a pinned Astrid builder instead of compiling Astrid from source, cutting build time and variance. Together these changes make the CI loop faster, more deterministic, and self-healing.

codewall

Installer security and reliability fixes

Several PRs tightened up installer robustness and safety. #61 ensures the publish gate and managed settings are readable under a strict umask 077, closing a permissions gap. #69 bounds runtime subprocess waits to prevent the installer from hanging indefinitely, and #70 adds test coverage for picker cancellation flows and Windows terminal edge cases. These changes reduce installer failure modes across platforms and harden it against misconfigured environments.

codewall

TLS capsule config caching for protocol layer

#68 caches the protocol capsule's TLS configuration instead of recomputing it repeatedly, reducing overhead on the hot path for TLS-secured protocol operations. This is a targeted performance fix that avoids redundant configuration work during capsule setup.

codewall

Routine dependency upgrades

Dependabot delivered three maintenance bumps: clap 4.6.6→4.6.7 (#54), hkdf 0.12.4→0.13.0 (#51), and actions/checkout 4→7 (#50). These keep the CLI argument parser, key derivation crate, and CI checkout action current with upstream security and compatibility fixes.

codewall

Timeline — Thursday, 24 September 2026

Thu 11:37codewall #61 — fix(install): publish the gate and managed settings readable under umask 077

Thu 14:48codewall #64 — ci: issue forms, Claude auto-fix, and reopen-for-testing on merge

Thu 15:00codewall #66 — ci(autofix): pin Claude to Opus 5.5

Thu 15:15codewall #65 — ci: use the pinned Astrid builder instead of building Astrid from source

Thu 15:29codewall #67 (Enforce Codewall policy on Claude Code prompts) · codewall #50 (chore(deps): bump actions/checkout from 4 to 7) · codewall #54 (chore(deps): bump clap from 4.6.6 to 4.6.7)

Thu 15:37codewall #68 (fix: Cache the protocol capsule TLS configuration (#24)) · codewall #69 (fix: fix(installer): bound runtime subprocess waits (#35))

Thu 15:46–15:49codewall #70 (fix: test(installer): cover picker cancellation and Windows terminals (#36)) · codewall #51 (chore(deps): bump hkdf from 0.12.4 to 0.13.0)

Sphere1 PRs merged

Fix dev build release commit target branch

#824 corrects the release automation so a dev build's release commit is pushed to its own dedicated branch instead of accidentally landing on main. This prevents dev/pre-release artifacts from polluting the main branch history and keeps release provenance clean for the sphere-sdk.

sphere-sdk

Unicity Network6 PRs merged

Codewall tenant configurability and policy control

#363 makes endpoint poll cadence tenant-configurable, letting different tenants tune polling frequency to their needs. #357 hides revoked endpoints from the fleet list by default, reducing clutter and accidental use of dead endpoints. #362 fixes rule/policy reloads to only affect the tenants actually impacted, avoiding unnecessary churn across unrelated tenants. Together these changes improve multi-tenant isolation and operational hygiene in codewall's semanticd service.

semanticd

CI autofix pinning for semanticd

#361 pins Claude to Opus 5.5 in the semanticd autofix workflow, mirroring the same stabilization effort applied in codewall to ensure consistent, reproducible auto-fix behavior in CI.

semanticd

Static file serving for staging installer/releases

#358 changes the staging deploy to serve the installer and release artifacts as static files rather than through dynamic handling, simplifying the deployment path and improving reliability for staging installs.

semanticd

Bridge package publishing to npm

#6 sets up CI to publish the bridge packages to npm under the @unicitylabs scope, with dev versions automatically derived from branch builds. This gives downstream consumers a reliable, versioned npm distribution channel for both stable and in-development bridge packages.

unicity-bridge

Timeline — Thursday, 24 September 2026

Thu 17:55unicity-bridge #6 — ci: publish the bridge packages to npm as @unicitylabs, with dev versions from branches

Thu 21:28semanticd #362 — fix: reload only affected tenants’ rules and policies

Thu 21:35semanticd #361 — ci(autofix): pin Claude to Opus 5.5

Thu 22:00semanticd #358 — fix(deploy): serve the staging installer and releases as static files

Thu 22:08semanticd #357 — feat(codewall): hide revoked endpoints from the fleet list by default

Fri 01:27semanticd #363 — feat(codewall): make endpoint poll cadence tenant-configurable

Project board comparison Stale statuses · No Status · open PRs not tracked

Astrid board ↗Backlog 170 · In progress 33 · No Status 3 · Done 904

⊘ NO STATUS

NOSTATUS

feat(cli,kernel): astrid events tail — live event-bus subscriber for IPC debugging

astrid #685 · No Status assigned

NOSTATUS

feat(cli,capabilities): astrid caps trace <agent> <action> — strace for capability resolution

astrid #691 · No Status assigned

NOSTATUS

Bind a specific LLM provider/model to a principal (umbrella)

astrid #961 · No Status assigned

✗ NOT ON BOARD

MISSING

feat: KV-backed memory with add_memory tool and /memory-export command

capsule-memory #3 · Open PR not tracked on any board

MISSING

fix: drop the imagined { data: ... } wrapper from session/compact response reads

capsule-react #16 · Open PR not tracked on any board

MISSING

Forward direct tool calls + attribute by principal

capsule-cli #16 · Open PR not tracked on any board

MISSING

feat: port background-process tools to the persistent process tier

capsule-shell #16 · Open PR not tracked on any board

MISSING

feat(distro): provider multi-select + per-provider model select (DO NOT MERGE until astrid #1016 ships)

astralis #8 · Open PR not tracked on any board

MISSING

fix(grok): launch MCP with host-safe relative aos-up

oracles #25 · Open PR not tracked on any board

MISSING

feat: add capacity planning and readiness-driven multiplexing

aos-ce #52 · Open PR not tracked on any board

MISSING

chore(deps): bump actions/setup-python from 6 to 7

oracles #28 · Open PR not tracked on any board

Sphere board ↗Backlog 48 · In Test 2 · In progress 17 · Ready 2 · Done 116

⚠ STALE STATUS

STALE

Feat/auto connect

sphere-sdk #90 · PR merged, still “Backlog” on board

✗ NOT ON BOARD

MISSING

ci: harden nightly integration workflow — drop artifact upload

sphere-cli #3 · Open PR not tracked on any board

MISSING

feat(trader): add 'sphere trader withdraw' subcommand

sphere-cli #9 · Open PR not tracked on any board

MISSING

feat(trader): add sphere trader withdraw subcommand

sphere-cli #12 · Open PR not tracked on any board

MISSING

Reject partial integer option parsing

sphere-cli #30 · Open PR not tracked on any board

MISSING

Update apps.json

sphere-apps #4 · Open PR not tracked on any board

MISSING

fix(cli)(#48): wrapper field-trial fixes — 3-shot bootstrap, UNICITY_ env strip, identical-path bind, post-spawn SET_STRATEGY

sphere-cli #50 · Open PR not tracked on any board

MISSING

Rewrite as the Astrid dev landing: 0.9-true claims, security-thesis hero

astrid-site #1 · Open PR not tracked on any board

MISSING

Phase 6: v1 → v2 SDK migration (uxf-v2 fork review artifact)

sphere-sdk #640 · Open PR not tracked on any board

Unicity Network board ↗Blocked 5 · In Dev 7 · No Status 1 · Todo 87 · Done 377

⚠ STALE STATUS

STALE

Streaming round processing with adaptive timing

aggregator-go #51 · PR merged, still “Todo” on board

⊘ NO STATUS

NOSTATUS

Allow webwallet to import Sphere's json

webwallet #5 · No Status assigned

✗ NOT ON BOARD

MISSING

EVM

bft-core #11 · Open PR not tracked on any board

MISSING

test: add comprehensive unit tests for uncovered modules

nostr-js-sdk #4 · Open PR not tracked on any board

MISSING

Add comprehensive unit tests (366 new tests)

nostr-sdk #4 · Open PR not tracked on any board

MISSING

Feature/test infrastructure

state-transition-sdk-js #106 · Open PR not tracked on any board

MISSING

feat: CI/CD fixes, documentation, security policy, and release automation

unicity-node #9 · Open PR not tracked on any board

MISSING

fix(faucet): use conservative transferMode for FAUCET_REQUEST sends

js-faucet #2 · Open PR not tracked on any board

MISSING

Add BDD test suite covering V2 SDK functionality

state-transition-sdk-java #66 · Open PR not tracked on any board

MISSING

test: FGP audit coverage (#1-#12) + hardening gap-documentation (#17)

finality-gadget #18 · Open PR not tracked on any board

MISSING

fix(aggregator): classify submit_commitment/get_inclusion_proof failures as unreachable

infra-probe #1 · Open PR not tracked on any board

MISSING

test: unicity-node audit coverage (#1 / #5 / #6) + hardening repros (…

unicity-node #15 · Open PR not tracked on any board

MISSING

feat(acp-adapter): expose SPHERE_AGGREGATOR_URL + SPHERE_TRUSTBASE_URL env overrides

js-faucet #3 · Open PR not tracked on any board

MISSING

config(sidecar): bump SIDECAR_CACHE_MAX_ENTRIES 10k -> 100k (#13)

ipfs-storage #14 · Open PR not tracked on any board

MISSING

feat(nginx)(sphere-sdk-#370): expose /api/v0/dag/import + /api/v0/dag/export

ipfs-storage #15 · Open PR not tracked on any board

MISSING

chore(ci): bump actions/checkout from 6 to 7

astrid-capsule-sif #5 · Open PR not tracked on any board

MISSING

Migrate to @unicitylabs/sphere-sdk 0.15.0

Boxy-Run #2 · Open PR not tracked on any board

MISSING

chore(ci): bump actions/cache from 5 to 6

astrid-capsule-sif #6 · Open PR not tracked on any board

MISSING

perf: black-box load/verification client for deployed aggregator/gateway

aggregator-go #166 · Open PR not tracked on any board

MISSING

chore: extract ML training pipeline into unicitynetwork/ml-training

semanticd #80 · Open PR not tracked on any board

⛔ Blocked itemsAll items in Blocked column across all project boards

Unicity Network board ↗

⛔ BLOCKED

Issue

Openclaw Prediction Market: Agent Wallet

uniclaw #3

Issue

Openclaw Prediction Market: Openclaw Plugin (Skill & Tools)

uniclaw #1

Issue

Openclaw Prediction Market: Frontend for Humans

uniclaw #4

Issue

Openclaw Prediction Market: API for Bots

uniclaw #2

Issue

[Permissioned MVP] Transition Flow Implementation - Ensuring single use for a nametag address by a token state

.github #12

Needs attention

bft-core #11 "EVM" by @MastaP — open 248 days, untracked on any board

Oldest open PR in the org at 248 days and completely missing from board tracking. No visible reviewer engagement. Action: assign a reviewer immediately, add to board, and get a merge/close decision this week.

critical

nostr-js-sdk #4 and nostr-sdk #4 (both 'comprehensive unit tests') by @b3y0urs3lf — open 231 days each, untracked

Two large test-suite PRs (366 new tests in nostr-sdk) sitting unreviewed for 231 days with no board presence. Action: decide whether these still apply against current codebase — either fast-track review or close and ask author to rebase/resubmit.

close or revive

sphere-cli #3, #9, #12 by @vrogojin — open 154, 143, 138 days, all untracked

Three overlapping sphere-cli PRs from the same author (#9 and #12 appear to be duplicate 'trader withdraw' submissions). None are on a board. Action: consolidate into a single PR, close the duplicate, and assign a reviewer for the survivor plus the CI-hardening PR (#3).

decision needed

sphere-sdk #90 "Feat/auto connect" — merged but still shown as Backlog

PR merged yet the board card is stuck in Backlog status, which risks masking completed work in reporting. Action: board owner to move card to Done and audit for other stale merged cards.

unblock

aggregator-go #51 "Streaming round processing with adaptive timing" — merged but still shown as Todo

Same stale-status issue as sphere-sdk #90 — merged PR still sitting in Todo column on the Unicity Network board. Action: update status to Done; consider adding automation to sync PR merge state with board columns.

unblock

capsule-memory #3 by @joshuajbouw — open 191 days, no board status, Astrid project

KV-backed memory feature PR has no reviewer and no board status after 191 days. Action: Astrid project lead to triage, assign a reviewer, and add the card to the board this sprint.

assign reviewer

Team activityAll members — author + involves sweep

Joshua J. Bouw @joshuajbouw

Merged four Codewall installer/protocol fixes: #57 auto-selecting the Claude principal, #56 provisioning Claude before enrollment, #49 reconciling stable AOS and plugins by default, and #23 switching HTTP deadlines to the Astrid clock. Still has four PRs open covering picker cancellation tests (#36), bounded runtime subprocess waits (#35), TLS config caching (#24), and the release-versioned Astrid CI image (#16), plus involvement in principal lifecycle isolation (#37) and the plane host migration (#6).

4 mergedcodewall installer4 open PRsAstrid clock

Pavel Grigorenko @MastaP

Merged codewall #45 to move CI onto self-hosted aos-linux runners, sphere-sdk #824 fixing dev build release commits to push to their own branch instead of main, and unicity-bridge #6 setting up npm publishing for bridge packages under @unicitylabs. Also involved in sphere-sdk #822 (custom-genesis mint/burn token plugins) and #823 (publish.yml dev build CHANGELOG dating).

3 mergedCI runnersnpm publishingsphere-sdk release fixes

Alexander Khrushkov @KruGoL

Involved in sphere-sdk #824, the fix ensuring a dev build's release commit is pushed to its own branch rather than main.

1 involvedsphere-sdk release

Risto Laanoja @ristik

Involved across the three foundational unicity-bridge PRs: #3 (batching return service, Ethereum Sepolia deployment, per-chain-family plugin), #2 (wallet plugin interface, wallet value format, v2 Nile vault), and #1 (porting bridge packages to state-transition-sdk 3.0.1).

3 involvedunicity-bridgebridge architecture

Jamie Steiner @jvsteiner

Extremely active merging 15 PRs across codewall and semanticd: enforcing Codewall policy on Claude prompts (#67), pinning Claude to Opus 5.5 (#66, #361), switching to the pinned Astrid builder (#65), CI automation for issue forms and auto-fix (#64), permission fixes for gate/managed settings (#61), Claude hook trust and native tool gate (#60), several protocol enrollment recovery fixes (#48, #44, #42), principal lifecycle isolation (#37), edge collection reporting (#30), the plane host migration (#6), tenant-configurable poll cadence (#363), and staging installer static file serving (#358). Has one open PR (semanticd #333) tackling tenant policy store/compose/tick fingerprint rebuild issues, and was involved reviewing six other codewall PRs (#70, #69, #68, #59, #57, #49).

15 mergedcodewall CI/CDsemanticdheaviest contributor1 open PR

@b3y0urs3lf

Opened three issues/PRs flagging gaps: codewall #63 on missing UserPromptSubmit hook enforcement, codewall #62 to align Codewall's repo automation with SIF's (board columns, autofix, test categorization), and semanticd #360 requesting tenant-configurable poll cadence via Fleet settings. Also involved in codewall #58 reporting that install falsely reports success while enrollment and hook events silently fail.

3 open PRscodewall policy gapsbug reports

@jait91

Merged codewall #28 for durable signed endpoint telemetry capture/upload and semanticd #362 fixing tenant-scoped rule/policy reloads. Has three PRs open: codewall #59 (Claude project MCP inventory via hooks), codewall #43 (fixing Astrid fuel allowance exceeded for non-admin identities), and semanticd #359 (showing MCP servers/repos by project), plus involvement in codewall #30.

2 merged3 open PRstelemetryMCP inventory

@lploom

Working on the bridge/sphere ecosystem with six open PRs: sphere #529 (bridge module for asset bridging via wallet modules), sphere-sdk #822 (custom-genesis mint/burn token plugins), and four unicity-bridge PRs — #3 (batching/Sepolia/chain plugins), #2 (wallet plugin interface and Nile vault), #1 (state-transition-sdk 3.0.1 port), and #5 (mainnet vault payout modes). Also involved in codewall #23 and unicity-bridge #4 (testnet e2e plan and work log).

6 open PRsunicity-bridgesphere-sdkbridge module

No activity this window

@igmahl, @martti007, @ahtotruu, @vrogojin, @0xt1mo

Sweep method (permanent): Each report runs involves:USERNAME for every team member in addition to org-level PR/issue sweeps. Catches closes, reviews, comments, and assignments — not just authored items.

Long-standing open PRsAll open PRs older than 7 days — sorted oldest first

Age	PR	Author
248d	EVMDraft bft-core #11	@MastaP
231d	test: add comprehensive unit tests for uncovered modules nostr-js-sdk #4	@b3y0urs3lf
231d	Add comprehensive unit tests (366 new tests) nostr-sdk #4	@b3y0urs3lf
191d	feat: KV-backed memory with add_memory tool and /memory-export command capsule-memory #3	@joshuajbouw
170d	Feature/test infrastructure state-transition-sdk-js #106	@b3y0urs3lf
162d	feat: CI/CD fixes, documentation, security policy, and release automation unicity-node #9	@0xgetz
154d	ci: harden nightly integration workflow — drop artifact upload sphere-cli #3	@vrogojin
143d	feat(trader): add 'sphere trader withdraw' subcommand sphere-cli #9	@vrogojin
142d	fix: drop the imagined { data: ... } wrapper from session/compact response reads capsule-react #16	@joshuajbouw
138d	feat(trader): add sphere trader withdraw subcommand sphere-cli #12	@vrogojin
137d	fix(faucet): use conservative transferMode for FAUCET_REQUEST sends js-faucet #2	@vrogojin
134d	Add BDD test suite covering V2 SDK functionality state-transition-sdk-java #66	@b3y0urs3lf
127d	test: FGP audit coverage (#1-#12) + hardening gap-documentation (#17) finality-gadget #18	@b3y0urs3lf
127d	fix(aggregator): classify submit_commitment/get_inclusion_proof failures as unreachable infra-probe #1	@vrogojin
123d	Forward direct tool calls + attribute by principal capsule-cli #16	@jvsteiner
119d	test: unicity-node audit coverage (#1 / #5 / #6) + hardening repros (… unicity-node #15	@b3y0urs3lf
119d	feat(acp-adapter): expose SPHERE_AGGREGATOR_URL + SPHERE_TRUSTBASE_URL env overrides js-faucet #3	@vrogojin
118d	config(sidecar): bump SIDECAR_CACHE_MAX_ENTRIES 10k -> 100k (#13)Draft ipfs-storage #14	@vrogojin
117d	Reject partial integer option parsing sphere-cli #30	@samsamtrum
116d	feat(nginx)(sphere-sdk-#370): expose /api/v0/dag/import + /api/v0/dag/export ipfs-storage #15	@vrogojin
113d	Update apps.json sphere-apps #4	@Vadya05
110d	feat: port background-process tools to the persistent process tier capsule-shell #16	@joshuajbouw
106d	fix(cli)(#48): wrapper field-trial fixes — 3-shot bootstrap, UNICITY_ env strip, identical-path bind, post-spawn SET_STRATEGY sphere-cli #50	@vrogojin
95d	chore(ci): bump actions/checkout from 6 to 7 astrid-capsule-sif #5	@dependabot[bot]
94d	Migrate to @unicitylabs/sphere-sdk 0.15.0 Boxy-Run #2	@MastaP

June release8/8 done · 0 days to deadlineon trackboard ↗

✔ What's moving

All 8 release items completed

100% of scoped work items for the June 2026 Unicity release are marked done with zero open items remaining.

Release deadline reached with full completion

Deadline is today, June 30, 2026, and progress tracking shows no outstanding tasks blocking sign-off.

Final validation window now active

With coding complete, focus should shift to smoke testing, changelog review, and tagging the release build.

Go/no-go decision ready for stakeholders

Release owner can proceed to final approval since no blockers or unassigned work remain in the tracker.

⚠ What worries

No visibility into QA or regression testing status

Item completion does not confirm testing coverage; without explicit QA sign-off, undetected defects could ship on the deadline day.

Zero-day buffer for last-minute issues

With 0 days remaining, any late-discovered bug or deployment failure has no slack for remediation before the June 30 deadline.

Deployment and rollback readiness unconfirmed

Task completion in the tracker does not verify that deployment scripts, infra changes, or rollback plans have been rehearsed for release day.

Lack of item-level detail obscures risk concentration

With no open items listed, it's unclear which owners handled critical path work, making it hard to assess single-point-of-failure risk post-release.

Unicity project — daily brief