yams/docs/developer/architecture
Trevon 9cb6421593
feat: daemon stability fixes, vector search optimizations, and docs refresh (#46)
* fix(daemon): resolve sign-conversion warnings

* fix(daemon): add IO thread startup barrier

* refactor: consolidate toLowerCopy clones

* fix(daemon): add atexit handler for static host map cleanup

* fix(build): add missing include, fix daemon_helpers syntax, use atomic barrier

* feat(docs): docs cleanup, and metadata refactor updates

* fix(daemon): resolve Windows-only PostIngestQueue shutdown SIGSEGV (#45)

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

* feat: submodule bump, multiclient optimizations and benchmark optimizations

* feat(perf): reduced contention with update to placement of flushPathCacheBuffer()

* fix(metadata): invalidate path cache on document mutation

* fix(metadata): hydrate cached counters before first write

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-10 10:30:38 -04:00
..
README.md feat: daemon stability fixes, vector search optimizations, and docs refresh (#46) 2026-06-10 10:30:38 -04:00

Developer Architecture Notes

This index points to architecture references that mirror the live implementation. Always validate statements against the cited source modules.

Core Architecture References

Supporting Design Notes

API References

Operations and Performance Guides

Contribution Workflow

  1. Update architecture docs and any related traceability artifacts in the same change set.
  2. Anchor new prose to specific functions, classes, or modules under src/.
  3. Capture validation evidence (integration logs, benchmarks) alongside the change with timestamps.
  4. Run mkdocs build --strict and archive the log before submitting changes.
  5. Flag future work explicitly with issue references; avoid speculative language.

Missing topics should be proposed via issue (outline + intended source references) prior to documentation work.