tenant-engine/.custodian-brief.md
custodian-sync dbd0b8b17c chore(consistency): sync task status from DB [auto]
Updated by fix-consistency on 2026-07-23:
  - update .custodian-brief.md for tenant-engine
2026-07-23 21:56:27 +02:00

28 lines
1 KiB
Markdown

<!-- custodian-brief: generated by fix-consistency — do not edit manually -->
# Custodian Brief — tenant-engine
**Domain:** infotech
**Last synced:** 2026-07-23 19:56 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams
### Service skeleton, domain model, and the three boundary-contract APIs
Progress: 0/7 done | workplan_id: `f2fcafb4-edef-4e8e-9401-d781b4d0c585`
**Open tasks:**
- · Task: Service skeleton `d22b0ce8`
- · Task: Domain model — tenant, grouping, capability role, plan grant `cfceea30`
- · Task: Storage layer `ade9374a`
- · Task: Cache-read API (for key-cape) `425cab98`
- · Task: Live-lookup API (for flex-auth) — fail closed `2a04ce4c`
- · Task: Write API — grant, revoke, assign-plan `3a2d1ee7`
- · Task: Closure review `eecf4bc8`
---
## MCP Orientation (when available)
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.