# Future TranscriptX integration seam

Transcribe does **not** depend on TranscriptX and must not be integrated into TranscriptX before its 1.0 release.

## Handoff

```text
transcribe.notebook JSON
        ↓
future pure adapter (post–TranscriptX 1.0)
        ↓
whatever TranscriptX's post-1.0 document/import contract requires
```

Portable export rules: [contracts/notebook-export.md](contracts/notebook-export.md).

## Non-goals for this seam document

- Do **not** lock synthetic timestamps (e.g. page `i` → `[i, i+1)`).
- Do **not** lock fake speaker labels (e.g. `PAGE` / `NOTEBOOK`).
- Those may be *one* future compatibility strategy among others, but synthetic timing/speakers can leak into timing-, interaction-, or speaker-based analysis as plausible nonsense.

## What Transcribe guarantees (export)

- Portable `format: "transcribe.notebook"` interchange with page order, effective/raw/edited text, content fingerprints, provenance, and notebook `content_revision` when present
- No required absolute filesystem paths in the export
- Page-first domain (not timed speaker segments)
- Organisation tags as `tags: string[]` slugs on notebook and page, plus an optional `tag_catalog` snapshot (`personal_corpus.tag-catalog` defs) so labels/colours survive interchange

## Organisation tags (shared with TranscriptX Theme F)

Both products should use the same catalog envelope and slug rules: [contracts/tag-catalog.md](contracts/tag-catalog.md).

- Transcribe notebook tags → future TX **library** (transcript) tags
- Transcribe page tags stay page-scoped (do not invent fake speakers or timestamps to carry them)
- TX must not treat tags as Group membership
- Copy `src/transcribe/tagging/kernel.py` and `colors.py` (relative imports); do not share a runtime package before TX 1.0

## Reverse import (Transcribe 1.6 — not shipped)

After **Transcribe 1.0**, ROADMAP **1.6** may import TranscriptX **export files** (transcript + optional audio + summary + speaker strings) as contextual evidence around notebooks. That is a file adapter, not a runtime dependency either way, and it does **not** replace this export seam.

```text
TranscriptX export bundle (files)
        ↓
future Transcribe context-import adapter (1.6)
        ↓
ContextCollection / ContextRecord (evidence around notebook pages)
```

Do not call TranscriptX APIs. Do not re-run ASR. Do not port speaker/audio analysis modules. Pin the TX export contract when TX 1.0 exists; a frozen fixture is allowed if that contract is late. Sequencing: [ROADMAP.md](ROADMAP.md) After 1.0 § 1.6.

## Related

- Product boundaries: [PRODUCT.md](PRODUCT.md)
- Analysis port planning: [ROADMAP.md](ROADMAP.md) · [analysis_module_porting.md](dev/analysis_module_porting.md) · [analysis_wave1_plan.md](archive/plans/analysis_wave1_plan.md)
- Post-1.0 autobiography (includes 1.6 TX file import): [ROADMAP.md](ROADMAP.md) **After 1.0**

Note: analysis ports use a **canonical `AnalysisDocument`** inside Transcribe ([contracts/analysis-document.md](contracts/analysis-document.md)). That is separate from this future *export* handoff into TranscriptX, and from 1.6 context import the other way.