Curriculum/protocol engineering add 5 frontmatter fields

[DRK28122006]

Summary

Describe the problem, the change, and the user/system impact.

Scope

• In scope:
• Out of scope:

Invariants

List the business and engineering rules that must remain true.

• Canonical identity is defined where records/events are involved.
• Re-running the operation does not duplicate effects.
• Partial failure cannot silently corrupt state.
• Public outputs do not expose private or internal data.

Design

Explain the source of truth, read/write boundaries, error behavior, and why this is the simplest safe approach.

Duplicate and idempotency review

• Stable idempotency/dedupe key:
• Persisted-data duplicate check:
• Same-batch duplicate check:
• Retry behavior:
• Conflict behavior:

Privacy and security review

• Data classification:
• Public fields explicitly allowlisted:
• Private links/identifiers suppressed:
• Secrets and permissions reviewed:

Data, migration, and rollback

• Schema/data changes:
• Backup completed or not applicable:
• Dry-run/preview result:
• Expected affected-record count:
• Rollback procedure:

Verification

• Syntax/build/compile
• Formatting/lint
• Type checks
• Unit tests
• Integration tests
• Repeat-run/idempotency test
• Malformed-input test
• Partial-failure test
• Privacy-output test
• Before/after reconciliation

Commands and actual results:

Operations

• Configuration changes:
• Deployment/restart steps:
• Health checks:
• Monitoring/alerts:
• Post-deploy verification:

Agent declaration

• I read the applicable AGENTS.md instructions.
• I did not perform unapproved destructive production actions.
• I have clearly stated any checks I could not run.
• The patch does not include unrelated refactoring.

[coderabbitai]

Warning

Review limit reached

@DRK28122006, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 55 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 622ca2e7-81b9-4845-90e7-beec1a72a9a5

📥 Commits

Reviewing files that changed from the base of the PR and between f2fb926 and c2a76cb.

📒 Files selected for processing (19)

• curriculum/04-Protocol Engineering/01-beginner/01-protocol-concepts/01-protocol-vs-application.md
• curriculum/04-Protocol Engineering/01-beginner/01-protocol-concepts/02-state-machines.md
• curriculum/04-Protocol Engineering/01-beginner/01-protocol-concepts/03-communication-patterns.md
• curriculum/04-Protocol Engineering/01-beginner/02-standards/01-specification-writing.md
• curriculum/04-Protocol Engineering/01-beginner/02-standards/02-versioning-strategies.md
• curriculum/04-Protocol Engineering/01-beginner/02-standards/03-interoperable-design.md
• curriculum/04-Protocol Engineering/02-intermediate/01-implementation/01-testing-protocol-compatibility.md
• curriculum/04-Protocol Engineering/02-intermediate/01-implementation/02-scaling-design.md
• curriculum/04-Protocol Engineering/02-intermediate/01-implementation/03-resilience-patterns.md
• curriculum/04-Protocol Engineering/02-intermediate/02-governance-and-ecosystem/01-upgrade-paths.md
• curriculum/04-Protocol Engineering/02-intermediate/02-governance-and-ecosystem/02-interchain-protocols.md
• curriculum/04-Protocol Engineering/02-intermediate/02-governance-and-ecosystem/03-community-feedback.md
• curriculum/04-Protocol Engineering/03-advanced/01-lead-architect/01-optimizing-latency.md
• curriculum/04-Protocol Engineering/03-advanced/01-lead-architect/02-consensus-economics.md
• curriculum/04-Protocol Engineering/03-advanced/01-lead-architect/03-security-modeling.md
• curriculum/04-Protocol Engineering/03-advanced/02-global-adoption/01-regulatory-compliance.md
• curriculum/04-Protocol Engineering/03-advanced/02-global-adoption/02-performance-auditing.md
• curriculum/04-Protocol Engineering/03-advanced/02-global-adoption/03-enterprise-integration.md
• website/docusaurus.config.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}