Docs

Your first Procedure

Write one useful Procedure with your AI, share it, get it approved, and run it.

Last verified: 2026-09-28

This tutorial walks a Member through creating, repairing, sharing, and running one useful CompanyOS Procedure. Owners approve the Share Request that makes it Workspace-wide, and can author Company content directly.

Finish the Quickstart first so your AI Client can read real Workspace knowledge while you write.

What you are building

A CompanyOS Procedure is a Workspace-wide internal instruction record. It tells an AI Client how to produce a repeatable output for Members using visible knowledge and the client’s own tools. It is not a template. It gives input guidance and output rules. It does not embed a tool script, execute actions on your behalf, or rewrite source files.

You will:

  1. Use the seeded System Procedure Create a Procedure.
  2. Declare Required Inputs (and fix any Missing Requirements).
  3. Store the content as your Personal draft with store_procedure.
  4. Share it and let an Owner approve the Share Request.
  5. Complete a first run of the published Procedure.

Before you start

  • You are a Member of the Workspace. Every Member authors Personal Procedures; an Owner approves sharing and edits Company content.
  • The Quickstart is done: at least one ready file, one connected AI Client, and one grounded answer.
  • Your AI Client is connected to the Workspace.

Step 1 — Start from the System Procedure

CompanyOS seeds protected System Procedures into every Workspace. They are published by default and cannot be archived, deleted, or edited by Members or Owners.

  1. In your AI Client, open or search for the System Procedure Create a Procedure.
  2. Follow its guidance conversationally. Tell it what repeated work you want to capture (for example, a weekly status update, interview prep brief, or launch checklist).
  3. Prefer a task your team already repeats. The goal is one useful workflow, not a perfect catalog.

The System Procedure teaches the AI Client to gather requirements, shape output rules, and store the content with store_procedure.

Step 2 — Declare Required Inputs and repair gaps

A Required Input is information the Procedure must have before an AI Client may produce the output. Attach Input Source Hints when useful (Member in chat, a CompanyOS Knowledge Tool, or a connected read-only provider).

  1. Review the content stored by store_procedure.
  2. List every Required Input explicitly—do not leave “implied” inputs.
  3. If the content has a Missing Requirement, store_procedure returns the gap with repair guidance, and the web app shows the same gap.
  4. Repair it by asking the AI Client to store the content again, until every Required Input and the output structure are complete. The web app does not edit content; its Edit button gives you a prompt to paste into your AI Client.

A Template can shape a repeated Member-facing output. Linking one is optional for this first tutorial; you can share a standalone Procedure. The Procedure stays the instruction. The Template stays the shape.

Step 3 — Store your Personal draft

store_procedure creates or updates your content. A new slug becomes a Personal draft owned by you; only your own AI Client sees it.

  1. Store the Procedure with slug, title, description, and markdown.
  2. Review the returned scope (personal), state (draft), and link.
  3. Follow the link to review the draft as a human: tone, Required Inputs, output rules, and any linked Template.
  4. Confirm nothing sensitive or incorrect would reach the Workspace when shared.

Step 4 — Share and get Owner approval

Sharing moves your Personal content into the Workspace; only an Owner approves or rejects it.

  1. Set share: true when storing, or choose Share on your draft in the web app. The request carries every Personal Template the Procedure links.
  2. An Owner opens the Approvals section, sees you as the requester with the shared Templates, and approves or rejects.
  3. Approval moves the content to Company scope and publishes it; rejection returns it to your Personal draft for repair.

Owners skip the queue for their own content: an Owner’s share request is approved in the same request, and Owners update Company content directly from their AI Client.

Step 5 — First run

  1. In any Member’s connected AI Client, discover the published Procedure with find_procedures and read it in full with use_procedure.
  2. Supply every Required Input when asked. The AI Client should refuse to produce the final output until Required Inputs are satisfied.
  3. Let the client use visible Workspace knowledge and its own tools to produce the output according to the Procedure’s rules.
  4. Check the result once end-to-end. That first run is the proof the workflow is real.

Member path: run a published Procedure

Members run published Company content and keep their own Personal Procedures:

  1. Connect an AI Client if you have not already (Quickstart).
  2. Ask to run the named CompanyOS Procedure, or call find_procedures to list visible Procedures.
  3. Provide Required Inputs and review the grounded output.

What not to expect

  • Procedures do not silently send email, mutate Integrations, or rewrite Company Files.
  • System Procedures stay CompanyOS-managed; do not try to edit Create a Procedure or Create a Template.
  • Another Member’s Personal content stays private to that Member, including from Owners, until it is shared.
  • To run the Procedure on a schedule and email the result, see Scheduled Procedures.