---
id: CUST-WP-0000c
type: workplan
title: "Repo Integration: activity-core (DB-first bootstrap)"
domain: infotech
repo: the-custodian
status: archived
owner: custodian
topic_slug: custodian
created: "2026-03-02"
updated: "2026-03-11"
state_hub_workstream_id: "b802bcf5-da82-4778-a2d8-fec2b02d877e"
note: >
  Pre-ADR-001 DB-first onboarding workstream created when activity-core was
  registered. Superseded by repo-owned workplans in activity-core
  (custodian-WP-0001, custodian-WP-0002, and successors). Retroactive record
  to satisfy ADR-001 consistency checker (C-08).
---

> **Terminology note:** Historical text in this archived workplan may use the legacy term "workstream". The fleet term is **workplan** (`canon/standards/workplan-terminology-fleet_v0.1.md`).

# CUST-WP-0000c — Repo Integration: activity-core

Bootstrapping workstream for `activity-core` registration. Work continues in
`~/activity-core/workplans/` (e.g. `custodian-WP-0001-temporal-backbone.md`,
`custodian-WP-0002-triggers-ops.md`).

## Integrate CLAUDE.custodian.md → CLAUDE.md

```task
id: CUST-WP-0000c-T01
status: done
priority: high
state_hub_task_id: "f0d2ad65-c8ed-4f36-bb48-ca4b6b033439"
```

## Write first workplan and initialise workplans/

```task
id: CUST-WP-0000c-T02
status: done
priority: high
state_hub_task_id: "77276b8b-fff3-474b-ab27-bd99f1f1a54c"
```

Produced `custodian-WP-0001-temporal-backbone.md` and
`custodian-WP-0002-triggers-ops.md` in activity-core.

## Ingest SBOM

```task
id: CUST-WP-0000c-T03
status: cancel
priority: medium
state_hub_task_id: "cbca1200-26c2-43e7-a92f-97fc2e53a27b"
```

## Register known EPs and TDs

```task
id: CUST-WP-0000c-T04
status: cancel
priority: low
state_hub_task_id: "d53e1c7f-acea-458b-b6c2-0ce384fa946e"
```