Read or write a writable point's priority array via the Haystack pointWrite op
domain: project-haystack.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
To inspect current control state, send a grid with just the point's id to pointWrite; the response lists all 17 priority levels with level, levelDis, val, and who
To write a value, send a grid with id, level (1-16, with level 8 requiring an explicit duration), val (or null to release that level), and optionally who to attribute the write
Use level 8 with a duration tag for a temporary override that should expire automatically
Set val to null at a given level to release that level's override and let lower-priority levels take effect again
Re-run the read form afterward to confirm which level is currently winning and what value is in effect
Known gotchas
Level 17 is the default/fallback level - writing there sets the point's baseline rather than a temporary override
Omitting who causes the server to attribute the write to the authenticated user's display name, which may not be what you want for audit trails
Only points tagged writable expose a priority array; calling pointWrite on a non-writable point fails
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?