Files

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.9 KiB

Raw Blame History

Slack History Import

This directory contains helpers to ingest historical Slack exports as context sources for the workspace.

Goal

Use old Slack history to recover durable project context, stakeholder relationships, Jira references, and past decisions without treating the raw archive as current truth.

Recommended Use

import selected channels, not the whole export blindly
prefer recent or relevant historical windows
promote only durable, project-relevant facts into workspace memory
keep raw imported artifacts under generated/
keep the raw Slack export under archives/slack/export/ when you want the workspace to find it later
for a first pass on a large export, let the importer auto-detect fidelity* channels and auto-tune message selection
for reusable project profiles, set AIW_CHANNEL_PREFIX so the importer can auto-detect project-specific channels without hardcoding a prefix

Supported Export Shape

The importer expects the standard Slack export structure:

one folder per channel
one JSON file per day inside the channel folder
optional users.json at the export root

Usage

Manual example:

python3 scripts/slack/import_slack_export.py \
  --export-path /absolute/path/to/slack-export \
  --channel-prefix "${AIW_CHANNEL_PREFIX:-fidelity}" \
  --output-dir scripts/slack/generated

This generates:

scripts/slack/generated/slack_context.jsonl
scripts/slack/generated/slack_summary.md

Use the OpenCode command /slack-import ... for the guided workflow.

Large Export Behavior

For very large multi-year exports, the importer is designed to be selective by default:

auto-detects channels whose names start with fidelity when no channels are specified
uses AIW_CHANNEL_PREFIX when set; otherwise defaults to fidelity for this workspace profile
auto-tunes the message limit based on archive size
when no date filters are provided, performs an initial full-history sweep across the detected fidelity* channels
preserves coverage across channels and years, not only recent history
prefers recent messages plus older high-signal messages
preserves strong Jira-linked messages even when they are old
highlights repeated human participants with cross-channel, multi-year, or high-signal involvement so they can be added to people memory
prioritizes Jira IDs, approvals, scope changes, root-cause notes, points, and durable technical patterns

Override behavior if needed:

--channels fidelity-preguntas,fidelity-ios
--all-channels
--max-messages 8000
--since 2025-01-01

Recommended Archive Location

If you want the workspace to find the export later without needing a custom path each time, place the extracted export here:

archives/slack/export/

The /archive-import and /slack-import commands will use that location automatically when no explicit path or environment variable is provided.

2.9 KiB Raw Blame History