> ## Documentation Index > Fetch the complete documentation index at: https://docs.holos.io/llms.txt > Use this file to discover all available pages before exploring further. # Procedures > Author, corroborate, and publish the canonical step sequences your team performs by. A **Procedure** is a canonical step sequence: the how-to document your team performs by. Each new capture either corroborates its steps or raises a proposal for you to review, so the written procedure and the way the work is actually done converge over time. Every procedure gets a short ID (`PRC-107`) that appears in lists, breadcrumbs, and URLs. Renaming a procedure never breaks its links; the ID is what resolves. Procedures stand on their own. Filing one under a [skill](/dashboard/skills) is optional, and the same procedure can be linked into any number of [guidebooks](/dashboard/guidebooks). The guidebook only points at it; the procedure owns all of its content. ## Creating a procedure There are three ways to create one: 1. **From the [Procedures](https://app.holos.io/procedures) list**: click **New procedure**, name it, and it opens ready for authoring. You can link it to guidebooks and add steps after. 2. **From a skill page**: the skill's **Procedures** section offers **From a capture** (seeds the steps from the capture's extracted sequence) or **Write it by hand**. 3. **Extracted from a document**: right-click a PDF in a guidebook's References card and choose **Extract procedure**. A draft is generated from the document, steps, callouts, and outline structure included. See [Guidebooks](/dashboard/guidebooks#extracting-a-procedure-from-a-document). A procedure can be written before anything is recorded; authoring doesn't wait on a capture to seed it. ## The procedures list The list at [**Procedures**](https://app.holos.io/procedures) shows every procedure in the organization: short ID, title, its skill (if filed), and a `{n} steps · {n} captures` summary. Search matches titles and short IDs, so a pasted `PRC-107` lands on the row. The **All** / **Needs review** toggle filters to procedures with open proposals; the Needs review badge counts pending proposals across the org. ## Description The **Description** is the how-to prose: context, safety framing, prerequisites, and any diagrams or media. It's a full rich-text editor, and images pasted or dropped in belong to the procedure itself. ## Steps Steps are the heart of a procedure. Each step has a **title**, an optional **description**, and a kind: | Kind | Renders as | | - | - | | **Step** | A numbered step | | **Info** | A blue callout banner | | **Caution** | A yellow callout banner | | **Warning** | An orange callout banner | | **Danger** | A red callout banner | Callouts sit in the sequence but don't consume a step number, so safety notices can be placed exactly where they matter without renumbering the work. Steps can be nested up to five levels deep with **Indent** / **Outdent**, reordered by dragging, and managed from a right-click context menu (**Add step above**, **Add step below**, **Edit step**, **Delete step**). Deleting a step offers an **Undo**. Step text supports limited inline markdown: `**bold**`, `*italic*`, `__underline__`, and links. How nested steps are numbered is an organization-wide setting (**Settings → Procedure numbering**): **Outline** (`1. → a) → i)`, the default), **Decimal** (`1 → 1.1 → 1.1.1`), or **Plain** (flat `1. 2. 3.`). ### Sources When a capture corroborates a step, the step gains a citation chip (`{capture} · 3:42`). Hovering previews the video frame at that timecode; clicking opens the capture viewer at that moment. Hand-written steps simply have no chip yet. Steps added or edited since the last publish carry a small `NEW` or `EDITED` marker so you can see what has drifted from the published standard. Publishing clears the markers. ## 3D guide Link a 3D object to a procedure and the page splits in two: the model on the left, the steps on the right. Selecting a step shows you where it happens on the model. ### Linking an object Use the object button in the procedure header to link an object. If the procedure's guidebook already tracks one, it is offered first. The same menu opens the object, links a different one in its place, or unlinks it. ### Component tags A step points at the model through its **component tags**. On a CAD model, a tag such as `CB1` or `TB1:7` matches the part with that name, and selecting the step outlines the part. Tags are edited in the step editor, with suggestions drawn from the model's part names and from the step's own text. A tag that matches nothing in the model is listed as not in this model. That is a normal state: the model may trail the document, or the object may have been swapped. ### Selecting a step Selecting a step highlights its parts and points, and the camera eases to the angle they are best seen from. For a point that is head-on to its surface; for parts it is the side nothing else on the model blocks. The camera never goes below the floor. * Click the step again to deselect it and return to the default view. * Click empty space around the model to deselect the step and leave the camera where it is. * The selected step is kept in the page's address, so a refresh or a shared link opens on that step. ### Points A 3D scan has no named parts to tag: the whole model is one mesh. **Points** fill that gap. A point is a named spot you place on the model's surface, and its name works exactly like a component tag: add it to a step and selecting the step shows the point. A step can mix part tags and points freely. To place a point: 1. Click **Add point** in the top-right corner of the 3D guide (or **+** beside **Points** once the object has some). You can also click **place a new point** in a step's tag field while editing the step. 2. Click the model where the point goes. 3. Name it and click **Save**. If a step was selected, or you started from a step's editor, the point is linked to that step and added to its tags. Otherwise it is placed unlinked, and you can link it to a step later. A point cannot share a name with a part in the model. ### The Points list **Points** in the top-right corner lists every point on the object, alphabetically, with how many steps use each one (or **unused**). Each row can: * **Link** the point to the selected step, or unlink it * **Rename** it: the tag is renamed on every step that uses it * **Delete** it: if steps use the point, you are asked first, and the point is removed from those steps too Clicking a pin on the model selects it and opens the list at its row. With no step selected, selecting a point moves the camera to it. Drag a pin along the surface to move it. ### Reading the model Pins keep the same size on screen however far you zoom. * A pin on the selected step is orange and shows its name. When a step uses several points, they are numbered in the order the step lists them. * Other pins are small white dots; hover one to see its name. * A pin on a surface facing away from you is dimmed. * A pin hidden behind the model is not shown, unless it is on the selected step, in which case it stays faintly visible so you know it is round the back. ### When the model changes Points stay on their feature when the object's model is later rotated, rescaled or re-centered: the dashboard records each of those changes and moves the points with the model, in the draft and in published versions alike. If the model is re-converted from its original upload, points placed before that may no longer sit on their feature, and the guide says so. Check them and drag any that moved. ### Versions Publishing freezes the points along with the steps, so a published version always shows its points where they were when it was published. Moving or renaming a point marks the draft as having unpublished changes. ## Captures and proposals Use **Link capture** to attach a recorded session. Its extracted steps are compared against the sequence: where they agree, the capture is added as a source on those steps; where they differ, each difference comes back as a **proposal** (add a step, reword a step, or remove a step) with the capture's rationale and a citation. You **Accept** or **Dismiss** each proposal individually; a dismissed proposal won't be raised by that capture again. **Check for changes** re-runs this alignment against every linked capture at any time. ## Publishing and versions The page you edit is always the **draft**. Clicking **Publish** snapshots the current sequence as an immutable revision (`v1`, `v2`, …), optionally with a version note, and further edits open on a new draft. The version chip in the header shows the latest published revision, or **Draft** if nothing has been published yet; a dot beside it means the draft has unpublished changes. Clicking the chip opens **Revision history**, where each revision lists who published it, when, its note, and its step and change counts. Opening a revision shows the sequence exactly as published, along with **Changes in this version**, the edit history that led to that publish. Snapshots are immutable; there is no unpublish, only publishing the next version. Procedures extracted from a document also show **External history**: the source document's own revision table, read-only, as written. ## Activity The **Activity** feed records everything as readable sentences: steps moved or reworded, captures linked, checks run, and where an extracted draft came from. Publishes appear as dividers (`{Name} published v3`), splitting the feed into per-version chapters. ## Deleting **Delete** on the procedure page permanently deletes the procedure and removes it from any guidebooks. Linked captures and their extracted steps are not affected, and published versions stay available for audit. You must type the procedure's short ID to confirm. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.