Expand description
P1 syscall requests and their causation (spec §7.6).
A syscall is not a sixth wire input class. It reaches the kernel one of exactly two ways, and in both the caller is derived from kernel-owned state rather than declared by the host:
- the current operation’s provider tool call — recognised while resolving the provider effect;
- a child’s request, attached to its
ChildCompletedfact — the parent kernel derives the caller from the attempt.
There is no AgentRequest { actor_id }, and no SDK-side path that fills an actor in.
Structs§
- Activate
Skill Request - Append
Workflow Nodes Request - Child
Attempt Causation - Memory
Query Proposal - Memory
Write Proposal - A proposal, not a record. It carries no tenant/namespace, no record id, no author or trust level, no timestamp and no session provenance: the kernel derives all of those from the operation’s memory binding, the envelope’s accepted time and the syscall causation.
- Page
InRequest - Provider
Tool Causation - Publish
Channel Request - Read
Object Request - Receive
Channel Request - Receive
Mailbox Request - Request
Memory Query Request - Request
Memory Write Request - Send
Message Request - Submit
Workflow Request - Update
Task Request
Enums§
- Memory
Kind - Syscall
Causation - How the kernel derived the caller of a syscall. Never host-supplied.
- Syscall
Request