chore(consistency): sync task status from DB [auto]

Updated by fix-consistency on 2026-08-16:
  - update .custodian-brief.md for prj-canon-federation
This commit is contained in:
custodian-sync 2026-08-16 02:42:29 +02:00
parent ab6f2d8ea3
commit 8b559ef999

View file

@ -1,27 +1,29 @@
<!-- custodian-brief: generated by statehub register; fix-consistency may replace this file -->
# Custodian Brief - prj-canon-federation
<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief prj-canon-federation
**Project:** prj-canon-federation
**Domain:** infotech
**State Hub:** http://127.0.0.1:8000
**Topic ID:** `cee7bedf-2b48-46ef-8601-006474f2ad7a`
**Domain:** infotech
**Last synced:** 2026-08-16 00:42 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Open Workplans
## Active Workstreams
### Bootstrap State Hub integration
### Canon federation foundation: boundary, rename, and model placement
Progress: 0/10 done | workplan_id: `7a96da54-050d-4210-96f9-0bb411aaaec8`
Workplan file: `workplans/PRJ-WP-0001-statehub-bootstrap.md`
**Open tasks:**
- ! Build the concept-ownership ledger `0ca7878c`
- ! Rename identity-canon to commerce-canon `45cd377e`
- ! Scaffold commerce-canon to the canon layout standard `743a2da9`
- ! Land the identity model in InfoTechCanon `986a0ac6`
- ! Land the counterparty model in CommerceCanon `0a29bb3e`
- ! Distribute the research corpus as provenance `776905c6`
- ! Publish cross-canon interface cards `3eee0510`
- … and 3 more open tasks
Open tasks:
- T01 - Review generated integration files
- T02 - Verify local developer workflow
- T03 - Seed first real workplan
---
## MCP Orientation (when available)
## Session Start
1. Read `GOAL.md`, `SCOPE.md`, and `AGENTS.md` (prj- flavor: `GOAL.md`, no `INTENT.md`).
2. Check inbox: `GET /messages/?to_agent=prj-canon-federation&unread_only=true`.
3. Scan `workplans/`.
4. Update task statuses in workplan files as work progresses.
Last generated: 2026-08-16
If the state-hub MCP server is reachable, call:
`get_domain_summary("infotech")`
This provides richer cross-domain context.
If the MCP call fails, use this file as your orientation source.