Add synthetic fixtures and proposed policy contracts for safely demonstrating future Lariza capabilities. Assisted-by: Codex: GPT-5.6
20 lines
813 B
Markdown
20 lines
813 B
Markdown
# Governance demo
|
|
|
|
This tiny payment service is a stable target for demonstrating repository and
|
|
organization governance features without using production code.
|
|
|
|
## Demonstration scenarios
|
|
|
|
1. Preview an organization policy inherited by this repository.
|
|
2. Show why `main` requires approvals, resolved conversations, and trusted CI.
|
|
3. Change `internal/payment/**` and require the Payments Owners group.
|
|
4. Request a temporary exception using the issue template.
|
|
5. Compare audit-only and enforced policy decisions.
|
|
6. Explain which policy source won when repository settings conflict.
|
|
|
|
The `.lariza/policy.yaml` document is an intentionally proposed contract. It is
|
|
not consumed by upstream Gitea and gives future Lariza APIs and UI a versioned,
|
|
reviewable fixture.
|
|
|
|
Run the sample locally with `go test ./...`.
|