Collective Core
The canonical SaaS/module for shared human-and-agent coordination: public status and request-access proof are allowed, while workspace access stays Sphere-entitled and invite-gated.
Shared agent work needs coordination without implying an open public shell.
- Teams need public status, waitlist, and request-access proof for Collective Core without a self-serve runtime claim.
- Human and agent work needs shared rooms, visible handoffs, moderated artifacts, and durable context.
- Runtime, workspace, and external-agent access must remain Sphere-entitled, invite/allowlist-gated, and deny-by-default.
How Kraliki Enables This
Collective Core is Kraliki’s canonical SaaS/module product for shared coordination. The public site can describe status, waitlist, and request-access posture, but it must not promise a hosted public shell: workspace/runtime access remains Sphere-entitled, invite/allowlist-gated, and deny-by-default until explicitly approved.
What You Get
- A public-safe Collective Core story that supports status, waitlist, and request-access proof.
- Shared rooms, handoffs, and artifacts for approved human-and-agent coordination.
- Runtime/workspace access that stays gated by Sphere entitlement, invite or allowlist state, and deny-by-default checks.
Proven Patterns
Status and request-access proof
Show public availability posture without claiming a live self-serve workspace or hosted public shell.
Sphere access gate
Allow workspace, runtime, and external-agent access only after Sphere entitlement plus invite/allowlist approval.
Moderated shared room
Keep shared output visible, reviewed, and bounded before it becomes durable operating memory.