Skip to main content

Repositories and packages

RepositoryPackage and registry state verified 2026-10-10Role and dependency directionBelongs hereDoes not belong here
drumee/server-runtime@drumee/server-runtime; next 0.1.0-alpha.3, latest 0.1.0-alpha.1generic Node backend runtimesession, ACL, dispatch, push, intrinsic SQLMFS/product behavior
drumee/ui-runtime@drumee/ui-runtime; next 0.1.0-alpha.2, latest 0.1.0-alpha.1generic browser runtimeLETC, Kind, Skeleton, services, WebSocket clientFinder, Window Manager, SSR
drumee/system-mfs@drumee/system-mfs 0.1.0-alpha.1; next and latestoptional backend capability, no npm runtime dependenciesMFS SQL, namespace, tree, permission primitivesidentity provisioning, transfer UI/jobs
drumee/window-manager@drumee/window-manager 0.1.0-alpha.2; next and latestoptional UI capability; peer-depends on ui-runtimegeneric window lifecycle/interactionsFinder or Desk policy
drumee/finder@drumee/finder; next 0.1.0-alpha.4, latest 0.1.0-alpha.1optional UI/MFS browsing capability; peer-depends on ui-runtime, with an optional Window Manager peerlogical browsing, interaction, transfer orchestration, media requests, syncauthorization, SQL, physical storage, backend jobs
drumee/transientintegration/evidence workspace; no public assembler packageintegrates and validates the layersbootstrap, Hello, MFS service/transfer/media adapters, kernel harness, cross-package evidenceproduction Finder source or final package boundary

All five extracted packages are public on npm. Tags are reported because these are alpha releases and may move; consumers should verify the registry at install time. The intentional prerelease channel is next. npm retains latest at 0.1.0-alpha.1 for server-runtime and Finder while next selects their corrected Phase 4.9 releases.

Licensing found​

The five extracted repositories each declare AGPL-3.0-only in package metadata and contain an AGPLv3 LICENSE, including drumee/finder.

transient has no root LICENSE, and its remaining integration artifacts must be evaluated from their own metadata. Do not assume one repository's license automatically supplies absent metadata elsewhere. This is a source-metadata summary, not legal advice.

Historical repositories​

server-team and ui-team are behavioral/provenance sources only. Current standalone packages explicitly test that they do not import them. See Refactor History for traceability.

Integration evidence​

The standalone repositories are authoritative for current package APIs. transient is authoritative only for integrated bootstrap, backend adapter, data-plane, and cross-package validation evidence. Its Finder validation resolves the sibling standalone repository through KERNEL_FINDER_ROOT; it does not carry a second production Finder implementation. The verified harness demonstrates integration contracts but is not a supported production npm-only Kernel distribution or installer.