Adam
/
AyCode.Core
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
AyCode.Core/docs
History
Loretta 0ad9250e4c [LOADED_DOCS: 3 files, no new loads] 
Add Rule #6, AUTH topic, ADRs, config & doc updates

- Codified Rule #6 (authority, rule scope, skill invocation) in all primary copilot-instructions.md files
- Clarified skill pre-load/lazy-load rules and LOADED_DOCS prefix
- Forbid skill/template version labels in Decision Log governance
- Scaffolded new AUTH topic with README, ISSUES, and TODO files
- Added repo/project ADR folders and templates; new ADR for AcBinaryHubProtocol decorator stack
- Migrated cross-cutting issues/TODOs to Closed with detailed resolution
- Made FruitBankHybrid.Shared/appsettings.json the canonical config source; suppressed Razor SDK auto-publish to avoid file collisions
- Updated protocol/wire format docs for AcBinaryHubProtocol
- Minor config: updated ports, WaitForFlush, and csproj content rules
 		2026-04-26 13:44:12 +02:00
..
AUTH [LOADED_DOCS: 3 files, no new loads] 2026-04-26 13:44:12 +02:00
adr [LOADED_DOCS: 3 files, no new loads] 2026-04-26 13:44:12 +02:00
ARCHITECTURE.md [LOADED_DOCS: 4 files, no new loads] 2026-04-24 21:54:04 +02:00
CONVENTIONS.md [LOADED_DOCS: 4 files, no new loads] 2026-04-24 21:54:04 +02:00
GLOSSARY.md [LOADED_DOCS: 4 files, no new loads] 2026-04-24 21:54:04 +02:00
README.md [LOADED_DOCS: 4 files, no new loads] 2026-04-24 21:54:04 +02:00

README.md

AyCode.Core documentation

Top-level documentation for the AyCode.Core repo (Layer 0 — core framework).

Reference docs (flat)

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 protocol
  • AyCode.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.