iamjosuho OrbTrack Triage Skill (Pass 2: Impact Scan & PARA Classification)
Principle
OrbTrack is a staging area and nothing more — unprocessed, awaiting classification — at memorbs/HQ/OrbTrack/. orbtrack-triage acts as Pass 2 of the Two-Pass pipeline: it performs Impact Scanning over entity pages, enriches bi-directional links, and moves items to their permanent PARA destinations. A triage pass is complete when OrbTrack is 100% empty.
Workflow (Strict Order)
List items in OrbTrack:
- A bundle orb (a folder shaped
{name}/{name}.md) is one item and moves as a whole — never split it apart:ls "$VAULT/memorbs/HQ/OrbTrack/"
- A bundle orb (a folder shaped
Route special types first:
- Business card images →
business-card-ingestion - Audio recordings / voice files →
recording-transcription
- Business card images →
Scan Impact & Update Entity Pages (Pass 2 Core Value):
- For each orb in OrbTrack, analyze mentioned entities and update corresponding pages:
memorbs/Long-Term/People/— People mentionedmemorbs/Long-Term/Projects/— Projects impactedmemorbs/Long-Term/Orgs/— Companies/entities mentionedmemorbs/HQ/glossary.md— New terms
- Frontmatter Schema Enforcer: Ensure target entity page frontmatter includes
aliases: [](authority control) andorb_emotions: [](accumulated emotion tags likejoy,anxiety,fear,sadness,anger,disgust). - Fact vs Decision Updates:
- Fact Updates (e.g. status changes): Overwrite directly with latest state.
- Decision/Principle Updates: Retain change history and context in the page body.
- Ensure Reachability: Ensure bi-directional wiki links (
[[...]]) exist between the orb and related entity/MOC pages.
- For each orb in OrbTrack, analyze mentioned entities and update corresponding pages:
Move along the PARA Decision Tree:
| Judgement | Destination | PARA |
|---|---|---|
| Has a firm deadline or deliverable | memorbs/Long-Term/Projects/ |
P |
| An area of responsibility or interest you keep coming back to | memorbs/Islands/ |
A |
| Reference material, study notes | a single orb under memorbs/Islands/{相關島}/, linked from that Island's MOC |
R |
| Information about a particular person or organization | memorbs/Long-Term/{People,Orgs}/ |
— |
| Finished, or no longer relevant | memorbs/Dump/{category}/ |
Ar |
PARA's R gets no folder of its own. An Island is defined as an area of responsibility or interest, so subjects of long-term interest live as orbs hanging off the relevant Island.
Update Status & Move (
mv):- Move the file/folder (
mv). - Update frontmatter:
status: unprocessed→status: processed(oractivefor entity/island pages).
- Move the file/folder (
Record the Triage Commit:
- If this pass processed one or more items, append one concise
triageentry at the top ofmemorbs/log.md, linking the moved orbs and every changed Long-Term, Island, or glossary page. Use a short operational note (for example,已完成 N 筆分流與影響更新。); do not duplicate orb content or classification reasoning.
- If this pass processed one or more items, append one concise
Verify Zero-Leftover:
- Confirm
memorbs/HQ/OrbTrack/is completely empty.
- Confirm
Red Flags
| Excuse | Reality |
|---|---|
| "OrbTrack is basically where notes live, leaving it there is fine" | OrbTrack is a staging area. Triage is only finished when OrbTrack is 100% empty. |
| "I'll skip Impact Scan and just move the files" | Impact Scan (Step 3) ensures entity pages stay updated with new information. Skipping it leaves structured memory stale. |
| "This one doesn't fit any Island, I'll invent a folder" | PARA's R has no standalone folder. Ask user whether to start a new Island (island-reclamation). |
| "Rough classification is fine, filename doesn't matter" | Filenames and dates must conform to memorb-conventions. |