# Phase 999.1: L5 Publication Factory - Backlog Context

**Captured:** 2026-04-04
**Status:** Backlog
**Why backlog:** important final AITP step, but it depends on finishing the
runtime simplification, projection-aware routing, and topic-family reuse
foundations first.

**Formal draft:** `research/knowledge-hub/L5_PUBLICATION_FACTORY_PROTOCOL.md`

## Idea

Add `L5` as the final AITP output layer.

`L5` is not a new scientific-truth layer.
It is the publication / communication / writing factory that consumes completed
topic results and turns them into paper-grade outputs.

The intended ordering remains:

- research truth is established through `L0 -> L1 -> L3 -> L4`
- reusable memory is promoted into `L2`
- only then should `L5` transform the finished topic into manuscript-ready
  outputs

## Core rule

`L5` may reorganize, compress, narrate, and polish.
`L5` may not invent new scientific claims, hidden evidence, or fake certainty.

If a manuscript section needs missing evidence, missing related work, missing
validation, or unresolved claim boundaries, the work should reopen the topic in
`L0-L4` rather than patch the gap inside `L5`.

## Intended inputs

- `L0` source records, citations, code references, and raw material
- `L1` scoped question, terminology, assumptions, and non-goals
- `L3` candidate evolution, method routes, rejected paths, and strategy memory
- `L4` validation results, review bundle, failure modes, and final adjudication
- `L2` promoted reusable knowledge objects when they exist
- runtime summary surfaces such as:
  - `topic_synopsis.json`
  - `topic_completion.json|md`
  - `runtime_protocol.generated.json|md`
  - `topic_skill_projection.active.json|md`

## Intended outputs

- `paper_manifest.json`
- `claim_evidence_map.json`
- `paper_outline.md`
- `figure_table_plan.md`
- `related_work_map.md`
- `limitations_and_scope.md`
- manuscript draft:
  - `manuscript.md` or `main.tex`
- optional publication helpers:
  - `abstract_variants.md`
  - `cover_letter.md`
  - `response_to_reviewers.md`
  - `supplementary.md`

## Workflow sketch

1. Freeze a completed-topic snapshot before writing starts.
2. Select publication target:
   - paper
   - thesis chapter
   - technical report
   - talk/slides
3. Extract only paper-worthy claims already supported by `L0-L4`.
4. Build a claim-to-evidence map before drafting.
5. Organize narrative:
   - motivation
   - problem
   - method
   - validation/results
   - scope limits
   - outlook
6. Generate full manuscript draft.
7. Run writing audits for:
   - overclaim
   - unsupported statements
   - missing citations
   - scope drift
8. If audit fails, reopen topic work outside `L5`.

## Why this matters

The user wants AITP to end not only in validated topic completion but also in
a complete paper-production layer.

That means the final mature AITP vision becomes:

- `L0-L4`: do the research honestly
- `L2`: preserve reusable knowledge
- `L5`: turn completed research into polished publication outputs

## Dependencies before promotion from backlog

- Phase 16 should thin `L1` and bundle `L4` review outputs.
- Phase 17 should prune redundant runtime views.
- Phase 18 should add bounded projection-aware routing.
- Phase 19 should stabilize topic-family reuse.

Only after those foundations are stable should `L5` become an active milestone.
