---
name: archive-application-assets
description: Archive and process company, internship, club, hackathon, competition, bootcamp, scholarship, and other activity applications from prompts, web links, images, screenshots, PDFs, documents, or Markdown in an Obsidian Application Answer Bank. Use whenever a user provides, imports, completes, submits, finalizes, revises, or asks to organize an application form or its answers; preserve source provenance and submitted answers, classify completion, deduplicate experiences, extract reusable atomic answer chunks into 13 Question Type folders, connect evidence, and update indexes, logs, and the status dashboard.
---

# Archive Application Assets

Preserve each application as a historical record and convert only verified completed content into reusable experience cards and answer chunks.

## Locate the archive

1. Read the Obsidian vault path from `%APPDATA%/obsidian/obsidian.json` when the path is not already known.
2. Locate `지원 아카이브/AGENTS.md` in the vault and read it before editing.
3. Read these vault documents:
   - `20 Answer Bank/00 System/Answer Bank 자동 처리 규칙.md`
   - `20 Answer Bank/00 System/완성 지원서 판정 규칙.md`
   - `20 Answer Bank/00 System/청크 스키마.md`
   - `20 Answer Bank/02 Question Taxonomy/분류 기준.md`
4. Read [vault-schema.md](references/vault-schema.md) for required paths and fields.
5. Read [classification.md](references/classification.md) when classifying questions or resolving overlaps.

## Process an application

### 0. Capture the source

- Identify the source as `prompt`, `url`, `image`, `pdf`, `document`, or `markdown`.
- Record the original URI or filename, capture time, extraction method, and verification status using [source-provenance.md](references/source-provenance.md).
- Preserve supplied files under the Application attachment directory before transforming their contents.
- Treat OCR and extracted text as provisional until the user or source confirms ambiguous fields.

### 1. Preserve the source

- Create or update one note under `10 Applications/<year>/<category>/`.
- Preserve question wording, required status, character limit, selected values, attachments, and submitted answers.
- Never rewrite a submitted answer in place.
- Mark uncertain or missing data as `미확인`; do not infer it.
- Copy supplied screenshots or files into `90 Attachments/Applications/<application>/` when available.

### 2. Classify completion

- `완성`: all required narrative answers and final/submission evidence are present.
- `부분 완성`: only some answers are final or submission status is unclear.
- `미완성`: blank form, draft, or posting analysis.

For incomplete applications, save the Application and next action but do not create verified Answer Bank assets. Record the reason in `지원서 처리 로그.md`.

### 3. Extract canonical experience cards

- Identify real events, projects, decisions, and outcomes across all answers.
- Merge repeated mentions of the same event into one card using a stable `canonical_key`.
- Update an existing card when a later application adds verified facts.
- Separate verified facts from claims needing evidence.
- Use [experience-card-template.md](assets/experience-card-template.md).

### 4. Extract atomic answer chunks

- Split long answers when the event, problem, key action, competency, outcome, lesson, or rhetorical purpose changes.
- Keep one coherent reusable message per chunk.
- Assign exactly one `primary_type` and store the file only under that Question Type folder.
- Add up to three `secondary_types`; do not duplicate the chunk file into those folders.
- Link the source Application, source question, canonical experience cards, and evidence.
- Remove phone numbers and personal or school email addresses from chunks.
- Use [answer-chunk-template.md](assets/answer-chunk-template.md).

### 5. Link evidence

- Record GitHub repositories, portfolio pages, documents, metrics, screenshots, and submitted files under `06 Evidence`.
- Distinguish an existing verified file from a filename or planned artifact.
- Do not invent metrics or claim completion for a planned project.

### 6. Update navigation and status

Update all applicable files:

- `답변 자산 인덱스.md`
- `04 Experience Cards/경험 카드 인덱스.md`
- each affected Question Type guide's extracted-chunks section
- `05 Answer Drafts/답변 조립 작업대.md` when a new reusable combination is created
- `00 System/지원서 처리 로그.md`
- `99 Dashboard/지원 현황.md`
- the Application's Answer Bank processing fields and section

## Reuse assets for a new answer

1. Classify the new question by its main evaluation intent.
2. Select one primary experience and zero to two supporting chunks.
3. Verify roles, actions, outcomes, numbers, and evidence against the experience card.
4. Rewrite organization-specific motivation and contribution plans for the new target.
5. Never combine facts from different events as if they happened in one event.
6. Save the draft under `05 Answer Drafts`; after submission, preserve the final answer in its Application.

## Validate every run

- Confirm each completed Application has processing metadata and a log entry.
- Confirm every chunk ID is unique.
- Confirm every chunk exists in exactly one primary Question Type folder.
- Confirm every experience reference resolves or is explicitly empty for plan/value chunks.
- Confirm no Answer Bank chunk contains a phone number or personal/school email address.
- Confirm index counts match actual files.
- Confirm incomplete applications produced no verified chunks.
- Report created, updated, merged, skipped, and needs-evidence counts to the user.