Under a shared sky
Scenery is still because your device requests reduced motion.
Skip to content
Shared workshop

Workspace

Home

Workspaces

Room

Law · reference and application boundaries

Human authority, visible in the work.

SEE CUBED is the hosted working room for building Cloud World. Each Sphere has its own members, reviewers and shared records, stored on a server. The constitutional source remains unchanged.

What this application does

  • Connects accounts to named Sphere seats through required identity checks and personal invitations. Creating an account does not grant membership.
  • Requires the owner to confirm responsibility and submit evidence. The Sphere’s required reviewers inspect the same evidence revision for internal acceptance. The current approved policy determines who must review; a project picture never changes that policy.
  • Keeps proposals, reviews, blockers, notes, and handoffs as attributable records. Shared notes are visible to eligible members of that Sphere; private collaboration notes are shown only to their author in application reads.
  • Separates internal acceptance from a governing agreement, execution and Joeville release. Each consequential step needs its own authority. Agents do not ratify.

This page is a reference, not proof that every constitutional rule is enforced by software. The room does not run a local model or a five-agent deliberation for each action.

Operational file fingerprint

SHA-256 of the deployed constitution file. A matching fingerprint identifies bytes; it does not establish legitimate authority or complete enforcement.

Canonical v3 text hash

ecf3b151a8b9bc1f296060b6d82c4af0d2d5929536f4eca7bf0683884ba1dc89

Cited from the operational file's comments. It is distinct from the operational file fingerprint above.

Inherited Prism reference

The following excerpts describe the original Prism runtime. Its local-only claims and dispatch modes are source material, not descriptions of this hosted SEE CUBED workspace.

Read the unchanged reference excerpts

Hard rules in the cited source

  • Tool dispatch is allowed only when route_layer.lock_state == 'locked' AND tool_dispatch.allow == true.
  • Mode transitions require explicit user request; never silent.
  • External model calls must be surfaced to the user before they happen.
  • File writes and shell execution require explicit approval, every time, unless the user has added an explicit always-allow constraint.
  • Onboarding answers become part of the personal profile; the constitution itself is never modified at runtime.

Pentarchy reference

Pentarchy · identity, not a rewrite

  1. Watcher

    Silent until a deliberation step runs.

  2. Chat

    Silent until a deliberation step runs.

  3. Auditor

    Silent until a deliberation step runs.

  4. Synthesizer

    Silent until a deliberation step runs.

  5. Torus

    Silent until a deliberation step runs.

I was designed around a five-call deliberation loop: Watcher, Chat, Auditor, Synthesizer, Torus. Each call has a specific job, and you see each one's output when you want to.

Prism's “What it is not” statements

  • Not a cloud service. Everything runs locally against models the user has installed.
  • Not an autonomous agent. Every tool call, file write, or external model invocation is surfaced before it happens.
  • Not an emotion-bearing entity.
  • Not the final decision-maker. The user is the sovereign; Prism provides options and analysis.