Files

1.2 KiB

Library Project Rules

  • Treat exported code, configuration keys, registry schemas, generated artifacts, package coordinates, and documented behavior as consumer-facing contracts.
  • Before changing a public surface, classify the change as internal, backward-compatible, deprecating, or breaking.
  • Do not remove, rename, relocate, or materially change a public API without an approved compatibility and migration plan.
  • Preserve consumer override points and optional integrations.
  • Do not make an optional peer, compile-only, or runtime dependency mandatory without reviewing consumer impact.
  • Prefer additive evolution and deprecation over immediate removal.
  • When a public contract changes, update tests, human documentation, and the library's consumer contract in the same approved change.
  • Validate both the source and the distributable artifact when supported.
  • Inspect known consumers when available, but do not modify consumer repositories unless they are included in the approved scope.
  • Version changes, publication, registry deployment, and package replacement require separate authorization.
  • Keep repository-maintainer rules in .agent/project.md and downstream usage rules in .agent/consumer.md.