Living Document Notice
Published 2026-09-17. The evolving architecture, revisions, and connected notes for this dispatch live in the Stax Digital Garden.
Cross-Realm Delegation Semantics
Summary
Project management tools fail when tasks become detached from the human beings responsible for their completion. Yeoman provides explicit cross-realm graph predicates that allow task engines to delegate action items directly to sovereign contact URNs.
The Disconnect Between Tasks and People
In conventional project management suites, tasks exist in an isolated silo from contact directories. When a task is marked as ‘delegated’, it frequently dissolves into a vague text string (Assignee: Bob), losing all connection to Bob’s preferred communication channels, working cadence, or outstanding commitments.
In the Bosun architecture, task tracking lives in Realm 03 (Trice), while identity lives in Realm 02 (Yeoman). Tasks establish cryptographically typed bindings to human agents using standardized graph relation predicates.
+-------------------------------------------------------------+
| Cross-Realm Task Delegation Model |
| |
| +--------------------------+ |
| | Trice Task: TRC-2041 | |
| | "Review Columnar Engine" | |
| +--------------------------+ |
| │ │ |
| [assignedToContact] │ [waitingOnContact] |
| │ ▼ |
| │ +-------------------------+ |
| │ | Yeoman Contact: Charles | |
| │ | (Reviewing Codebase) | |
| ▼ +-------------------------+ |
| +-------------------------+ |
| | Yeoman Contact: Ada | |
| | (Primary Author) | |
| +-------------------------+ |
+-------------------------------------------------------------+
Canonical Delegation Predicates
The Bosun Spec relations engine defines three universal delegation predicates:
assignedToContact: Declares the primary human executor responsible for driving a deliverable to completion.waitingOnContact: Designates a blocking dependency where forward progress is halted pending input, review, or approval from a specific individual.consultedProvider: Binds an advisory or clinical professional whose expert opinion informs the task’s execution.
Markdown Frontmatter Implementation
A Trice task delegates authority by referencing the Yeoman contact URN inside its $pkm.relations block:
---
title: "TRC-2041: Columnar Compression Benchmark"
status: blocked
$pkm:
id: "urn:uuid:0191fa30-3001-7000-8000-000000000041"
realm: trice
relations:
assignedToContact: "urn:yeoman:contact:0191fa30-1001-7000-8000-000000000001"
waitingOnContact: "urn:yeoman:contact:0191fa30-1002-7000-8000-000000000002"
---Graph Inversion: The 1-on-1 Agenda Generator
Because relationships are indexed as bidirectional graph triples, a contact dossier can effortlessly query all tasks currently blocked on that individual. Before entering a 1-on-1 meeting with Charles Babbage, Yeoman evaluates:
SELECT task.title, task.status
FROM tasks task
JOIN relations rel ON rel.source_id = task.id
WHERE rel.predicate = 'waitingOnContact'
AND rel.target_urn = 'urn:yeoman:contact:0191fa30-1002-7000-8000-000000000002';This dynamically generates an agenda of items requiring Charles’s input, eliminating preparation overhead and preventing dropped commitments.
- Directus Target: yeoman
- Garden Source Reference: MOC - Bosun PKM Tools, MOC - Fleet Operations
- Garden Source Reference: [YMN-1006 - Cross-Realm Delegation Semantics](YMN-1006 - Cross-Realm Delegation Semantics)