Files
fidelity-ai-workspace/.opencode/commands/archive-import.md
david.delagneau 374991a568 Refactor workspace structure and documentation
- Deleted obsolete files: obsidian-vault.md, onboarding.md, workspace-model.md
- Updated opencode.json to remove references to deleted files.
- Revised profile.md to clarify the status of legacy paths and communication evidence.
- Adjusted prompts to reflect new file paths and improve clarity.
- Enhanced daily logs with focus, work-items, and blockers properties.
- Updated work-item notes to include systems, workstreams, people, and related properties.
- Improved context maintenance guidelines to ensure accurate and durable project knowledge.
- Refined base filters to exclude template files and ensure only relevant notes are displayed.
- Updated daily templates to ensure proper formatting and consistency.
- Modified workflows to align with the new vault structure and improve context synchronization.
2026-04-16 16:28:30 -06:00

2.8 KiB

description
description
Import a historical communication archive and refine workspace memory

Use a historical communication export as archive evidence for the workspace.

Interpret this as historical recovery, not as current truth and not as model training.

Inputs:

  • $ARGUMENTS may contain an export path, channel names, or date filters
  • if no explicit path is given, use AIW_SLACK_EXPORT_PATH when available
  • Fidelity profile alias: FIDELITY_SLACK_EXPORT_PATH
  • otherwise, if archives/slack/export/ exists, use it as the default import source
  • if no channels are specified, auto-detect channels using AIW_CHANNEL_PREFIX
  • Fidelity default prefix: fidelity

Run the importer:

!prefix="${AIW_CHANNEL_PREFIX:-fidelity}"; if [ -n "$ARGUMENTS" ]; then python3 scripts/slack/import_slack_export.py $ARGUMENTS; elif [ -n "$AIW_SLACK_EXPORT_PATH" ]; then python3 scripts/slack/import_slack_export.py --export-path "$AIW_SLACK_EXPORT_PATH" --channel-prefix "$prefix"; elif [ -n "$FIDELITY_SLACK_EXPORT_PATH" ]; then python3 scripts/slack/import_slack_export.py --export-path "$FIDELITY_SLACK_EXPORT_PATH" --channel-prefix "$prefix"; elif [ -d archives/slack/export ]; then python3 scripts/slack/import_slack_export.py --export-path archives/slack/export --channel-prefix "$prefix"; else echo "Provide archive import arguments, set AIW_SLACK_EXPORT_PATH, set FIDELITY_SLACK_EXPORT_PATH, or place an extracted export in archives/slack/export."; fi

Read:

@core/README.md @core/memory/operational-memory.md @core/integrations/communication-model.md @vault/01-current/current-work.md @vault/01-current/work-items.md @vault/03-context/project.md @vault/03-context/process/context-maintenance.md @vault/04-people/index.md @vault/04-people/manager.md

Imported summary, if present:

!if [ -s scripts/slack/generated/slack_summary.md ]; then cat scripts/slack/generated/slack_summary.md; else echo "No archive summary generated."; fi

Imported archive context, if present:

!if [ -s scripts/slack/generated/slack_context.jsonl ]; then cat scripts/slack/generated/slack_context.jsonl; else echo "No archive context generated."; fi

Instructions:

  • treat the archive as historical evidence
  • promote durable project-relevant context automatically when confidence is high
  • prefer durable role/person associations, recurring architecture patterns, repeated work-item references, approval/scope history, and process lessons
  • create or update vault/04-people/*.md when a human repeatedly affects project flow
  • avoid promoting outdated daily status unless it changes current understanding
  • update existing memory when the archive clarifies or corrects it
  • keep ambiguous or likely outdated facts as archive-only context
  • write promoted memory to vault/

Return:

  1. What was imported
  2. Which files were updated
  3. Which historical facts were promoted or intentionally left as archive-only context