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. |
||
|---|---|---|
| .. | ||
| LOGGING | ||
| SIGNALR | ||
| SIGNALR_BINARY_PROTOCOL | ||
| adr | ||
| README.md | ||
README.md
AyCode.Services documentation
Topic documentation for the AyCode.Services project (Layer 0, service abstractions).
Topics
LOGGING/— Remote logger (variant — sends log entries over the wire)SIGNALR/— SignalR transport (tag-based protocol, generic hub methods)SIGNALR_BINARY_PROTOCOL/— Binary-over-SignalR wire format, chunked framing
Navigation
Per the AI Agent Core Protocol (folder navigation rule), start from this README when browsing docs/. Each topic folder has its own README.md with the main content, plus optional TOPIC_ISSUES.md (known issues) and TOPIC_TODO.md (planned work).
See also
- Base logger (framework):
../../AyCode.Core/AyCode.Core/docs/LOGGING/README.md - Server-side logger (variant):
../../AyCode.Core.Server/docs/LOGGING/README.md - Server-side SignalR:
../../AyCode.Services.Server/docs/SIGNALR/README.md - Binary serializer (used by SIGNALR_BINARY_PROTOCOL):
../../AyCode.Core/AyCode.Core/docs/BINARY/README.md