Files
govoplan-approvals/docs/APPROVALS_DOMAIN_BOUNDARY.md

1.1 KiB

Approvals Domain Boundary

Purpose

Generic approval and sign-off chains with delegation, substitution, four-eyes principle, escalation, and signatures.

Owns

  • approval requests
  • sign-off chains
  • delegation and substitution facts
  • four-eyes constraints
  • escalation state
  • signature references

Does Not Own

  • module-specific business decisions
  • workflow orchestration engine
  • identity and RBAC primitives

Integration Candidates

  • workflow
  • audit
  • files
  • notifications

Seed State

The current repository state is intentionally small:

  • module manifest and entry point
  • tenant-level permission definitions
  • manager and viewer role templates
  • documentation topic describing the module boundary
  • Gitea issue workflow templates
  • manifest contract test

No runtime API, database model, migration, WebUI route, or navigation item is registered yet. The first implementation slice should preserve the boundary above and only add user-visible surfaces once the workflow model is clear.

First Implementation Slice

Define reusable approval request, step, actor, delegation, substitution, and decision result contracts for consuming modules.