Skip to content

fixture(demo/rules): define project architectural rules for demo application #49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
waleedcodes merged 3 commits into from
Oct 9, 2026
Merged

fixture(demo/rules): define project architectural rules for demo application #49

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c71a567
fixture(demo): create demo project rules file
waleedcodes Oct 9, 2026
29bd94e
fixture(demo): specify authentication and data privacy constraints
waleedcodes Oct 9, 2026
a15e610
fixture(demo): add ownership and idempotency rules
waleedcodes Oct 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions examples/demo-app/.proofcode/rules.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# Project Rules

Define organizational and architectural standards for your codebase. ProofCode evaluates every code change against these rules.

- **Rule 1 (Authentication):** Every API route must authenticate the user.
- **Rule 2 (Data Privacy):** Never expose passwordHash or secrets in responses.
- **Rule 3 (Resource Ownership):** Users can only access their own orders or user resources.
- **Rule 4 (Test Coverage):** All public API endpoints require tests.
- **Rule 5 (Financial Safety):** Payment operations must be idempotent.
Loading