Skip to main content

project-board

The Project Board client: the pb command a machine runs to join a board.

Install from reviewed source

APP_REPOSITORY=/path/to/app-ecosystem
APP_COMMIT=<approved-full-commit>
APP_EXPORT=$(mktemp -d)
test "$(git -C "$APP_REPOSITORY" rev-parse "$APP_COMMIT^{commit}")" = "$APP_COMMIT"
git -C "$APP_REPOSITORY" archive "$APP_COMMIT" | tar -x -C "$APP_EXPORT"

python3 \
  "$APP_EXPORT/products/project-board/packages/project-board/scripts/install_from_source.py" \
  --source-root "$APP_EXPORT"
"$HOME/.local/bin/pb" procedure install --target codex --target claude-code

# After pb setup creates the target configuration:
"$HOME/.local/bin/pb" source use-code \
  --repository "$APP_REPOSITORY" \
  --ref "$APP_COMMIT" \
  --expect "$APP_COMMIT"

The source installer creates and smokes one complete release environment and installs an inert user launcher for releases/current. Its one pip install invocation resolves the four first-party distributions (project-board, app-foundation, service-foundation, and connection-hub with its client extra) from the clean export together with their third-party dependencies. The client needs no KDCube package and no Connection Hub command line (W322). The checkout is not an import path. pb source status reports the active release and environment, launcher version, target receipt, the App Ecosystem commit, every selected package tree, and the source reported by the supervised relay.

Package contents

  • project_board.client: the pb command. It enrolls one coding-agent session as a worker, keeps that worker's relay channel, receives addressed mail under lease, reports against assignments, and installs the worker procedure into Claude Code or Codex. Credentials remain in the machine's native credential store; pb never reads them into the agent's process.
  • project_board.contract: the references, worker identity, operation outcomes, plan shapes, and mail contracts that the client and the server both speak, defined once here.
  • project_board.procedures: the operator, worker-host, setup, testing, and live-acceptance runbooks that travel with the client they operate.

The server side stays in its own repository and depends on this package for the contract.

What the relay keeps on the host (the outbox, reconciliation receipts, mail, leases and markers), how each store is partitioned, its retention bound and the relay store read log line are in Storage and retention.

Select host source

A published distribution remains a supported independent source. Install and smoke its complete release environment, make it current, and verify the relay restart with:

pb source use-release --expect-version 2026.09.26.2220

The source deployment selects one reviewed App Ecosystem commit:

pb source use-code \
  --repository /path/to/app-ecosystem \
  --ref <commit-or-ref> \
  --expect <full-40-character-commit>

The code release is exported from Git objects and verified blob by blob. It contains project-board, app-foundation, service-foundation, and connection-hub from the App Ecosystem commit. The commit and package trees form one path-independent release ID. A release selected before W322 also named connection-hub-cli and a KDCube commit; it stays readable, keeps its id, and can still be rolled back to. One host-wide releases/current pointer is shared by the pb launcher and every relay definition; each target keeps its source-action receipt. An installed relay must report the candidate source before the switch succeeds. A failed start restores the previous current release and target receipt.

Running python -m project_board.client.entrypoint with checkout package paths on PYTHONPATH is an explicit development process. It does not change the host selector, and pb status reports that process as unpinned checkout code.

Why it is packaged

A machine that runs agents installs one package family and selects one durable source manifest. Commands and the relay therefore load the same reviewed implementation, while the release ID, repository commits, and package-tree identities give deployment and status checks precise facts to compare.

Metadata

Release files for project-board 2026.9.26.2220

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for project-board 2026.9.26.2220
File Size Uploaded Provenance
project_board-2026.9.26.2220.tar.gz 848.2 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for project-board 2026.9.26.2220
File Interpreter ABI Platform
project_board-2026.9.26.2220-py3-none-any.whl Python 3 none any Details

Total release size: 1.6 MB

Release files / project_board-2026.9.26.2220.tar.gz

Download URL project_board-2026.9.26.2220.tar.gz
Size 848.2 kB
Tags Source
SHA-256 checksum
How to use checksums
0d07e8e2265233551d78f0efea85b545d8fc1345f0daf4159f81630d2fe153f2
BLAKE2b-256 checksum
How to use checksums
d570463525fd5ca6f9f2c49eabba403bffed43dda4be7ca14f2769e2d3f17114
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.

Transparency log

Release files / project_board-2026.9.26.2220-py3-none-any.whl

Download URL project_board-2026.9.26.2220-py3-none-any.whl
Size 735.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f5196ab05e6bf4e79767fe590ad32c79633c374506624840e235d4045291fe99
BLAKE2b-256 checksum
How to use checksums
ff1d5eb71a7d9ca66f00f5ab2ae1d8f15a923827b4eb4001f21467c58b186909
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.

Transparency log

Security for project-board 2026.9.26.2220

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for project_board-2026.9.26.2220.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page