AGENTS.md (2212B)
1 # radrootsd - code directives 2 3 - this repo defines `radrootsd`, the standalone Radroots daemon 4 - keep this repo cloneable, inspectable, buildable, testable, and usable from its own checked-in source and public dependency surface 5 - do not make this repo responsible for platform-wide release contracts, signed artifacts, builder selection, publication, promotion, deployment transport, or private dependency coordination unless represented in this repo's public contract 6 - prefer the smallest coherent change that fully addresses the request; do not mix unrelated cleanup, speculative refactors, compatibility scaffolding, or roadmap work into the same change 7 - inspect the relevant implementation, tests, manifests, and docs before changing behavior 8 - do not invent requirements, APIs, dependencies, release processes, or external integration behavior 9 - do not depend on private repositories, unpublished artifacts, local machine layouts, absolute paths, or internal monorepo context 10 - preserve explicit boundaries between daemon lifecycle, configuration, service state, storage, network integration, and domain behavior 11 - keep startup, shutdown, error handling, and recovery behavior deterministic and observable without leaking sensitive data 12 - prefer explicit typed models, deterministic behavior, narrow side effects, and direct service boundaries over stringly or implicit behavior 13 - avoid hidden production panics; use typed errors for expected failure modes 14 - avoid `unsafe` unless it is strictly necessary, locally justified, and documented with nearby invariants 15 - do not expose secrets, private keys, credentials, tokens, invite codes, private identifiers, sensitive user data, or sensitive event content in code, logs, tests, fixtures, docs, or examples 16 - prefer tests that exercise daemon behavior through stable public or repo-owned interfaces 17 - use checked-in, repo-owned validation first; run the smallest documented validation that credibly covers the change 18 - if validation cannot run, report exactly what was skipped and why; never claim validation passed unless it actually ran 19 - keep commits focused and reviewable, using `<scope>: <imperative summary>` unless a repo convention overrides it