fidelity-ai-workspace/.agents/workflows/archive-import.md at 1ad707373aa29ccf0c5385b21ee49dd20c861687

Files

david.delagneau 1ad707373a Add daily logs and templates for project fidelity

- Created daily log entries for May 13, 14, 18, 19, 20, and 21, capturing work done, findings, and next steps.
- Established a daily logs index for easy navigation of daily notes.
- Developed templates for daily logs, decisions, meeting notes, people, systems, and work items to standardize documentation.
- Introduced base files for filtering and displaying various types of project knowledge, including daily notes, decisions, people, systems, work items, and workstreams.
- Added maps for current work, fidelity apps, and fidelity domain to enhance project navigation and context.

2026-05-21 12:28:07 -06:00

3.1 KiB

Raw Blame History

description

description
Import a historical communication archive and refine workspace memory

// turbo-all 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 @workspaces/fidelity/project-knowledge/01-current/current-work.md @workspaces/fidelity/project-knowledge/01-current/work-items.md @workspaces/fidelity/project-knowledge/03-context/project.md @agent-memory/memory/context-maintenance.md @workspaces/fidelity/project-knowledge/04-people/index.md @workspaces/fidelity/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 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 workspaces/fidelity/project-knowledge/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 workspaces/fidelity/project-knowledge/

Return:

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

3.1 KiB Raw Blame History

3.1 KiB

Raw Blame History