80 lines
4.5 KiB
Markdown
80 lines
4.5 KiB
Markdown
---
|
|
description: Import a historical Slack export and refine workspace memory from it
|
|
---
|
|
|
|
Use a Slack export as a historical context source 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 in the arguments, 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`
|
|
- if no message limit is specified, auto-tune message selection based on archive size
|
|
- if no date range is specified, do an initial full-history sweep across the detected `fidelity*` channels
|
|
- preserve broad coverage across years and channels while still prioritizing high-signal messages
|
|
|
|
First, 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 Slack 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
|
|
@project-knowledge/01-current/current-work.md
|
|
@project-knowledge/01-current/work-items.md
|
|
@project-knowledge/03-context/project.md
|
|
@project-knowledge/03-context/systems/index.md
|
|
@project-knowledge/03-context/workstreams/index.md
|
|
@project-knowledge/03-context/process/index.md
|
|
@project-knowledge/04-people/index.md
|
|
@project-knowledge/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 Slack summary generated."; fi`
|
|
|
|
Imported Slack context, if present:
|
|
|
|
!`if [ -s scripts/slack/generated/slack_context.jsonl ]; then cat scripts/slack/generated/slack_context.jsonl; else echo "No Slack context generated."; fi`
|
|
|
|
Instructions:
|
|
|
|
- treat the Slack archive as historical evidence, not promoted memory by itself
|
|
- assume this may be a large multi-year export
|
|
- assume the first import should preserve evidence from the beginning of the project, not just recent history
|
|
- promote durable project-relevant context automatically when confidence is high
|
|
- prefer promoting:
|
|
- repeated Jira IDs and titles still relevant to current understanding
|
|
- durable role/person associations
|
|
- recurring architecture or debugging patterns
|
|
- past approvals or decisions that still matter
|
|
- create or update `project-knowledge/04-people/*.md` when the archive shows a human repeatedly contributing across channels, years, or high-signal technical/process discussions
|
|
- store people conservatively:
|
|
- exact role only when explicitly supported by the archive
|
|
- otherwise store collaboration pattern, communication style, and project relationship
|
|
- actively look for:
|
|
- Jira IDs plus explicit titles, sizing, and scope changes
|
|
- repeated architecture themes around XFlow, SwiftUI, REST, GraphQL, auth, and entry-point behavior
|
|
- ownership or responsibility boundaries between framework and consuming app teams
|
|
- recurring pipeline or dependency failures that shaped project work
|
|
- named people who repeatedly drive approvals, technical framing, or debugging direction
|
|
- prioritize high-signal messages such as Jira references, approvals, scope changes, root-cause notes, points, and persistent technical constraints
|
|
- favor messages that help reconstruct project history across multiple years, not just the newest ones
|
|
- avoid promoting outdated daily status unless it changes current understanding
|
|
- update existing memory when the archive clarifies or corrects it
|
|
- if historical facts are ambiguous or likely outdated, summarize them as archived context instead of promoting them
|
|
- write promoted memory to `project-knowledge/`
|
|
|
|
Return:
|
|
|
|
1. What was imported
|
|
2. Which files were updated
|
|
3. Which historical facts were promoted or intentionally left as archive-only context
|