# Workshop

Route: /workshop · Status: changing · Checked against code: 2026-11-16 f2187eee

The Workshop is where you build your own tool in words. You say what you need («a client portal
for Nord: stages, decisions, what we need from them»), answer a few questions, read a short plan,
and the page gets built. It works on your PulsOne data, inside PulsOne. It is always on: there is
no switch for it in Settings.

## What you see

- **My tools** — a card of its own in the sidebar: «Create a tool» on top, your tools below.
  Empty, it is only the button. A tool that belongs to a project is not listed here: it is a tab
  of that project.
- **The ribbon** under the button (frame 12e): ★ · your workspaces · +. A workspace is a filter of the
  card, never a mode: the menu above never changes. No tab picked shows every tool; ★ the starred
  ones; a workspace its own tools and the starred ones (a star pins a tool in all of them). A tool's
  «…» puts it into workspaces, gives it a date («For a goal») or sends it to the archive. Dated tools
  stand under «For a goal · <workspace>»; past the date they go to «Archive · N» by themselves, data
  kept, «Bring back» returns them. The card's «…» on a picked workspace renames it, removes it (its
  tools stay) or hands the whole workspace over to a client.
- **Create** (`/workshop`) — the switch **Own · Template** on top. **Own**: one question, «What tool
  do you need?», a field with a project pill (which project the tool works on and lives in, or none),
  a microphone, a few starts, three ready ones («Or take a ready one»), and the builds you left
  unfinished.
- **Template** («Ready made», frames 14, 14b; `/workshop?side=template`) — [All | Tools | Workspaces],
  a search, chips (Clients, Content, Study, For a goal, Team), cards: a sketch of the page, the name,
  Tool or Workspace, the data a tool reads as icons, what a workspace holds («Client portal · CRM ·
  3 rules»), how many installed it. Pick one: a dark bar comes up with ● project ▾ (a tool), ▦
  workspace ▾ and **Install**. Installing is a copy, not a build: no AI, free, seconds. The tool is
  yours and empty (none of the author's data). A workspace template goes into a new workspace and
  offers its rules as «Turn on?» cards (the rule window opens with the rule's words; nothing turns on
  by itself).
- **Connect your own services** — a strip above a tool from a template or a handoff that needs a
  service you have not given it: «Connect GitHub» opens the same «+ Service» window (page Workshop).
  Until then that service's block does not work; once connected, the tool takes it at once (a new
  version, free).
- **The build** — the whole screen: a chat on the left, a scene on the right. Until there is a
  page, the scene is the po mark: it listens, thinks, leans in when it asks, dozes after 40 s
  without an answer, and smiles when the plan is ready.
  - «Understood» — what the Workshop heard, in your words.
  - **Questions** — one at a time, with options as buttons, «Or answer in your words…», Next and
    Skip. Answered ones become lines above.
  - **«OnePuls will do this»** — when a request needs no tool (a training plan). Go to OnePuls,
    or Stay: the build starts again, looking for what a tool could do.
  - **The plan** — comes in two steps. First five lines in seconds: what you get (every screen),
    which data, who sees it, AI inside, what it writes outside. While you read them the
    assignment for the builder is written; then the plan shows the screens it will build, and
    Build becomes active. No price: a build is not linear, the price comes after. «Expand the
    plan» shows the whole assignment, written for a person. Build, or Change (say what to change).
  - **Services** — the outside services the plan reads, connected, and «Connect a service».
  - **Connect right here** (frame 15c) — when the brief names a service you do not have
    («my own tracker instead of Trello»), the first question offers to connect it; a question that
    picks a service has «+ Own service» beside its options. Either opens the same «+ Service» window
    as Settings; what you connect lives on the Connectors page «Workshop». Once it is connected the
    Workshop reads your services again and the questions start over, in that service's words.
  - **Building** — Plan ✓, Page ⟳, Check ○. No percent. Under it, what the AI does right now:
    writing app.js, the checker sent back 3 remarks, editing a file, the checks passed. Stop ends
    the build. The talk above stays open, so you can scroll back to the plan; the chat follows
    new lines only while you are at its end.
  - **Done** — where the tool lives, what it cost («spent $0.28»), Open; for a tool that replaces a
    service, «Bring over from «…»» too.
- **The input** — modes **Plan** (talk about the plan) and **Edit** (change the live tool), **Point**
  (pick one block on the preview; the change is about that block only), the mic, send.
  Computer and phone switch the preview's width.
- **A tool** (`/workshop/tool/<id>`, or a project's tab) — its page on the whole work area, the
  **access pill** by its name, and ✎ Change, which opens the build on the live version. A member
  of the project's team sees the tool in the project's tab without the pill and without ✎.
- **The access pill** — Only me · Project team · Anyone by link, view only. One window for any tool:
  - **Project team** shows only for a tool that lives in a project with people in it.
  - **By link**: the address (`pulsone.app/v/…`, a random token) with Copy — shown when it is made,
    later only «New link», because PulsOne keeps only its fingerprint; an end (none, a day, a week,
    a month); a password; «Visible: … · What is hidden», from the tool's own description of what a
    guest sees; Revoke link; Send to Telegram or by email.
  - **Entry codes, one per person** («Code · Anna»): 6 digits for the tool's address, a day, a week
    or 30 days. A new code shows a card: the code, Copy, New code, Ends, Opens, Visible, Send,
    Revoke code. Codes already given are listed by name with New code and Revoke.
  - The link mode is greyed out with its reason when a guest has nothing to see, when what a guest
    sees is not named field by field, when the platform put the tool's links out, and on the Free
    plan for the first 7 days of the account.
- **A guest's page** (`/v/<token>` or `/v/<tool id>` + code) — no account: the tool's page, read
  only, with only what the tool shows guests; «Runs on PulsOne» and «Report abuse» at the foot.
  A revoked or expired link says «This link no longer works».
- **View as** — in the build's header, beside computer and phone (frame 19c): you, each person with
  a code by name, the team, a guest by link, each AI participant. The preview shows the tool through
  their eyes on the build's test data. The access pill sits by the name there too.
- **AI in the access window** (frame 19b) — below people, the AI participants in one list: OnePuls,
  your own agents, your own AI by MCP. Each row says what it reads, what it writes (by itself or with
  «yes»), where it works (the «AI here» block, a rule) and who pays (the balance, or your own AI).
  OnePuls and «own AI by MCP» switch on and off; **Own agent** opens its window: a name, what it does
  in your words, skills (your projects with «Instructions for AI»), what it reads, what it writes, by
  itself or with «yes», where it works. Nothing outside what the tool shows an AI can be picked.
- **Hand over to a client** (frame 17b) — «Hand over» at the foot of the access window, «Hand over
  to a client» on a workspace, or say it in the build («Передай Норду, я остаюсь сопровождать»: no
  build, the card comes filled in). To whom (an email, a company); what goes: the data (N collections ·
  M records), the rules, the address, hosting on the client's account; your services do NOT go: each
  in amber, «connects their own»; a tool that reads PulsOne projects says it will read the client's.
  «You»: **I look after it** | **Leave**. «Hand over» makes a link (shown once, 14 days, used once):
  copy it or send it by Telegram or your mail. A waiting handoff is listed in the window with Cancel.
- **The client's page** (`/handoff/<token>`, frame 17c) — no PulsOne needed to look: from whom, what,
  the data, the rules, who looks after it, hosting on their account, «Connect your own services»,
  **Accept and sign in with Google** or «Sign in by email» (a new account is made on the spot). Only
  the address the maker named can accept. After it: the tools, their services to connect, the maker's
  rules offered as «Turn on?».
- **The steward** — the maker who stayed sees the client's tool in their card: ✎ Change (builds on
  their own balance), the journal (to read), the data as the team sees it. The client sees
  «Looked after by …» in the access window with **Remove**: the steward's next call is refused.
- **Journal** — by the pill: who did what in the tool (you, the team, which AI, which rule, which
  button), in batches with **Undo** for a whole batch. On top, what an AI proposed: **Yes** applies
  the batch, **No** drops it. An undo is refused whole if someone changed one of its records since.
- **«AI here» on a tool's page** — pick a participant, ask; the answer, and «waits for your yes: N»
  when it proposed changes. Out of AI balance: the block says so; the page works as before.
- **A button that does several things at once** — a script the builder wrote, run on PulsOne with no
  network; its writes are one batch in the journal.
- **Writing into your services** — a tool may send things to a service you connected («every request
  becomes a task in the tracker»). The plan says so in «Writes outside»: which service, what goes there,
  and how: «with your yes» or «by your rule». A button's write waits for your yes: a strip right above
  the tool, «Waits for your yes: 1 to «Tracker»» with what goes out, **Yes** / **No**. A rule's write goes
  by the service's right on the page («Allowed» goes at once, «With confirmation» waits). An AI only ever
  proposes. Nothing is ever deleted in a service. What went out has its line in the journal, without Undo.
- **«Replace a service»** — say you want your own tool instead of a service you pay for («my own tracker
  instead of Trello»). The plan says what it brings over and which fields. After the build, **Bring over
  from «…»** in the tool's header (and in Done) copies the items into the tool once: one batch in the
  journal, **Undo** takes it all back; pressing it again brings only new items. The service stays
  connected until you remove it; cancelling its subscription is yours to do.

- After a handoff the tool is the client's whole: its versions, data and journal; the maker keeps no
  copy. The maker's links and codes, AI participants and waiting proposals do not go with it; the
  tool's home becomes shared; the client's own OnePuls is in it by default.

## How to use it

1. In the sidebar card **My tools**, press «Create a tool». Write or dictate what you need, pick
   the project if it works on one.
2. Answer the questions, read the plan, change it in words if needed, press **Build**.
3. When it is done, open it from **My tools** or the project's tab.
4. To change it: ✎ Change, mode **Edit**, say what to change («make the overdue status red»), or
   **Point** at a block first. The old version keeps working until the new one is done.
5. A ready one: **Create** → **Template**, pick a card, **Install**. Connect your own services if the
   strip asks.
6. For a client: the pill → **Hand over**, their email, I look after it or Leave, send them the link.
7. To open it to others: press the pill by its name. **Project team** lets the project's people
   work in it. **By link** gives a guest a read-only view; copy the link (or give a code) and send
   it. **Only me** closes everything at once. «Revoke link» kills the old address at once; the next
   one is another.

## How it works

- One build goes step by step: Understand (questions) → Picture (the short plan for you) → Plan
  (the assignment for the builder, to that picture) → Builder → Checker, back to the Builder if
  the Checker finds problems. The screen asks the server for the next step and shows where it is.
- A tool's page runs in a sandbox: it cannot read PulsOne's pages, cookies or storage, cannot open
  windows or leave its frame, and talks to one address only — the data gateway. PulsOne hands it a
  short pass (15 minutes, this tool, you, the live version); the gateway gives it only what the
  plan declared.
- Every change is a new version; the live one moves only when the new one is done. Deleting a tool
  keeps its data.
- A build spends the same AI balance as OnePuls.
- **Who sees what is held on the server.** The tool's description (manifest, `audience`) names,
  per role, what the team and a guest see: collections, their fields, the PulsOne data it reads.
  The gateway cuts everything else out before it answers — a guest never receives a hidden field,
  even if the page asks for it. A guest only reads; a list that is not theirs comes back empty.
  The page is told whose eyes look (`pulsone.ready()` → `role`) to hide its buttons from a guest.
- **Every call is checked again.** A team member's pass is good while they are in the project and
  the pill lets the team in; a guest's while the link or code is alive. Removed from the project,
  revoked, switched to Only me: the next call is refused, not fifteen minutes later.
- Wrong codes and passwords: the sixth try within 15 minutes is refused, by tool and by address.
  A wrong code never says whether the tool exists.
- **An AI is a participant with a pass, like a person** (§2.10). What any AI may read and write is the
  tool's description (manifest `ai`: what it reads, what it writes, what it never sees); a participant
  gets a part of it. The server cuts the rest out the same way it does for a guest. An AI's write goes
  at once only when you let it write by itself; otherwise it waits for your «yes». A write into an
  outside service waits for «yes» (or runs by your own rule) for any AI.
- **Who pays**: OnePuls and your agents spend your AI balance, checked before each call; a guest never
  calls an AI; your own AI by MCP runs on its provider.
- **Scripts (Code Mode)**: the builder's script runs on our side in an isolate with no network; it
  reaches data only through the same doors as a page, as the person who pressed the button.
- **Writing outside** (Ф5): only a script writes into a service, only what the description declares
  (`outside`: the service, a create or update tool that is not «Never» there, the argument names), and
  only through PulsOne's connector, which holds the key: the page, the isolate and the builder never see
  it. From a button or an AI it is a proposal; from your rule, the right on the page decides; a rule
  fired by another service's data (a letter, an event) only proposes.
- **Bringing data over** (Ф5): the server reads the service page by page and maps each item into a
  collection by the description's map (`imports`); no AI reads your items, it costs no AI balance. A
  service's text lands as text in a record and is never run or obeyed. Each record remembers the item's
  own id, so a second press adds only what is new. Reading needs «Allowed» on the service's page.

## What OnePuls can do here

- records in the person's Мастерская tools (as their participant; a write waits for «да» unless it writes by itself) (tool.record.put, tool.record.remove, tool.template.propose, tool.workspace.add, tool.star)
