Meeting To Tree

Meeting to Tree

Turn one logical meeting's exact source artifacts into reviewable Context Tree updates. Use existing readers, First Tree member communication, and first-tree-write; do not build a parallel reader, confirmation store, or Tree writer.

Establish the meeting source

• Require at least one concrete meeting artifact and clear intent to update the Context Tree. If either is missing, ask for it and stop.
• Process one logical meeting at a time. When supplied artifacts may belong to different meetings, separate them using explicit source evidence or ask the user to group them.
• Use the environment's ordinary reader for each exact provider document, attachment, local file, or pasted record. For a Feishu source, use the available Feishu reader or CLI; keep provider authorization, download, OCR, parsing, completeness, and revision handling in that reader layer.
• Do not use a calendar, search for related meetings, scan a time window, or follow links embedded in a source to discover adjacent material.
• Preserve the user-declared or document-visible order. If order is unknown, do not infer that one artifact overrides another.
• If an artifact is unreadable or incomplete, identify the gap. When the gap could contain a correction or later decision, do not call the affected point settled.
• Use the exact source through the ordinary reader in the current task. If the reader already provides a transient local file, reuse it. Do not create or retain an additional raw copy solely for this Skill. Never write raw meeting content to the Context Tree, a source repository, or parallel persistent state.

Identify durable Tree candidates

Read the available artifacts in order and identify claims that may change durable team context:

• a decision or explicit non-choice and its surviving rationale;
• a constraint future work must respect;
• a durable ownership or responsibility change;
• a cross-domain relationship.

For every candidate:

1. Separate proposals, discussion, and final statements.
2. Scan all later material for correction, withdrawal, replacement, disagreement, completion, or cancellation.
3. Keep only the surviving current statement.
4. Preserve the surviving rationale, qualifiers, and consequences.
5. Distinguish supported conclusions from uncertain interpretations.

Progress, plans, actions, blockers, risks, and other member-specific updates are signals, not required output categories. Consider them only when they establish or change a durable candidate above. Do not create a complete meeting summary before applying the Tree write bar.

Evidence strength matters:

• Human-confirmed minutes or an explicit decision record may confirm an item when wording is unambiguous and no later material overrides it.
• AI-generated notes may identify an item but cannot alone prove human confirmation.
• A transcript confirms only what it explicitly records. Do not infer speaker identity, authority, or agreement from participation.
• When provenance or wording is ambiguous, state the uncertainty instead of promoting it to a fact.

Before mapping members or sending any confirmation, apply the Context Tree Double Test as a preliminary filter. Keep a claim only when it both establishes or changes context future agents must respect and would remain durable if the meeting's implementation work were rewritten. first-tree-write will reapply the normal write gate after any confirmation reply.