loyalty-agent-service/docs/specs/00_MIGRATION_REPORT.md

Migration Report

Summary

The migration of the monolithic FSD (Functional Specification Document) Markdown files to the OpenSpec standard is complete. The goal was to decompose massive, human-oriented Word-converted markdown files into Agent-Friendly, atomic, and structured OpenSpec documents.

Completed Tasks

1. Decomposition: All major monolithic files have been decomposed into domain-specific subdirectories.
2. Archiving: The original monolithic markdown files have been moved to docs/specs/archive/.
3. Format Standardization: The newly created documents follow the OpenSpec format, including proper YAML frontmatter (title, type, status, domain).
4. Cleanup: Unnecessary UI clutter, malformed artifacts (e.g. [Image Removed]), and verbose narrative instructions were removed or converted into structured business rules and data schemas.

Output Structure

The new documentation is organized into the following domains under docs/specs/:

• customer_management/: Profiles, Accounts, Cards, Pool Balances, Transactions, Adjustments, etc.
• reward_campaign/: Campaign Structures, Rules, Criteria, Formulas, Counter Definitions, Transaction Categories, etc.
• onetargeting/: Segmentation, Audiences.
• onecatalogue/: Catalogues, Categories, Master Items, Vouchers.
• onemarketing/: Messages, Campaigns, A/B Testing, Whitelists, Blacklists.
• oneaccess/: Users, Permissions, Profiles.
• oneadmin/: Framework behavior.
• system_management/: Application parameters.
• introduction/: Terminology.
• reference/: References, Change History.

Next Steps

• Implement Agent tooling capable of reading these OpenSpec files to generate test cases or boilerplate code.
• Ensure any future updates to the requirements are made directly to the atomic OpenSpec files, not the archived monolithic documents.