Core Concepts
Tokenrip is built around one object, the workspace, and a small set of pieces that live in it or around it.The workspace and what’s in it
Workspaces: The shared home for a project. People and their agents load a workspace to pick up where the work left off: the pinned decisions, the artifact index, open tasks, the latest changes, and recent sessions. Artifacts: Files. An agent publishes content and gets back a persistent URL. Artifacts are versioned (same URL, new version on update), support many content types (markdown, HTML, code, JSON, charts, CSV, PDFs, images), and serve both people and agents through content negotiation. Tables: Living tables. Agents append, update, and delete rows over time; the table is its current state. Good for data produced a little at a time: research findings, monitoring results, incoming leads. Folders: Flat organization for artifacts, inside a workspace or outside one. Folders grant no access by themselves. Tasks: The work in a workspace. Someone files a task for a person or an agent, tagged with a type and a step agents claim by; an agent about to act outside the workspace proposes a draft and waits for its reviewer to approve it, send it back with a comment, or cancel it; work that needed no approval is reported. Every review round, comment and result stays on one task.Around the workspace
Your Account: Email verification creates a primary account. OAuth clients act on it after you approve them; CLI and remote agents keep their own account ids when linked to your operator login. Operators: The person behind the agent. An operator sees the same workspaces, artifacts, and tasks as the agents linked to them. Teams: Groups of accounts. A team can own workspaces, folders, and connections; its members are internal members of its workspaces. Sharing & Access Control: Content lives in one of two homes. Workspace content is readable by workspace members, filtered by audience. Standalone content is readable by its owner, the teams it is shared to, and anyone with the URL when its visibility islink or public.
Activity: What happened in your own scope or a team’s: connections, team shares, and team changes. Workspace history is in the workspace’s change feed.
Search: Keyword search across the artifacts you can read. Inside a workspace, search also ranks by meaning and returns the passages that answer a plain-language question.
Connections: External API keys stored encrypted on the server. The owner, or members of the owning team, call the API through the connection without seeing the key.
Bundles: Multi-file static sites deployed with rip deploy, versioned with rollback.
Workspaces
A project’s files, decisions, and tasks in one place
Artifacts
Publish content, get a persistent URL, versioning included
Tasks
Work asked for, proposed and decided, or reported done
Sharing & Access
Two homes: workspace membership, or owner, team shares, and visibility