# CT.M3 — ContentReferenceAndBundleWorkflows

## Summary

| Field | Value |
|--------|--------|
| **Module ID** | CT.M3 |
| **Track** | [Content tooling — internal authoring](../tooling/internal_authoring.md) (cross-cutting; not E1–E9) |
| **Stage target** | Pre-production |
| **Status** | Planned (see [dependency register](module_dependency_register.md)) |

## Purpose

**Workflow depth** after the MVP studio: project-wide **reference graph**, safer **renames**, **schema version** warnings across files, and optional **content bundle** manifests to reduce client/server drift.

## Responsibilities

- Build an index of IDs and references across `content/**` for find-usages and rename planning.
- Emit optional **hash/version manifest** for CI and deploy pipelines (aligns with tech stack bundle note).
- Document operational practices (PR review for content, bundle promotion).

## Key contracts

| Contract | Role |
|----------|------|
| `ContentBundleManifest` (optional) | Lists files, schema versions, content hashes |
| Reference report | Machine-readable graph for CI or review tools |

## Module dependencies

- **CT.M1** — ContentValidationPipeline
- **CT.M2** — AuthoringStudioApplication (recommended for integrated UX)

## Dependents (by design)

- None within the CT track; ops/deploy may consume manifests.

## Related implementation slices

Content tooling **Slice 3** — reference index and optional bundles.

## Source anchors

- Plan: [`internal-content-authoring.md`](../../plans/internal-content-authoring.md)
- [Module dependency register](module_dependency_register.md)
