feat(guidelines): add core guidelines for Brain architecture including processes, tasks, and queries to enhance documentation and understanding of the framework

[r2luna]

What:

• Bug Fix
• New Feature

Description:

Related:

Summary by CodeRabbit

• Documentation
  • Added a comprehensive, presentation-focused guide for the Brain architecture covering core concepts, invocation styles, configuration options, extensive usage examples (creation, chaining, nesting, validation, delaying, canceling, queueing), testing patterns, visualization instructions, and best practices for transactions and payload propagation.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new Blade template documenting the Brain architecture for Laravel Boost: Processes, Tasks, and Queries, with usage examples, invocation styles, payload propagation, configuration options, testing patterns, visualization instructions, and best practices. (Documentation-only; no runtime or API changes.)

Changes

Cohort / File(s)	Summary
Brain Architecture Documentation resources/boost/guidelines/core.blade.php	New comprehensive Blade guide covering core concepts (Processes, Tasks, Queries), invocation patterns, chaining/nesting, validation, delaying/canceling/queueing, payload flow and annotations, configuration options, testing approaches, visualization (brain:show), and best practices.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 A guide hops forth, ears held high,
Lines of wisdom under a clear sky,
Processes, Tasks, Queries—one neat trail,
Docs bloom softly with every detail,
Hop on, explorer, and follow the tale.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: adding core guidelines documentation for the Brain architecture (processes, tasks, queries) to enhance framework understanding.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/laravel-boost-guidelines

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

resources/boost/guidelines/core.blade.php (1)

185-185: Clarify the interaction between cancelProcess() and transaction behavior.

Line 185 states the process "still commits its transaction" on cancellation, while line 337 states "tasks that throw will roll back all previous work." Both may be accurate (cancel ≠ throw), but a reader could easily misunderstand when a rollback occurs vs. when a commit occurs. Consider adding a brief note here distinguishing cancellation (commit) from an exception (rollback).

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@resources/boost/guidelines/core.blade.php`:
- Line 79: Rename the class FullfillOrder to the correct spelling FulfillOrder
and update every reference to that class (constructors, type hints,
imports/usages, factory/tests) so they match the new name; update class
declaration "class FullfillOrder extends Process" to "class FulfillOrder extends
Process" and then search for and replace all usages of FullfillOrder
(instantiations, type annotations, service bindings, test references, and any
serialization/queue payload names) to avoid breaking references.