Writebacks Are Files

Overview

In a relayfile mount, the agent does not call a provider API to mutate state. It writes a file. The mount daemon picks up the change, validates the payload against the canonical schema, signs and delivers the request to the provider, and records the result. Auth, retries, idempotency, dead-lettering, and the audit trail are handled on the other side.

When to use this skill

• The user asks the agent to take an action against a provider (comment, message, create, update, close, react, …).
• You see a writable path under <mount>/<provider>/… and want to know what shape the file should be.
• A previous write didn't seem to take effect and you need to find out why.
• You're about to call a provider SDK directly — stop and check if relayfile already exposes a writeback for that mutation.

The contract in one sentence

Drop a JSON file at the canonical writeback path; the provider receives the corresponding mutation within ~30 seconds.

Find the canonical path