Module write_attribution
Expand description
Which of an app’s own live invocations its next writes belong to.
An agent has no filesystem access of its own: it invokes an app’s action, and the app writes through the workspace mount, so the version is signed for the device’s person. Before writing for an invocation, the app names the paths it is about to write and the invocation they are for, over the same lane the local clipboard uses. The host resolves the invocation against its own custody of that app’s live invocations and takes the actor from there; nothing in this envelope names who acted. When that actor is an agent acting for the session’s person, the filesystem records it beside those versions. It grants nothing, and a refusal never stops the write.
Structs§
- Request
- The absolute paths an app is about to write for the invocation it sends this under. A folder covers what is under it.
Constants§
- MAX_
PATHS - Most paths one request names.
- MAX_
PATH_ BYTES - Longest path a request names, in bytes.
- MAX_
WIRE_ BYTES - Largest encoded request.
- PROTOCOL
- Purpose-separated envelope identifier.
Functions§
- decode
- Decode and validate an envelope.
- is_
envelope - Whether
bytesis a write attribution envelope rather than another command of the same lane.