/thebrain-bird-address

name: thebrain-bird-address
description: "Use BIRD Book Deconstructor 2.2 to apply the formal BIRD 2.1 Knowledge Address protocol to complex manuscript text and TheBrain Thoughts. Use when splitting books into chapter/section/item knowledge nodes, assigning Book Address, structured Knowledge Index (Weight, Type, Keyword, Alias), Routes, verified Deep Links, and Semantic Roles; producing BIRD Excel workbooks, TheBrain scaffolds, Roam JSON, monochrome printable double nine-grid cards, or a routed handoff from iMandalArt to A4 eight-page booklets; or auditing and migrating existing BIRD/TheBrain indexes."

BIRD Book Deconstructor 2.2

Convert complex structural text into addressable, searchable, cross-linked book nodes for TheBrain, Excel, Roam Research, Obsidian, and AI Agents.

Version 2.2 is the Skill integration release. Canonical interchange objects remain `BIRD-2.1` for backward compatibility.

Three Kings 2.2 Integration

BIRD is the **address and route king** in the three-skill publishing chain:

`iMandalArt 2.2 eight angles -> BIRD 2.2 Book Address + Index + Route + Deep Link -> A4 Booklet 2.2`

• Receive the center, eight angles, source identities, and spatial order from iMandalArt.
• Turn reusable claims into stable Book Addresses and `W + T + K + A` Knowledge Indexes.
• Send seven ordered Routes, citations, pending Deep Links, and merge reasons to the booklet manifest.

Formal Protocol

• `B = Book Address`: stable book/project hierarchy address; answer "where in the book?"
• `I = Knowledge Index`: structured index object `W + T + K + A`; answer "what knowledge object?"
• `R = Route`: ordered cross-node or cross-chapter paths; answer "where does it lead?"
• `D = Deep Link`: exact permanent application address; answer "how is it opened?"

Read [`references/bird-2.1-spec.md`](references/bird-2.1-spec.md) before assigning Index Weight, Index Type, or Semantic Role.

Do not use the old `B = Branch` or unstructured `I = title` interpretation. Mark legacy input as `BIRD 1.x` and map it into 2.1. Preserve valid BIRD 2.0 fields during migration; add `Role` only when evidence supports it.

Distinguish Two Types

• `StructuralType`: book function, such as `部 / 章 / 節 / 項`.
• `IndexType`: knowledge kind inside `I`, using `C / M / P / B / T / O / E / L / S / A / X`.

Never put `章` into `IndexType`, or `Concept` into `StructuralType`.

Choose the Mode

• **Single Node**: analyze one existing Thought and output one BIRD object.
• **Deconstruct Text**: split complex prose into chapter, section, and atomic item nodes.
• **Excel Workbook**: create a validated `.xlsx` with BIRD analysis, manuscript Notes, and code tables.
• **TheBrain Scaffold**: turn the validated Excel hierarchy into empty or selectively populated Thoughts with structural Types and workflow Tags.
• **Roam JSON Export**: convert canonical BIRD objects or flat `BIRD分析` rows into a Roam-importable page/block array.
• **Monochrome Double Nine-Grid**: compose one A4 landscape printable visual with the main table of contents and three Routes on the left, and the Knowledge Index on the right.
• **Audit/Migrate**: check or convert existing TheBrain or legacy Excel rows.

Deconstruct Text

1. Identify book, part, chapter, section, existing numbering, central question, and argument order. 2. Preserve existing addresses. Use `待編` only when no reliable address exists; do not silently renumber. 3. Treat `章` and `節` as structural containers. Treat `項` as the normal manuscript unit: one claim, explanation, evidence/example, and transition. 4. Split when the claim, reader question, independent case, definition, or reusable reasoning step changes. Do not split mechanically by paragraphs. 5. Target 700-1000 Chinese characters per standard item Note; allow 300-600 for bridges/definitions and up to 1200 for an indivisible case. 6. Build one BIRD object per item:

• assign one `B`;
• assign one `I.W`, one `I.T`, one canonical `I.K`, and zero or more deduplicated `I.A`;
• assign two to five meaningful `R` targets when supported;
• preserve verified `D` byte-for-byte or leave it blank/pending for proposed nodes.

7. Preserve the author's stance, metaphors, examples, and evidence. Mark missing material `待補`; never fabricate support. 8. Return a structure tree, BIRD table, JSON objects, and item Note drafts unless the user requests only one format.

Read [`references/manuscript-structuring.md`](references/manuscript-structuring.md) for segmentation and output templates.

Assign the Index

For every node, apply this order:

1. Choose `K`: one canonical retrieval term, 4-10 Chinese characters or 2-4 English words. 2. Choose `T`: one code from the controlled Index Type table. 3. Choose `W`: importance to this specific book, not general fame. 4. Add `A`: genuine synonyms, translations, abbreviations, or established alternate spellings. Exclude the canonical keyword itself. 5. Assign the optional BIRD 2.1 `Role` only when graph or hierarchy evidence supports it; otherwise leave blank.

Do not turn every noun into an Index. Create an index object only when the term supports retrieval, interpretation, or routing.

Build Routes

• Use `B` for the table-of-contents location and `R` for meaningful cross-links.
• Prefer ordered routes such as `FIRE -> 語意索引 -> AI對話`.
• Store Route targets as existing Thought names, Book Addresses, or verified Deep Links.
• Exclude self-links, direct hierarchy repetitions, and nearby siblings without a semantic reason.
• Mark a proposed target `待建` rather than inventing its address.

Preserve Deep Links

Copy each supplied `D` exactly from `brain://` through the final character. Never decode, encode, normalize, shorten, repair, rename, or regenerate its slug. For a proposed Thought, use a blank cell in Excel and `待建立 Thought 後貼入` in prose.

Before returning, compare every displayed `D` with its source string. Do not claim tool verification unless a tool returned that exact value in the cur