---
roadcrew_template_name: "enhancement.template.md"
roadcrew_template_type: "enhancement"
roadcrew_template_version: "v1.0"
roadcrew_last_updated: "2025-11-03"
roadcrew_min_version: "1.6.0"
roadcrew_license: "Apache-2.0"
roadcrew_copyright: "Copyright (c) 2025 North Star Holdings, LLC"
spdx_license_identifier: "Apache-2.0"
name: Enhancement
about: Publish memory-bank folder to customers via distribution
title: "[TBD] Publish memory-bank/ folder to .roadcrew/memory-bank/"
assignees: []
---

# Publish memory-bank/ folder to .roadcrew/memory-bank/

## Overview & User Story

Enable customers to access comprehensive project documentation (architecture, patterns, decisions, progress) via `.roadcrew/memory-bank/` folder. This mirrors the living documentation we maintain internally and gives customers reference material for understanding Roadcrew philosophy and patterns.

**User Story:** As a customer using Roadcrew, I want to have access to comprehensive documentation about why decisions were made and what patterns we follow, so that I can understand the rationale behind the system and make informed decisions about adoption.

## Acceptance Criteria

- Memory Bank folder (`memory-bank/`) is published to `roadcrew/memory-bank/` during distribution sync
- All 6 documentation files are included: 00-description, 01-brief, 02-architecture, 03-patterns, 04-progress, 05-decisions
- Publishing script (`publish-distribution.ts`) includes explicit task for memory-bank sync
- No internal-only exclusions needed (all memory-bank files are customer-safe)
- Customers can access via `.roadcrew/memory-bank/` after submodule update

## Technical Implementation

- Add `PUBLISH_TASK` entry in `scripts/publish-distribution.ts` (lines 70-137)
  - Source: `ROADCREW_INTERNAL_ROOT/memory-bank`
  - Destination: `ROADCREW_DIST_ROOT/memory-bank`
  - Use standard directory sync (no exclusions like commands/)
- Update `.cursor/rules/memory-bank.mdc` to reference `.roadcrew/memory-bank/` for customers
- Update `COMMANDS-PUBLISHING-FLOW.md` to include memory-bank publishing flow
- Verify memory-bank syncs during next distribution release
- Test with `npm run publish:dist --dry-run` before production

## Dependencies

- `COMMANDS-PUBLISHING-FLOW.md` (published, establishes pattern)
- `memory-bank/` folder (created Nov 3, 2025)
- `scripts/publish-distribution.ts` (main publishing script)

## Definition of Done

- [ ] Tests written first and passing (>35% coverage)
- [ ] All acceptance criteria met
- [ ] Code reviewed and approved
- [ ] Merged to dev branch
- [ ] Validated in staging

## Estimated Effort

**Classification:** 3 (🟢 ai-solo)

Rationale: Straightforward addition of single publish task (< 5 lines code), no special exclusion logic needed, mirrors existing commands/rules pattern. Simple enough for autonomous AI execution.

---

**Related Spec:** See `COMMANDS-PUBLISHING-FLOW.md` for comprehensive publishing architecture documentation.

**Related Epic:** EPIC-1171 (Post-Launch Optimization - Distribution Published)

**Created:** 2025-11-03