Files
fidelity-ai-workspace/.opencode/commands/archive-import.md
david.delagneau 8026da5719 Refactor AI workspace for improved context management and communication integration
- Introduced new commands and skills for workspace memory curation, professional communication, and status reporting.
- Updated existing commands to utilize new skills and improve clarity in instructions.
- Created a new workspace context command to load reusable core and active project profile.
- Enhanced Mattermost inbox integration with support for generic environment variables.
- Established a clear separation between project-independent core logic and project-specific profiles.
- Improved documentation across various files to reflect changes in workflow and command usage.
- Added operational memory management rules to ensure accurate context promotion and correction.
- Updated README and workflow documents to guide users in utilizing the new structure effectively.
2026-04-16 08:35:53 -06:00

2.9 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
  • compatibility fallback: 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
  • compatibility/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 @ai/AGENTS.md @ai/context/index.md @ai/context/project.md @ai/context/process/context-maintenance.md @ai/context/people/index.md @ai/context/people/manager.md @ai/work-items/index.md @ai/state/current.md @ai/state/work-items.md @knowledge/agent-memory-rules.md @knowledge/memory-promotion-rules.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 person files 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

Return:

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