UnityAILab/pgm-libs
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
PGM libraries (PsyGraphMedia *Internal): core, platform, net, identity, collab, dist, hcom, ai, plus the web kit
57 commits 2 branches 16 tags 5.2 MiB
  • Rust 84.6%
  • HTML 8.7%
  • JavaScript 6.1%
  • CSS 0.5%
  • Shell 0.1%
Find a file
Exact
VibeRoller hub 9cf78cd258 Merge work/sponge into develop
2026-10-27 20:30:46 +00:00
crates pgm-libs 5.29.0: plan_assess (T-280), machine in-use (T-314), queued in session summaries (T-287), from VibeRoller 5.33.0 2026-10-27 19:29:58 +00:00
web pgm-libs 5.28.0: the board archive (archivedAt, archive / restore / archive all done / archived, the 48 h / 30 day sweep), product scoping + sweep, web kit board.js (T-190, from VibeRoller 5.32.0) 2026-10-27 04:38:21 +00:00
.gitignore PGM libraries 5.1.0: the eight PGM crates (core, platform, net, identity, collab, dist, hcom, ai) and the web kit, from VibeRoller 5.1.0 (native/crates at cd27395, unchanged; their history stays in VibeRoller); build.sh / build.cmd; Linux + Windows check, cargo test passes 2026-10-22 09:38:04 +00:00
build.cmd PGM libraries 5.1.0: the eight PGM crates (core, platform, net, identity, collab, dist, hcom, ai) and the web kit, from VibeRoller 5.1.0 (native/crates at cd27395, unchanged; their history stays in VibeRoller); build.sh / build.cmd; Linux + Windows check, cargo test passes 2026-10-22 09:38:04 +00:00
build.sh PGM libraries 5.1.0: the eight PGM crates (core, platform, net, identity, collab, dist, hcom, ai) and the web kit, from VibeRoller 5.1.0 (native/crates at cd27395, unchanged; their history stays in VibeRoller); build.sh / build.cmd; Linux + Windows check, cargo test passes 2026-10-22 09:38:04 +00:00
Cargo.lock pgm-libs 5.29.0: plan_assess (T-280), machine in-use (T-314), queued in session summaries (T-287), from VibeRoller 5.33.0 2026-10-27 19:29:58 +00:00
Cargo.toml pgm-libs 5.29.0: plan_assess (T-280), machine in-use (T-314), queued in session summaries (T-287), from VibeRoller 5.33.0 2026-10-27 19:29:58 +00:00
CHANGELOG.md pgm-libs 5.29.0: plan_assess (T-280), machine in-use (T-314), queued in session summaries (T-287), from VibeRoller 5.33.0 2026-10-27 19:29:58 +00:00
NAMES.md T-316: pgm-libs 5.24.0: mirror pgm-sandbox-internal (new) and the current pgm-net-internal (machine module) 2026-10-26 01:17:13 +00:00
README.md PGM libraries 5.1.0: the eight PGM crates (core, platform, net, identity, collab, dist, hcom, ai) and the web kit, from VibeRoller 5.1.0 (native/crates at cd27395, unchanged; their history stays in VibeRoller); build.sh / build.cmd; Linux + Windows check, cargo test passes 2026-10-22 09:38:04 +00:00

README.md

PGM libraries

The reusable libraries behind VibeRoller, PGM Gateway, PGM ShaDow Chat, PGM Hyper Prod Man and PGM Prod Suit. Nothing here knows any one product: what a library needs from the program around it is a trait (ChatHost, AiHub) or a parameter (folders, settings).

  • crates/: the eight Rust libraries. Names, what each holds and their order: NAMES.md. How to use one: each crate's README.md.
  • web/: the web kit, the page-side pieces products share (markdown, board + calendar, notes, calls, servers / channels, server settings, attachments, profiles). What each expects from its page: web/README.md.

Using them from another project

By git tag, so a build is always the same code:

[dependencies]
pgm-core-internal = { git = "https://git.unityailab.com/UnityAILab/pgm-libs.git", tag = "v5.1.0" }
pgm-net-internal = { git = "https://git.unityailab.com/UnityAILab/pgm-libs.git", tag = "v5.1.0" }

Use the same tag for every PGM crate in one program. The web kit is copied into a product's web/ from the same tag.

Working on them

  • cargo test --workspace; Linux and Windows (--target x86_64-pc-windows-gnu) both build.
  • The libraries change only through develop (one worktree per person), are tagged vX.Y.Z on main, and follow the versioning law (MAJOR / MINOR / PATCH, CHANGELOG.md). A change that would break a product is a MINOR or MAJOR, with its reason in the CHANGELOG.
  • Where they came from: VibeRoller's native/crates (VibeRoller 5.0.0 – 5.1.0, its commits a2aeabc … cd27395). Their history up to here stays in the VibeRoller repository. Until VibeRoller builds from this repository, its copy is kept identical.