---
id: TEN-WP-0001
type: workplan
title: "Bootstrap State Hub integration"
domain: infotech
repo: tenant-engine
status: finished
owner: codex
topic_slug: netkingdom
created: "2026-07-23"
updated: "2026-07-23"
state_hub_workstream_id: "c9f8ca93-f9df-4ad7-b48f-16915874a341"
---

# Bootstrap State Hub integration

Canonical owner of tenant-as-an-entity facts for NetKingdom: existence, onboarding grouping, capability roles, and plan/subscription assignment.

## Review Generated Integration Files

```task
id: TEN-WP-0001-T01
status: done
priority: high
state_hub_task_id: "00827f3d-4089-4cab-a5d1-11d6980debf7"
```

Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`.
Replace generated placeholders with repo-specific facts where needed.

**Done 2026-07-23:** `INTENT.md` and `SCOPE.md` rewritten from the generated
stub into the full Purpose/Responsibility-Boundary/Non-Goals shape matching
the ratified `net-kingdom/canon/standards/tenant-engine-boundary-contract_v0.1.md`
(Ownership Model + Source-of-Truth Matrix condensed into this repo's own
docs, not duplicated wholesale). `topic_slug` corrected from the
auto-assigned `custodian` default to `netkingdom`, matching `key-cape` and
`user-engine`'s convention. `.claude/rules/{repo-identity,architecture,repo-boundary,stack-and-commands}.md`
placeholders filled in (copied from `repo-seed`, the fleet's bootstrap
template). `AGENTS.md`/`.custodian-brief.md` left as generated — both carry
an explicit "state-hub template sync" marker meaning they're managed by
`fix-consistency`, not hand-edited.

## Verify Local Developer Workflow

```task
id: TEN-WP-0001-T02
status: done
priority: high
state_hub_task_id: "edcdce43-e804-424d-8215-7648926c7680"
```

Identify the repo's install, test, lint, build, and run commands. Add or refine
those commands in the agent instructions so future coding sessions can verify
changes confidently.

**Done 2026-07-23:** Stack decided — Python 3.12 + FastAPI, matching
`qonto-assistant`'s fleet convention for small headless services (this repo
plays a structurally similar role: a narrow, security-adjacent API a couple
of other services call synchronously). `make install-dev`/`test`/`lint`/`run`
commands documented in `.claude/rules/stack-and-commands.md` ahead of the
actual `Makefile`/`pyproject.toml`, which land in `TEN-WP-0002`.

## Seed First Real Workplan

```task
id: TEN-WP-0001-T03
status: done
priority: medium
state_hub_task_id: "3f4482ab-52dc-4582-b52b-d2b0ae1e9a61"
```

Create the first implementation workplan for the repository's most important
next change. After workplan file updates, run the sync locally from this repo
checkout:

```bash
statehub fix-consistency
```

**Done 2026-07-23:** `TEN-WP-0002-domain-model-and-scaffold.md` created —
service skeleton, domain model (tenant/grouping/role/plan-grant), and the
cache-read + live-lookup APIs per the boundary contract. Registered via
`statehub fix-consistency`.