activity-core/.custodian-brief.md

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — activity-core

**Domain:** custodian  
**Last synced:** 2026-05-14 15:49 UTC  
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*

## Active Workstreams

### activity-core WP-0003 — Event Bridge Implementation
Progress: 0/24 done  |  workstream_id: `b4eb45a9-69e3-4ab0-b00c-67a53c3117c5`

**Open tasks:**
- · [repo:activity-core] T34: Refactor ActivityDefinition model — add rules/instructions fields  `ca1bf66f`
- · [repo:activity-core] T35: Create src/activity_core/rules/ module skeleton  `54c25eae`
- · [repo:activity-core] T36: Implement RuleEvaluator (sandboxed AST walker)  `a1ed0d8b`
- · [repo:activity-core] T37: Implement InstructionExecutor  `cdd349f1`
- · [repo:activity-core] T38: Alembic migration — add task_spawn_log table  `4cd9833c`
- · [repo:activity-core] T39: Implement IssueSink adapter interface and IssucCoreRestSink  `38177fcf`
- · [repo:activity-core] T40: Formalize EventEnvelope model  `65d77939`
- … and 17 more open tasks

---
## MCP Orientation (when available)

If the state-hub MCP server is reachable, call:
`get_domain_summary("custodian")`
This provides richer cross-domain context.
If the MCP call fails, use this file as your orientation source.