Remove obsolete documentation files including ALL_TASKS_COMPLETE.md, COMPLETION_REPORT.md, COMPREHENSIVE_FINAL_REPORT.md, FAQ_Compliance.md, FAQ_General.md, FAQ_Operational.md, FAQ_Technical.md, FINAL_COMPLETION_SUMMARY.md, IMPLEMENTATION_STATUS.md, IMPLEMENTATION_TASK_LIST.md, NEXT_STEPS_EXECUTION_SUMMARY.md, PHASE_1_COMPLETION_SUMMARY.md, PHASE_2_PLANNING.md, PHASE_2_QUICK_START.md, PROJECT_COMPLETE_SUMMARY.md, PROJECT_STATUS.md, and related templates. This cleanup streamlines the repository by eliminating outdated content, ensuring focus on current documentation and enhancing overall maintainability.

This commit is contained in:
defiQUG
2025-12-08 06:24:28 -08:00
parent 0e4be6446a
commit d13eca034d
112 changed files with 14024 additions and 159 deletions

View File

@@ -101,19 +101,19 @@ Use **Semantic Versioning (SemVer)** format: `MAJOR.MINOR.PATCH`
## CROSS-REFERENCE STANDARDS
### Internal Document References
Format: `[Document Title](relative/path/to/document.md)`
Format: `[Document Title](path/to/document.md)` where path is relative to the current file
**Examples (Note: These are example formats, not actual links):**
- `[Title VI: Cyber-Sovereignty](02_statutory_code/Title_VI_Cyber_Sovereignty.md)` - ✅ Valid example
- `[CSP-1113 Technical Specification](csp_1113/CSP-1113_Technical_Specification.md)` - ✅ Valid example
- `[Document Title](relative/path/to/document.md)` - ⚠️ Example format only
- Example format (not a link): `relative/path/to/document.md` (example path only, not a real link)
### Section References
Format: `[Section Name](document.md#section-name)`
Format: `[Section Name](path/to/document.md#section-name)` where section-name is the anchor ID
**Examples (Note: These are example formats, not actual links):**
- `[Section 1.1: Server Standards](11_technical_specs/Technical_Standards.md#section-11-server-standards)` - ⚠️ Example format only
- `[Section Name](document.md#section-name)` - ⚠️ Example format only
- `[Section 1.1: Server Standards](11_technical_specs/Technical_Standards.md#section-11-server-standards)` - ✅ Valid example (links to actual section)
- Example format (not a link): `document.md#section-name` (example format only, not a real link)
### Anchor-Only Links
Format: `[Section Name](#anchor-name)`
@@ -128,7 +128,7 @@ Format: `[Section Name](#anchor-name)`
- `[Go to Section](#section-name)` - Links to heading "## Section Name" in same document
### Directory Links
Format: `[Directory Name](path/to/directory/)`
Format: `[Directory Name](path/to/directory/)` where path points to a directory (prefer linking to specific files)
**Guidance:**
- Use when linking to a directory of related documents
@@ -136,7 +136,8 @@ Format: `[Directory Name](path/to/directory/)`
- Directory links are valid but may be flagged by verification scripts
- Prefer specific file links when possible
**Example:**
**Example (not a link):**
- Example format: `path/to/directory/` - ⚠️ Example format only
- `[Operational Examples](08_operational/examples/)` - Links to examples directory
### Related Documents Section
@@ -157,7 +158,7 @@ All major documents shall include a "Related Documents" section at the end listi
### Terminology
- Use consistent terminology throughout all documents
- Define acronyms on first use: `Digital Banking and Institutional System (DBIS)`
- Define acronyms on first use: `Digital Bank of International Settlements (DBIS)`
- Refer to Glossary for standard definitions
### Placeholder Content