Update ID format to use per-repo prefixes and random suffix Migrated all issue, TODO, and decision IDs to a new 4-part format: <PREFIX>-<TOPIC>-<TYPE>-<RAND>. Added per-repo prefix declarations in copilot-instructions.md and documented conventions in REPO_PREFIXES.md. Updated all topic registries, logs, cross-references, and documentation to use the new format. Introduced MIGRATION_ID_MAPPING.md for old-to-new ID mapping. Enhanced skills and protocol audit logic to validate and enforce per-repo prefixes and topic codes at runtime. Clarified Framework-First doctrine and ensured all references are unambiguous. |
||
|---|---|---|
| .. | ||
| AUTH | ||
| adr | ||
| ARCHITECTURE.md | ||
| CONVENTIONS.md | ||
| GLOSSARY.md | ||
| README.md | ||
README.md
AyCode.Core documentation
Top-level documentation for the AyCode.Core repo (Layer 0 — core framework).
Reference docs (flat)
ARCHITECTURE.md— Repo architecture overviewCONVENTIONS.md— Coding conventionsGLOSSARY.md— Domain glossary
Sub-projects with docs
AyCode.Core/docs/— Logger, Binary serializer (paired topics: LOGGING/, BINARY/)AyCode.Core.Server/docs/— Server-side logger variant (LOGGING/)AyCode.Services/docs/— Remote logger variant, SignalR, SignalR binary protocolAyCode.Services.Server/docs/— Server-side SignalR + data source
Navigation
Per the AI Agent Core Protocol (folder navigation rule), start from this README when browsing docs/. Single-file reference docs remain flat at the repo-root level; multi-file topics live in named subfolders at the sub-project level.