Agreement & Documentation APIs & Webhooks

[JoseSzycho]

This pull request introduces full-featured API resource definitions and validating webhooks for both the Agreement and Documentation CRDs, significantly expanding Milo's extensibility and enterprise-readiness in managing legally critical resources.

Overview

Agreement

• Introduces DocumentAcceptance and related resource APIs, enabling tracking of acceptance of critical agreements (ToS, NDAs, etc.) by users or machine identities.
• Implements strong resource references: links DocumentAcceptance objects to accepted DocumentRevision, subject (e.g. Organization, User), and accepter records, supporting provenance, auditability, and trust.
• Adds DocumentAcceptance webhook with in-depth validation:
  • Confirms referenced DocumentRevision exists and matches provided version.
  • Validates referenced subject and accepter are allowed by targeted DocumentRevision schema.
  • Ensures correct registration of acceptance context and signatures (web, email, CLI scenarios).

Documentation

• Adds Document and DocumentRevision CRDs:
  • Document resources define "what" the agreement or published doc is (title, category, jurisdiction, type, etc.).
  • DocumentRevision resources model the full lifecycle of published document versions, including effective dates, versioning constraints, and content.
• Implements Document and DocumentRevision validating webhooks:
  • Prevents deletion of Document if revisions exist.
  • Validates DocumentRevision creation constraints (version must increase, effective date in the future, targets match allowed subject/accepter kinds).
  • Supports immutable spec enforcement for DocumentRevision.

[joggrbot]

📝 Documentation Analysis

All docs are up to date! 🎉

---

✅ Latest commit analyzed: aa1e7d7 | Powered by Joggr