111k

Topoo Cloud

Product model for the Topoo private cloud control plane.

Topoo Cloud turns distributed serverless infrastructure into a customer-facing private cloud with concrete projects, nodes, resources, deployments, and operating state.

Customers buy and operate Topoo capacity. They should not need to understand which upstream provider implements a runtime, database, storage service, network, or security capability.

Project & Node Model

Define Project as the unified product and release subject, and Node as a permission-scoped code container and attention boundary.

Node Workbench & Lifecycle

Unify Source, editors, Agent Submissions, Node Versions, Artifacts, Project Releases, and Deployments into one lifecycle.

Project Control Plane

Define Cloud Project as the integration boundary for modules, runtime resources, domains, source, and deployments.

Runtime & Resources

Describe Topoo-facing Nodes, storage, databases, queues, domains, secrets, and their real operating state.

Source & Deployment

Separate code provenance from runtime artifacts while keeping every deployment traceable to its source version.

Source Control Model

Map GitHub source history, Topoo Project revisions, Agent submissions, and deterministic release control into one product model.

Implementation Status

See the binary audit of completed and not-completed source-control capabilities.

Deployment Control Plan

Understand the problem, product direction, and ownership boundaries for Agent submissions and controlled releases.

Core terms

TermMeaning
WorkspaceThe tenant and policy boundary that owns projects, members, plans, and shared capacity.
Cloud ProjectThe externally unified product and release subject that organizes Nodes, environments, resources, domains, deployments, and observability.
NodeA persistent, permission-scoped code container and attention boundary inside a Project.
Node WorkbenchThe common editing and lifecycle surface for a Node; specialized visual and no-code editors operate on the same canonical Source.
AgentAn actor that works under a Node's scope, identity, permissions, and operating procedure.
SessionA temporary execution context attached to a Node; it does not define a new responsibility boundary.
SubmissionA bounded proposed change from a person, Agent, or Session; it does not carry Production authority.
Source RevisionOne immutable Source state recorded by Topoo and traced to a GitHub commit or detached imported snapshot.
Node VersionAn immutable accepted Node state that pins Source, Submissions, Checks, dependencies, and delivery metadata.
ArtifactAn immutable build output produced from an exact Node Version and build contract.
ResourceA project-bound capability such as a database, object store, queue, domain, secret, or AI service.
Project ReleaseThe accepted, immutable set of Node versions that represents the product.
DeploymentBinding and promotion of an accepted Project Release Artifact Set into an Environment, linked back to Node Versions, Source Revisions, Checks, and approvals.

Product rule

Topoo Cloud is the customer-facing abstraction.

Upstream providers are implementation details. Product language, quotas, status, billing, and documentation must describe Topoo capabilities first.

Provider-specific identifiers may exist in internal adapters and diagnostics, but they must not define the customer model.

Relationship to toProject

toProject documents the project object for agent-led work and execution.

Topoo Cloud documents the infrastructure control plane used to run and expose software. A Cloud Project may host or deploy outputs produced by toProject, but the two concepts have different responsibilities and must not be collapsed into one model.