# Proposal: Legacy Import

## Intent

Import valuable material from `agentic-semantic-web/` (legacy repo) into the restructured `asw/` repo. The legacy repo was the standalone single-file version of ASW. It contains packs, templates, examples, lab experiments, error pages, and documentation that belong in the current repo.

**Goal: everything worth keeping lives in `asw/`. Legacy repo is archived.**

## Scope

### Triage Categories

Material from `agentic-semantic-web/` falls into:

**Import as-is:**
- `packs/apache/` → `packs/apache/`
- `packs/caddy/` → `packs/caddy/`
- `packs/flask/` → `packs/flask/`
- `packs/nginx/` → `packs/nginx/`
- `packs/pandoc/` → `packs/pandoc/`
- `packs/python/` → `packs/python/`
- `packs/hugo/` → `packs/hugo/` (base Hugo pack)
- `errors/` → `packs/` (distributed to relevant packs, or shared errors dir)
- `LICENSE`

**Import and adapt:**
- `examples/` → `examples/` (update CSS paths to `dist/asw.css`)
- `templates/` → review, merge into packs or docs
- `llms.txt` → `docs/llms.txt` (update for current state)
- `content/vocabulary.md` → `docs/vocabulary.md`
- `content/philosophy.md` → `docs/` (may already exist)
- `content/agent-directive.md` → `docs/` or merge into existing docs
- `themes/` → `src/themes/` or `examples/themes/` (needs decision)

**Import as reference/lineage:**
- `openspec/changes/pico-absorption/` → content for `docs/lineage.md`
- `content/architecture.md`, `content/design-tokens.md` → inform specs, don't import verbatim
- `MISSION_REPORT.md`, `SIZE_AUDIT.md` → historical, extract lessons into lineage

**Do not import:**
- `dist/agentic.css` — superseded by `dist/asw.css`
- `agentic.css` (root) — old entry point
- `src/layers/` — superseded by current `src/layers/`
- `build.sh`, `migrate-tokens.sh` — legacy build tools
- `web-fonts.css` — evaluate if still needed
- `lib/open-props/` — replaced by `vendor/open-props/`
- `lab/hugo-demo/` — superseded by `site/`
- `.pi/` — agent config, not framework material
- `index.html` — legacy landing page

**Needs triage decision:**
- `lab/` (non-Hugo) — some experiments may be worth keeping in `src/lab/`
- `docs/missions/` — historical mission reports, lineage value?
- `content/charts-css-exploration.md` — inform charts spec?
- `content/architecture-research.md` — inform design decisions?

### Out of Scope
- Modifying imported CSS (that's the css-refactor change)
- Creating new content
- Archiving the legacy repo (separate operational task)

## Prerequisites

- **Depends on:** `repo-restructure` (directories must exist first)

## Approach

1. Triage: review each directory/file, confirm category
2. Import packs (bulk, low risk)
3. Import examples (need path updates)
4. Import docs (need review/merge)
5. Write `docs/lineage.md` from pico-absorption and historical material
6. Final audit: nothing valuable left behind

## Risks

- **Stale content** — legacy material references `agentic.css`, old paths, old URLs. All imported material needs path/name updates.
- **Duplication** — some legacy content already exists in ASW in evolved form. Need careful merge, not overwrite.