← 101CONTENT HISTORY

Update to 101

Snapshot Nov 9, 2026 · 00:21 UTC · version 2.0.5

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save 101 and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when an internal 101 write workflow must check the current tool schema, required data, entity references, mutable state and central policy before one API mutation.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 43
    }
  ],
  "name": "write-preflight",
  "skill_md_contents": "---\nname: write-preflight\ndescription: Use when an internal 101 write workflow must check the current tool schema, required data, entity references, mutable state and central policy before one API mutation.\nversion: \"1.0.0\"\nrole: helper\ninvocation: internal\nintents:\n  - writes.preflight\ndepends_on:\n  - entity-resolution\nrequired_tools:\n  - whoami\noptional_tools:\n  - get_project_summary\n  - list_projects\n  - get_task\n  - get_event\n  - get_company\n  - get_price_list\nresources:\n  - path: ../shared-resources/context-and-identity.md\n    kind: semantic-guide\n    required: true\n  - path: ../shared-resources/safety-and-permissions.md\n    kind: semantic-guide\n    required: true\n  - path: ../shared-resources/events-and-positions.md\n    kind: semantic-guide\n    required: true\ncompletion:\n  statuses:\n    - готово\n    - частично\n    - заблокировано\n---\n\n# Preflight Before a Write\n\nInput: the user's explicit action, command, selected entities, proposed fields and original state. Output: valid arguments for one command or a specific blocker. This instruction does not itself authorize a write.\n\n1. Read the current command schema: field names, types, required fields and constraints. Use the original API format.\n2. Verify the explicit intent to perform this exact write and that its material parameters are unambiguous. If a material choice remains, return the missing distinction to the goal owner before invoking the write. Reading, a recommendation and an attachment do not replace write intent.\n3. Check entity access through `entity-resolution`. Pass the resolved company in the field the command accepts: `company_guid` or `companyGuid`. Do not ask again for an already known company.\n4. Reread the mutable object and available permissions immediately before writing. For an event in a selected project, check `permissions.canCreateTransaction` through `get_project_summary`. A company-fund-only event does not require an invented project; the relevant command checks its permissions. For `isSelectionOnly=true`, use permissions from the `list_projects` row: code `5036` when reading the summary does not itself prohibit the first event. Role and balance do not prove write permission.\n5. If the command replaces a full list, preserve unchanged elements and compare the current state with the original. Stop on a conflict.\n6. Follow the standard server confirmation procedure. Do not invent tokens, confirm for the user or add a parallel procedure. Do not invoke app-only commands from ordinary conversation.\n7. After writing, verify the result. If the response is lost, establish the actual state first; retry only with proven idempotency or proof that the operation did not execute.\n\nFor events, use the [result and recovery rules](../shared-resources/events-and-positions.md). Return the command, arguments, fresh facts and readiness basis to the primary workflow. Do not guess a missing required part.\n"
}

SHA-256 of public snapshot: c50108c02007ac0a14fb9cfeacfb3a1ad80f3f7afacc84f9feeb06230c2d2782